Legal
Privacy policy
Last updated
Bio collection is not open yet. These visitor-data terms describe what will apply no earlier than 20 November 2026.
How Trizlink collects, uses and protects information, written so you can decide what to share before you share it.
Introduction
This policy covers the Trizlink website, the web application and the Android app. It explains what is collected, why, how long it is kept and what you can ask us to do about it.
Using Trizlink means this policy applies to you. If you disagree with it, the correct response is not to use the service, and to delete any account you have already created.
Information we collect
Eleven categories, listed separately because they are collected for different reasons and kept for different lengths of time.
Personal information
Your name, email address and profile image, taken from the account you sign in with. For paid plans we also hold the billing contact and the record of what was purchased.
File uploads
Images and documents you upload for bio pages, avatars and social posts, together with their file names, sizes and types.
Usage data
Which features you use and when, plus technical details your browser sends β device type, operating system, browser version and approximate region.
Link analytics data
When someone follows one of your short links we record the time, the referring page, the device class and a country-level location. IP addresses are used to derive that location and are not retained alongside the click record.
Cookies and tracking technologies
Storage used to keep you signed in, remember your appearance settings and measure product usage. The full list is in the cookie policy.
Notifications
The Android app asks for notifications only when you turn an alert on. It is optional, it is requested at the moment it is used, and refusing it leaves the rest of the app working.
What does a bio page collect from visitors?
No earlier than 20 November 2026, when Bio collection opens, a Contact block can store the bio page display name or title, submission time and the fields a visitor sends: a name, email address, phone number or message. While email confirmation is pending, an Email Collection block can store the submitted address, page display name or title, request and expiry times, and a digest of the confirmation token. The token itself is not stored. Following a valid confirmation link removes the pending request. The subscriber record then stores the page display name or title, email address and confirmation time. Unconfirmed addresses do not appear in the subscriber inbox.
To limit abuse of these forms, Trizlink derives a salted fingerprint from a visitor's IP address and browser user agent. It stores that fingerprint with an hourly window, action and request count. The raw IP address and user agent are not stored in this counter. Counter rows older than seven days are removed by the next daily cleanup.
AI requests
For each AI suggestion, Trizlink sends the model only what that feature needs:
- Draft a post: the brief you typed (up to 400 characters), the kind of post, and any current draft (up to 1,200 characters).
- Bio taglines: the display name or page title, and the current tagline.
- "What stands out" insights: your workspace's click totals for this period and the last, up to 8 of your busiest links (short code, title and clicks), and the daily counts. No visitor-level rows.
- Voice: the transcript or transcripts of a recording (the browser's own, where it makes one, and the server's) and, for a new link, up to 50 label names and 50 folder names from that workspace.
Trizlink adds none of your email address, password or payment details to a request; what you type or say is sent as you gave it.
Your recordings
A recording is made only when you press Start. Its audio is stored privately, with no public link, and deleted within 24 hours of recording. One exception: if the storage service cannot be reached or does not confirm the deletion when the audio is due to go, it is deleted at a later hourly check. Its transcripts and the proposal made from them stay until you delete the recording, the workspace it belongs to, or your account. A recording never writes anything by itself. A post, a tagline or a link is saved only after you confirm the proposal.
Your own AI keys
You can add your own Anthropic or OpenAI key. It is stored encrypted by Trizlink, used only for your own AI requests, and sent only to the provider it belongs to. It is never shown back in full: you see the provider and its last four characters. You can remove it at any time, and it is deleted with your account.
Microphone
Microphone access is requested only when you press Start in the recording sheet, after its purpose is shown. On the web your browser asks. The Android app asks for one permission for this: recording audio (RECORD_AUDIO).
How we use your information
To operate your account and the links it owns, to produce the analytics you asked for, to answer the AI requests you make and turn your recordings into proposals, to answer support requests, to bill paid plans, to detect abuse, and to decide what to build next.
Who can read a bio page message or subscriber address?
When Bio collection opens, contact messages will go to the page's workspace inbox. Any workspace member can read messages and confirmed subscriber addresses; a manager can delete them. An Email Collection address will be used to request confirmation and will appear as a subscriber only after confirmation. If workspace alerts are enabled, Trizlink may email its verified owner about a new message or subscriber. The alert identifies the bio page and submission kind, with an inbox link; it does not include the visitor's message text.
Free accounts help pay for themselves. We may use content from free accounts to improve and train the features we build. This does not cover your recordings, their transcripts or the text of your AI requests. Content in a paid plan is not used this way without your explicit consent. You can object to this at any time by writing to us, and moving to a paid plan stops it.
We do not sell personal information, and we do not use the contents of your links or messages for advertising. The dashboard shows promotions for other products made by the Trizlink team; to count each one once a day, the app keeps a random identifier on your device, which is sent to us with that count, is not linked to your account and is not shared with anyone else.
We also email account holders occasionally about what has changed in Trizlink; every one of those messages carries a one-click unsubscribe link that needs no sign-in, and using it leaves the mail you asked for β workspace invitations, the traffic alerts you set up and your scheduled reports β arriving exactly as before.
Third-party services
Trizlink relies on outside providers for authentication, hosting, file storage, email delivery, payment processing, product analytics, AI answers and voice transcription. Each receives only the data its function needs, and each is bound by its own agreement with us.
Card payments are handled by Polar, which sells the paid plans as the merchant of record. When you pay by card, Polar receives your email address, your account identifier, the plan and the number of seats, and collects your card and billing details itself under its own privacy policy. Your card details never reach Trizlink. Polar tells us whether a subscription is active, when it renews and when it ends, and we keep that record.
Payments are not refunded. Cancelling stops the next renewal, and your plan runs to the end of the period you have already paid for.
When a company buys a white-label licence, a buyout or a renewal, or asks about one, we keep the buyerβs name, email address, company, domain and order details to issue, verify and renew the licence. Our licensing service stores the order for us. White-label payments are made by bank transfer through Wise, and we keep the transfer reference and any proof the buyer uploads, to verify the payment. White-label licence, buyout and renewal payments are final and are not refunded.
Our product analytics includes SESSION RECORDING. Microsoft Clarity records how pages are used β pointer movement, clicks, scrolling and the sequence of screens β and replays it to us as a recording of the session rather than as a count of visits. Text you type into a field is masked before it leaves your browser. Clarity is a separate controller of what it records under its own policy, not a processor acting only on our instructions, so its policy governs that data alongside ours. This is stated the same way in the cookie policy.
The other three analytics destinations β Google Analytics 4, Amplitude and Sentry β receive events and errors, never a recording. An error report carries the fact that something failed and where, never the message or the content you were working on.
AI answers come from Anthropic, with two exceptions that send a request to OpenAI. Unless you have added your own Anthropic key, requests run on free credit provided through FilesHub, a storage and AI-routing service run by the team behind Trizlink. OpenAI receives a request in only two cases: you are on a paid plan and the free credit is unavailable, or you added your own OpenAI key. Each provider receives the material listed under AI requests and no other data about you. A request paid for by your own key is also governed by that provider's terms with you.
Groq transcribes your recordings, so it receives the audio. On the web, where your browser offers speech recognition, the browser may also process the audio while you record and send it to the browser's maker under that maker's policy. The Android app does not use browser speech recognition. FilesHub stores the audio privately until it is deleted. For each request on the free credit, FilesHub receives usage counts only: the credit account, the model, the token counts and the time. The usage report never carries what was written or said, or anything that identifies you.
When Bio collection opens, FilesHub will receive the visitor's email address, bio page display name or title and confirmation link to send a signup confirmation. If workspace alerts are enabled, it will also receive the verified owner's email address, page display name or title, submission kind and time, record reference and inbox link. An accepted send request does not prove that an email reached its recipient.
Data sharing and disclosure
We share data with the providers above, with people you invite into your own workspace, and where the law requires it. Nothing else.
If Trizlink is ever sold or merged, account data may transfer to the acquirer. You would be told before that happened, with enough notice to export or delete first.
Data security
Traffic is encrypted in transit, stored data is encrypted at rest, and access is restricted to the people who need it to run the service. The detail is in the data security document.
No system is perfectly secure. We will tell affected users about a breach that puts their data at risk rather than waiting to be asked.
Your rights (GDPR)
You may ask for a copy of your data, correct it, delete it, restrict or object to how it is used, take it elsewhere in a portable format, and withdraw a consent you gave earlier.
Write to hello@trizlink.com and we will answer within 30 days. You also have the right to complain to your local data protection authority.
Data retention
Account data is kept while the account exists. Link analytics are kept for as long as the link does. Deletion timing depends on the record and request, as the Data deletion document explains.
When is a bio page visitor record deleted?
When Bio collection opens, a contact message or confirmed subscriber address will stay in its workspace until a manager deletes that record or the workspace is deleted. Deleting the bio page alone will not delete either record. A pending confirmation expires after seven days; its link cannot confirm an address after expiry, and a daily cleanup removes expired requests. Deleting the workspace removes its messages, pending confirmations and confirmed subscribers.
A recording's audio is deleted within 24 hours; its transcripts and proposals stay until you delete them, the workspace or the account. Your own AI key stays until you remove it or delete the account, and the "What stands out" insights, written per workspace from aggregate counts, stay until regenerated or until the workspace is deleted. A record of each AI request (who made it, when, the feature, the provider, the model, the level and the token counts) is deleted once it is 13 months old; a record of a free-credit request also waits until it has been reported to FilesHub. If you delete your account, those records stay for the rest of that time, no longer linked to you.
Polar, the merchant of record for card payments, keeps its payment records under its own policy. Contact us if you need to know which Trizlink billing records remain after account deletion.
Children's privacy
Trizlink is not intended for anyone under 16, and we do not knowingly collect their data. If you believe a child has created an account, tell us and we will remove it.
International data transfers
Our providers operate in several countries, so your data may be processed outside the one you live in. Where that leaves the European Economic Area we rely on Standard Contractual Clauses or an adequacy decision.
Changes to this policy
We update this page when what we do changes. Material changes are announced in the app and in the RSS feed at least 14 days before they take effect, and the date at the top always reflects the current version.
Contact us
Privacy questions go to hello@trizlink.com. Account and billing questions go to support@trizlink.com.
Questions about this document? Email support@trizlink.com or use the contact form.