Overview
Below is an account of the personal data Diamond Proxies (“Diamond Proxies”, “we”, “us”) gathers as you use the website, the dashboard and the proxy network — our reasons for gathering it, the parties that see it, and the say you have over it. Read it together with our Terms of Service.
Condensed to a sentence: we take only what it takes to open an account, collect payment, hand you credentials and count your bandwidth. Personal data is never sold, no advertising trackers run on this site, and the contents of whatever you route through the network are not something we look at.
What we collect
Account data
Discord OAuth is how you sign in. Approving it passes us four things from Discord — your user ID, username, avatar image URL and email address. The ID is what identifies your account internally; the remainder is there to render your identity in the dashboard and to let us reach you. Your Discord password never reaches us, and we have no visibility into your servers or messages.
Payment data
Checkout is Stripe's. Card number, billing name, billing address and any tax ID are collected by Stripe directly and land with Stripe — not with us.
The full card number, CVC and expiry date are never visible to us and are never stored on our side. What we retain is the record of the transaction: Stripe's order and payment identifiers, the amount and currency, the status, plus the card brand and final four digits where Stripe passes them back.
Service data
- Bandwidth balance, purchases, manual adjustments and the history of your orders.
- The proxy sub-account issued to you, its credentials, and their current state.
- Usage totals as the network reports them — bytes drawn down over time, broken out by destination or endpoint wherever that detail is available upstream.
- Coupons redeemed, together with any internal notes our team has attached to the account.
Technical data
Ordinary request telemetry passes through our hosting, database and analytics providers: IP address, user agent, timestamps, the pages requested and diagnostic detail when something breaks. It keeps the site up, lets us trace faults, and backs our rate limiting and abuse controls.
Traffic metadata
Establishing and metering a connection is impossible without metadata, so our infrastructure necessarily handles it — where the request came from, the host it is bound for, timing and byte counts. What comes back to us are the derived usage totals. The contents of your traffic are not inspected, not stored and not sold, and we build no profile of what you browse.
Communications
Emails you send us and tickets you open in our Discord community are kept — the thread and anything attached to it — so that we can actually help and so there is a record of how the matter ended.
How we use it
- Opening your account, authenticating you, and keeping the session alive.
- Collecting payment, producing receipts and invoices, and satisfying tax and accounting duties.
- Issuing your proxy credentials and crediting purchased bandwidth to the balance.
- Metering consumption so the balances and history you see are correct.
- Answering support requests and alerting you about orders, credentials or the state of your account.
- Spotting, investigating and heading off fraud, abuse, chargebacks and breaches of our acceptable use policy, and keeping the network safe.
- Reading aggregate product usage so we know what to improve.
- Meeting our legal obligations and answering valid legal requests.
Your data does not feed automated decisions with legal or comparably significant consequences, with one exception: automated fraud and abuse screening. Where such a check locks you out, you are entitled to ask for a human to look at it again.
Legal bases (UK/EU)
For anyone in the United Kingdom or the European Economic Area, the bases we rely on under the UK GDPR and the GDPR are these:
Cookies
The cookie list is short, entirely first-party, and contains no advertising cookies:
- Authentication. Session cookies from our auth provider that keep you signed in and allow the session to refresh. Strictly necessary — without them the dashboard simply will not function.
- Preferences. Interface settings such as your theme choice, held in local storage.
- Analytics. Aggregate, privacy-preserving page analytics from our hosting platform, which construct no cross-site advertising profile.
Your browser can block or clear all of these. Be aware that clearing the authentication cookies logs you out and leaves the dashboard unable to load.
Who we share it with
Your personal data is not sold, and it is not shared for cross-context behavioural advertising. It reaches only the processors that keep the Service running, and each of them receives no more than its role requires:
There are also disclosures the law requires or permits us to make:
- answering a valid subpoena, court order or law-enforcement request, once we have checked it for validity and scope;
- bringing or defending legal claims, and investigating abuse of the network; and
- passing data to an acquirer or successor in a merger, acquisition or asset sale — with these same protections travelling with it.
How long we keep it
Security
Data is encrypted in transit. Database access runs behind row-level security, so one account can never read another's records. Secrets and provider API keys live server-side and nowhere else. Administrative access is confined to the staff who need it and every admin action is logged.
Perfect security does not exist. Where a breach touches your personal data and is likely to put your rights at risk, you and the relevant supervisory authority will be notified within the timeframes the law sets.
Your rights
Where you live determines which of the following you can exercise:
- obtaining a copy of the personal data we hold on you, in a portable format;
- having inaccurate or incomplete data put right;
- having your data erased, except records we are obliged to keep for legal or accounting purposes;
- restricting or objecting to particular processing, legitimate-interests processing included;
- pulling back consent wherever consent was the basis; and
- facing no penalty or discrimination for using any of these rights.
Write to privacy@diamondproxies.com from the email address on the account and you will hear back inside 30 days, though we may have to confirm your identity first. UK and EEA residents unhappy with the outcome are free to take it to their national data protection authority.
International transfers
Our operations and those of our processors span several countries, the United States among them. When personal data leaves the UK or the EEA, the protection travels with it via the safeguards our processors have in place — in practice the UK Addendum and the European Commission's Standard Contractual Clauses.
Children
Nobody under 18 should be using the Service, and we do not knowingly gather data from children. If you think a child has handed us personal data, tell privacy@diamondproxies.com and it will be deleted.
Changes to this policy
Any update to this policy moves the “last updated” date at the top of the page. Where the change is material — a fresh category of data, a new purpose, a new type of recipient — you will hear about it beforehand, whether through the dashboard, by email or in our Discord community.
Contact
Privacy questions, data requests and abuse reports go to privacy@diamondproxies.com. Everything else goes to support@diamondproxies.com.