Privacy

Tildew privacy policy

This policy is published by MZEUS LABS LLP and applies to the Tildew Chrome extension, the Tildew app on iPhone and Android, and the tildew.com website.

Effective date: 16 October 2026.

Summary in plain words

Tildew turns the public YouTube video you are watching into a transcript and typed, timestamped notes in Chrome's side panel. To do that we need to know who you are (you sign in with Google or Apple, so we hold that account’s user id, its email address (with Apple, possibly a private relay address) and your name when it gives one), which video you asked about, and whether your subscription is active. The video's audio is transcribed and summarised by Google Cloud Vertex AI on our servers; Google does not use that content to train its models, and neither do we. We keep transcripts and notes against the video, so the next person who asks about the same video gets a cached answer instead of a fresh transcription. We do not read your browsing history, we run no ads inside Tildew and no third-party analytics (our own pages, the extension's side panel and the app's screens send a few named events to our own server, described in section 13; the app also sends crash reports from release builds through Google Firebase Crashlytics, described in “The Tildew app”), we never see your card details, and we do not sell your personal data. If you arrive from one of our Google ads and press Allow, we tell Google Ads when that visit leads to a Chrome Web Store click or a purchase (section 13). You can delete your account yourself at tildew.com/account/delete, or email privacy@tildew.com and we will do it.

1. Who we are

