Takeroom

Privacy Policy

Last updated

Draft pending legal review. This document describes, honestly and in detail, what Takeroom actually does with your data. It has not been reviewed by a lawyer, and several questions below are marked as open because they cannot be answered by writing — they need counsel and, in some cases, signed agreements. Do not submit this to App Store Connect or Google Play Console in this state.

1. Who we are

Takeroom is an application that edits video you record yourself. This policy covers the Takeroom app and this website.

Takeroom is operated by NEXARLABS LTD, a company registered in England and Wales, company number 16703034, registered office 71–75 Shelton Street, Covent Garden, London, WC2H 9JQ. Privacy contact: hello@takeroom.app.

Open item whether an EU representative is required under Article 27, and the controller/processor analysis, still need legal input.

2. What we collect

  • The take you upload — both picture and audio.
  • What we derive from it — where each person appears in frame, who is speaking in each moment, the cut decisions, any reframes you make, the transcript, captions, chapters, show notes and clip candidates.
  • Correction Still frames — a poster frame and a thumbnail frame taken from each episode.
  • Your account — the identifiers held by our authentication provider, including the relay address if you use Sign in with Apple.
  • Your subscription state — an anonymous app-user identifier and what you are entitled to, held by our billing provider.
  • Correction Your purchases — the plan you buy through the App Store or Google Play, and any “Extra hours you bought”.
  • Technical records — device and operating system, app version, IP address, crash reports, and the server-side access logs and job records that processing a take necessarily creates.

3. The other person in your footage

Takeroom exists to edit conversations, which means almost every upload contains someone who is not the account holder. Correction The app does not currently ask you to confirm that everyone recorded agreed.

If you appear in footage someone else uploaded and you want it removed, write to hello@takeroom.app and we will act on it.

Open item the notice obligations owed to a person who is recorded but is not our user, and the in-app attestation that should accompany every upload, both need legal input.

4. Why we process it, and on what basis

PurposeWhat it involves
Making the cutReading the take, working out who is speaking, choosing the shots, producing the edit you asked for.
TranscriptionTurning speech into word-timed text so captions, chapters, show notes and clip candidates can exist.
Account and billingSigning you in and knowing what you have access to.
Security and abuseKeeping the service working and stopping misuse.

We do not train models on your footage. Your take is processed to produce your edit and for nothing else.

Open item the lawful basis for each purpose above, and whether speaker attribution engages the special-category rules that apply to biometric identification, are questions for counsel.

5. How long we keep it

WhatHow long
The take you uploadedCorrection Deleted 7 days after it was uploaded. Storage clears expired files once a day, so a file can last up to about a day longer. This is also the window in which you can re-cut it without uploading again.
An upload that never finishedCorrection The unfinished parts are deleted 3 days after the upload started.
The audio copy made for transcriptionCorrection Deleted after 1 day. Because storage clears expired files once a day, it can last up to about 2 days.
Derived artifacts (cuts, transcript, chapters, notes)Kept with your episode until you delete it. Correction This includes the edit, the transcript, who spoke when, the face-position tracks and the still frames. They have no expiry date. They are deleted when you delete the episode or your account.
Copies of still frames on the delivery networkCorrection Still frames are delivered through a content delivery network. Copies cached there can outlive a deletion until their cache time runs out.
Job recordsKept while the episode exists.
Server access logsKept on a short operational rotation.
AccountUntil you delete your account.
Billing recordsKept as long as tax and accounting law requires, which is longer than the account itself.
BackupsDeleted data disappears from backups on the backup rotation, not instantly.

Open item the cache time deployed on the content delivery network, and whether deleting an episode or an account should clear its cached still frames.

Open item every duration above must be read out of the deployed storage lifecycle configuration and confirmed by observing a real object expire, before this page goes live. Do not publish a number that has not been verified against the running system.

6. Who else processes it

ProviderWhat they handle
Amazon Web ServicesStorage, compute, queueing and delivery. Your upload is stored and processed here.
Amazon Web Services (content delivery network)Correction Delivers the poster and thumbnail frames of your episodes to the app.
Amazon Web Services (language-model service)Correction Reads the words of your video — never the video — to find chapters and highlights. Nothing is sent until you allow it in the app.
ClerkAuthentication and account identity.
RevenueCatSubscription state and entitlements.
Apple and GoogleCorrection Store billing. You buy a plan or extra hours through the App Store or Google Play.
CloudflareCorrection Cookieless visit counts for this website (Cloudflare Web Analytics). Not used by the app.
SentryCorrection Crash reports from the app.

Speech recognition runs on our own servers, not through a third-party transcription service.

Open item the processing region for each provider, the transfer mechanism where data leaves its region, and executed data-processing agreements with each.

7. Security

Uploads travel over encrypted connections and are stored encrypted. Correction A sentence about restricted access and time-limited links was removed. See the corrections box.

Open item this section must describe only what is actually configured. The same claims appear in the Google Play Data safety form, and an inconsistency between the two is itself a violation.

8. Your rights

Depending on where you live you may have the right to see the data we hold about you, correct it, delete it, restrict or object to how we use it, receive a copy, withdraw consent, and complain to your data protection authority. In California you may also have rights to know, delete, correct and limit certain uses.

To exercise any of these, write to hello@takeroom.app.

