Retention and Destruction

Retention and Destruction Policy

Last updated August 25, 2026

This is Reactr's written schedule for how long recordings are kept and what destroys them. It is published here, at a stable address, and linked from the consent screen every person sees before a camera or microphone is switched on.

The short version: the full recording of your session is permanently destroyed within 30 days, automatically, whether or not you ask. Your finished clip stays up until you delete it. Cancelling wipes everything immediately.

What Reactr does not collect

Reactr records video and audio as ordinary content. It does not create or store a face template, faceprint, voiceprint, or any other biometric identifier, and it runs no facial recognition, expression analysis, emotion scoring, age estimation, or speaker identification on a recording. There is no such classifier anywhere in the software, and an automated test blocks one from being added without the separate consent flow that would require. Because no biometric identifier is collected, there is nothing of that kind to retain or destroy.

This policy is published regardless, so that anyone asking the question can read the answer rather than take it on trust.

The schedule

What	Kept for	What destroys it
Raw session recording and the uploaded pieces of it	30 days from the session	Automatic sweep, no request needed
A session you cancel	Not kept	Deleted the moment you tap Cancel and Delete, including pieces already uploaded
Your finished clip	Until you delete it	Your delete control, the end of the campaign, or a moderator takedown
The email address you gave to be told your clip was ready	Until the 30 day sweep	Cleared by the same sweep that destroys the footage, or immediately if you delete
The record of the consent you gave	With the session	Cleared when the session is deleted
Session bookkeeping: an identifier, the campaign, timestamps, status	Indefinitely, with no recording attached	Retained to count sessions and prove destruction ran

How destruction is actually enforced

Raw footage never leaves the machine that received it. Only a finished clip is ever copied to storage. The full session recording and its uploaded pieces exist in one place, which is what makes destroying them a single, verifiable act rather than a hunt across copies.
A sweep runs on its own. It runs when the service starts and every 24 hours after, finds every session older than 30 days, and permanently removes the session recording and its chunks. It does not wait for anyone to ask, and there is no queue for it to fall behind.
Cancelling deletes everything, then and there. Cancel and Delete removes the session's files from disk, deletes any stored clip, and clears the markers, the consent record, the handle you typed, and the email address. What remains is an identifier with nothing attached to it.
Every destruction is recorded. A cancel writes a session deleted event and the sweep writes a purge event, each with the session identifier and the time. That record is how Reactr can show the schedule ran rather than assert it.
Deletion is deletion. Files are removed, not flagged. There is no hidden copy kept behind a deleted marker.

Asking for something to be deleted sooner

You do not have to ask. While you are recording, and on the screen where your finished clip appears, there is a control that deletes everything immediately. It is the same deletion the sweep performs, run early.

If you cannot reach that control, or you want a session deleted that you no longer have the link to, write to us at reactr.gg/contact. Deletion requests are actioned within 72 hours. Tell us the campaign and roughly when you recorded, and we will find it.

Nothing is sold, and nothing is disclosed

Reactr does not sell, lease, trade, or otherwise profit from a recording, and does not disclose one to a third party except where you asked for it to be shown: a clip you entered to be featured, and a moderator approved, appears on Reactr or with the campaign it belongs to. There is no advertising tracker on a recording page and no data broker in this pipeline. A campaign's sponsor sees counts and approved clips, never a recording you did not enter.

State laws this schedule is built against

Reactr treats the strictest of these as the floor everywhere, rather than serving different disclosures to different states.

Illinois (BIPA). Requires a published retention schedule and destruction guidelines, written notice, and a written release before collecting a biometric identifier. Reactr collects none, and publishes the schedule anyway. Its outer bound, destruction within three years of the last interaction, sits far outside the 30 days used here.
Texas (CUBI). Requires notice and consent before capture and destruction within a year of the purpose ending. The consent screen and this schedule are served identically to Texas visitors; no disclosure is geo-fenced.
Washington (My Health My Data). No health inference of any kind is drawn from a recording, and none is possible without the expression analysis that does not exist here.
California (CCPA and CPRA), and Colorado, Connecticut, Utah, and Virginia. The consent screen doubles as notice at collection: it names what is captured, why, how long it is kept, and how to delete it. Reactr does not sell or share personal information as those laws define it, so there is nothing to opt out of. Access, correction, and deletion requests go to the address above.

Changes to this schedule

If the retention term or the destruction mechanism changes, this page and the consent screen change together, and the consent screen's version identifier changes with them. Every consent Reactr holds is stored with the version of the wording that person actually read, so it is always possible to say which schedule someone agreed to rather than which one is current.

What is captured, what is measured on the rest of the site, and where it is stored are covered in the privacy policy. Copyright and creator opt-out are on the copyright and takedown page.