Tildew is a product of MZEUS LABS LLP, a limited liability partnership registered in India. MZEUS LABS LLP is the data controller (under India's Digital Personal Data Protection Act 2023, the "data fiduciary") for the personal data described here.

For anything in this policy, write to privacy@tildew.com. That address reaches the people who can actually act on your request.

2. What Tildew does

Tildew has a single purpose: it takes the public YouTube video you are currently watching and produces a transcript and typed, timestamped notes in Chrome's side panel.

Tildew acts only on the video you explicitly ask about. It does not watch your tabs in the background, does not build a history of what you browse, and does not read the captions or transcript panel on the YouTube page. It works on public YouTube videos.

New accounts may receive a free allowance of credits, which may be one-time or may refill each month; everything beyond it is a paid subscription, billed monthly or yearly.

3. Data we collect and why

The table below is the complete list. If a kind of data is not in this table, we do not collect it.

DataWhy we have itLegal basis (GDPR / UK GDPR)How long we keep it
Google account identity — your Google user id, your email address, and your display name if your Google profile provides one. Collected when you sign in with Google; exchanged for a Tildew sign-in session. To create and recognise your account, tie your subscription and usage limits to you, and let you sign in on another machine. Your consent when you choose to sign in, and performance of our contract with you (we cannot run a paid account without an account). While your account exists. When you delete your account we delete the name, email and picture; a record that the account was deleted, and when, stays (section 7).
Apple account identity — only if you choose Sign in with Apple: the Apple user id Apple gives Tildew, the email address Apple shares (your own address, or a private relay address ending in privaterelay.appleid.com if you choose Hide My Email), and your name, which Apple sends only the first time you sign in and only if you share it. Apple gives Tildew no picture. We also keep the token Apple issues at sign-in, for one purpose only: to tell Apple to end Tildew’s access when you delete your account. Exchanged for a Tildew sign-in session, like a Google sign-in. To create and recognise your account, tie your subscription and usage limits to you, and let you sign in on another device. Your consent when you choose to sign in, and performance of our contract with you. While your account exists. When you delete your account we ask Apple to end Tildew’s access, then delete the email, the name and Apple’s token, and the link from your Apple user id to your account. If you created your account with Sign in with Apple, your account id is built from your Apple user id, so the deletion record and any purchase records keep it (section 7).
Sign-in links — which sign-in (Google or Apple, by that provider’s user id) leads to which Tildew account, and a one-way hash of an email address used to recognise the same Gmail address. If Apple and Google report the same verified Gmail address (using the same Gmail address with both), we may link them into one Tildew account (unless that address already belongs to more than one Tildew account). Other addresses, including Apple’s private relay addresses, are never linked automatically: they get their own account. So the same person reaches the same account in the extension and on the website, with one free allowance. Performance of our contract with you. While your account exists. When you delete your account we delete your sign-in links and Apple’s sign-in token. What stays after deletion is listed in section 7: it is not all deleted.
The public video you ask about — its YouTube video id, title, channel, duration and YouTube category. The title, channel, duration and category are fetched from the YouTube Data API using the video id. To fetch and transcribe the right video, to choose sensible note formatting for the kind of video it is, and to cache results so the same video is not processed twice. Performance of our contract with you. See section 7. The video-metadata cache has no automatic expiry today.
Your choices — the mode you picked and the language you asked for. To produce the notes you actually asked for. Performance of our contract with you. With the job record, and in your account settings while your account exists.
Credit balance — how many credits your plan granted this period, how many are in use, and when the period renews. To enforce your plan's limits fairly and to spot abuse. Performance of our contract with you, and our legitimate interest in preventing abuse of the service. While your account exists.
Subscription record — status, plan, and the end of the current billing period, received from Paddle. To know whether your subscription is active and which plan you are on. Performance of our contract with you, and our legal obligation to keep accounting records. While your account exists, and afterwards where we need it for accounting and tax records.
App store purchase record — when you buy in the Tildew app: the store's transaction or order id (on Google Play, also its purchase token), the product, the storefront country, the price and currency (Apple), the renewal date and whether it renews, and a random purchase code we create for your account (so the store can tell us which account bought). To give you what you bought, to keep one plan per account, and to handle refunds. Performance of our contract with you, and our legal obligation to keep accounting records. Kept as purchase records, with your account's identifier, for as long as we need them for billing, refunds and fraud prevention — also after you delete your account. The link from the purchase code to your account is kept permanently, so that a purchase can never move to another account and a later charge on a deleted account can never be credited to anyone. Nothing else of the account is kept with them.
Ad click id — only if you arrive from our Google ad and press Allow. To tell Google Ads when an ad visit leads to a Chrome Web Store click or a purchase, so we can measure our ads. Your consent (the Allow button). You can withdraw it at any time (section 13). Kept in your browser up to 89 days; sent to us when you click through to the Chrome Web Store or open checkout; we keep it up to 100 days. A Web Store click record is not linked to any account. A purchase record is linked to your account through the Paddle transaction id, and is deleted when you delete your account. “Off” (section 13) stops every upload that has not happened yet and forgets the id in your browser; clearing tildew.com’s site data only forgets it in your browser. To have a record erased sooner, email privacy@tildew.com.
Server request logs — IP address, user agent and timestamps, recorded by Google Cloud Run when your browser, the extension or the Tildew app calls our API (including the usage events tildew.com and the app send). Operations and debugging, security, and rate limiting. Our legitimate interest in keeping the service running, secure and not abused. Under Google Cloud's logging retention for our project; these are operational logs, not a profile of you.
Transcripts and notes — produced from the video's audio. To give you the output you asked for, and to serve the same video from cache next time. Performance of our contract with you. See section 7.
Extension-side data — your session and recent results, held in the extension's storage in Chrome, keyed to your account. To keep the side panel working while you use it, without re-fetching everything. Performance of our contract with you. Your session is cleared when you sign out; which sign-in you used last stays (section 7).
Usage events on tildew.com and in the side panel — the event name (for example card_open or summarize_click), the page template (for example /library, or panel for the extension's side panel), and at most: view (grid/list), notes mode, language, video type, filter, sort, tab, a bucketed count, purchase kind, plan, whether the browser is desktop Chrome, and whether the visit holds an allowed ad click id (a yes/no, never the id; sent with the landing_view and store_click events); in the side panel also which screen it shows (sign-in, free credits, plans or the main panel), whether a YouTube video is open (a yes/no), whether your credits cover the video, which copy or export format you used, and the code of an error message it showed. The side panel also sends the extension’s version number (for example 0.6.2) with each event; the website does not. On every page and in the side panel we also record page views, which named button you pressed (for example demo_play), the kind of place a link leads to (for example youtube or terms, never the address itself), how far down a page you scrolled (25, 50, 75 or 100%), and which summary mode or language you switched to. Never a video, a title, what you typed, an id, your IP address or your browser details. To see which pages and buttons are used and fix what is confusing. Our legitimate interest in understanding and improving how the site is used. 90 days.
Usage events in the Tildew app — the same kind as the row above, from the app’s screens: the event name, the screen (for example app/library), and at most which button you pressed, the kind of place a link leads to, which tab of a note you switched to, which notes language you chose, which notes mode you picked (Quick, Detailed or Deep), what the time line under Summarize said (for example need_credits), the short error code when a summary could not be made, the sign-in provider and a short outcome code, the name of the place in the app where an error was handled, whether it runs on iPhone or Android, and the app’s own version number (for example 0.1.0). Never a video, a title, what you typed, an id, your IP address or your device model, system version or any identifier. To see which screens and buttons are used and fix what is confusing or broken. Our legitimate interest in understanding and improving how the app is used. 90 days.
Crash reports from the Tildew app — the device model, operating system version and app version, the stack trace, the type of error, the phone’s state at the moment of the crash (for example free memory and storage), the place in the app where a handled error happened, the last few screens and buttons from the row above, and a random installation identifier Google Firebase creates for this installation of the app. The app’s own error messages are removed on your phone (for a crash inside the phone’s system software, the system’s own short description of the crash is kept); your name, email address and account id are never included. While crash reporting is on, Firebase also records a small session event each time the app starts (the time, the installation identifier and the same device and app details), which it uses to count crash-free sessions. To find and fix crashes and errors in the app. Our legitimate interest in keeping the app working. 90 days, then deleted by Google Firebase Crashlytics.
Notifications from the Tildew app — if you allow notifications, the address Google Firebase Cloud Messaging gives your phone for this app (a push token), whether it is an iPhone or Android phone, which Tildew account and sign-in it belongs to, a random code we make when an account and sign-in first register this phone (a new one whenever a different account or sign-in registers it, so a phone shows only notifications for whoever is signed in now), and when it was last sent to us. A notification itself carries only the number of the summary job, whether it finished or failed, and that random code: never a video, a title or any notes. To tell you when a summary is ready or could not be finished. Performance of our contract with you (the service you asked for), and your consent to notifications, which you can withdraw in your phone’s settings at any time. Until you sign out (or shortly after, if removing it then fails), delete your account or turn notifications off for Tildew (the app removes it at its next start), and otherwise about 60 days after the app last sent it.
Free allowance. To give the free allowance fairly, we store a one-way keyed hash of your Google or Apple account identifier together with an identifier of the current free period, the end date of that period, the day of the month it renews, the date a free allowance was first claimed, whether the account has ever had a paid subscription or tester access, whether free use was blocked for misuse, and how many of your first summaries were delivered. This means the free allowance is given at most once per period per account, is not given to accounts that have paid, and deleting and recreating an account does not give a second free allowance in the same period. We check it when you sign in or start a summary. The hash contains no name or email and cannot be linked back to you without a secret key only Tildew holds. We keep it after you delete your account, for this purpose only. When a free allowance is first claimed, we count first claims per network for one day, using a keyed hash of your IP address that changes every day; it is deleted after two days and the IP address itself is never stored. The extension also creates a random browser ID, and the Tildew app a random installation number; we keep only a keyed hash of it, so a free allowance can be claimed only once per browser or app installation. It is used for nothing else. To limit the free allowance to once per period per account, a limited number of first claims per network per day, and, for the first claim, once per browser or app installation. Our legitimate interest in preventing abuse of a promotional offer. See section 7.

We do not collect your browsing history, the contents of other tabs, your location, your contacts, or any special category data. We do not ask for your age, and we do not serve age-gated content.

4. How the notes are made (AI processing)

When you ask for notes, our servers fetch the public video's audio and send it to Google Cloud Vertex AI (Gemini models) to be transcribed and summarised. This happens under Google Cloud's data-processing terms. Google does not use customer data submitted to Vertex AI to train its models. We do not train any model on your content either.

Transcripts, notes and the video-type classification are stored keyed to the video, not to you. That is why a video someone has already processed comes back quickly. A separate, per-user record links your account to the job you requested, so we can show you your own history and count your usage.

There is no automated decision-making that produces legal effects or similarly significant effects on you. The AI writes notes; it does not decide anything about you.

5. Sharing and sub-processors

We do not sell personal data. We share it for advertising in one case only: ad measurement, described after the table. We do not hand it to data brokers. Apart from that, the only third parties that touch it are the service providers below (each acting on our instructions) and the sign-in provider you choose, Google or Apple, which acts under its own terms.

ProviderWhat it does for TildewWhat it sees
Google — Google sign-inVerifies who you are when you sign inYour Google user id, email address and display name
Apple — Sign in with AppleVerifies who you are when you choose Sign in with Apple, tells us if you stop using it with Tildew or change email forwarding for a Hide My Email address, and ends Tildew’s access when you delete your accountThe Apple user id, the email address Apple shares, your name (first sign-in only), and the token Apple issued to Tildew when we ask Apple to end that access
Google — Cloud RunRuns the Tildew APIRequest logs: IP address, user agent, timestamps
Google — FirestoreStores accounts, jobs, notes, counters and subscription recordsEverything in the table in section 3, except card data
Google — Cloud StorageStores audio and transcript artefacts during and after processingAudio and transcript chunks
Google — Cloud TasksQueues the transcription and summarisation workJob identifiers
Google — Vertex AI (Gemini)Transcribes and summarises the videoThe video's audio and the resulting text
Google — YouTube Data APIReturns the video's title, channel, duration and categoryThe video id we ask about
Google — YouTube image server (i.ytimg.com)Shows the video's thumbnail on a PDF you export, the still frame on the demo video, and the example episode's thumbnail on the tildew.com home page. Your browser fetches it directly, the same way the YouTube page does; Tildew's servers are not involvedThe video id, as part of the image address
Google — YouTube player (youtube-nocookie.com)Plays the Tildew demo video on tildew.com. It loads only when you press play on it; before that, nothing from the player has reached your browserThat you played that video, and what YouTube's player normally records: your IP address, your browser, and storage it sets in your browser for playback
Google — Firebase CrashlyticsCollects crash reports and session-start events from the Tildew app on iPhone and AndroidThe crash reports described in section 3: device model, operating system and app version, stack trace and an installation identifier; never your name, email address or account id
Google — Firebase Cloud MessagingDelivers the Tildew app’s notifications (on iPhone through Apple’s push service)The push token and the notification: the summary job’s number and whether it finished or failed
Apple — Apple Push Notification serviceShows the Tildew app’s notifications on an iPhoneThe same notification, addressed to your iPhone
PaddleMerchant of record: takes payment and manages your subscriptionYour billing details and card data, which it collects directly. Card data never reaches Tildew. Paddle tells us your subscription status, plan and period end.
Apple and GoogleApp Store and Google Play: take payment for purchases made in the Tildew appYour payment details stay with them. They tell us what was bought, when it renews and whether it was refunded.
Chrome Web Store (Google)Distributes and updates the extensionWhatever the Web Store records about installs; we do not receive your identity from it

We may also disclose data if the law requires it, or to establish or defend legal claims, or if the business is sold or merged — in which case this policy travels with the data and we will tell you.

Google Ads (ad measurement). If you arrive from one of our Google ads and press Allow, Google Ads receives, as an independent controller under Google’s own controller–controller terms, the ad click id, the time, and for a purchase its amount, currency and Paddle transaction id. It does not receive your name, email address or account id. Section 13 explains how to turn this off.

There are no advertising SDKs and no third-party trackers inside the extension or the app. The only part of the app that collects data about how the app runs is Google Firebase Crashlytics, with the Firebase components it needs (installations and sessions). Sign-in uses Google’s and Apple’s sign-in SDKs (see “The Tildew app” below), and Firebase Cloud Messaging delivers its notifications.

6. International transfers

MZEUS LABS LLP is in India. Tildew runs on Google Cloud in the project tildew-prod. Our own servers and stored data sit in the asia-south1 region (Mumbai, India). Five things are not pinned to that region: the Vertex AI model that listens to the video runs on Google's global endpoint, the YouTube Data API and Google Sign-In are global Google services, Sign in with Apple is a global Apple service, Google Firebase Crashlytics (the app’s crash reports and session-start events) is a global Firebase service that may process data in any Google data-center location, and Google Firebase Cloud Messaging and Apple’s push notification service, which deliver the app’s notifications, are global services.

If you are outside India, your data will be processed in India and, for the global Google services above, potentially elsewhere in Google's infrastructure. Those transfers rely on Google's standard contractual terms for its cloud services, including the standard contractual clauses where they apply. Sign in with Apple is a service you use directly with Apple, under Apple’s own terms and privacy policy.

7. Retention

Here is what is true today. Some of these numbers are operational settings and may change as the product changes; when they do, we will update this page.

  • Your library (the transcripts and notes you paid for): kept until you delete them or delete your account.
  • App-side data: on your phone the app keeps your sign-in session in the system’s secure storage (in the iPhone Keychain; on Android encrypted with a key kept in the Android Keystore) and clears it when you sign out; it keeps a copy of your library list and of the notes and transcripts of the last 50 summaries you opened, so they open without a connection, deleted when you sign out or, after you delete your account, the next time the app connects to our server; it remembers which sign-in button you used last (no account data), the notes language you last chose, whether you have seen the introduction, and that the app has been opened on this phone before; it keeps a random installation number, sent when an account claims its free time (as the extension’s browser number is), in the system’s secure storage on iPhone and in the app’s storage on Android; it is kept after you sign out, and on iPhone even after you delete the app, so a second account on the same phone cannot claim free time again; from the moment you press Summarize, it keeps, under your account’s user id, a random number for that press, the summary’s job number once our server gives one, the video it is for and its length, the mode and language you chose, the most credits it may use, whether music was allowed, and when you pressed; this is removed as soon as the notes are ready (they are then in your library), when you dismiss a summary that failed, or when you sign out; a press that our server refuses because your account is already running its maximum number of summaries is kept on the phone, with the same details plus the video’s title when we know it, until it starts, you cancel or dismiss it, you sign out, or 24 hours have passed; a summary you started elsewhere (in the Chrome extension) is shown while it runs but never kept on the phone; a press whose answer never arrived is not sent again on its own after 10 minutes (only if you press Try again) and is removed the next time the app reads this list after that; on iPhone, what you share to Tildew from another app waits, with the time you shared it, in storage shared only between Tildew and its share sheet until Tildew is next open; if it holds a YouTube video link, the app then keeps only that video’s link and the time it was saved, also after you close the app, until it fills it into Summarize or you sign out (a link saved more than a day earlier is dropped instead of used the next time the app starts), and drops everything else; on Android, a YouTube video link you share to Tildew is kept as that link only, in the app’s saved state, until the app fills it into Summarize, you sign out, or Android discards the app’s state; like other apps, it also lets iPhone and Android keep the state of its screens (which tab and which summary were open, what you typed in Search) so they look the same when you come back, and it keeps copies of the video pictures it has shown (YouTube’s thumbnails) in a cache the system may clear; whether the app has asked you about notifications (so it asks only once), and, while notifications are on and you are signed in, the random code of this phone’s current registration, with the account and the sign-in it belongs to (a one-way fingerprint of the sign-in, never the sign-in itself; see “Notifications”); nothing else.
  • Job records: expire automatically 30 days after the job is created.
  • Transcript chunks (the pieces a transcript is assembled from): expire after 7 days.
  • The stored transcript file itself: deleted by the storage bucket's own 180-day lifecycle.
  • Cached transcript versions, cached notes and video-type classifications: expire after 175 days.
  • The video-metadata cache: no automatic expiry today. It is keyed to the video rather than to you. We may add an expiry later; if we do, this page will say so.
  • Spend and accounting ledgers (what a job cost us to run): 30 days.
  • Usage counters: kept while your account exists.
  • Usage events (which page, which button): 90 days. The daily copies we analyse are rebuilt from those events and deleted within three days, so no copy outlives an event by more than three days.
  • Crash reports from the Tildew app: 90 days, kept by Google Firebase Crashlytics. They are not linked to your account, so deleting the account cannot remove them; they expire on their own after 90 days.
  • Push tokens (if you allow notifications): until you sign out (or shortly after, if removing it then fails), delete your account or turn notifications off for Tildew, and otherwise about 60 days after the app last registered.
  • Subscription record: kept while your account exists, and afterwards where accounting and tax rules require it.
  • Purchase and refund records: eight years after the transaction, as required by Indian company and tax law.
  • App store purchase records (purchases in the Tildew app): for as long as we need them for billing, refunds and fraud prevention, also after you delete your account. The link from a purchase code to the account it belongs to is kept permanently (see “When you delete your account” below).
  • Ad measurement records (adConversions): 100 days. A purchase record is also deleted when you delete your account. Withdrawal records (adRevocations): 100 days.
  • Extension-side data in the extension’s storage in Chrome: your session is cleared when you sign out. The extension also remembers on this computer whether you last signed in with Google or Apple, only to show that button first; it names no account and stays after sign-out until you remove the extension.
  • Apple notices: Apple tells us when you stop using Sign in with Apple with Tildew, delete your Apple Account, or turn email forwarding to a Hide My Email address off or on. We keep each notice, with your Apple user id, for 90 days, and note on your sign-in link whether forwarding is on.
  • Server request logs: kept under Google Cloud's logging retention for our project, for operations, security and rate limiting.
  • Free-allowance hashes (section 3): the account hash (and, where a Google and an Apple sign-in were linked, a record that their two hashes share one free allowance) and its free-allowance record (an identifier of the current free period, period end date, renewal day, the date of the first claim, paid or tester status, misuse flag and delivered-summary count) are kept even after you delete your account, for this purpose only; the daily network hash is deleted after two days; the browser-ID hash is kept for as long as it is used for this purpose.

When you delete your account (at tildew.com/account/delete, or by email):

  • Deleted, usually within a few minutes: your profile (name, picture, email), your library and every notes document, your transcript copies, sessions, your sign-in links and Apple’s sign-in token (we first ask Apple to end Tildew’s access), listen windows, unused credits (including credits you bought; they are not refunded), and job records.
  • Kept without any link to you: the shared transcripts and notes for the videos themselves (they carry no user identity and other customers may be using them), and the spend ledgers of your past jobs with your account id removed, until their normal 30-day expiry.
  • Kept as financial records: purchase and refund records, whether we billed you through Paddle or you bought through Apple or Google in the Tildew app, for at least eight years as Indian company and tax law requires, and for as long as we need them for billing, refunds and fraud prevention; they are used for nothing else.
  • Kept as a record of the deletion: that this account was deleted, and when, under its account id (built from your Google or Apple user id) — no name, email or picture — so a late payment notice for the old account can be recognised and never grants anything.
  • Also kept after deletion, for sign-in safety (not everything about your sign-ins is deleted):
    • A record that you stopped using Sign in with Apple with Tildew or deleted your Apple Account, keyed by your Apple user id (a time and a counter: no email, no token), kept with no expiry so an old sign-in can never be replayed
    • Apple’s notices about your Apple account, for 90 days
    • A one-way hash of an email address that more than one account claimed (never the address itself), kept with no expiry so that address is never linked automatically again
  • Also kept after deletion, for purchases in the Tildew app: the store purchase records described in section 3, and the link from your account’s random purchase code to the deleted account id, kept permanently so that a purchase can never move to another account and a later app store charge on the deleted account is never credited to anyone.

8. Security

  • All traffic between the extension, our API and our providers runs over TLS.
  • Our services run under least-privilege service accounts: each one can reach only what it needs.
  • No client — including the extension in your browser — can read or write our database directly. Everything goes through our API, which checks your session first.
  • Secrets and API keys live in Google Secret Manager, not in code or in the extension.

No system is perfectly secure, and we will not pretend otherwise. If a breach affects your personal data, we will notify you and the relevant authorities as the law requires.

9. Your rights

Depending on where you live, you have some or all of the rights below. We apply them to everyone as far as we practically can, whether or not your local law grants them.

  • Access — ask what we hold about you. Email privacy@tildew.com.
  • Rectification — ask us to correct data that is wrong. Your name and email come from your Google or Apple account, so correcting them there is usually fastest; email us if something is still wrong.
  • Erasure — delete your account and the data tied to it: do it yourself at tildew.com/account/delete (it asks you to sign in once more with Google or Apple, whichever your account uses), or email privacy@tildew.com from the address you signed in with. If you use Apple’s Hide My Email, email us from any address and tell us the relay address; we confirm through it. Either way we confirm when it is done.
  • Crash reports from the app — these are not linked to your account, so erasing the account cannot remove them; they expire after 90 days.
  • Restriction — ask us to stop processing while a dispute is sorted out. Email us.
  • Portability — you can export your notes yourself using the export buttons in the extension. For anything else, email us.
  • Objection — object to processing we base on legitimate interests (security, abuse prevention). Email us and tell us why.
  • Withdraw consent — sign out in the extension. If you use Sign in with Apple, you can also stop using it with Tildew from the Sign in with Apple settings of your Apple Account (on your iPhone, iPad or Mac, or at account.apple.com): Apple then tells us, and every Tildew sign-in session from that Apple sign-in ends. Your Tildew account and library stay until you delete them. Signing out ends your session on that machine. Ad measurement is withdrawn separately, with the On/Off control in section 13 on tildew.com (signing out of the extension cannot clear the website’s storage). Withdrawing consent does not undo processing that already happened.
  • Complain — you can complain to your data protection supervisory authority. In the UK that is the Information Commissioner's Office; in the EU it is your national authority; in India it is the Data Protection Board of India.

We will respond to a request within the time your law allows, and within one month where GDPR or UK GDPR applies. We may need to confirm that the request really comes from you.

California (CCPA/CPRA): we do not sell personal information and we do not share it for cross-context behavioural advertising. We have not done so in the past twelve months. There is nothing to opt out of, and we will not discriminate against you for exercising any privacy right.

10. Children

Tildew is not directed at children and is not intended for anyone under 18. We do not knowingly collect personal data from children. Tildew is a paid product behind a Google or Apple sign-in. If you believe a child has given us personal data, email privacy@tildew.com and we will delete it.

11. Chrome permissions and the Web Store policies

Tildew's use of the data it collects complies with the Chrome Web Store User Data Policy, including the Limited Use requirements for data from your Google account (sign-in). Website purchase data is not Google user data. In plain terms: we collect only what the stated single purpose needs, we use it only to provide and improve that single purpose for you, we do not transfer it except to the providers listed in section 5 and where the law requires, we do not sell it, and we do not use it for advertising, creditworthiness or lending.

Tildew's single purpose is stated in section 2: turning the public YouTube video you are watching into a transcript and timestamped notes in the side panel.

The extension asks only for the permissions that purpose needs:

  • sidePanel — to show the notes in Chrome's side panel, which is where the product lives.
  • storage — to hold your session and current results, keyed to your account and cleared on sign-out, and to remember whether you last signed in with Google or Apple.
  • identity — to run the Google or Apple sign-in that creates your account.
  • scripting — to read the id of the video you are on so we know which video you are asking about.
  • Host permission for youtube.com — so the extension can work on the YouTube page you are watching, and nowhere else.
  • Host permission for the Tildew API — so the extension can talk to our own servers.

We do not request permissions for other sites, and the extension does not act on pages outside YouTube.

12. Payments

Paddle is the merchant of record for Tildew subscriptions. When you subscribe, Paddle collects your payment details and handles the transaction, refunds and any tax. Your card number never reaches Tildew's servers and we could not retrieve it if we wanted to.

What we receive back from Paddle is limited: whether your subscription is active, which plan you are on, and when the current period ends. Paddle processes your payment data as its own controller under its own privacy policy, so please read that too.

If you delete your Tildew account, Paddle keeps its own customer record (your email and invoices) under Paddle's policy; we keep the purchase and refund records described in section 7.

Purchases in the Tildew app are made through Apple or Google, which act as their own controllers for the payment under their own privacy policies; we receive only the purchase record described in section 3.

13. Cookies and tracking

The extension sets no cookies. On the website and in the extension we use no third-party analytics and load no analytics script (in the app, Google Firebase Crashlytics collects crash reports — see “The Tildew app”). Our own pages, the extension's side panel and the Tildew app send a few named events (which page or screen, which button) to our own server so we can see what is used; they contain nothing that identifies you, and section 3 lists every field. The tildew.com website sets one cookie, __session, only after you sign in there: it keeps you signed in to your library and account pages and is used for nothing else. It is not a tracking cookie and no third party can read it. The extension keeps its own sign-in in Chrome's storage, not as a cookie. The demo video on tildew.com is a YouTube embed on its privacy-mode host (youtube-nocookie.com): it loads only if you press play, and from that point YouTube may set storage in your browser for playback, under Google's own privacy policy rather than ours.

If your browser sends Global Privacy Control, we treat it as “No”: we show no ad bar, store no ad click id and send none. If an id was already stored, we withdraw it and delete it. Do Not Track changes nothing, because we do not track you across sites.

Ad measurement

When you arrive from one of our Google ads, the address carries an ad click id (gclid, gbraid or wbraid). A small bar asks whether Tildew may tell Google Ads when that visit leads to a Chrome Web Store click or a purchase. The question is the same for every visitor, in every country.

  • Allow keeps the id in this browser’s own storage (the key is tw_adclick) for up to 89 days. If you click a Chrome Web Store link, or open checkout in this browser, we send the id to our server, which tells Google Ads. A newer ad visit replaces the id. Nothing is sent unless you pressed Allow.
  • No thanks stores nothing but your answer, and the bar stays away for 90 days.
  • We never send your name, email address, account id, IP address or browser details to Google Ads.
  • Global Privacy Control is honoured and treated as Off.

The Tildew app on iPhone and Android

The Tildew app shows the library, notes and transcripts of your Tildew account on your phone, and makes new summaries from a YouTube link you paste or share to it, exactly as the extension does. You sign in with Google or Apple, as in the extension, and everything in sections 3 to 9 applies to it. Five things are specific to the app.

Usage events. The app sends a few named events to our own server, the same kind the website and the extension send: which screen you opened, which button you pressed (for example reader_share), the kind of place a link leads to (for example youtube), which tab of a note you switched to, which notes language you chose, which notes mode you picked (Quick, Detailed or Deep), what the time line under Summarize said (for example need_credits), the short error code when a summary could not be made, whether a sign-in with Google or Apple finished, was cancelled or failed (with a short error code), the name of the place in the app where an error was handled (for example reader_load), whether it runs on iPhone or Android, and the app’s own version number (for example 0.1.0), so we can tell which release a problem comes from. Never a video, a title, what you typed, an id, your IP address or your device model, system version or any identifier. We keep them for 90 days (section 7). There is no advertising identifier, no tracking across other companies’ apps or websites, and no analytics SDK from anyone else in the app.

Crash reports. When the app crashes, or catches an error it can recover from, it sends a crash report to Google Firebase Crashlytics. A report holds the device model, the operating system version, the app version, the stack trace (which lines of the app’s code were running), the type of error, and the phone’s state at the moment of the crash (for example free memory and storage), the name of the place in the app where it happened, the names of the last few screens and buttons from the list above, and an installation identifier: a random number Firebase creates for this installation of the app, not linked to your Tildew account. The app removes the text of its own error messages (only fixed error codes are kept) before a report leaves your phone (for a crash inside the phone’s system software, the system’s own short description of the crash is kept), and never gives Crashlytics your name, email address or account id. While crash reporting is on, Firebase also sends a small session event each time the app starts (the time, the installation identifier and the same device and app details), which it uses to count crash-free sessions. Like any connection, a report reaches Google from your phone’s internet address. Builds made for development and debugging send no reports and no events. Builds you install from TestFlight or a Google Play testing track are release builds and do send them. Crash reports are kept for 90 days.

Purchases. In the app you subscribe or buy extra time through Apple (App Store) or Google (Google Play), never through our website. The store takes the payment and keeps your payment details; we receive only the purchase record described in section 3 (see also section 12).

Notifications. The first time you press Summarize, the app asks whether it may send you notifications. If you allow them, the app gives our server its push token so we can tell you when a summary is ready or could not be finished, also for summaries you started in the Chrome extension. A notification carries only the summary job’s number and whether it finished: the words you see are written by the app on your phone. We stop sending when you sign out, delete your account or turn Tildew’s notifications off in your phone’s settings. Builds made for development and debugging receive none.

Saved summaries. So that they open without a connection, the app keeps on your phone a copy of your library list (the titles, channels, lengths and picture links of your summaries) and the notes and transcripts of the last 50 summaries you opened, in the app’s own private storage, where other apps cannot read them, and never included in a backup. They are deleted when you sign out, and when you delete your account (the next time the app connects to our server).

14. Changes to this policy

If we change this policy, we will post the new version at this same address and update the effective date at the top. If a change is significant — new categories of data, a new purpose, a new kind of sharing — we will tell you in the extension or by email before it takes effect, where the law requires it. The date at the top always tells you which version you are reading.

15. Contact

MZEUS LABS LLP (a limited liability partnership registered in India)
Privacy contact: privacy@tildew.com

Write to us in plain language. You do not need to cite a law or use a form. Tell us what you want and which email address you signed in with, and we will take it from there.