Privacy policy

Who we are

TadaSnap (“we”, “us”) operates the TadaSnap Chrome extension, the website at this address and the API behind them. We are the controller of the personal data described here. Questions and requests go to privacy@tadasnap.com.

What we collect

1. Captures you make

Screenshots and screen recordings you take with the extension, including microphone audio and camera video only when you turn them on for a recording. Also the edits you make (annotations, framing, zoom segments, guide steps), titles and descriptions, and comments. Captures stay on your device until you choose to share, upload or sign in and save them. Nothing is uploaded silently.

2. Context attached to a capture

When you capture a page we attach a small amount of context so the result is useful to whoever receives it:

• the page URL and title;
• browser name and version, operating system, viewport and screen size, device pixel ratio;
• the time of the capture.

In feedback mode we also record, only while the capture is in progress, console errors and warnings and the method, URL and status code of network requests that failed. We never record request or response bodies, cookies, headers, form input or anything you type. You can turn context capture off entirely in the extension settings.

3. Click and cursor data during tab recordings

To power auto-zoom, guides and interactive demos, tab recordings log where you click, the visible text of the element you clicked, cursor positions and scroll positions, plus a screenshot of the visible area at each click. Key presses are only counted, so we can detect typing pauses; the keys themselves are never recorded.

4. Your account

When you sign in with Google or an email link we store your email address, name and profile picture as provided by the sign-in method, plus your plan and settings.

5. People who view or comment on share pages

Viewers don't need an account. To count unique views we store a random identifier in the viewer's browser storage; it is not linked to a person. Guests who comment give a display name and, optionally, an email address used only to notify them of replies. Guest comments get a private token stored in their browser so they can edit or delete their own comments.

6. People who watch a Magic Demo

When someone opens a Magic Demo link, we record one viewing, so the owner of the demo can see how it went. A viewing holds:

