Skip to content
urlify.eu.cc

Legal

Privacy Policy

urlify.eu.cc inspects every redirect, which means it necessarily sees traffic data. This page states exactly which fields that involves, why each one is needed to make a routing decision, and how long any of it survives.

Last updated

Who this covers

urlify.eu.cc has two kinds of people in it, and they are treated differently. Account holders sign in and create links. Visitors click those links and may never know urlify.eu.cc exists. Account holders give us data deliberately; visitors do not, so the visitor side is kept to the minimum a routing decision actually requires.

What is processed when a link is clicked

A redirect is a decision, and the decision needs inputs. When a short link is resolved at the edge, the following are read from the request:

IP address
Used to enforce rate limits and as a feature in bot scoring. It is the bucket key for abuse control, so without it a single client could exhaust the service for everyone.
User agent
The browser or client string. A primary signal for distinguishing an automated client from a person.
Country code
Derived by Cloudflare at the edge from the network path, not from GPS or any device permission. Country-level only — no city, no coordinates.
Requested path
The short slug that was asked for, and the timestamp.
Verdict
The classification the model returned for the request, plus its confidence, so the link owner can see why traffic was allowed, challenged or blocked.

Scoring happens inside the Cloudflare Worker handling the request. The request is not forwarded to a third-party classification service, and no advertising or profiling network is contacted as part of resolving a link.

What is not collected

  • No precise or device-level location. Country is inferred from the network path only.
  • No cross-site tracking of visitors, and no advertising identifiers on the redirect path.
  • No reading of the destination page’s content, and no injection of anything into it.
  • No special-category data (health, beliefs, biometrics). Nothing in the product asks for it and nothing in the schema stores it.

Account data

Creating an account stores an email address and either a password hash or, if you use “Continue with Google”, the identifier your provider returns. Passwords are never stored in a readable form. Alongside that sit the things you create: your links, routing rules, and the audit log of changes made to them.

Where data is stored

Application data lives in Cloudflare D1, with a Cloudflare KV namespace used for short-lived cache and rate-limit state. Both are operated on Cloudflare’s infrastructure. Because the service runs at the edge, requests are handled in the region closest to the visitor.

How long it is kept

Rate-limit state
Minutes. It exists only to smooth bursts and expires on its own.
Click and verdict records
Retained while the link exists, because they are the analytics the link owner is there for. Deleting a link deletes them.
Audit log
Retained for the life of the account. Its purpose is to answer “who changed this?” later, which a log that deletes itself cannot do.
Account record
Until you delete the account, after which it and the links under it are removed.

Cookies, storage, and consent

Two categories are strictly necessary and are not optional, because the site cannot function without them: the session cookie that keeps you signed in, and the abuse-control state that enforces rate limits. Your consent choice itself is stored locally under the key urlify.consent.v1 so you are not asked on every page.

Everything else is off until you switch it on. Nothing in the two categories below is loaded, and no script from them is added to the page, before you make a choice in the banner — the gate runs before the tags, not after.

Analytics — PostHog
Product analytics: which pages are opened and which features are used. Configured with person_profiles: “identified_only”, so a signed-out visitor is counted but no persistent profile is built for them. Stores its state in local storage and a cookie. Off unless you choose “Accept all” or “Analytics only”.
Advertising — Google AdSense
Loaded only on “Accept all”. Google may set its own cookies and use them for ad selection and measurement under its own policies. Choosing “Essential only” or “Analytics only” means this script is never added to the page at all.
Error reporting — Sentry
Strictly necessary, and deliberately narrow: stack traces and the page an error occurred on, with 10% of navigations sampled for performance regressions. Session replay is disabled and sendDefaultPii is off, so no recording of your screen and no IP attached to events. With replay off it sets no cookies.

You can change your mind at any time by clearing site data for this domain, which removes the stored choice and brings the banner back. Withdrawing consent stops future collection; it does not retroactively delete what a third party already received, which is why the gate runs before the tag rather than asking the tag to forget.

Why we are allowed to process it

For readers under the UK/EU GDPR, the lawful bases are these, and nothing is stretched to fit:

Contract
Your account, your links and the analytics attached to them. You asked for the service; this is the service.
Legitimate interests
Abuse control, bot scoring, rate limiting and error reporting. The interest is keeping a service that resolves other people’s links from being turned into a delivery mechanism for malware or a free load generator.
Consent
Analytics and advertising only, given in the banner and withdrawable at any time.
Legal obligation
Retaining records where we are required to, for instance in response to a valid legal request or a report of abuse.

Who else touches the data

The service runs on Cloudflare (compute at the edge, D1 database, KV namespace) and the ML scorer runs on our own server behind a Cloudflare tunnel, called only over an authenticated channel. Beyond that, the processors are those named above: PostHog for analytics if you consent, Google for advertising if you consent, Sentry for error reporting, and an email provider to deliver transactional mail such as verification and password resets. Data is not sold, and it is not shared with data brokers.

Because urlify.eu.cc runs at the edge and its providers are global, data may be processed outside your country. Where that involves a transfer out of the UK/EEA it relies on the transfer mechanisms those providers publish, typically Standard Contractual Clauses.

Your rights

You can ask for a copy of your data, ask for it to be corrected, ask for it to be deleted, ask us to restrict or stop a particular use, or object to processing based on legitimate interests. Account holders can already do most of this directly: the console exports your links and analytics, and deleting the account removes it and the links under it.

For anything not available in the console, email privacy@urlify.eu.cc and we will respond within 30 days. If a request concerns a link you clicked rather than an account you hold, include the link and the approximate time, since that is the only way to locate the record — we hold no identifier that would let us find you by name.

If you are in the UK or EU and think we have got this wrong, you can complain to your data protection authority as well as to us. We would rather hear it first.

Children

urlify.eu.cc is a developer tool and is not directed at children under 16. We do not knowingly create accounts for them; if you believe one exists, write to privacy@urlify.eu.cc and it will be removed.

Security

Passwords are hashed, sessions are cookie-based with CSRF protection, requests to the scoring service are signed and time-limited, and the API is rate limited per client. Suspected vulnerabilities go to security@urlify.eu.cc; please give us a reasonable window to fix an issue before publishing it.

Changes to this policy

The date at the top is the only version marker, and it moves whenever the substance changes rather than when a typo is fixed. If a change widens what is collected or adds a third party, the consent record is invalidated so the banner asks again instead of inheriting a decision you made about something else.

Contact

urlify.eu.cc is an independently operated service, run online with no premises open to visitors, so there is no counter to walk up to — these mailboxes are monitored and are the real contact surface:

Related reading: the Terms of Service cover what you may and may not point a link at, and the contact page has a form if you would rather not use email.