Privacy and data
Solo recording starts locally. The two-person studio transmits camera and microphone to the other participant. A finished video uploads to cloud storage only when you choose Share link. Recordings stay in browser memory until downloaded or the page is closed. Theme, color and language preferences use localStorage and can be removed through browser site settings.
If you voluntarily submit an email for iPhone app early access, it is stored separately and used only for messages about that early access. The form does not include your script, audio or video.
Hosting and authentication are handled by the Sites provider.
This describes current beta behavior. Operator details, a privacy contact and applicable terms must be completed before public launch.
Optional product analytics
With your consent, we store page paths, broad referral categories, device and browser categories, all five UTM campaign tags, a random per-tab session identifier, named clicks and error categories for up to 90 days in the hosting database. We do not include scripts, video, audio, other query-string values or raw error messages. Hosting infrastructure may separately process connection information. You can change your choice below.
Recording together and sharing video
When you join a room, your camera, microphone and any screen or source audio you choose to share are transmitted to the other participant through an encrypted WebRTC connection, directly or through a relay when configured. The host records both participants in their browser. The guest is asked to agree before joining. Room connection data, including network information used to establish the call, is stored in the hosting database. Invitations expire after 24 hours; expired rooms are removed when new rooms are created. Closing a room removes its connection data immediately. Invitation and rejoin keys are stored in sessionStorage for the current tab.
Scripts shared within a room travel over the participant connection and are not saved in the room database. The host can explicitly upload a finished recording to cloud storage. Uploaded video and its title belong to the signed-in account and remain until deleted in My videos. Anyone holding an enabled viewing link can watch without signing in. Revoke link stops future access; it cannot erase copies a viewer already made. Deleting a cloud video removes the stored file and sharing link. Local backups are separate and remain in the browser.
Account sign-in
When Google or email sign-in is enabled, Supabase processes your email address and authentication details to create and verify your account. With Google, you first approve the sign-in on Google’s page. Access and refresh tokens are stored in browser localStorage to keep you signed in; signing out clears that browser session. A temporary return path is stored in sessionStorage during Google sign-in. The server verifies your identity before granting access to your rooms and cloud videos. See Supabase privacy information.
Cookies and browser storage
TAKT uses browser storage to provide the studio you request. The current script, up to 20 named drafts and display preferences stay in localStorage. The latest completed recording is backed up in IndexedDB when space is available. These records remain until replaced or removed through your browser’s site-data settings. The Clear button removes the current script; it does not delete your video backup.
Our analytics uses sessionStorage rather than an analytics cookie. The consent controls cover this similar storage technology too. No analytics identifier is created and no analytics event is sent by TAKT before you accept. Refusing analytics does not restrict recording or downloading.
| Storage | Purpose | Duration |
|---|---|---|
| Script, theme, accent and language | Local studio state | Until changed or cleared |
| Latest take backup | Local recovery, subject to available space | Until replaced or cleared |
| takt-demo-dismissed | Remember that you cleared the sample | Until site data is cleared |
| takt-consent-v2 | Your choice, timestamp and notice version | 180 days |
| takt-session | Optional analytics identifier for this tab | Tab session or withdrawal |
| Analytics database events | Visits, named clicks and error categories | Up to 90 days |
Change or withdraw consent
Open Cookies & privacy on any page and choose Reject analytics. Future analytics events stop and the analytics tab identifier is removed. Previously received events expire under the retention rule; withdrawal does not automatically erase past events. New consent applies to subsequent activity. Analytics has no advertising category because TAKT currently includes no advertising trackers.
Hosting and permissions
The studio processes scripts and recordings in your browser. TAKT’s analytics contains page paths, broad referral categories, a random tab identifier and event names, without script text, video, audio, URL query strings or raw error messages. The hosting platform separately handles requests, connection information and sign-in where used. Camera, microphone and screen-sharing permissions are controlled by your browser and are separate from analytics consent.