• which steps were shown, and for how long;
• which hotspots and buttons were pressed, and whether the end was reached;
• the kind of device and browser;
• the site the viewer came from: the name of the site only, never the full address;
• the campaign tags in the link, if it has any;
• a named link (the one thing that can name a person, chosen by the demo's owner);
• the times of a viewing;
• the country, when the network provides it.

We don't store an IP address. A viewing sets no cookie, and no cookie is sent with it. If you are signed in to TadaSnap when you open a demo's link, the page checks your sign-in once, so that views of your own demos aren't counted; who you are is not stored with the viewing. A demo shown inside another site never does this. To count viewers, the viewer's browser keeps a random id. We store it only as a scrambled value that can't be turned back into the id. A viewing collects no name, email address or typed text. Our hosting providers keep their own access logs, which include IP addresses, for a limited time.

If the owner makes a named link's own narration, the values they put on that link (such as a name) are sent once to ElevenLabs, a voice company, to make that audio.

If a viewer's browser sends Do Not Track or Global Privacy Control, the viewing isn't recorded in Insights at all.

The owner of the demo sees these numbers. Viewings are deleted after 13 months (395 days), and when the demo is deleted.

7. Usage analytics, session recordings and error reports

We use PostHog to understand how people use TadaSnap so we can make it better. On our website and web app, and in the extension's own screens (the popup, the editor and its settings), PostHog records the pages and screens you open, what you click, which features you use (for example “recording exported” or “auto-zoom turned on”), your browser, device, IP address and the approximate location it gives, and, when you're signed in, your account id, email and plan so we can tell your visits apart. It also records sessions on those pages so we can replay how a screen was used and find what's confusing or broken. Text you type into fields is hidden in these recordings.

Analytics never runs on the websites you visit or capture: the extension doesn't send PostHog or Sentry anything about other sites, and the content of your captures and recordings is never sent to either of them.

We use Sentry to catch errors. An error report contains the error message and where it happened in our code, your browser and device, your IP address, the page or screen of TadaSnap you were on and, when you're signed in, your account id. On our website, a report can include a short replay of the moments before the error, with text and images hidden. We don't use advertising trackers.

8. Payments

Pro subscriptions are sold by Paddle, our merchant of record. Paddle collects your payment details and billing address and handles taxes and invoices under Paddle's privacy policy. We receive your subscription status, plan, country and the email used at checkout. We never see your card number.

Answers to a Magic Demo's form

The owner of a Magic Demo can put a form on a card. When someone sends it, the answer is kept as a lead, for the owner. This is separate from captures (the extension never records what you type) and from viewings (a viewing and Insights never hold what was typed into a form). A lead holds:

• the email address and every answer a person types into a form;
• which form and step it was on, and when it was sent;
• the name of the link they came by, if it has one;
• the words they agreed to, and when;
• the domain of the email address (the part after the @), so the owner can see which companies the leads come from.

Only the owner of the demo can read them. TadaSnap's staff don't read them. The email address and the answers are encrypted before they are stored, and the key is not in the database. No IP address, browser details or cookie are stored with a lead. Before sending, a person sees a box they have to tick to agree that the owner may contact them. The words are the owner's, and the owner can add a link to their own privacy notice.

When the owner connects an app and turns it on (a webhook, Slack, HubSpot, Salesforce or Zapier), each new lead is also sent to that app, which keeps it under its own terms.

Leads are kept only for a Pro plan: on Free, a form isn't shown to viewers and nothing is collected. Leads are deleted after 2 years (730 days), and when the demo is deleted for good (a demo in the bin keeps its leads until then). The owner can delete one lead, all of a demo's leads, or everything for one email address, and can export them as a CSV. Deleting a lead here doesn't remove the copies already sent to the owner's connected apps. A person who wants their details removed should ask the owner of the demo. A calendar or survey that a demo shows on a card is handled by that provider, under its own policy: what is typed into it doesn't reach us and is not a lead.

What we don't collect

• Your browsing history or the contents of tabs you don't capture.
• Keystrokes, passwords, form input or clipboard contents.
• Anything at all while you are not capturing. No capture ever starts without your explicit action, and recording state is always visible.

Hide private info

Hide private info helps hide emails, keys, card numbers and passwords when you record a tab. What it finds never leaves your computer: a recording keeps only where they were. They are covered on the page before the recording is made.

On-device captions and noise removal

Captions and noise removal happen on your computer, in the extension. Your audio never leaves it to be analysed, and we never see it. No cloud AI for recordings and the video editor.

• Noise removal uses RNNoise, which ships inside the extension. Nothing is downloaded.
• Captions use Whisper, a speech model made by OpenAI. The first time you make captions, the extension asks before it downloads the model once (154 MB, or 501 MB for Best) from Hugging Face, where the model is published. The model is a data file, not code: the extension checks every file against a fingerprint it ships with and keeps nothing that doesn't match. That download is an ordinary file request. It carries what any download does (your IP address and browser details) and nothing about you, your recordings or your account.
• After that, captions work offline. You can remove the model in the extension's settings at any time.
• Captions you make are part of your edit. They stay on your computer until you share or save the recording; a share link then shows them to its viewers.
• A share link never shows its viewers the captions of parts you removed.

Cloud AI in a Magic Demo

In a Magic Demo you can ask cloud AI to write step text, translate, describe a picture, make a voice or answer a question about your demos. It runs only when you ask, only on that demo's content, and the first time it shows you exactly what is sent and to whom.

Typed text, cookies, headers, what a page sent or received, and anything about the people who watch are never sent. Nothing is sent for a recording or from the video editor. The lists below are the same ones the editor shows you before the first use of each kind; when one of them changes, the editor asks again.

What these companies do with what they receive:

• Anthropic does not use what is sent through its API to train its models without permission. How Anthropic handles data
• ElevenLabs may use what is sent to improve its service unless that is switched off in the account. How ElevenLabs handles data

For each use we record that it ran, what it cost and when, so your plan's monthly credits can be counted. That record holds numbers only: never what was sent or what came back. Your yes to each kind is kept with its date, and you are asked again when what is sent changes. On-device options are free: translation and text in Chrome where your computer supports them, and captions made on your computer.

How we use it

• To provide the service: store and serve your captures, render exports, create share links, deliver comments and notifications.
• To keep it safe: rate limiting, spam prevention on guest comments, abuse investigation.
• To bill you if you subscribe to Pro.
• To improve the product using usage analytics, session recordings and error reports (see section 7).
• To answer support requests.

We don't sell personal data and we don't use your captures to train machine-learning models.

Where it is stored

Account data, item metadata, comments and edit documents live in a Postgres database and authentication service hosted by Supabase. Files (images, recordings, exports) live in an S3-compatible object store. Everything is encrypted in transit (HTTPS only) and at rest. Files are served through short-lived signed links, so a share link can be turned off at any time.

Data is processed by these providers on our behalf: Supabase (database and sign-in), our object storage provider, Paddle (payments), Resend (transactional email), PostHog (product analytics and session recordings) and Sentry (error reports). Each is bound by a data processing agreement. Some of them process data in the United States; transfers rely on standard contractual clauses.

When you ask for cloud AI in a Magic Demo, what the lists above name is sent to Anthropic or ElevenLabs, and to nobody else.

Who can see your data

• People you share with. A share link shows the item, its edits, comments and, for feedback captures, the technical context. You choose the audience: public, anyone with the link (default), your workspace, or password protected. Only items you mark public may be indexed by search engines; everything else is sent with a noindex instruction.
• Our processors, listed above, strictly to run the service.
• Authorities, only if the law requires it, and we will tell you when we are allowed to.

How long we keep it

• Items and files: until you delete them. Deleted items sit in your trash for 30 days so you can restore them, then they are permanently purged.
• Account: until you delete it. Deleting your account removes all items, files and comments within 30 days.
• Local captures in the extension: on your device only, until you clear them.
• Guest commenter names and emails: as long as the comment exists.
• Answers to a Magic Demo's form: 2 years (730 days), or until the owner deletes them or the demo.
• Analytics events: up to 12 months. Session recordings: 30 days. Error reports: up to 90 days.
• Billing records: as long as tax law requires, held by Paddle.

Your rights and controls

Wherever you live, you can:

• Export everything (items, metadata, comments, settings) from Settings → Export data, or by emailing us.
• Delete single items, or your entire account from Settings → Delete account.
• Access and correct your profile from Settings.
• Turn off context capture, the unread badge and email notifications in the extension and Settings.

If you are in the EU, UK, Switzerland, California or another place with privacy laws, you also have the right to object to or restrict processing and to complain to your local authority. We rely on performance of a contract for providing the service, legitimate interests for security, product analytics and error reports, and consent where the law requires it. Email privacy@tadasnap.com; we answer within 30 days.

Cookies and browser storage

• Sign-in session cookies (required to keep you signed in).
• A cookie that remembers the password for a protected share link for 7 days, so you don't have to type it on every visit.
• Browser storage for your theme, dismissed hints, the random viewer identifier and, for guests, your comment name and token.
• A PostHog cookie and browser storage with a random identifier, so visits and screens from the same browser count as one person.

We don't use third-party advertising cookies.

Chrome Web Store disclosures

TadaSnap has a single purpose: capture, polish and share screenshots and screen recordings. The extension requests permissions only for that purpose and asks for optional permissions (microphone, camera) at the moment you turn the feature on. Content scripts run only after you start a capture. No code is loaded from remote servers: the speech model for captions is a data file, downloaded once after you agree and checked against a fingerprint shipped with the extension, and the analytics and error-reporting code is bundled into the extension. The extension sends usage events, session recordings of its own screens and error reports to PostHog and Sentry as described in section 7; it never sends anything about the websites you visit or capture.

TadaSnap's use and transfer of information received from Google APIs to any other app will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Children

TadaSnap is not directed at children under 16 and we don't knowingly collect their data. If you think a child has an account, email us and we will delete it.

Changes to this policy

When we change something meaningful we will update the date at the top and, for significant changes, tell signed-in users by email or inside the app before the change takes effect.

Contact

Privacy requests: privacy@tadasnap.com. Everything else: support@tadasnap.com. See also our terms of service.