Privacy Policy
Last updated: November 19, 2026
TrimLink is a URL shortener. We built it to tell link owners how their links perform without tracking the people who click them. This page explains, in plain language, exactly what we collect and why.
1. Who we are and who this covers
TrimLink ("TrimLink", "we", "us") runs the URL shortener at trimlink.co and the short links it serves, including short links on custom domains that our customers connect. You can reach us at support@trimlink.co.
This policy covers four groups of people:
- Account holders: people who sign up and create links.
- Link visitors: people who click a TrimLink short link or scan a TrimLink QR code.
- Website visitors: people who browse trimlink.co or use our free tools.
- Others: people who open a shared analytics report, follow a referral link, download a resource or write to us.
2. What we collect from account holders
- Account details: your email address, your name if you give one, and your password. We store the password only as a salted one-way hash (scrypt), never in readable form. If you sign in with Google, Google sends us your name, email address and profile picture.
- Sign-in sessions: each time you sign in we store the IP address and browser string (user agent) of that device with the session, to keep your account secure. A session expires 30 days after it was last used, and we delete it when you sign out or delete your account.
- What you create: your links (the destination URL, short code, title and the other settings you choose), custom domains, QR codes, folders, tags, UTM templates, API keys (stored as a one-way hash), webhook addresses, and the email addresses of people you invite to a team.
- Billing: our payment provider Polar handles checkout. We receive your plan, subscription status and a customer ID. We never see your full card number.
- Usage: how many links, QR codes and tracked clicks you use, so we can apply plan limits. We also record which signup button you used and, if you answer it, where you heard about us.
- Messages: what you send us by email or through the contact form.
- Feedback: if you send feedback from the dashboard, we store your rating and message with your account and forward them, with your name and email address, to our team inbox so we can reply. Your first feedback earns 10 bonus links, whatever it says.
- Emails we send you: which getting-started emails we have sent you, and your choice if you unsubscribe from them, so we respect it.
3. What we collect when someone clicks a short link
Link statistics are the core of TrimLink, and we built them to count clicks without identifying the people who click. For each click we store only:
- The time of the click.
- Country, region and city, read from the location headers our hosting provider adds to the request. The IP address itself is not stored with the click.
- Device type: desktop, mobile or tablet.
- Browser family (Chrome, Firefox, Safari, Edge, Opera or other) and operating system family (Windows, macOS, iOS, Android, Linux or other). No version numbers.
- The referring page, with its query string and fragment removed, because that is where tokens and personal details usually sit.
- Whether the click came directly, from a QR code scan or through our API.
- UTM campaign tags (the five standard
utm_values) from the short link or the destination URL. We keep a value only if it looks like a campaign name: values that look like an email address, a phone number or a URL are dropped, and each value is capped at 100 characters.
What we never store with a click: the IP address, the full user agent string, cookies, a device fingerprint, or any ID that could link two clicks to the same person. Redirects set no cookies. Clicks from bots and link-preview crawlers are not recorded.
Click-fraud check: to stop one device from inflating a link's count, we keep a counter for about six minutes after a click. The counter is keyed to a one-way hash (SHA-256) of a few request headers (user agent, language and accepted formats) or, when those headers are missing, to the IP address itself. It lives only in our cache, is never written to the click record, and expires on its own.
Unique visitors: the Pro plan and above show an estimate of unique visitors. We calculate it statistically from country, device type and hour of the click. Nothing per person is stored.
The link's owner, their team and anyone they share a report with can see these statistics. If a link is broken, paused or expired, the visitor sees a TrimLink page instead of a redirect, and that page loads our error monitoring (see section 6).
4. Website visitors, free tools and other contacts
Website analytics (no cookies)
We use Vercel Web Analytics, from our hosting provider, to count visits to our public pages (such as the home, pricing, blog, tools, documentation, sign-in and sign-up pages). It sets no cookies and stores nothing on your device. Visits are counted with a temporary identifier derived from the request that resets every 24 hours, so a visit cannot be linked to you on another day. For each page view it records the page address with all query parameters removed, the referring site, your approximate location (country, region and city), and your browser, operating system and device type. We see only totals. It never runs on the dashboard, shared reports, invitation links or short links, and it does not load at all if your browser sends a Global Privacy Control signal.
Free tools and rate limits
To keep the free tools and forms from being abused, we count requests per IP address in short-lived counters in our cache. They expire on their own within a few hours. The free QR code tool works without an account: to count its use, your browser computes a one-way hash of a few device settings (browser string, screen size, color depth, time zone, language, number of processor cores and platform). The hash is kept in that browser tab's session storage, is cleared when you close the tab, and is sent with each QR request. URLs you check with the URL Expander or safety checker are sent to Google Safe Browsing, fetched by our servers, and their domain may be looked up in public WHOIS records.
Shared analytics reports
When someone opens a shared report link, we log the time, the IP address with its last part removed (the last block of an IPv4 address is set to zero, and an IPv6 address is cut to its first 48 bits), a short browser and device label such as "Chrome mobile", and whether a password was entered correctly. The report's owner can see the time, the label and the password result, but not the IP address. The log is deleted when the share is deleted.
Referral links
When someone opens a TrimLink referral link, we store the referral code, a one-way hash (SHA-256) of the IP address, the browser string and the time, and set the tl_ref cookie (see section 9) so the referral can be credited at signup.
Resources, waitlist and messages
If you give us your email address to download a resource or join a waitlist, we store it with the resource name and send you the download link. When you later sign up with the same address, we mark it as converted. Messages sent through the contact form go to our support inbox (see section 8 for abuse reports).
Account security and abuse prevention
When an account is created or creates a link, we may process limited security signals: HMAC hashes of IP-derived values, hashes of standard request headers, email domains and patterns of similar destination URLs. These records never hold raw IP addresses, full user agents, full email addresses, raw destination URLs or query values. We use them only to stop abuse such as multiple free accounts made to get around limits, spam, phishing and fraud. On the sign-up form, Vercel BotID runs an invisible check in your browser to confirm a person is signing up, and the result is used only to accept or refuse that sign-up. Destination URLs are checked against Google Safe Browsing when a link is created and again on a regular schedule.
5. Why we use data and our legal bases
We use personal data only for the purposes below. If you are in the European Economic Area, the United Kingdom or Switzerland, the right column shows the legal basis we rely on under the GDPR.
| Purpose | Legal basis |
|---|---|
| Run your account, create and redirect links, connect domains, make QR codes, send service emails | Contract: we need it to provide the service you signed up for |
| Show link owners click statistics | Legitimate interests: link owners need to know how their links perform, and we collect only the coarse data listed in section 3 |
| Keep accounts secure, prevent abuse, spam, phishing and fraud, rate limit free tools, run bot and Safe Browsing checks | Legitimate interests in a safe service, and legal obligations where we must act on illegal content |
| Count visits to our website, find and fix errors | Legitimate interests in understanding and improving the website, using the privacy-protective setup described in sections 4 and 6 |
| If you have not created a link yet, send up to two getting-started emails (about one day and about seven days after signup). Invite you to leave a review with the welcome email | Legitimate interests. Each getting-started email has an unsubscribe link that works without signing in, and you can ignore the review invitation |
| Handle payments, invoices and taxes | Contract and legal obligations (Polar handles most of this as merchant of record) |
| Answer messages, abuse reports and legal requests | Legitimate interests and legal obligations |
Some security checks are automatic, for example refusing a sign-up that fails the bot check, or pausing a link that Google Safe Browsing flags as dangerous. You can ask for a person to review any such decision by writing to us. We do not use personal data for any other kind of automated decision.
We do not show ads, we use no advertising or social media pixels, and we do not build profiles of the people who click links. We do not sell personal information and we do not share it for cross-context behavioral advertising, as those terms are defined in California law.
6. Who receives data
We use the service providers below to run TrimLink. They process data on our behalf and only for the work listed, except where the table says a provider acts under its own privacy policy.
| Provider | What it does for us | Data it receives |
|---|---|---|
| Vercel (United States) | Hosting, content delivery, website analytics, sign-up bot check, connecting custom domains | Every request to trimlink.co and short links, including IP address and browser string while the request is handled, page views as described in section 4, and the custom domain names you add |
| Supabase (United States) | Main database | Everything we store about accounts, links, clicks and the other records in this policy |
| Upstash (United States) | Cache for fast redirects, rate-limit and click-fraud counters | Link data, IP addresses and header hashes in short-lived counters |
| Polar | Checkout, subscriptions, invoices and sales tax, as merchant of record | Your name, email address, billing address and payment details, collected by Polar under its own privacy policy |
| Namecheap Private Email | Sending our emails and receiving yours | Email addresses and the content of emails |
| Sentry (United States) | Error monitoring | Error details, page address, browser and device type, and the IP address of the request |
| Sign in with Google, Safe Browsing checks, website icons | Your Google account details if you choose Google sign-in, destination URLs we check, and the domain names whose icons we show in the dashboard and tools | |
| Trustpilot | Review invitations | Your name and email address, through a copy of the welcome email sent to verified accounts |
We do not record sessions. Sentry receives error reports and timing data for a sample of page loads. No replay of what you see, click or type on the page is made. Successful short-link redirects load no scripts at all.
Our uptime monitoring service (Better Stack) checks that the site responds and receives no personal data. When we check a domain for safety, its public registration (WHOIS) record may be looked up.
Data you send elsewhere: if you set up webhooks, the Zapier integration or API access, we send your link and click data to the places you choose. Those services handle it under their own terms.
Other disclosures: we may disclose data when the law requires it, to protect people from harm or fraud, or to a buyer if TrimLink is sold or merged. In a sale, this policy keeps applying to data collected under it until you are told otherwise.
7. Where your data is stored
Our database and cache run in the United States, and our other providers mainly process data in the United States. If you use TrimLink from another country, your data is transferred there. Where the law requires a transfer safeguard, such as for data from the EEA, the UK or Switzerland, we rely on the data processing terms our providers offer, which include the European Commission's Standard Contractual Clauses.
8. How long we keep data
| Data | How long we keep it |
|---|---|
| Account details, links, domains and settings | While your account is open. See below. |
| Sign-in sessions (IP address and browser string) | 30 days after the session was last used, or sooner when you sign out |
| Click records | Kept with no end date. We do not delete click records on a schedule, and deleting a link or closing your account does not delete those click records either. They hold none of the identifiers listed in section 3. Your plan only sets how far back your dashboard lets you look: Free 30 days, Starter 90 days, Pro 1 year, Growth 2 years, Teams all time. Ask us and we will delete them. We will update this policy before we start deleting them on a schedule. |
| Click-fraud counters | About 6 minutes |
| Rate-limit counters for free tools and forms | A few hours at most |
| QR tool device hash in your browser | Until you close the browser tab |
| Shared report access log | Until the share is deleted |
| Referral link records | Not deleted on a schedule yet. Ask us and we will delete them. |
| Resource download and waitlist emails | Until you ask us to delete them or unsubscribe |
| Security signals for abuse prevention | 30 days |
| Records of abuse actions we took | 90 days |
| Abuse reports, including the reporter name and email | 180 days after the report is resolved, and never more than 365 days |
| Abuse notices sent to account holders | 365 days |
| Error reports in Sentry | 90 days or less, deleted by Sentry |
| Support emails | As long as needed to handle your request and any follow-up |
| Feedback you send from the dashboard | While your account exists |
| Records of getting-started emails sent and your unsubscribe choice | While your account exists, so we never send them twice or after you opt out |
| Payment and tax records | Polar keeps them as long as tax law requires. We keep your plan and subscription history while your account is open. |
When you delete your account
You can delete your account in Settings. When you do, we immediately:
- cancel any paid subscription,
- stop your short links from redirecting,
- sign you out everywhere and revoke your API keys.
For 30 days we can restore the account if you ask, and about a week after deletion we send you one email explaining how to do that. After 30 days we close it for good and change the stored email address so it can no longer be used to sign in. Our system does not yet erase every record tied to a closed account on its own: your name, links and their click statistics stay in our database. If you want them fully erased, email us from your account address and we will erase them and confirm when it is done, within one month. Before you delete your account you can download a copy of your data in Settings.
10. Your rights
Depending on where you live, you can ask us to:
- give you a copy of the personal data we hold about you,
- correct data that is wrong,
- delete your data,
- limit how we use it, or object to a use based on legitimate interests,
- send your data to you or another service in a machine-readable format,
- withdraw a consent you gave, without affecting earlier use.
Many of these you can do yourself: edit your profile, download all your data as a JSON file, or delete your account in Settings. For anything else, email support@trimlink.co from the address on your account. We may ask you to confirm your identity, and we answer within one month (California residents: within 45 days). We will not treat you differently for using these rights.
If you only clicked a TrimLink short link, we usually cannot find your click, because we store nothing that identifies you. Tell us the link and the time and we will check what we can.
If you are in the EEA, the UK or Switzerland, you can also complain to your local data protection authority. We would appreciate the chance to fix the problem first.
11. Security
All traffic to TrimLink uses HTTPS. Passwords and API keys are stored only as one-way hashes, sign-in cookies cannot be read by page scripts, and our database provider encrypts stored data. Access to production data is limited to the people who run TrimLink. No system is perfectly secure, so if you find a weakness please tell us at support@trimlink.co. If a breach affects your personal data, we will tell you and the authorities when the law requires it.
12. Children
TrimLink is not meant for children. You must be at least 13 years old to create an account, or older if the law where you live requires it. If you believe a child has given us personal data, email us and we will delete it.
13. Changes to this policy
When we change this policy we update the date at the top. If a change matters for how we use your data, we will tell account holders by email or in the dashboard before it takes effect.
14. Contact
Questions about privacy or this policy: support@trimlink.co. To report a link that is abusive, use the contact form. Our Terms of Service explain the rules for using TrimLink.