Legal
Privacy policy.
Tellane makes interactive product demos. Three kinds of people touch it — our customers, the buyers who drive their demos, and the leads those buyers become — and this page says what we collect from each and why.
Last updated August 23, 2026
Who this covers
“Tellane”, “we” and “us” mean the operator of tellane.com. This policy applies to the Tellane website, the web application, the Chrome capture extension, the public demo player, and the API.
It distinguishes three roles, because the rules are different for each:
- Customers — people with a Tellane account who build lanes. For your account data, Tellane is the data controller.
- Viewers — people who open a lane a customer published. Tellane records how the lane was driven on the customer's behalf; the customer decides what to do with it. For that data, the customer is the controller and Tellane is the processor.
- Leads — viewers who fill in a form inside a lane. Same as above: the form answers belong to the customer who published the lane.
If you have a Tellane account
We collect what it takes to run your account:
- Identity — your name, email address, and optional profile photo. If you sign in with Google, we receive your name, email, and avatar from Google and nothing else.
- Credentials — a salted hash of your password (never the password itself), and, if you turn on two-factor authentication, an encrypted authenticator secret and hashed backup codes.
- Sessions — the IP address and browser of each signed-in device, shown to you under Settings → Profile so you can sign any of them out.
- Workspace content — the lanes, stops, captured screens, prospect links, and settings you create. Captured screens are images of your own product; you are responsible for what they show.
- Billing — plan, seat count, and invoices. Payment is handled by Paddle, our merchant of record; card numbers never reach Tellane.
- Integration secrets — Slack webhook URLs, HubSpot tokens, and webhook signing secrets you connect, encrypted at rest. API keys are stored only as hashes and shown to you once.
- Onboarding answers — the role and goal you pick in the first-run wizard, used to tailor the checklist.
If you drive a lane
When you open a demo at {workspace}.tellane.com/l/… or on a customer's own domain, the player sends a small stream of events back to Tellane so the customer can see how their demo performs: that a drive started, each stop you reached, whether you clicked the call to action, and whether you reached the end, with timings.
Each event carries:
- a random session id for this drive and a random visitor id kept in your browser's local storage so repeat drives can be counted as one person — neither is tied to your name unless you later fill in a form;
- your device class (desktop, tablet, mobile), the referrer and the source the link came from;
- your approximate location (city and country) derived from your IP address at the edge — the IP address itself is not stored in analytics;
- the prospect token if the customer sent you a personalized link.
Customers may also load their own Google Analytics 4 or Google Tag Manager container inside the player; when they do, Google's terms apply to those tags. Tellane never sells viewer data or uses it for advertising.
If you fill in a lead form
Some lanes ask for an email address, and optionally a name and company, before continuing. Those answers go to the customer who published the lane, joined with the engagement of your drive (stops reached, time spent, CTA clicked) and your approximate location. The customer may forward them to their own tools — a CRM such as HubSpot, Slack, Zapier, or their own webhook endpoint. To exercise your rights over that data, contact the company whose demo you drove; if you don't know who that is, write to us and we'll put you in touch.
How we use information
- To provide the service: host lanes, play them, show analytics, deliver leads, send the emails you asked for (verification, invitations, lead alerts, digests, billing notices).
- To keep accounts safe: verify email addresses, enforce two-factor checks, rate-limit abuse, and investigate security incidents.
- To bill: seats, plan changes, invoices, and trial reminders.
- To improve Tellane, using aggregate, de-identified usage. We do not profile individuals.
- To respond when you contact us.
We do not sell personal information, and we do not run third-party advertising.
Who we share it with
Only service providers that help us run Tellane, each bound by contract to use data solely for that purpose:
- Hosting and content delivery — the servers, storage, and network that run the application and serve captured screens.
- Payments — Paddle, our merchant of record, handles checkout, payment details, invoices, and sales tax; their name appears on your statement.
- Email delivery — a transactional email service sends the messages described above.
- Sign in with Google — only if you choose it.
A current list of providers is available on request at [email protected].
Integrations you connect yourself — HubSpot, Slack, Zapier, Google Analytics, your own webhooks — receive exactly what the integration says it sends, and only after you connect it. We will also disclose information when the law requires it, or to protect the rights and safety of Tellane, our customers, or others.
Where data lives and how long
- Application data is kept for as long as your workspace exists.
- Drive analytics are kept for as long as the lane's workspace exists; the free plan shows the last 7 days but the underlying events are not deleted early.
- Workspace exports you request are kept for 7 days, then removed.
- Deleted workspaces wait in a 14-day grace period during which any admin can cancel, then every lane, screen, lead, and event is purged.
- Deleted accounts are removed immediately once you confirm the emailed link.
- Sessions expire on their own and can be revoked at any time under Settings → Profile.
- Backups may hold copies for a limited period after deletion.
Your choices and rights
Depending on where you live — including the EU/EEA and UK under the GDPR, and California under the CCPA — you may have the right to access, correct, export, restrict, or delete your personal information, and to object to certain processing. Most of it is self-serve:
- Export a whole workspace (lanes, leads, events) as a zip from Settings → Workspace.
- Change your name, email, photo, and password under Settings → Profile.
- Delete your account from Settings → Profile, or a workspace from Settings → Workspace.
- Turn off each notification email under Settings → Notifications.
For anything else, email [email protected]. We answer within 30 days and never charge for a request. If you are in the EU/EEA or UK you can also complain to your local supervisory authority.
Cookies and local storage
Tellane uses no advertising or cross-site tracking cookies. What it does set:
| Name | Purpose |
|---|---|
| Session cookies (app) | Keep you signed in; a second, short-lived one holds a pending two-factor check; an optional 30-day one remembers a trusted device |
tellane.visitor (local storage, player) | A random id so a returning viewer is counted once. Clearing site data resets it. |
tellane.sidenav and similar (local storage, app) | Remember interface preferences such as the collapsed sidebar |
Children
Tellane is a business tool and is not directed at anyone under 16. We do not knowingly collect information from children; if you believe we have, tell us and we will delete it.
Changes to this policy
When this policy changes in a way that matters, we email every account holder before it takes effect and update the date at the top.
Contact
Questions about privacy: [email protected]. Anything else: the contact page.