Privacy Policy

Privacy enquiries: privacy@rii.link

No data protection officer has been appointed; the conditions of Art. 37 GDPR and §38 BDSG are not met.

rii.link processes data in two distinct roles, and which rights you have against whom depends on it:

As controller we process the data of our own users: account, billing, support, and visits to this website. This policy applies to that directly.

As processor we handle the click data generated when someone opens a link on a customer’s domain. The purposes and means there are determined by the customer who created the link — they are the controller and we act on their instructions under Art. 28 GDPR. If you clicked such a link and want access or erasure, contact the operator of that domain; we support them in answering.

We conclude a data processing agreement under Art. 28(3) GDPR with our customers. It is available on request at privacy@rii.link.

Account and sign-in. Email address, password hash, verification status, workspace membership and role. An account cannot be maintained without these.

Configuration. Domains, paths, routing rules, response bodies, QR codes and uploaded files — what you create in the dashboard.

Click and analytics data. Timestamp, host, path, status code, response time, browser, operating system, device type, language preference, country of origin, referrer and query string of each request. The IP address is truncated before durable storage to its /24 IPv4 or /48 IPv6 network prefix and never stored in full; it serves only to derive the country of origin and to detect abuse.

Email forwarding. Enabling this routes messages through our mail server: sender, recipient, subject, headers and body are processed for the duration of delivery. We store no mailboxes; after successful forwarding only a delivery log remains.

Dashboard assistant. If you use the assistant in the dashboard, your messages are sent to Anthropic, whose AI model answers them. Each request also carries your workspace’s name and plan, your role, your timezone and the page you have open, plus the workspace data the assistant reads to answer you — for example domains, paths, routing rules, analytics figures, team members or email forwarding logs. A short title for each conversation is generated the same way. Nothing is sent to Anthropic unless you use the assistant.

Link safety checks. Whenever a link destination is created or changed — in the dashboard, through the API or MCP, or with the anonymous shortening form on this website — we send the destination URL to Google Cloud Web Risk to check it against known malware and phishing sites, and we periodically re-check recently created or changed destinations. Only the URL is sent, and it is sent from our servers: Google receives neither your account details nor your IP address. A destination classified as unsafe is refused.

Abuse reports. Anyone can report a short link as abusive, with or without an account. We store the reported URL, the category you choose, your description and — only if you provide it — your email address, so that we can contact you about the report. We also store the network prefix of the address the report was sent from, truncated to /24 (IPv4) or /48 (IPv6). Every new report triggers an alert in an internal Slack channel with the reported link and its category only; your description and email address are not posted there and stay in our own database.

Support. Tickets, messages and attachments you send us.

This website. Server logs kept by the host, plus cookieless traffic measurement. No profiling, no recognition across sessions.

This website sets no cookies of its own and embeds no third-party cookies during normal use. Traffic measurement works without cookies and without a cross-device identifier.

One exception: when you start filling in a form that sends an email or reaches our team (contact, integration request, abuse report, changelog or status updates, emailed admin link), we load Cloudflare Turnstile to confirm the submission comes from a person; on the link-shortening form we load it only if a submission is classified as automated. We only ever contact Cloudflare in those cases; only then does it receive your IP address and set a cookie. This serves to prevent misuse of our forms and is strictly necessary within the meaning of §25(2)(2) TDDDG, so it requires no consent.

After sign-in the dashboard stores access tokens in your browser’s localStorage. That is strictly necessary for operation within the meaning of §25(2)(2) TDDDG and therefore requires no consent. Signing out deletes the tokens.

Separately, every page on this site runs Vercel BotID, an automated bot-detection check. It is not conditional the way Turnstile is: its script runs on every visit, served first-party from rii.link rather than a third-party domain, and the signals it collects are evaluated by Vercel — already listed as a processor in section 7.

We use the following service providers. Art. 28 GDPR agreements are in place with all of them.

Anthropic receives data only when you use the dashboard assistant, and Google receives link destination URLs only (see section 3).

Two components are deliberately absent because neither receives any data: geolocation runs against a database held locally with no outbound lookup, and error diagnostics run on an instance we operate ourselves.

Where the providers named in section 7 process outside the EEA, or — processing within the EEA — access from a third country cannot be ruled out, we base the transfer on EU standard contractual clauses (Art. 46(2)(c) GDPR). Documentation is available on request.

Account and configuration data are kept for as long as the account exists. After deletion we remove them from replicas and backups within 30 days.

Click and analytics data: This data is kept for as long as the account exists. Automated, plan-based deletion windows are in preparation; until then you can request erasure at any time.

Dashboard assistant conversations are deleted automatically 180 days after their last activity; you can delete a conversation yourself before then. We keep a monthly count of assistant messages per workspace for quota purposes, without any conversation content.

Abuse reports: the reporter's email address, the description and the truncated IP address are deleted 12 months after the report is resolved. We keep the anonymous record of the report (the reported link, category, status, dates and what we did about it) to evidence how we handled it. On request we remove your email address from a report earlier.

Email forwarding delivery logs and support tickets are kept for as long as they are needed to handle and evidence the matter.

Statutory commercial and tax retention periods remain unaffected.

You have the rights of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20) and objection (Art. 21 GDPR). A message to privacy@rii.link is enough.

You may also lodge a complaint with a supervisory authority. Ours is the Berliner Beauftragte für Datenschutz und Informationsfreiheit.

If you gave consent to a changelog or status subscription, you can withdraw it at any time (Art. 7(3) GDPR), without affecting the lawfulness of processing carried out before the withdrawal — see section 12 for how we delete that record on request.

If you write to us via the contact form or by email, we process your details to handle the enquiry (Art. 6(1)(b) or (f) GDPR) and keep them for as long as follow-up questions can be expected.

When you confirm one of our email subscriptions (changelog and status updates) we record the confirmation timestamp, your email address, your IP address and your browser’s user agent, as evidence that the address consented (Art. 7(1) GDPR). That record is an email in our mailbox — there is no subscriber database — and we delete it on request.