Legal

Privacy Policy

Last updated: 9 November 2026

The short version. What you record with Earwig is yours. We hold it to run Earwig for you, you choose how long we keep it, and you can delete it at any time. We never sell your data, we never use your recordings or transcripts to train AI models, and we use no advertising trackers. Product analytics in the app stay off until you switch on Help improve Earwig. We do look at how you use Earwig (never what was said in your shoots) to decide which emails to send you, and this page explains exactly what that means. Private mode keeps a shoot on your phone.

Our two roles

Data protection law gives Earwig two different jobs, depending on whose data it is.

Business customers can read our data processing agreement on our DPA page. The companies that help us are listed on our sub-processors page and under Companies that help us below.

Who we are

Earwig is run by Harry Winteringham, a sole trader trading as HW Studio, based in the United Kingdom. For UK GDPR purposes, Harry Winteringham is the data controller for the data this policy describes as ours.

ICO registration number: ZC112104.

Data Protection Officer: we have not appointed a Data Protection Officer. Our privacy lead is Harry Winteringham.

Email: privacy@earwig.io

What we collect about you

This is the data about you as a customer. What you record is covered in the next section.

  • Your account. Your email address, for sign-in and to identify your account. If you sign in with Google, Google gives us your name, email address and profile identifier. If you sign in with Apple, Apple gives us your name and email address, or, if you choose Hide My Email, a private relay address that forwards to your inbox; that relay address is then your account email and we never see your real one. We never receive your Google or Apple password.
  • Your setup answers. The shoot types you pick on the "What do you film?" screen, the editing software you use (including anything you type for "Other") and the language you record in. We store them with your account to set Earwig up for how you work, to choose which help and emails are useful to you, and to understand who uses Earwig.
  • Your marker buttons. The names you give your marker buttons, and which buttons you use, so they appear on your markers and in your exports, including in Earwig Sync.
  • Your account activity. A record of your shoots (when, how long, how many moments you marked), when you last used Earwig, and when you last opened a shoot in your editing software through Earwig Sync. We need this to run your plan and minutes, show you your history and help you when something goes wrong, and we also use it to choose which emails to send you (see How we choose the emails we send you). Because it is part of running your account, it is kept whatever your Help improve Earwig setting. It never includes what was said in your shoots.
  • Product analytics (Help improve Earwig). Which screens and features you use, how long sessions last, and counts of crashes and freezes from Apple's diagnostics. For your account these are recorded only if you switch on Settings → “Help improve Earwig”, which is off until you choose it. We keep them on our own servers and send them to our analytics provider, PostHog. Switch it off and we stop recording them for your account. While it is on we also keep some details that help us improve Earwig: the questions and goals you write for a shoot (up to 500 characters each), which of your markers ended up in the finished edit, whether you kept or dismissed markers Earwig suggested, and the conditions of each shoot (phone model, battery level, type of microphone, number of speakers and language).
  • Before you have an account. While you go through the app's first screens, it sends a few events (which screens you saw, and the shoot types you pick) under a random id that is made when the app opens and forgotten when it closes. On its own it is not linked to your name, your email or any lasting device id. We keep these events on our own servers and send them to our analytics provider, PostHog. If you then create an account and switch on Help improve Earwig, they are joined to that account; if you do not, they stay unlinked. Our server also counts views of a few web pages (gift and share-code links and some Field Notes pages) and sends those counts to PostHog. They carry no cookie and nothing that identifies you.
  • Records of what you agreed to. When you agree to our Terms or to the "Before you record with Earwig" screen, we keep which wording you agreed to and when, with your account id, the app version and a device identifier (on iPhone, Apple's per-vendor identifier; on the web, a random id kept in your browser; in Earwig Logger for Mac, a random id kept on your Mac). This is our evidence that you were told. The per-vendor identifier is not the advertising identifier and is never used for advertising or tracking.
  • Earwig Sync. When you sign in to the Earwig Sync app for DaVinci Resolve or Premiere Pro, or open the Sync web app, we record the time. With Help improve Earwig on, we also record which editor, the app version and the operating system, which of your markers were kept or cut in the edit, and each timeline build (which editor, how many timelines and the marker timecodes it used), and whether a download of Sync, or the link in a Sync set-up email you asked for, led to Sync being set up on your computer. With it off, downloads and link clicks are only counted, not linked to you.
  • Earwig Logger for Mac. The Logger listens to several microphones at once on a shoot. In its free mode the transcript and your notes stay on your Mac and we hold nothing from the shoot. With an Earwig account, each channel's audio is streamed to our live transcription provider (Speechmatics) as a phone recording is, and the transcript lines, channel names, markers, speaker names, tags and notes are stored with that shoot on your account. Channel summaries are made by sending each channel's recent lines, and the notes you have logged, to Anthropic. Keyword alerts run on your Mac. If you write a “watch for” note or a shoot brief, it is sent with the channel's name and recent lines to Anthropic for the channel summary. On a team log, each member's name, channel, shared selects and alerts are stored with the shoot; when a keyword is heard on a teammate's channel, the keyword and that line are sent to our server to alert them; and the “story so far” sends recent transcript to Anthropic and can be emailed to the team. When the Logger asks your phone to read the camera's timecode, we send your phone one push notification and keep the request in memory for ten minutes. The Logger has its own plan, paid through Stripe, and we record how many minutes of each channel were transcribed to meter it.
  • Payments. On the web, Stripe takes your payment; we never see your card. In the app, Apple takes your payment and we receive your subscription status and Apple's signed record of each purchase. When you open a payment screen or buy a plan or hours in the app, we keep a record of each step (the plan chosen, the result Apple reported, our check of Apple's receipt and Apple's own notice about the purchase), with your account id, Apple's transaction ids, the price and currency, so we can make sure every payment reaches your account. Whether you saw a payment screen and closed it is recorded only while Help improve Earwig is on.
  • Push notifications. When you are signed in, the app sends us your device's push token and whether you have allowed notifications, each time it opens. We use the token to send you service and product notifications through Apple's Push Notification service. If you have not allowed notifications, iOS does not show them. You can turn them off in iOS Settings. We do not use them for advertising.
  • Bluetooth and phone movement. To read timecode from a timecode box, the app listens for nearby Bluetooth signals; nothing from this is sent to us. If motion capture is switched on (it is off by default), a record of how the phone moved during a shoot is uploaded and stored with that shoot.
  • If we contact you about Earwig. We sometimes write to people who work in film and television to tell them about Earwig. For that we hold a name, company, email address and public Instagram name, taken from public sources or from you, and whether our email was opened. When someone signs up or asks to hear from us, we also keep a note of how useful Earwig is likely to be to them, and Anthropic may draft a message for Harry to send. We do this under our legitimate interests in finding customers. Tell us to stop at privacy@earwig.io and we will delete it.
  • Referral and share codes. Your share code contains your first name, which is shown on the page your code opens. When a friend joins with your code, we tell you their first name and whether they have filmed, because that is what unlocks your reward. When you share from the app, we record which app you shared to and where in Earwig you shared from.
  • Affiliate links. If you are an Earwig affiliate, your link page shows your first name and how many people joined, filmed and became paying customers through your link. Anyone you give that page's address to can see those counts, so keep it to yourself.
  • Things you tell us. Support messages and bug reports: your email, what you write, any shoot link you add, and the app version, device or editor. An Earwig Sync problem report also sends the last part of Sync's log, which can contain clip and folder names. If you dictate a message in the app, Apple's speech recognition turns it into text, on your phone where it can, otherwise on Apple's servers, and only the text reaches us. If you tell us why you are leaving, in the app or after cancelling with Apple, we keep the reason and anything you write. If you answer a trial feedback or pilot report form, we keep your answers.
  • The emails we send you. A copy of each email we send you (subject, text and when), whether it was delivered or bounced, and, for the emails where we can tell, whether it was opened or a link in it was used.

What we collect on our website

  • Early access, Friend of Earwig, the Android list, the free-Resolve waitlist and the newsletter. Your email address, which list you joined and, for Friend of Earwig, which phone you use. We add you to our email list (held by Resend) and may send a welcome email or an offer code.
  • An email address you type but do not send. On the Follow Earwig page and on gift links from a friend, the page sends us the email address as soon as you have typed a complete one, even if you do not press the button. We keep it for 30 days, never add it to a mailing list and never email it. It only tells us someone started and did not finish.
  • The savings calculator. Your email address and the figures you enter, so we can send you your report. We also keep your address in our list of contacts with the form it came from.
  • Support tickets and Earwig Sync bug reports. As under Things you tell us above. If you are signed in we link the ticket to your account. Tickets are emailed to Harry. Anthropic reads each one to sort it by topic and urgency and to draft a reply, which Harry reads and sends himself.
  • Ask Earwig. The question you type into the Ask Earwig chat is sent to Anthropic to write the answer. We do not store your question or the answer.
  • Production pilot applications. Your name, work email, company, role, the show or format, shoot days a month, number of shooters, edit suite and start date. These stay one-to-one: we do not add pilot applicants to our email list.
  • Booking a call. Your name, email and what you are shooting. The Calendly booking calendar loads only after you send this form; Calendly then receives your name and email and the time you pick, and tells us about the booking.
  • Team and production plans. If you buy a plan for your team, the email addresses of the people you add as members, and the plan details. Stripe handles the payment.
  • Blog comments. Your name, your comment and, if you give it, your email address (never shown publicly), plus a scrambled version of your IP address to stop spam.
  • The Marker game. The name you put on the leaderboard, your score, and a scrambled version of your IP address to stop flooding. If you claim a prize, your email address so we can send the code.
  • Competitions. See Competitions and content you submit.

Your shoots: recordings, transcripts and markers

We hold this content as your processor (see Our two roles).

  • Live transcription. While you record, your audio is streamed to Speechmatics (a UK company, ICO registered ZA137980) for real-time speech-to-text. Under our data processing agreement, anything Speechmatics holds is kept no longer than 7 days, used only to provide the service and never used to train AI models.
  • Audio recordings. At the end of a normal shoot the phone uploads the full recording, which we store on Cloudflare R2, tied to that shoot, so we can make the transcript, keep it in sync with your footage and let you play it back. No recording is uploaded for markers-only shoots, private shoots, or shoots that start when you have no transcription minutes left. If your minutes run out part way through a shoot, the phone carries on recording and that recording is still uploaded at the end.
  • Transcripts. Stored with your shoot as text, with word-level timings and, where available, speaker labels.
  • Markers, notes, briefs and questions. The moments you mark, your notes and labels, the brief and questions you prepare, which questions were asked, and the AI results made from them (titles, summaries, marker notes, fact-checks, suggested questions, Pickup Reports, selects and themes).
  • Video and subtitle files. If you use features that upload footage or make subtitles, those files are stored on Cloudflare R2 with your shoot. If you only log markers and never upload footage, no video is stored on our servers.
  • Sync timing data. A small amount of timing information so your transcript lines up with your footage. It is timing data, not a recording.

How it is protected. Transcript text and word timings are encrypted with AES-256-GCM before they are written to the database, using a key made for each user from a secret kept in our host's protected settings, apart from the database. Some shorter pieces of text from your shoots are stored without that extra layer, protected by the database's own encryption and access controls: the quote saved with each marker and the lines around it, quotes in selects and themes, AI summaries and Pickup Reports, and your question goals and debriefs. Recordings and media are reached only through links that expire within hours, made for you or the people you share with. Earwig decrypts your content to show it to you, to run the AI features you use and, if you ask us for support, to help with your account.

Private mode and shoots kept on your phone

Private mode. The shoot stays on your phone. The words are transcribed on your phone as they are said. The audio is not sent to us or to any transcription provider, and no recording of it is kept. Your markers, notes and transcript are saved on your phone only. None of our AI providers sees a private shoot. Your iPhone may use Apple's own on-device model to summarise it, which happens entirely on the phone.

What we still record. While Private mode is on, the app sends us no product-analytics events, apart from a single note that Private mode was switched on or off, so we can count how many people use it. That note contains nothing from your shoot.

Uploading is your choice. Nothing from a private shoot reaches our servers unless you save it to your account, or switch on "Upload private shoots automatically" in Settings. If it is uploaded we receive its markers, notes and transcript, never its audio, and from then on it is stored and protected like any other shoot.

No signal. If Earwig cannot reach our servers when you start a shoot, it keeps that shoot's markers and transcript on your phone, with the words transcribed on the phone, until you upload it. It uploads only when you ask, or if you have switched on automatic upload.

Deleting. Discarding a private shoot deletes it from your phone. A shoot that has not been uploaded exists only on your phone, so we cannot recover it if it is deleted or the phone is lost.

AI processing

Our AI provider is Anthropic (Claude). Under Anthropic's API terms, what we send can be kept for up to 30 days for safety review and is then deleted, and it is never used to train AI models. A data processing addendum covers it (see International data transfers).

With AI on for a shoot, Earwig sends that shoot's transcript, or parts of it, with your brief and questions, to Anthropic for: marker notes, the title and summary after each shoot, fact-checks (claims may be turned into web searches made through Anthropic), research, live question suggestions, Brief and Automarker, Pickup Reports, selects, themes and rough cuts. When Earwig Sync names your B-roll, it sends still frames from your footage with a short piece of the transcript around each one; the rest of your footage stays on your computer. If you ask the Earwig Sync app on a Mac to analyse footage, it takes the sound from each file and uploads it, with the file name and start timecode, to be transcribed by Speechmatics and marked by Anthropic, and it sends up to 60 still frames from each file to Anthropic; the video itself is not uploaded. In the web app's shoot page, if you turn the camera on with AI on, single frames from the camera are sent with recent transcript lines to write scene notes; the frames are not stored.

With AI off, or in Private mode, nothing from that shoot is sent to Anthropic, including the summary after the shoot.

Things you ask for directly use Anthropic whatever the AI setting: reading a brief or questions you type, dictate, photograph, screenshot or upload as a PDF (in the iPhone app, photos, screenshots and PDFs are read on your phone and only the text is sent; anywhere else, a picture of a brief you upload is sent to Anthropic to be read), reading a timecode from a photo in the web app, the Ask Earwig chat, and the guided first marker when you set up the app (the sentence you speak is used to write a short note and the next question, then discarded).

Wiggy learning your style. When you plan a shoot with Wiggy, it can include up to 12 sentences you said in earlier shoots so its questions sound like you.

How we use Anthropic to run Earwig. As controller, we also use Anthropic to sort support messages and draft replies (Harry reads and sends every reply himself), to write the weekly summary email we send you (your first name and the titles of that week's shoots), and to prepare a regular internal summary for Harry of accounts that may need help, which contains names, email addresses, plans and activity counts, never recordings or transcripts.

On your phone. Speech recognition in Private mode and for dictated messages uses Apple's speech recognition, and some summaries use Apple's on-device model. What runs on the phone stays on the phone.

We never use your recordings or transcripts to train AI models, ours or anyone else's.

How we choose the emails we send you

We use what we know about how you use Earwig to decide which emails to send you, when to send them and what to say, so they are about your own shoots rather than the same for everyone. In data protection terms this is profiling. It never sets your price, your plan or your access to Earwig.

What we use:

  • Your account: your first name, when you signed up, and the editing software, language and shoot types you told us.
  • Your plan, from Apple or Stripe: whether you are in a free trial or paying, when it renews or ends, whether renewal is on, and whether a payment failed.
  • Your account activity: the dates and lengths of your shoots, how many moments you marked, when you last used Earwig, and whether you have opened a shoot in your editing software.
  • Product analytics, only if you have switched on Help improve Earwig: whether you already use a feature, so we do not send you tips about it.
  • What you told us: the reason you gave if you told us why you were leaving, and replies to our emails.
  • The emails we have sent you: which ones, when, whether they were delivered and, where we can tell, opened.

What we never use for this: anything said in your recordings, your transcripts, your notes, the names of your shoots, or anything about the people you film. We do not buy data about you or look you up anywhere else.

How it works. Simple rules decide who gets which email: for example, when a payment fails, when your plan is about to end with renewal off, or when you have filmed but not yet opened the shoot in your edit. Some of these emails are sent automatically, and some include an offer, such as a discount or extra hours. To check the emails actually help, a share of people chosen at random do not get a particular email, and we compare what both groups do next.

Your choices. Emails with news and offers only reach you under the soft opt-in or your consent, as described in Legal basis for processing, and each one has an unsubscribe link. You can also object to this tailoring at any time by writing to privacy@earwig.io, and we will stop. Emails about your plan that you need, such as a failed payment, are not marketing and are not affected by unsubscribing.

Sharing your shoots

Live Share. When you share a shoot with a Live Share PIN, the people you share it with see the transcript as it happens. It mirrors your shoot and closes when the shoot ends; viewers keep no copy on our servers unless they have their own Earwig account and save it.

Sharing with your editor. You can invite another Earwig account by email, or send a share link with its PIN. Anyone you invite, or who opens the full link with its PIN and signs in, gets ongoing access to that shoot's markers, transcript and audio through their own account and Earwig Sync, until you remove them. Anyone with the link alone, without the PIN, can see the shoot's title, how many markers it has and a shortened form of your email address. You can see who has access, remove anyone, and reset the link and PIN from the shoot's Share panel.

Emails about your shoots. The emails we send you after a shoot, and any you ask us to send to your editor, contain what you marked: quotes, notes, summaries and files made from them. They pass through our email provider, Resend. Shoot emails you send to a client from your own email app go from your account, not ours.

You are responsible for making sure the people you share with may receive the content, including anything said by the people you recorded. If you need help removing someone's access, contact privacy@earwig.io.

The people you record

Special category data. Interviews can reveal things UK GDPR (Article 9) protects most closely: racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic or biometric data, health, and sex life or sexual orientation.

Your role and ours. For the people you record, you (or your production company) are the controller and Earwig is your processor. We process that content only on your instructions: to transcribe it, keep it in sync with your footage, store it, and run the AI features you use. We do not use it for anything else and we do not use it to train AI models.

Your responsibility. You need a lawful basis for recording, and, where it captures special category data, an Article 9 condition. In practice that usually means the explicit consent of the person you record, or the special purposes (journalism) exemption in the Data Protection Act 2018 where it genuinely applies. Tell the people you record that you are using Earwig, that the conversation is transcribed and, if you use AI features, processed by AI. Honour any request they make to have their words deleted. Before your first shoot Earwig asks you to confirm you understand this.

If you record in a medical, clinical or emergency services setting, more rules may apply. Check your organisation's data protection policy first.

If you have a concern about a recording that includes you, contact privacy@earwig.io and we will pass it to the person who recorded it.

Children

Who can use Earwig. Earwig is a professional tool for people aged 18 or over, as our Terms say. Children may not use it, including through an organisation. If we learn that an account belongs to someone under 18, we will close it and delete its data.

Children you film. If you record anyone under 18, for example in a school or care setting, you must record them with the Earwig phone app in Private mode and keep that shoot on your phone: do not upload it or send it to Earwig Sync. In Private mode the words are made on your phone and nothing is sent to us or our providers, so we never receive a child's voice or words. You (or your production company) are responsible for the consent of a parent or guardian and for safeguarding.

Competitions and content you submit

If you enter one of our competitions by sharing content you made or logged with Earwig, we collect the video or files you send and the contact details you give (such as your name and email or social handle). We use them only to run the competition (reviewing entries, and choosing and contacting winners) and, if you give us permission, to feature your entry with credit in our marketing. The legal basis is your consent, which you can withdraw at any time by emailing privacy@earwig.io. We keep entries as long as we need them to run the competition and, if you agreed to marketing use, as long as we feature them or until you ask us to stop.

Companies that help us

Third party

Speechmatics: live speech-to-text

Audio is streamed to Speechmatics for live transcription. Speechmatics is a UK company (Cambridge), ICO registered (ZA137980), certified to ISO 27001:2022 and SOC 2 Type II. Under our data processing agreement, which includes the ICO's UK Addendum to the EU Standard Contractual Clauses, anything Speechmatics holds is kept no longer than 7 days, used only to provide the service, and never used to train AI models.

speechmatics.com/legal/privacy-policy
Third party

Anthropic (Claude): AI features

Receives the text described under AI processing: transcript text and briefs for the AI features you use, support messages, and the account details in our internal summary. Under Anthropic's API terms, what we send can be kept for up to 30 days for safety review and is then deleted; it is never used to train AI models.

privacy.claude.com
Infrastructure

Render: application hosting and database

Our web service and database run on Render in Frankfurt (EU). Transcript text is encrypted before it is written to the database. The secret the keys come from is kept in Render's protected settings, apart from the database, so Render, as our host, could in principle reach it; Render does not look at customer data as part of its service.

render.com/privacy
Infrastructure

GitHub: scheduled jobs and backups

Some scheduled maintenance jobs, including the nightly database backup, run on GitHub-hosted machines. A backup is encrypted and passes through that machine on its way to our storage, which makes GitHub (part of Microsoft) a processor even though it is never the destination. The machine is destroyed after each run and keeps no copy.

GitHub privacy statement
Infrastructure

Cloudflare R2: media storage

Your recordings, and any uploaded video and subtitle files, are stored on Cloudflare R2 in Western Europe. They are reached only through links that expire within hours, made for you or the people you share with; there is no public or browsable index of your media. Files are deleted when you delete the shoot or your account, or automatically if you switch on footage auto-delete.

cloudflare.com/privacypolicy
Third party

Resend: email

Used for login emails, emails about your account and your shoots, internal notifications to our team about account activity such as a new sign-up, and, if you have chosen to hear from us, emails about Earwig itself: news, new features and offers. Every email with news or offers carries an unsubscribe link, and so do the emails about your shoots that you can turn off (the weekly summary, shoot reminders and replies to your comments). Unsubscribing never stops login codes, receipts or your shoot files. If you sign in with Apple's Hide My Email, we only ever hold the relay address Apple gives us. If you give us a different contact address (for example, to receive a download link), we store it against your account and treat it the same way; you can ask us to remove it at any time. Resend tells us whether each email was delivered or bounced and, for some emails, whether it was opened or a link in it was used.

resend.com/legal/privacy-policy
Third party

PostHog: product analytics

EU hosted (Frankfurt). Receives the product analytics described above: for your account, only while Help improve Earwig is on; in your browser, only if you choose Accept on our banner; and, without either, the anonymous first-screen events and page-view counts described under Before you have an account. Never used for advertising or cross-site tracking. We do not record your screen.

posthog.com/privacy
Third party

Stripe: web payments

Processes payments on the web. All card data is handled by Stripe; we never store or see it. Stripe may keep your email address and payment method for billing.

stripe.com/privacy
Third party

Apple: App Store, sign-in and notifications

Apple processes in-app purchases and manages billing, provides Sign in with Apple if you choose it, and delivers push notifications using your device's push token. Apple acts under its own privacy policy.

apple.com/legal/privacy
Third party

Google: optional sign-in

If you choose "Sign in with Google", Google shares your name, email address and profile identifier with us. We ask only for basic profile and email access.

policies.google.com/privacy
Third party

Calendly: booking a call

Loads only after you send the book-a-call form, and receives your name, email and the time you pick.

calendly.com/privacy

Providers used only for one feature. Meta (Instagram): if you connect an Instagram account to Earwig's Producer, Meta signs you in and we store your Instagram username and an access token, encrypted, to read your own posts and their figures. Pexels: when the Producer looks for stock footage, the search words are sent to Pexels; nothing about you is sent. ntfy: we send ourselves an alert when someone signs up, which contains a masked form of the email address.

Providers we test but do not use for your data. We use Soniox, a speech-to-text provider, only to compare transcription quality on Earwig's own recordings. Our code can also connect to other providers (Deepgram for speech-to-text, Google Gemini for video, ElevenLabs for voice), and these are switched off. We will not send your data to any of them without first updating this page and giving business customers notice.

International data transfers

Some of our providers process data outside the UK. Where they do, the transfer is covered by the safeguard below. We check the data bridge list at least once a year.

  • Speechmatics: UK company; live audio uses its EU endpoint. UK Addendum to the EU Standard Contractual Clauses.
  • Anthropic: our contract is with Anthropic Ireland, Limited (the EEA, which UK law treats as adequate); processing may take place in the United States under Anthropic's Data Processing Addendum, which includes the UK Addendum to the EU Standard Contractual Clauses.
  • Render: our web service and database run in Frankfurt (EU). Render Services, Inc. is a US company certified to the UK Extension to the EU-US Data Privacy Framework (the UK-US data bridge), with the UK Addendum as the fallback in its DPA.
  • Cloudflare (R2): files stored in Western Europe; Cloudflare, Inc. is a US company certified to the UK-US data bridge, with the UK Addendum as the fallback.
  • GitHub: United States. GitHub, Inc. is certified to the UK-US data bridge, and its DPA also applies the UK Addendum.
  • Resend: United States, used to send login, account and marketing emails. Resend is certified to the UK-US data bridge, and its DPA also applies the UK Addendum to the EU Standard Contractual Clauses.
  • Calendly: United States. Calendly LLC is certified to the UK-US data bridge, with the UK Addendum as the fallback.
  • PostHog: EU hosted (Frankfurt). PostHog, Inc. is also certified to the UK-US data bridge and applies the UK Addendum.
  • Google: United States, for optional sign-in. Google LLC is certified to the UK-US data bridge.
  • Stripe: Stripe, LLC in the United States receives payment data under the UK-US data bridge, with the UK International Data Transfer Addendum as the fallback.
  • Apple: United States, as an independent controller under Apple's own terms.

How long we keep it

  • Recordings, video and subtitle files. Until you delete the shoot or your account. If you switch on footage auto-delete, they are deleted automatically after 30 days.
  • Transcripts, word timings, speaker labels, markers, notes, briefs, questions and AI results (titles, summaries, marker notes, Pickup Reports, selects, themes). Kept with the shoot until you delete it or your account. Footage auto-delete removes the recording and media only: the transcript, markers and notes stay with the shoot, because they are the work you keep.
  • Deleted shoots. A deleted shoot goes to Recently deleted, where you can restore it for 30 days, and is then removed for good.
  • Streamed audio at Speechmatics. No longer than 7 days.
  • Private shoots on your phone. On your phone until you delete them. We hold nothing from a private shoot unless it is uploaded.
  • Live Share. Not stored separately; it exists only while the shoot is live.
  • Product-analytics events. On our own servers, 12 months from the event, then deleted automatically. PostHog keeps its copy for its own period, up to 7 years, which we cannot shorten. When you delete your account we delete ours and ask PostHog to delete theirs. The questions, goals, marker results and shoot conditions kept while Help improve Earwig is on are kept until you delete your account or ask us to remove them.
  • Support messages. 24 months after the last message on a ticket. Then your message, our reply and your email address are removed from our support records, and only the date and the kind of request are kept.
  • Payment step records. 24 months, or until you delete your account. Billing and tax records are kept as long as the law requires.
  • Your account, setup answers, account activity, the emails we sent you, leaving reasons and records of what you agreed to. Until you delete your account, except as below.
  • Email addresses typed but not sent. 30 days.
  • Marketing opt-outs: if you unsubscribe from our emails, turn off a kind of email, or tell us not to send you marketing, we keep your email address, with when and how you told us, on a list of people not to send marketing (or that kind of email) to. That includes an address entered on a sign-in screen with the "Don't email me news and offers" box ticked, whether or not the login code was used. We keep it for good, including after you delete your account, so that we never send you marketing again
  • Mailing-list sign-ups. If you join a mailing list on our website, we keep your address with the wording of the form, the page, and when you submitted it and confirmed it, until you unsubscribe (then as above). A sign-up nobody confirms is never used for news or offers, and the request to confirm it is deleted after 30 days. The page behind that email's link also has a button to stop these requests for good: we then keep the address only so that we never ask it again or send it news or offers. If you asked for a Friend of Earwig code on the Follow Earwig page, we also keep your address with that code, so it can be redeemed and your account can show you as a Friend, until you ask us to remove it
  • Codes and links you ask for: when we email you an offer code or a download link you asked for on our website or in the app, we keep a note that we sent it to your address for 30 days, so the same address is not sent it over and over. We also keep the address you entered in our list of contacts, with the form it came from, and an offer code stays recorded against the address it was given to, so it is never given out twice. Neither puts you on a mailing list. Both are kept until you ask us to remove them
  • The Android list: if you ask us to tell you when Earwig is on Android, we keep your address for that one email, and once it has gone a note that we sent it, so it never goes twice. Both are kept until you ask us to remove them. If any request not to email you is on record for the address, we send it no email about Android at all
  • Backups. Encrypted database backups are kept for up to 30 days, so something you delete can stay in a backup for up to 30 days after you delete it.
  • Server logs. Kept by our host for a limited period for security and fault-finding.

We never sell your data.

Cookies and browser storage

Earwig uses a few cookies and some browser storage. The ones below that run the service need no consent. Product analytics are optional: on the website we ask first, and load them only if you choose Accept. To change your choice, use Cookie settings.

  • sid: keeps you signed in. HttpOnly, SameSite=Lax, served over HTTPS.
  • oauth_state and mkt_bind: last 10 minutes while you sign in, to protect the sign-in and carry your email choice from the sign-in page.
  • mkt_ref: lasts 10 minutes while you sign in, to remember which Earwig offer or link brought you there.
  • ew_preview: lasts 7 days, and is set only if you open a preview link we gave you, so you can see a page before it is public.
  • foe_code: keeps a Friend of Earwig code you opened for 30 days, so it can be applied when you sign up.
  • ew_sync: set for 30 days when you use the link in an Earwig Sync set-up email, so the download that follows works for your computer. It is linked to your account only while Help improve Earwig is on.
  • Browser storage: your settings inside Earwig (theme, recording mode, transcription language, AI choices, export settings, prepared questions, recent screen state), your analytics choice, and on some pages the name, job and photo you entered, so they show without reloading. It stays in your browser; clearing your browser storage removes it.
  • Stripe sets its own cookies on its checkout page when you pay on the web. Calendly may set its own when the booking calendar loads.
  • PostHog, only if you accept: counts which pages and features are used. It keeps its identifiers in memory, so it sets no cookies. When you are signed in, events are linked to your Earwig account id. It does not record your screen or capture what you type.
  • No advertising cookies. No cross-site tracking.

Legal basis for processing (GDPR)

Under UK and EU GDPR, this is the legal basis for each thing we do with personal data as controller.

  • Your account and the service you signed up for. Your email, sign-in, shoots, recordings, transcripts, video and subtitle files, sync data, the AI features you use, sharing, emails about your account and shoots, and push notifications: contract (Art. 6(1)(b)). Switching AI on or off is a product choice, not consent.
  • The people you record. For interview content we act as your processor, so Earwig does not claim its own lawful basis for it. You, as controller, choose the basis and any Article 9 or Article 10 condition (see The people you record).
  • Setup answers and account activity. Our legitimate interests (Art. 6(1)(f)) in running and improving Earwig and setting it up for how you work.
  • Product analytics in the apps and Help improve Earwig. Only while you have switched Help improve Earwig on: consent (Art. 6(1)(a)), which you can withdraw in Settings at any time. This includes the Earwig Sync timeline builds and set-up links above.
  • Product analytics on the website. Only if you choose Accept on our banner: consent (Art. 6(1)(a)).
  • Onboarding analytics before you have an account (a random token made when the app opens and forgotten when it closes): our legitimate interests (Art. 6(1)(f)) in understanding how people first use the app.
  • The first-run onboarding demo (the sentence you speak, sent to Anthropic and then discarded): our legitimate interests (Art. 6(1)(f)) in showing you how Earwig works before you sign up.
  • Choosing and tailoring the emails we send you (see How we choose the emails we send you): our legitimate interests (Art. 6(1)(f)) in sending customers emails that are relevant to how they use Earwig and in keeping them as customers. For news and offers, the email itself also needs the soft opt-in or your consent, as below. You can object at any time and we will stop.
  • News and offers to customers. When you create an account, the sign-in screen offers a box: “Don’t email me Earwig news and offers”. If you tick it, we never send you news or offers. If you leave it unticked, we may email you news and offers about Earwig’s own products under the soft opt-in in the Privacy and Electronic Communications Regulations (regulation 22). Each of those emails has an unsubscribe link, and you can object at any time. Accounts that were never shown the box get no news or offers this way.
  • Email lists you join on our website (early access, Friend of Earwig, the Android list, the free-Resolve waitlist, the newsletter): consent (Art. 6(1)(a)), given when you join and confirm by pressing the button behind the link in the email we send to check the address (at most three such emails in 30 days, and none once you press the button on that page to stop them). We keep a record of when you joined, when you confirmed and what the form said. Accounts and mailing-list entries from before 10 October 2026 get no marketing emails unless you join a list again. You can withdraw your consent at any time with the unsubscribe link in any marketing email
  • Knowing whether our emails were opened or used. Our legitimate interests (Art. 6(1)(f)) in knowing your markers and the links you asked for arrived and worked.
  • Referral and affiliate codes. Contract (Art. 6(1)(b)): running the reward or affiliate scheme you joined.
  • Email addresses typed but not sent, and the savings calculator. Our legitimate interests (Art. 6(1)(f)) in knowing where people stop, and in sending the report you asked for.
  • Records of what you agreed to. Our legitimate interests (Art. 6(1)(f)) in being able to show you were told your duty to the people you record and agreed to our Terms.
  • Our internal summary of accounts. Our legitimate interests (Art. 6(1)(f)) in helping customers who are stuck.
  • Support tickets, Sync bug reports, leaving reasons and Ask Earwig. Contract (Art. 6(1)(b)) where you are a customer; otherwise our legitimate interests (Art. 6(1)(f)) in answering you and improving Earwig.
  • Pilot applications, booking a call and team plan enquiries. Steps you ask us to take before a contract (Art. 6(1)(b)), or our legitimate interests (Art. 6(1)(f)) in replying to you.
  • Blog comments, competitions and the Marker game prize. Consent (Art. 6(1)(a)).
  • Payments. Contract (Art. 6(1)(b)). Keeping billing and tax records: legal obligation (Art. 6(1)(c)). The record of each payment step in the app: contract, so that what you paid for reaches your account, and our legitimate interests (Art. 6(1)(f)) in checking our records against Apple’s.
  • Security, backups, preventing abuse and server logs. Our legitimate interests (Art. 6(1)(f)) in keeping Earwig safe and working.

Automated decisions. We do not make decisions about you based solely on automated processing that have legal or similarly significant effects. Rules do decide who is sent an email or an offer (see How we choose the emails we send you); an offer is an extra, and not getting one never changes your plan, price or access.

Your right to object to marketing. You can object to marketing at any time and we will stop. Use the unsubscribe link in any email from us with news or offers, or write to privacy@earwig.io. Unsubscribing does not stop login codes or receipts.

Your rights

You have the right to access your data, correct it, have it deleted, restrict or object to how we use it, and take it with you. Email privacy@earwig.io and we will respond within one month. Some things you can do yourself straight away:

  • Delete your account. In the iPhone app: Menu, then Settings, then Delete Account. On the website: your profile, then Delete account. This removes your recordings, video and subtitle files, transcripts and shoots, removes your phone's push token, and asks PostHog to delete your analytics. A few records stay: support messages you sent us, for the 24 months described under how long we keep things; records of codes you redeemed or shared; the date and length of past shoots, with your identity removed; payment transaction ids, so a purchase cannot be claimed twice; and your address on our do-not-email list if you unsubscribed. Deleting your account does not cancel an App Store subscription: cancel that in your Apple ID settings. Shoots saved only on your phone stay on the phone until you delete them there or remove the app.
  • Delete a shoot. Swipe left on it in the Earwigs tab of the iPhone app. This removes its recording, video, subtitle files and transcript after 30 days in Recently deleted.
  • Switch on footage auto-delete so recordings and media are removed after 30 days.
  • Export your transcripts, markers and AI results.
  • Turn off Help improve Earwig in Settings at any time.

Requests from authorities, breaches and changes

Requests from police, courts or governments. We hand over your data only when the law requires it, and we ask for the request in writing and check it is lawful and no wider than it must be. Unless the law forbids it, we tell you before we hand anything over, so you can challenge it. Recordings and transcripts may include journalistic material, and we treat any request for them on that basis.

If something goes wrong. If a breach puts your data at risk, we report it to the ICO within 72 hours where the law requires, and we tell you without undue delay if it is likely to put you at high risk. Business customers are told under the terms of their data processing agreement.

Changes to this policy. When we change this policy we update the date at the top. Before we add a company that will handle your recordings or transcripts, we update this page and the sub-processors page first, and we tell business customers in advance. If a change matters to how we use your data, we will email you.

California privacy rights (CCPA)

If you live in California, the California Consumer Privacy Act gives you the right to know what personal information we hold about you, to have it deleted, to opt out of its sale (we do not sell it), and not to be treated differently for using these rights.

Categories we collect: identifiers (email address, Google or Apple sign-in identifiers, account id, a per-vendor device identifier on records of what you agreed to, and a push token); commercial information (plan, purchases and payment records); audio and visual information (recordings, uploaded video and subtitle files); internet or other electronic activity (account activity, product analytics if you opt in, email delivery and opens); professional information (setup answers, transcripts and briefs); and inferences (which emails are likely to be useful to you).

We use it to provide Earwig, to support you and to send you emails as described above. We do not sell or share (as California law defines those terms) your personal information. Our service providers (Speechmatics, Anthropic, Render, Cloudflare, GitHub, Resend, PostHog, Stripe, Apple, Google and Calendly) receive it only to provide their service to us.

To make a request, email privacy@earwig.io. We will verify your identity and respond within 45 days.

How to complain

If you have a concern about how we use your personal data, please tell us first at privacy@earwig.io. We will acknowledge your complaint within 30 days.

If you are still unhappy, you can complain to the Information Commissioner's Office: Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF. Helpline 0303 123 1113. ico.org.uk/make-a-complaint

Frequently asked questions

Can Earwig access my transcripts?›
Your transcript text is encrypted with a key made for your account before it is written to our database, so a copy of the database on its own does not show it. Short pieces such as the quote saved with each marker and AI summaries are protected by the database's own encryption rather than that extra layer. Earwig's application decrypts your content to show it to you and to run the AI features you use, and authorised Earwig staff can reach it where needed to support you or restore a lost shoot. We never use it to train AI models, we never sell it, and you can delete it at any time.
Is my audio stored?›
In a normal shoot, yes. Earwig stores the recording on Cloudflare R2, tied to your account, so we can make the transcript, keep it in sync with your footage and let you play it back. While you record, the audio is also streamed to Speechmatics, which transcribes it and keeps nothing beyond at most 7 days. Your recording stays until you delete the shoot or your account, or, with footage auto-delete on, until it is removed automatically (30 days by default). Markers-only shoots upload no recording. In Private mode, no: the words are transcribed on your phone and the audio is not kept or sent anywhere.
Does Anthropic see my transcript content?›
Only when AI is on for that shoot. With AI on, Earwig sends the transcript, or parts of it, to Anthropic's Claude API for the AI features listed under AI processing. Anthropic does not use API data to train AI models. Turn AI off, or use Private mode, and nothing from that shoot is sent to Anthropic. A few things you ask for directly use Claude whatever the setting: reading a brief you give it, reading a timecode from a photo in the web app, the Ask Earwig chat and sorting support messages.
Do you use my data to decide which emails I get?›
Yes, how you use Earwig (your plan, when you filmed, whether you have reached your edit), never what was said in your shoots. News and offers only reach you if you have not opted out, and you can object to the tailoring itself by writing to privacy@earwig.io. The full detail is under How we choose the emails we send you.
Who can see my shoots?›
Only you, unless you share them. If you make a share link, anyone with the full link and its PIN can view that shoot until you reset the link, remove them or delete the shoot; the link alone shows its title and marker count. There is no public list of your shoots anywhere.
Can I delete my data?›
Yes. Swipe left on a shoot in the Earwigs tab to delete it. To delete your whole account straight away, in the iPhone app go to Menu, then Settings, then Delete Account, or on the website open your profile, then Delete account. Or email privacy@earwig.io and we will do it within one month.

Questions about your data?

If you have any questions about how we handle your data or want to make a request, get in touch.

privacy@earwig.io