FACE AND VOICE DATA POLICY

Effective October 27, 2026

This policy explains how StorySense AI, LLC ("StorySense," "we," "us," or "our") creates, uses, shares, stores and destroys face and voice data, including biometric identifiers and biometric information, when teams use StorySense to organize their footage. It covers everyone who appears or speaks in that footage, whether or not they use StorySense. In this policy, "the team" means the organization or person that uses StorySense for a project and controls its footage.

Our Privacy Policy covers the other personal information we handle. Where this policy says more about face and voice data, this policy applies.

What faces and voices are used for

With faces and voices on, the StorySense app finds the faces and voices in the footage a team analyzes, recognizes the same person across the clips and recordings of one project, and links people to the characters the team names. The team can then find its footage by who appears and speaks in it.

People are matched only within one project. We never match them across projects or teams, or against anything outside the project, such as public photos or identity databases.

What we create and where it is kept

• Face and voice fingerprints. Numbers that describe a face or a voice, sometimes called faceprints and voiceprints, which let the app tell whether two faces or two voices belong to the same person. The StorySense app makes them and keeps them on the computers of the project's members. They are never uploaded to StorySense.
• Face pictures. Small pictures of the faces found, cut from the footage around each face. They are saved with the project in our cloud storage, so that a member's app can make the face fingerprints it needs again, for example on a new computer. It makes voice fingerprints again the same way, from the project's saved recordings.
• Appearance records. When and where in the picture each face appears, and how clearly it was seen. These are saved with the project in our database.
• Matching results. Which faces, and which speakers across recordings, belong to the same person; the matches the team confirms or rejects; the links to the team's characters; and lines whose voice doesn't seem to match the speaker they are labeled with. These are saved with the project in our database.

Our database and cloud storage are in the United States. The footage, transcripts and other content a team uploads are covered by our Privacy Policy and Terms of Service.

When faces and voices are off

Faces and voices are off for a workspace until one of its owners or administrators turns them on, in Settings or when the app asks them before an analysis. The first time a member starts an analysis with them on, the app tells the member what face and voice data is made and kept, links to this policy, and asks them to confirm that the team has the permission described below. It makes no face or voice data for that member until they confirm. We keep a record of who confirmed and when. Turning faces and voices off stops new face and voice fingerprints and matching from then on. It doesn't delete what has already been made; deleting the footage or the project does.

With faces and voices off, StorySense can still suggest which of the team's characters appears in a clip, if the team has given its characters photos: an AI model run by our AI service provider compares the people in the clip's frames with those photos. We keep the answer, which person is which character, with the clip's analysis, and we keep no fingerprints from the comparison. It doesn't run for a project whose characters have no photos.

Whether faces and voices are on or off, our transcription provider separates the speakers within each recording to label who says what. Our Privacy Policy covers transcription.

How we use it

We use face and voice data only to provide these features to the team, on its behalf and on its instructions, and to support, secure and fix them.

We don't sell, lease or trade face and voice data. We don't use it for advertising, to build profiles of people, to make decisions about anyone, or to train AI models.

Who can see it, and who we share it with

Face pictures, appearance records and matching results can be seen by the project's members, by StorySense staff who need them to support or secure the service, and by the service providers that store and process them for us.

We disclose face and voice data only:

• to service providers that store or process it for us, under contractual terms that govern their use and protection of it: our cloud storage and database providers and, for the character photo comparison, our AI service provider;
• when the law requires it, such as under a valid warrant or subpoena;
• to a buyer of StorySense, bound by this policy, as part of a merger or sale of our business;
• with the consent of the person it is about.

Face and voice fingerprints stay on members' computers, so we never disclose them.

Permission from the people in the footage

The team decides what footage to analyze, and StorySense creates face and voice data on its behalf. Before analyzing footage with faces and voices on, the team is responsible for:

• telling the people in the footage, in writing, that face and voice data is being created and kept, why, and for how long (the team can share this policy for that);
• getting their consent, including a written release where the law requires one, as Illinois law does, and explicit consent where the GDPR applies;
• getting consent from a parent or guardian for a child;
• any other notice or consent the law requires where the footage is recorded or where the people in it live.

For people in the European Union or the United Kingdom, the team is the controller of their face and voice data, and StorySense processes it on the team's behalf.

How long we keep it

We keep face and voice data for no more than 24 months, and for less when the footage or project it was made from is deleted. We destroy it on this schedule:

• 24 months after face and voice data is made, we delete it, including the fingerprints on members' computers. We tell the workspace's owners and administrators at least 30 days before, so the team can analyze the footage again if it still needs the people recognized and still has permission.
• When footage is deleted, we delete the face and voice data made from it, including its face pictures.
• When a project is deleted, we delete the face and voice data made from its footage 30 days after the project is deleted.
• Each member's app deletes the fingerprints on that member's computer for footage and projects that have been deleted, or that the member can no longer open, the next time the member opens StorySense or one of its projects.
• Any member can delete all the face and voice fingerprints on their computer at any time, from Settings.
• Uninstalling StorySense doesn't delete the fingerprints on that computer, because the app deletes them only when it runs. To remove them, delete them from Settings before uninstalling, or delete the StorySense folder in the computer's application data.
• Copies in our routine backups are kept out of use and deleted when those backups are overwritten in the ordinary course.

Requests from people in the footage

Anyone who appears or speaks in footage analyzed with StorySense can ask what face and voice data we hold about them, or ask for it to be deleted, by emailing support@storysense.ai. Tell us enough about the footage for us to find it, such as who recorded it and when. You don't need a StorySense account. We may need to confirm who you are before we act.

Because the team that uploaded the footage controls it, we will tell the team about your request and help it respond, and we will answer you directly where the law makes us responsible for doing so. We respond within the time the law sets. If we decline a request, we will explain why, and you can appeal by replying to our answer. If you are in the European Union or the United Kingdom, you can also complain to your data protection authority.

Security

We protect face pictures, appearance records and matching results with access controls and encryption in transit and at rest, using at least the care we take with the other confidential information we hold, and the care that is standard in our industry. Fingerprints stay on members' computers, protected by those computers' own security.

If a security incident may have exposed face and voice data, we will tell the affected teams without undue delay, so they can tell the people concerned, and we will notify people directly where the law requires us to.

Changes to this policy

We will post any change to this policy on this page, with a new effective date. Before we use face and voice data in a way this policy doesn't describe, we will update this policy, tell the teams that use StorySense, and get any consent the law requires.

Contact us

StorySense AI, LLC, 8735 Dunwoody Place, Ste R, Atlanta, GA 30350, United States. support@storysense.ai