This policy explains what personal data UK Random Address Generator (ukaddressgenerator.org) processes, why, how long it is kept, and what rights you have under the UK General Data Protection Regulation and the Data Protection Act 2018. Generating addresses still requires no account and stores nothing. Holding an account, which you only need in order to raise your API limits, does store a small amount of personal data, and this policy says exactly what.
Addresses, postcodes, telephone numbers, personas, passwords and UUIDs are produced on request and returned directly to you. They are not written to a database, not logged and not linked to you.
The data itself is fictional. It does not describe identifiable living individuals, so generating it does not constitute processing personal data under UK GDPR. No building exists at any address this service produces.
No account is required and none of the data below is created. Standard request metadata — IP address, user agent, requested URL, timestamp, response status — is processed as by any web server, and the burst limiter holds your IP address in memory only, for at most a minute, to enforce fair use.
Lawful basis: legitimate interests, Article 6(1)(f), in keeping the service available and preventing abuse. Retention: the limiter entry expires within a minute; access logs are held by the hosting provider for a short operational period and are not used to build any profile.
An account exists only to attach API keys and a usage allowance to someone. There is no profile, no name field and no password. In full, an account record holds:
Sign-in is by emailed link, so there is no password to store or leak. When you request one, a record is written holding your email address, the time, an expiry, and a SHA-256 hash of the link token — never the token itself.
That record is deleted the moment the link is used. An unused link expires within fifteen minutes and its record is removed shortly afterwards. The IP address the request came from is deliberately not stored.
Your session is a signed cookie, not a database row: it carries your account identifier and an expiry, signed with a server key. There is no server-side session table, so there is nothing stored about your sessions at all.
Lawful basis: performance of a contract, Article 6(1)(b) — you cannot have an account without a way to sign in to it.
An API key is stored as an HMAC-SHA256 hash under a server-side key. The key itself is shown to you once, at creation, and is never written down by us — which is also why we cannot show it to you again or recover it if you lose it.
Alongside the hash we keep the key’s visible prefix, the label you gave it, when it was created, when it was last used, and whether it has been revoked.
A counter per account per billing period records how many requests you have made. It holds a number, the period dates and your account identifier. It records no detail of individual requests: not what you asked for, not when, and not from where.
Lawful basis: performance of a contract, Article 6(1)(b), for enforcing the allowance you are paying for. Retention: usage counters are kept as billing records for six years after the period they cover, in line with the UK statutory limitation period for contract claims.
Payments are processed by Paddle.com Market Ltd, which acts as merchant of record and is a separate data controller for the payment itself. Card details are entered on Paddle’s own checkout and never pass through this service — we do not see them, receive them or store them.
What we receive back from Paddle is a webhook telling us a subscription was created, changed or cancelled. From it we keep the Paddle customer and subscription identifiers, the status and the period dates, so that your plan on this service matches what you have paid for. We also record each webhook’s event identifier so that a redelivery is not applied twice; those records contain no personal data.
Paddle’s own handling of your data is covered by its privacy notice at paddle.com/legal/privacy. For refunds and cancellations see the refund policy.
If you send a message through the contact form, the name, email address, subject, message and originating IP address you supply are stored so we can reply, and forwarded to the operator’s inbox where an email provider is configured.
Lawful basis: legitimate interests, Article 6(1)(f), in answering enquiries. Retention: until the enquiry is resolved and no longer needed, and deleted sooner on request.
The data above is held in Google Cloud Firestore in the United Kingdom and processed on Google Cloud Run. Google acts as a processor on our instructions.
Sign-in emails are sent through Resend, which processes your email address in order to deliver them. Payments are handled by Paddle.com Market Ltd as described above.
Nothing is sold, and nothing is shared for advertising or profiling. There is no analytics or tracking script on this site.
No tracking or advertising cookies are set. Your theme preference is kept in your browser’s local storage and is never transmitted.
If you sign in, one cookie is set: a signed session cookie, HttpOnly, SameSite=Lax and Secure. It is strictly necessary for signing in and carries nothing beyond your account identifier and an expiry.
You have the right to be informed, of access, to rectification, to erasure, to restrict processing, to data portability, and to object. Exercising them costs nothing.
Email support@ukaddressgenerator.org from the address on the account. We will respond within one month, as UK GDPR requires, and usually much sooner. Deletion removes the account, its address, its API keys and its sign-in records; usage counters that form part of a billing record may be retained for the period described above, which is a legal-obligation basis rather than a choice.
If you are unhappy with how we have handled your data you can complain to the Information Commissioner’s Office at ico.org.uk. You can do that without going through us first.