Legal
Privacy Policy
Last updated
This policy describes what happens to information about you when you visit thalorin.ai. It is written to be checked: where it says the site does something, that behaviour is in the source and most of it is visible in your own browser's network tab.
Where a question cannot be answered from the source, this policy says so rather than filling the gap with a phrase that sounds like an answer.
What this covers, and what it does not
This covers the Thalorin marketing website: these pages, the contact form, and the careers form.
It does not cover the Thalorin product. If your organisation is a customer, the data you put into the product is governed by the agreement between your organisation and Thalorin. Tenant data, evidence and control records are handled under that contract, not under this page, and nothing here grants or limits rights over them.
The two are separate systems. A visitor to this website is not a product user, and reading this page tells you nothing about how your tenant is handled.
The short version
Browsing this site sends nothing to any analytics, advertising or tracking service. The pages set no cookies, write nothing to your browser's storage, read only the display preferences they need to draw themselves, and run no analytics. Our host still logs each request, as every host does; that is covered below.
Until 13 October 2026 a HubSpot tracker ran on every page and set cookies, and before July a LinkedIn advertising tag did too. Both have been removed. What is known about what they collected, and what is not, is in the section on tracking below.
We receive information you type only when you submit one of two forms. Both are described below, field by field.
The contact form
The contact form asks for your name, your email address, your company (optional) and your message. Nothing is transmitted while you are typing and no draft is saved anywhere.
Alongside those fields, the server records the IP address of the connection that submitted the form, a Cloudflare Turnstile token, and the time the form was loaded in your browser. The last two are anti-bot signals and are discarded once evaluated.
Fields that become email headers have newlines, tabs and control characters removed before use, and the email address is rejected outright if it contains header-injection patterns. This stops a submitted string rewriting the headers of the message we receive.
The submission is assembled into one plaintext email — name, email address, company, IP address, message, timestamp — and sent to our contact mailbox. Reply-to is set to your address, so our reply goes to you. We read it and answer it.
The careers form
The careers form is the more sensitive of the two, because an application is employment information about a named person. It asks for your name, your email address, your LinkedIn URL and your message, and it records the same IP address and anti-bot signals.
There is no file upload anywhere on this site. There is no mechanism to send us a document and none is stored.
The application becomes a plaintext email to the careers mailbox, with reply-to set to you. If a separate careers mailbox has not been configured, it goes to the contact mailbox instead.
Your IP address
Both forms capture the IP address of the submitting connection. It is read from a header set by our host at the edge, not from anything your browser can choose to send.
It is put to three uses. It is the key that rate-limits submissions. It is sent to Cloudflare to verify the anti-bot token. And it is written into the body of the email we receive.
That last use is worth stating flatly rather than leaving buried. Your IP address does not stay inside an abuse-prevention system. It is copied into ordinary email and persists wherever that email persists, which is longer than the anti-abuse purpose requires.
Bot protection, and what Cloudflare receives
Both forms use Cloudflare Turnstile. The Turnstile script loads from Cloudflare, so on those pages Cloudflare receives your IP address and user-agent as a function of the connection itself, before any challenge is decided. It also evaluates browser and interaction signals internal to Cloudflare that we cannot see.
On submission our server sends Cloudflare the token, our secret key and your IP address. The check fails closed: if Cloudflare is unreachable or verification does not succeed, the submission is rejected rather than let through.
Two quieter checks run alongside it. Each form records when it was loaded and the server compares that to submission time; anything faster than about two seconds is treated as automated. And the careers form carries a hidden field a person never sees. If either check fires, the submission is discarded and you are still shown the normal success message. That is deliberate, so automated clients cannot detect the trap — but it means a false positive looks exactly like success. If you send something important and hear nothing within a few working days, send it again.
Rate limiting, and what is written to Upstash
To stop the forms being used to flood our inbox, submissions are rate-limited through Upstash, a hosted Redis service, keyed on both your IP address and your email address.
Each counting key expires two hours after the first submission it counts. That is the only automatic deletion anywhere on this site, and nothing else is written to Upstash.
Until 13 October 2026 the limiter also kept per-identifier analytics counters that nothing expired, so IP and email addresses from earlier submissions may still be held there. That feature is now switched off.
Email delivery through Resend
Both forms send mail through Resend, which receives the full content of your submission in order to deliver it, and which retains delivery records according to its own terms.
From there the message sits in an ordinary mailbox and is subject to whatever that mailbox does — retention, search, backup, and forwarding by the people who read it.
Tracking: none — and what HubSpot still holds
There is no tracking, analytics or advertising code on this site. Our content-security policy permits no third-party analytics or advertising origin, and adding tracking of any kind — including analytics served from our own host — would need a change to the site's own code. A change like that would change this page with it.
That was not always so. From 12 May to 13 October 2026 a HubSpot tracking script ran on every page, without a consent gate or a cookie banner. On each page it reported the visit to our HubSpot account — the page and the page that referred you, your browser's user-agent, its own cookie identifiers, and, as a function of the connection, your IP address — and set cookies on this domain. Its form-capture feature was switched on, so the content of contact and careers submissions made while it ran may have been recorded in HubSpot as well as emailed to us. Which of the account's other features were enabled has not been confirmed, and we will not claim a configuration we cannot show.
From 11 May to 14 July 2026 the LinkedIn Insight Tag, an advertising tag, also ran on every page with no consent gate. It reported each visit to LinkedIn and may have set LinkedIn's advertising cookies. What LinkedIn received is held by LinkedIn under its own terms, not in an account of ours that we can edit; ask LinkedIn to delete it.
Removing the HubSpot script stopped new collection. It did not delete what HubSpot already held: those records stay in our HubSpot account until they are deleted there. Ask us and we will delete what we can locate. Form submissions can be found by the email address you used; records of visits can only be found by HubSpot's cookie identifier, as the next paragraph explains.
Cookies HubSpot set in your browser stay there until they expire — the longest about six months after your last visit before 13 October 2026 — or until you delete them. Until then your browser still sends them to our host with each request, but nothing in this site's code reads them. If you want HubSpot's record of your visits deleted, send us the value of the cookie named hubspotutk before you delete it; it is how that record is found, and once it is gone we cannot locate the record.
Cookies — the exact position
The pages of this site set no cookies. They write nothing to localStorage, sessionStorage or IndexedDB, and do no fingerprinting or device enumeration. To draw the page they read display preferences — reduced motion, pointer type, pixel density, graphics support — and none of that leaves your device.
Two qualifications, so that statement is not wider than it should be. On the two form pages, a script from Cloudflare runs in the page and draws the Turnstile check in a frame served from Cloudflare's own domain. That check examines browser and interaction signals to decide whether you are a person, as described above, and anything it stores in that frame is Cloudflare's, not this site's. And our host's firewall can answer a request it judges automated with a challenge page instead of the site; a browser that passes the challenge can be given a cookie by the host so that it is not challenged again.
Hosting, and logs
The site is hosted on Vercel at www.thalorin.ai. A host necessarily processes the IP address, URL and user-agent of every request it serves, and keeps request logs to operate the platform.
The bare address thalorin.ai is not served by us. Our domain registrar's forwarding service answers it and redirects to www, so a request to the bare address reaches that service — with your IP address and the address you asked for — before it reaches us.
Fonts are served from this domain rather than fetched from a font provider, so a page load sends nothing to Google.
Our own application logging records error conditions, and its log statements do not interpolate your name, email address or message. When a provider fails we log what kind of failure it was. For the email provider we also log its error message, because that is what makes a delivery failure diagnosable: for input-validation errors the message is withheld entirely, and for any other error your name, email address and company or LinkedIn URL are stripped out wherever they appear in it word for word.
Who receives your information
Beyond the people at Thalorin who read the mailbox, your information reaches the providers that operate this site:
- Vercel — hosting. Processes every request, including your IP address and the pages you view.
- HubSpot — no longer. From 12 May to 13 October 2026 it received visit data from every page and possibly form content, and it still holds what it received (see above).
- LinkedIn — no longer. From 11 May to 14 July 2026 it received visit data from every page through its Insight Tag, and holds it under its own terms.
- Our domain registrar's forwarding service — only for requests to the bare address thalorin.ai, which it redirects to www.
- Cloudflare — bot protection. Receives your IP address and browser signals when a form page loads, and your IP address again at verification.
- Upstash — rate limiting. Holds your IP address and email address as identifiers, in counting keys that each expire two hours after the first submission they count — and, for submissions before 13 October 2026, possibly in the analytics counters described above.
- Resend — email delivery. Receives the full content of your submission.
How long things are kept
We are not going to publish a retention schedule we do not operate.
Nothing in this site's code expires anything, with the single exception of the rate limiter's counting keys. Form submissions become email and last as long as that mailbox keeps them. What HubSpot collected before 13 October 2026 stays in our HubSpot account until it is deleted there, and the rate limiter's analytics counters from before that date stay in Upstash until they are deleted there. Resend keeps delivery records according to its own terms, and host request logs are kept according to the platform's settings.
Published retention periods for each of those are an open item. Until they are set, the practical position is that you can ask us what we hold about you and we will tell you and delete it. That is a working answer, not a substitute for the schedule.
Your rights
Depending on where you live, you may have the right to ask what personal information we hold about you, to have it corrected or deleted, to object to particular processing, and to receive a copy. Ask through the contact form and we will act on it.
To find your records we will generally need the email address you used. For HubSpot's records of past visits, the identifier is the HubSpot cookie in your browser rather than your name — so deleting that cookie before asking removes our ability to locate those records.
Two honest limits. A deletion covering a HubSpot record requires us to act inside HubSpot. And a message already delivered as email cannot be recalled from a recipient's mailbox by us; we can delete our copies.
Children
This site is aimed at organisations, not children. We do not knowingly collect personal information from children, and neither form asks for an age or is designed to attract a child's use.
If you believe a child has sent us information through one of these forms, tell us and we will delete it.
Security of this site
What is actually in place, and no more: www.thalorin.ai, where these pages are served, uses HTTPS with strict transport security (the bare address thalorin.ai is answered by our registrar's forwarding service, and that response does not yet carry it); a content-security policy restricts which origins the page may load from or talk to; framing and plugin content are blocked; form input is sanitised against header injection and length-bounded; bot protection fails closed; and submissions are rate-limited.
None of that eliminates risk and we are not going to claim it does. If you find a vulnerability, our disclosure contact is published at /.well-known/security.txt. Reports are read by people and answered.
Changes
When this policy changes, the date at the top changes with it. We keep no mailing list for policy notifications and will not create one for this purpose, so the date is the mechanism.
If a change materially widens what we collect or who receives it, we will say what changed rather than quietly reissuing the text.
Contact
Questions, requests and corrections go through the contact form. Security vulnerabilities go to the contact published in /.well-known/security.txt.
Thalorin Inc. Questions about this page go through the contact form.