Ad-account access is encrypted
The access you give Torii to your Meta, Google Ads and GA4 accounts is encrypted when it's saved and never shown in the app. The app only tells you whether each connection is set up.
Record every lead and order, and let only the real ones through.
This page covers what Torii keeps, who else handles it and how it works with your cookie banner, so you can answer your data protection lead, or your client's.
Everything Torii records from your site is kept in London: visits, leads and orders, the decision your rules made on each, and what was sent to each ad platform. If you use call tracking, call records and recordings are kept there too.
The Torii tag loads in the background from a global network, so it doesn't hold up your pages wherever your visitors are. What it records is sent to London.
Call tracking adds three specialist providers for tracking numbers, transcripts and AI call scoring. Every provider is listed below with what it receives.
The access you give Torii to your Meta, Google Ads and GA4 accounts is encrypted when it's saved and never shown in the app. The app only tells you whether each connection is set up.
Give each client its own Meta connection and it receives only that client's conversions, so one client's leads or orders never train another client's ads. We set this up with you during onboarding. A single account-wide connection suits a business running its own ads.
If your site passes Torii a lead's email or phone number, it's scrambled (hashed) in the visitor's browser first, so the plain details never reach Torii. Meta can still use the hashed version to match the conversion to the right person.
With call tracking, each caller's number is stored encrypted and shown masked by default, as +44 ••• ••• 123. Torii can still recognise a repeat caller.
Torii saves each visit, lead and order as it arrives, before your rules judge it, so you can show why one did or didn't count. Those records include personal data, such as IP addresses and browser details.
| Record | What it holds |
|---|---|
| Visits, leads and orders |
Each page view, click, lead or order the Torii tag records, with the page, the time and any value, plus the ad click and campaign that first brought the visitor and the one that most recently brought them back. Alongside it: the visitor's IP address, browser and device details, a random visitor ID, their cookie choice if your banner shares it, and Meta's and Google's browser IDs if those tags are on your site. |
| Hashed contact details Rolling out |
If your site passes Torii a lead's email or phone number, only a hashed version is stored, and it travels with that visitor's later conversions. The plain details never reach Torii. |
| Gate decisions |
For every visit, lead or order your rules check: whether it passed, was held or was rejected, which gate and which version of your rules decided, and why. Each review decision is kept too, with who made it, when and any note. |
| Delivery results |
For each conversion and each ad platform: whether it was sent, failed, was skipped or is still waiting to go, the reason for any skip or failure, and the platform's reply, such as Meta's confirmation that it arrived. Each attempt is kept, so you can see the full history of a retry. |
| Calls |
If you use call tracking: the caller's number (encrypted), the tracking number and the ad or source it belongs to, when the call happened and how long it lasted, the recording, the transcript with card numbers, contact details, names and addresses taken out, and the AI's rating of the call with a short summary. Callers hear a recording notice before they're connected. |
| Shopify orders |
From your store's order notifications: the order and its value, with the customer's email and phone number stored only in hashed form. Names and addresses are dropped before the order is saved. The shopper's choice in Shopify's own cookie banner comes with each checkout, so an order from a shopper who declined ad cookies isn't sent to Meta. |
| Ad-account access |
The access Torii needs to your Meta and Google accounts, stored encrypted. |
Torii keeps IP addresses and browser IDs because Meta needs them to match each conversion.
The Torii tag stores a few values in your visitors' browsers, under your own site's domain, so a later lead or order can be tied back to the ad click that started it. Each one is in this table with how long it's kept, ready to copy into your cookie notice. The tag also reads the cookies set by Meta's pixel and Google's tag, if those are on your site.
| Name | Where | Kept for | Holds |
|---|---|---|---|
_torii_vid | Cookie | 365 days | A random visitor ID |
_torii_sid | Session storage | The session | A random session ID |
_torii_ft | Cookie + local storage | 90 days | Where the visitor first came from: landing page, referring site, campaign tags and ad click IDs |
_torii_lt | Cookie + local storage | 30 days | Where the visitor most recently came from, updated when they arrive from an ad, a tagged link or another website |
_torii_uid | Cookie + local storage | 365 days | Hashed email and phone number, only if your site passes them to Torii Rolling out |
_torii_dni | Session storage | The session | The tracking phone number shown to this visitor |
_torii_cart | Session storage | The session | The visitor and ad click details already added to their Shopify basket, so they're only added once |
Two companies run Torii itself: Vercel and Supabase. The others receive data only when you use the feature that needs them, and they process it on their own services, so not everything stays in London. We can point you to each one's data-processing terms.
Runs the Torii app in London, and serves the Torii tag to your visitors from its global network so it loads quickly.
Hosts Torii's database in London on Amazon Web Services, and handles sign-in to the Torii app, including account emails. If you use call tracking, it also keeps call recordings in private storage.
Receives the conversions that pass your rules: what the conversion was, when it happened, its value and the page it happened on. To match each one, Meta also gets the visitor's IP address, browser details, Torii's random visitor ID and the browser IDs set by Meta's own pixel. Keep Meta's pixel on your site, because Torii skips any conversion without those IDs; hashed contact details will do the same job as they roll out. With call tracking, qualified calls are sent with the caller's number in hashed form.
GA4 receives the conversions that pass your rules, with their value, linked to the visitor's existing GA4 ID. Torii also reads GA4 traffic reports. From Google Ads, Torii reads campaign spend only, so you can see cost per conversion.
Provides the UK tracking numbers and puts each call through to the business's own phone line. Recordings are moved into Torii's private storage, then deleted from Twilio.
Turns answered calls of 10 seconds or more into transcripts. It gets each recording through a private link that expires after 10 minutes.
Its Claude AI reads each call's transcript, with the short description of the business you give Torii, and rates the call: qualified lead, existing customer, spam or wrong number, plus the outcome, the service asked about and a one-line summary.
Alerts the Torii team when something in the service needs attention. If you use call tracking, the team also gets a short notice of each call (the client name, tracking number or source, call status and duration) so they can check the service is working. The caller's number stays in Torii.
Off by default. You install Clarity yourself and it records under your own Clarity account. Torii stores only the IDs needed to link a gate decision to its recording, only when the visitor has accepted all cookies, and sends Microsoft nothing of its own.
Torii is in early access and every account is set up with us, so ask about data-processing terms, how long records are kept and how they're deleted before anything goes live.
Send your questions before the demo and bring whoever approves new tags for you or your clients. We'll go through what Torii would keep for your setup and what to add to your cookie notice.