Privacy Policy
Last updated: 2026-11-03
This policy explains what data ternis.link collects when you shorten links, open short links, or use the dashboard — and your rights over that data.
Controller: Ternis / ternis.link (legal@ternis.dev / platforms@ternis.dev). If you have questions about your data, contact us there.
Services and domains covered
This document applies to the Ternis link network, including:
| Purpose | Domains |
|---|---|
| Public short links | href.nz, meinlink.at, clicked.at, href.yt |
| Business and network links | href.re, ternis.link, int.ternis.link |
| Additional network redirect domains | links.thosted.de, short.thosted.de, go.thosted.de, go.ternis.net, go.ternis.dev, go.ternis.org, go.ternis.eu |
| Link management and administration | my.href.nz, dash.meinlink.at, dash.ternis.link, admin.ternis.link |
| Legacy dashboard addresses | my.ternis.link, my.href.yt (redirect to the current public dashboard) |
| QR generation and APIs | qr.href.nz, qr.t-api.de, links.t-api.de |
| Documentation, abuse reporting and security verification | docs.ternis.link, protected.ternis.link, abuse.ternis.link |
It also covers supported subdomains and customer-connected domains when they serve this application. Independent destination websites and other services linked from this application have their own policies. Account sign-in uses Ternis Auth at auth.ternis.net; its own notices also apply to authentication.
What we collect
Short links you create. Destination URL, short code, domain, and optional description, tags and expiry. Guest links additionally store a one-way hash of your IP address to enforce the daily fair-use quota — never the address itself.
API keys and link attribution. If you create a link through the API with a personal key (tl_…), the link stores which key created it (key ID, name and prefix) so you can filter your links per key on the dashboard and in the API. API-token metadata (creation, visibility changes, revocation) is kept in the same activity history as your other actions. Hiding a key's links from the dashboard (Show its links on the dashboard off) only changes where they are listed — nothing is deleted or moved.
API request log. Requests to API routes with audit logging enabled (including link, QR and authentication APIs, whether authenticated or not) write one audit row: HTTP method, host, path (without query string), response status, duration in milliseconds, a one-way IP hash, a truncated user-agent string, and — for authenticated calls — your user ID and the API key ID used. Request bodies, query strings, tokens and raw IP addresses are never stored. The log exists for abuse investigation and capacity planning. There is currently no automatic deletion schedule for these audit rows. Erasure and objection requests are assessed individually; retaining evidence for a legal claim requires a specific applicable justification, rather than a blanket exclusion from your rights.
Link usage (clicks). When someone opens a short link we count the visit and store coarse technical data: referrer, browser user-agent, a one-way IP hash (for unique-visitor counts), and an approximate country/city derived once and then kept without the address. For abuse investigation we additionally store the visitor IP encrypted, and it is automatically deleted after 30 days (see Retention).
QR codes, bio pages and link controls. We process QR generation records (such as format, time and associated link), bio-page content and interactions, link groups, device-targeting settings and password-protection settings where you use these features. Link passwords are stored as hashes. A URL, referrer or content field may itself contain personal data; avoid including secrets or unnecessary personal information in links you submit.
Standalone URL scans. Public scan forms, scan APIs and the admin sandbox log each scan request in the security database, including cached results, invalid or blocked URLs and unavailable/error outcomes. Records include the submitted URL, result, recommendation, cache status, time, request host/path, user-agent, IP hash and signed-in account ID where available. A recommendation alone does not deactivate a link. These records follow the security-evaluation retention described below.
AI-assisted security and moderation. When enabled, AI security providers receive the destination URL and hostname, available title/description, browser user-agent and account context (an account identifier, registration time and lifetime link count) for eligible link evaluations. Browser-signature evaluation can send a user-agent and requested path. We retain evaluation records containing the destination, associated account/link IDs, creator IP hash, user-agent where available, verdict, score, confidence, reasoning, action and metadata. Rules and AI results can trigger quarantine, link deactivation or bot protection; burst-rate checks can also deactivate links. To contest a decision, use the spam-appeal form when signed in or contact abuse@ternis.dev for human review. Human verification does not certify a destination as safe.
Campaign and optional visitor attribution. Redirect analytics can retain bounded query-parameter values and click tags supplied in a URL or request headers. Optional visitor identifiers are processed when attribution is enabled, with supported identifiers pseudonymized before storage and DNT/GPC controls applied by that feature. Query parameters and referrers can still contain personal information; hashing an identifier does not make all request data anonymous.
Accounts. If you sign in with Ternis Auth SSO we store your SSO subject ID, name, email address, avatar URL and role/plan. There are no passwords — authentication happens at the SSO provider.
Sessions and errors. Login sessions and a minimal error log (no raw IPs — only hashes) to keep the service running and debuggable.
Bot protection and CAPTCHA verification. To prevent automated scraper abuse, credential stuffing, and bot flooding, certain requests are screened by our verification gateways (such as protected.ternis.link):
- Verification Modes: Links and link groups can be configured with specific protection strengths:
off(direct redirect),standard(smart challenge),strict(mandatory verification check on every visitor), orcustom_captcha(zero third-party in-house challenge). Links can also be set to explicitly permit automated scrapers (allow_bots). - Cloudflare Turnstile: When enabled for standard/strict challenges, Turnstile evaluates visitor connection signals (IP address, TLS fingerprint, user-agent, headers) without tracking cookies. We validate the ephemeral single-use token on our server and do not store it.
- In-House Privacy CAPTCHA: For privacy-first challenges and Turnstile-free setups, our server generates arithmetic SVG challenges directly in memory. Challenges use HMAC-encrypted, short-lived tokens (5-minute TTL, single-use nonce to prevent replay attacks). Zero third-party scripts, external CDNs, or external tracking telemetry are involved.
- Protection of Legal Pages and Public Routes: Automated scrapers matching suspicious signatures (e.g. headless browsers, command-line harvesting tools) attempting to bulk-scrape public resources—including legal notices—are screened and redirected to the verification gateway before access is granted. Clean browser visitors access pages directly with zero latency.
- Verification Session Cookie: Once verified as human, an encrypted, signed session cookie (
tl_human_verified) is set for the.ternis.linkdomain (lifetime: 2 hours). It stores an encrypted timestamp and random salt to prevent repeated challenges across the network without profiling or cross-site tracking.
What we never store in plain text
Application IP-capture fields store hashes or encrypted addresses rather than readable IP addresses. IP addresses are necessarily processed to deliver network requests; infrastructure and external providers process technical connection data under their applicable arrangements. Day-to-day features (quotas, unique counts, rate limits) run on SHA-256 hashes, optionally mixed with a server-side secret. Raw visitor/creator IPs exist only in encrypted form for the 30-day abuse window described above.
Cookies
We use strictly necessary and functional preference cookies only. We do not use advertising, marketing, or cross-site profiling cookies. Link resolution and redirect analytics operate completely cookie-free.
A comprehensive inventory of all cookies, their domain, purpose, security flags, and exact maximum retention lifetimes is provided in our dedicated Cookie Policy (/pages/legal/cookies). Summary of active cookies:
- Session authentication (
{app}_session): Strictly necessary session identifier for authenticated dashboard access (HttpOnly,Secure,SameSite=Lax, max lifetime: session / 120 minutes of inactivity, up to 30 days if "Remember Me" is chosen). - CSRF Defense (
XSRF-TOKEN): Strictly necessary cryptographic token protecting forms against Cross-Site Request Forgery (Secure,SameSite=Lax, max lifetime: 2 hours). - Human Verification (
tl_human_verified): Strictly necessary human-verification cookie issued byprotected.ternis.linkremembering human verification across the network (HttpOnly,Secure,SameSite=Lax, max lifetime: 2 hours). - Language Preference (
clicked_locale): Functional preference cookie on clicked.at (SameSite=Lax, max lifetime: 1 year). - Interface Preferences (
tl-theme): Stored locally in browserlocalStorageon client devices only. - Third-Party Anti-Bot Cookies (
cf_clearance,__cf_bm): Only set when a link or gateway is explicitly configured with Cloudflare Turnstile, subject to Cloudflare's Turnstile Privacy Addendum. When our in-house Custom Privacy CAPTCHA is selected, zero third-party cookies are set.
Legal basis (GDPR)
- Contract / requested service (Art. 6(1)(b)): creating and resolving short links, your account.
- Legitimate interests (Art. 6(1)(f)): abuse prevention, security, capacity planning. We weighed this against your privacy by hashing IPs by default and encrypting plus auto-deleting the rest.
- Consent (Art. 6(1)(a)): where a feature explicitly requests it; it can be withdrawn for future processing.
Retention
| Data | Kept for |
|---|---|
| Links and their settings | While the link is retained; deactivation does not delete the link or its analytics. Hard deletion can preserve aggregate tombstones without the destination URL |
| Encrypted visitor/creator IPs | 30 days, then automatically and irreversibly deleted |
| API request log | No automatic deletion currently configured; subject to individual rights requests and any specifically justified retention |
| Activity history (your actions + admin actions on your stuff) | Indefinitely — never deleted automatically. Legal basis: legitimate interest in security, abuse prevention and transparency (Art. 6(1)(f)); only IP hashes (never raw addresses), truncated user-agents and labels are stored. Individual erasure requests (Art. 17) are honored on request — contact legal@ternis.dev |
| API-key attribution on links | As long as the link exists (survives key revocation; cleared only if the key row itself is deleted) |
| Security evaluations and appeals | No automatic deletion currently configured; retained for moderation and abuse review, subject to applicable rights and justified retention |
| Public-dashboard API session tokens | At most five active tokens per account; expired/revoked token records are pruned after 30 days |
| Generated account exports | Available for seven days |
| IP hashes and click records | May remain with historical analytics after encrypted IPs are pruned; hashes are pseudonymous, not necessarily anonymous |
| Accounts | Until you stop using SSO sign-in and ask for deletion |
| Error log entries | No automatic deletion schedule currently configured; subject to applicable rights and justified retention |
Sharing
We do not sell data and share nothing for marketing. Data is processed on infrastructure operated by ternis.net. Cloudflare processes bot-protection signals under its Turnstile terms. AI security providers receive the security inputs described above when AI checks are enabled. External processing is not limited to our own infrastructure. Where processing involves transfers outside the EEA, applicable transfer requirements and safeguards must be addressed; contact us for the arrangements applicable to your data. Abuse cases (spam, phishing, attacks launched through short links) may be reported to providers or authorities with the minimum data required.
Your rights
Access, rectification, erasure, restriction, portability and objection (GDPR Art. 15–21), plus the right to complain to your supervisory authority. Self-service lives in your dashboard settings: request a self-service export of your account data, or schedule complete account erasure (14-day grace period, cancellable, requires a fresh sign-in). Because guest links carry no account, include the short URL(s) in erasure requests so we can find them. These rights also apply to security and API logs. Any refusal or restriction must have an applicable legal basis, which we will explain. Where processing relies on consent, you can withdraw it; where it relies on legitimate interests, you can object. Contact: legal@ternis.dev or platforms@ternis.dev. Abuse reports: abuse@ternis.dev.
Public statistics and destination websites
Public network statistics expose aggregate counts rather than individual links, account details, IPs or user-agents. Link owners can access analytics for their own links. After a redirect, the destination operator is responsible for its own collection, cookies and content.
Changes
Material changes will be announced on the service at least 14 days before they take effect. The date at the top shows the current version.