Company
Access, correction, deletion: how to ask
Email support@roamingproxy.com. The Privacy Policy also names privacy@roamingproxy.com for these requests. Before you write, check the first section: some of this you can do yourself in less time than an email takes.
What we do not offer
There is no request form on this page and no self-service export button. There is no Data Protection Officer to escalate to, and we do not ask you to upload identity documents. The old version of this page was a nine-field form with an ID-verification step behind it.
Do it yourself, if it is one of these
The profile page in the dashboard lets you change your name and email address, and lets you delete your account outright. Account data is then deleted within 30 days of closure. API keys can be revoked individually at any time, and your metered usage is readable both on the usage page and over the API.
What to put in the email
Send it from the email address registered on the account. That is how we identify you, and it is why we do not need a document upload. State which right you are exercising — access, correction, deletion, restriction, objection, portability, or withdrawal of consent — and for a correction, say what is wrong and what it should be.
Do not include your password or a full API key. Neither is needed. We store passwords only as bcrypt hashes, so nobody here can read yours back — sending it puts it in an inbox for no benefit at all. The Privacy Policy commits to a response within 30 days, and notes we may need to verify your identity first.
What we actually hold about you
A request is easier to write when you know what there is to ask for. The full list is in the Privacy Policy; this is the shape of it.
Account data
Email address, full name, a bcrypt hash of your password, and creation and activation timestamps.
Authentication logs
Every sign-in attempt: the email entered, source IP, user agent, outcome and timestamp.
API request logs
Per call: the API key prefix, source IP, user agent, endpoint, response status and timestamp. Never the full key, never the proxied response body.
Usage records
Per-request counts and computed cost, which is what your invoice is built from.
The limit on erasure, stated plainly
We cannot delete authentication logs and API request logs on request while they are inside their 13-month retention window. They are what we use to detect abuse and what we produce as evidence of delivered service if a payment is disputed. They are deleted when the window expires, and they survive account closure until then.
Usage records are kept 7 years because invoices and tax records depend on them. Backups are retained up to 35 days, so a deleted record can persist in an encrypted backup for that long before ageing out. If you are in the EEA or the UK you can complain to your local supervisory authority.
Questions
- Can I export my usage data myself?
- Yes. Per-request metering is queryable over the API and shown on the usage page in the dashboard, so you do not need to ask us for a copy of it.
- Does deleting my account delete my invoices?
- No. Usage records and invoice records are kept for 7 years for tax and accounting reasons, as the Privacy Policy sets out.
- Do you use my requests to train models?
- No. The Privacy Policy states we do not use your content to train models, and the egress nodes do not log target URLs or response bodies in the first place.
Get a key
Create an account and mint an API key in the dashboard. The full endpoint reference — request shapes, parameters and error codes — is published at https://api.roamingproxy.com/v2/docs.