Automated decisions. Takeroom decides automatically how each person is framed and when the picture cuts to them. It does this from where faces appear and who is speaking. You can override any of it: change the directing style, reframe an individual shot, or re-cut the whole episode.

9. Deleting your account

You can delete your account from inside the app. Deleting it deletes the episodes and derived data associated with it, subject to the billing records noted above.

Correction All the ways to delete are on the delete account page.

The app lists what goes:

  • Your videos on Takeroom’s servers
  • Your uploads
  • Extra hours you bought
  • Your sign-in

This includes the derived data kept with each episode: the edit, the transcript, who spoke when, the face-position tracks and the still frames. Copies of still frames cached on the content delivery network can outlive the deletion until their cache time runs out.

The app also warns: “Deleting your account doesn’t cancel a subscription. If yours renews, cancel it in the store first, or you’ll keep being charged.”

10. Children

Takeroom is a general-audience product and is not directed at children. Do not upload footage of a child without the consent of a parent or guardian. If you believe a child's data has reached us through Takeroom, write to hello@takeroom.app and we will delete it.

Open item the minimum age and whether an age gate is required.

11. This website

Correction The waitlist. If you leave your email on the home page, we store it on our own Amazon Web Services account and use it only to send a short email confirming you joined (once our sending is set up) and the email that tells you Takeroom has launched. We do not share it or use it for anything else. To be removed at any time, reply to either email or write to hello@takeroom.app.

Correction Analytics. The site counts visits with Cloudflare Web Analytics, which sets no cookies and stores nothing on your device. It loads from Cloudflare only once it is switched on for the site. The site sets no cookies of its own.

Correction Hosting. The site is hosted on Cloudflare Pages. Cloudflare handles each request to the site and may keep short-lived logs that include IP addresses, to deliver the site and protect it from abuse.

12. Changes

If this policy changes we will update the date at the top and, for anything material, tell you in the app.

Open questions that drafting cannot close. Controller and processor roles; executed data-processing agreements; lawful basis per purpose; whether speaker attribution is biometric processing; what is owed to a recorded non-user; international transfer mechanism; whether a data protection impact assessment is required; which statutes actually apply; whether any disclosure counts as a sale or share; the Terms of Service and end-user licence; the breach notification procedure; and age gating. Each needs counsel before launch.

Corrections for counsel to review

Each change below states a fact the source shows. Counsel can accept or rewrite each one.

IdWhat changedOld wordingSource
p2 Added two items the app collects and the list left out: still frames, and purchases including extra hours bought. No wording. Neither item was listed. apps/backend/lambda/common/projects.py:65; apps/backend/lib/onecam-backend-stack.ts:450-452; apps/mobile/src/features/auth/copy.ts:136; apps/mobile/src/features/paywall/plans.ts:175-205; apps/mobile/src/features/topups/copy.ts:43-45
p3 Replaced a statement that the uploader confirms consent. The app asks no such thing. “When you upload a take you confirm that everyone recorded in it has agreed to you doing so.” apps/mobile/src/features/import/ImportScreen.tsx:27-28; bd mobile-apps-lkj.8
p5 Removed “no later than”: storage clears expired files once a day, so a take can last up to about a day past 7 days. Added unfinished uploads (3 days), the transcription audio copy (1 day, up to about 2), that derived data has no expiry, and the delivery-network cache, with a new open item. “Deleted no later than 7 days after the upload completes.” The other rows and the open item were not on the page. apps/backend/lib/onecam-backend-stack.ts:394-413, 467-480, 481-508 (once a day: 505-506), 706-721, 1050-1058; apps/backend/lambda/api/get_project.py:4-6
p6 Added processors the app uses: the delivery network, the language-model service, Apple and Google for store billing, and Sentry. No wording. The table listed only Amazon Web Services, Clerk and RevenueCat. apps/backend/lib/onecam-backend-stack.ts:706-721; apps/mobile/src/features/words/copy.ts:324-325; apps/mobile/src/features/auth/copy.ts:145-150; apps/mobile/src/features/topups/copy.ts:43-45; apps/mobile/src/lib/legal.ts:103-104; apps/mobile/scripts/eas-build-pre-install.js:55-61
p7 Removed a sentence that claimed more than is configured. Poster, thumbnail and export links are unsigned delivery-network links, not time-limited, and the live API has no authorizer. Kept the encryption sentence, which matches the configuration. “Access to stored footage is restricted, and upload and download links are scoped and time-limited.” apps/backend/lib/onecam-backend-stack.ts:394-398; apps/backend/lambda/api/get_transcript.py:5-6; apps/backend/lambda/api/get_job_status.py:14; LESSONS.md:169
p9 Added a link to the delete account page, the app’s list of what goes (verbatim), the derived data and the cache note, and the app’s subscription warning (verbatim). No wording. The section had only the first two sentences. apps/mobile/src/features/auth/copy.ts:135-142, 149-150; apps/backend/lib/onecam-backend-stack.ts:1050-1058, 706-721
p11 Restored the email sign-up (the home page has a waitlist form again, 2026-11-02): where it is stored, its one use and how to be removed. Added cookieless analytics and Cloudflare as its provider. Kept the hosting open item. “The pages of this site contain no cookies, analytics scripts or forms, and load nothing from other sites.” landing-page/site/index.html (form[data-waitlist]); landing-page/site/assets/js/site.js (waitlist and beacon); landing-page/infra/waitlist/