Privacy Policy

What we collect and why

Our guiding principle is to collect only what we need to run the Services, and here is what that means in practice:

Identity and access

When you create an account we keep your email address, a bcrypt hash of your password (never the password itself), whether your email is verified, your plan and its dates. If you sign in with Gully ID we receive and keep your Gully ID account identifier and its verified email address. Email verification and password-reset links are stored only as hashes and expire. We use this to sign you in, secure your account and send you service emails.

Signing in creates a session that lasts 7 days, or until you sign out. We store the session with your browser’s user agent so you can recognize it.

API keys

For each API key the portal stores a SHA-256 hash of the key with its name, a short prefix and its last four characters, and when it was created, last used, rotated or revoked. So that the gateway can check each request, its authentication table holds the key itself together with your account’s internal ID and the key’s rate-limit tier. That table is only reachable from our own services.

Usage metering

The gateway counts requests per key, network and method, with response times, and our metering database (VictoriaMetrics) collects those counters every 20 seconds. The portal turns them into hourly and daily totals per key, which is what your Usage page and plan limits are built from. We use this to show you your usage, enforce limits and run billing. The site and the sign-in pages show live gateway totals for all customers combined, never per key.

Gateway requests

Every request to rpc.gullyrpc.xyz carries your IP address, your key (if you use one) and the JSON-RPC request itself, which can include wallet addresses or a signed transaction. We use them to answer, meter and rate-limit the request. Your IP address is used for the per-IP limits, in short-lived counters. To answer quickly, the gateway caches answers by their request content (not by who asked), so a cached answer is just public chain data.

The gateway writes operational logs: the time, the project, the network, the method, the duration and, for some requests, the request body. These logs do not include your IP address or your key. The portal logs errors. Our web server does not keep access logs.

Billing information

Paid plans are paid at the Gully Pay checkout, so we never see or store card numbers or wallet keys. We keep a record of each checkout: the plan, the period, the amount and currency, the Gully Pay session and transaction IDs, the payment method type and the status, and a billing-history entry for each paid period. We pass your account email to Gully Pay when you start a checkout. We keep these records for accounting and tax purposes.

Website interactions

gullyrpc.xyz loads no analytics or tracking scripts and sets no cookies of its own. Its pages load fonts from Google Fonts, so Google receives your IP address and browser details when the fonts load; the portal does too. The live numbers on the site come from aggregate metering, not from anything about you.

Cookies

The portal sets one cookie of its own, gully_session, after you sign in. It keeps you signed in and expires with the session (7 days). We use no advertising or cross-site tracking cookies. Cloudflare, which carries our traffic, may set strictly necessary security cookies to protect the Services from bots and attacks.

Voluntary correspondence

When you write to [email protected], we keep your message and email address so we can answer and keep a record of what was agreed.

When we access or share your information

We don’t sell personal data or share it for advertising. These providers process some of it because they run part of the Services for us:

We also access or disclose information when we believe in good faith that it is needed:

• To help you with a support request you make, with your consent.
• To fix an error that stopped an automated process, looking at the minimum data needed.
• To keep the Services safe, investigating abuse, fraud or security incidents, including through logs and metadata.
• When the law requires it, in response to a valid legal process such as a subpoena or court order. Where we can, we tell you first.
• If Gully Labs is sold or merges, your data may move to the new owner, still under this policy, and we’ll tell you.

Transactions you send through the gateway, and the addresses and amounts in them, are published on their blockchain. That is public and permanent; nobody, us included, can change or delete it.

Your rights

Wherever you live, you can ask us to:

• tell you what personal data we hold about you and give you a copy (in a portable format);
• correct data that is wrong or incomplete;
• delete your account and personal data;
• stop or restrict a use of your data, or object to it.

Write to [email protected] from your account’s email address; we may need to verify that you are the account holder. We answer within the time the law sets. We won’t treat you differently for using these rights. Some data we must keep by law, such as payment records, and we can’t delete anything that is on a public blockchain. Depending on where you live (for example in the EU, the UK or California), you may also have the right to complain to your data protection authority.

How we secure your data

All traffic to our sites and the gateway is encrypted with HTTPS. Passwords are stored as bcrypt hashes and API keys in the portal as SHA-256 hashes. Our databases are reachable only from our own services on private networks, never from the internet, and only the Gully Labs team can access the servers. Daily backups are kept on the server.

What happens when you delete data

• When you revoke a key in the portal, the gateway stops accepting it within about 30 seconds.
• When we delete your account at your request, your account, sessions, keys and usage totals are deleted from our active database at once, and our database backups roll off within 14 days.
• Per-key counters in the metering database roll off after 2 months, and logs are overwritten as they rotate.
• Payment records we must keep for accounting and tax are kept for the period the law requires, then deleted.

Data retention

Location of site and data

Our servers are hosted by OVHcloud, and Cloudflare carries traffic through its global network. Our providers may process data in countries other than yours, including the United States. Where the law requires it, for example for data from the EU or the UK, we rely on our providers’ standard contractual clauses or similar safeguards for those transfers.

Age

The Services are for adults. You must be at least 18 to use them, and we don’t knowingly collect data from anyone younger. If you believe someone under 18 has given us personal data, write to [email protected] and we will delete it.

Changes and questions

We may update this policy as needed to comply with the law, reflect changes to the Services (for example a new upstream provider) or improve it. We refresh the “Last updated” date above whenever we do, and for a significant change we tell account holders by email or in the portal. Questions, requests or complaints: [email protected]. Gully Labs LLC, Oregon, USA.