Privacy Policy

Last revised: October 15, 2026

SayLessAI provides creator video tools and Sealed by SayLessAI, a Gmail deal agent. This policy explains what we collect across those services, how we process the content you provide, who we share it with to run the products, and the choices you have.

1. Information you give us

  • Account details. Your email address and sign-in identifiers when you register or log in. If you sign in with Apple and choose to share your name, Apple sends it to SayLessAI once, on your first sign-in, and SayLessAI stores it as your account display name.
  • Uploaded media. The video takes, audio, and images you upload for editing, plus any scripts, captions, and notes you provide.
  • Sealed account content. The rate cards, package terms, pitch-profile details, deal updates, and replies you enter so Sealed can manage your brand conversations.
  • Sealed financial information. Income figures you enter, including average and lifetime GMV, proposed and agreed deal amounts, and payment status, so Sealed can prepare negotiations and track your deals.
  • Billing details. Subscription status and payment records. Card details are handled by our payment processor and are not stored by SayLessAI.
  • Device and notification details. If you enable push notifications while signed in, SayLessAI stores a push notification token for this device and the device label, linked to your SayLessAI account, to deliver job updates and show or manage signed-in devices.
  • App diagnostics. When a SayLessAI mobile app reports a crash, a diagnostic record may include the crash message, stack trace, whether the crash was fatal, app build number, platform, and crash time. The app may also send short lines of numbers about how well uploads, downloads and editor playback run: sizes, times, speeds, number of tries, number of plays, freezes and rebuilds, and how each one ended. Download and playback lines carry a short code that names the edit they are about, and playback lines also carry a random code for that session. None of these lines holds file names, web addresses or video content. When a signed-in session is available, SayLessAI links these records to your account so we can diagnose failures, fix stalls on slow connections and protect app reliability. Sealed currently keeps JavaScript crash details in the device log and does not transmit those details to SayLessAI.

2. How we process your uploads

To edit your footage, SayLessAI runs it through the following steps. Each step processes your content to deliver the feature you asked for, and the last one helps us keep the editor working well:

  • Upload processing. Your footage is transferred to our object storage and prepared for editing.
  • Transcription. Your audio is converted to text so the editor can protect the words you meant to keep and trim dead air.
  • Voice synthesis. When you request AI Voiceover, a voice track is generated to fit your footage.
  • Editing and rendering. The cut is assembled and a finished video is produced for you to review and export.
  • Optional AI tools. Script Writer, Video Breakdown, Live Script, Remix, and AI Video Studio process the specific inputs you provide to those tools.
  • Finding and fixing editing problems. While we keep your uploads and working copies (section 5), we may review an edit or run it again, including through the providers in section 3, to find and fix problems in the editor and check its quality. We do not use them to train AI models.

3. Service providers we share content with

We use trusted third parties strictly to operate these features. They process your content on our instructions, only to perform the task you requested and, for your uploads, for the uses described in section 5:

  • Object storage: a cloud storage provider, to store your uploads, working copies and rendered videos.
  • Transcription: speech-to-text providers, to turn the speech in your footage into text.
  • Video analysis: an AI video analysis provider, which may watch short sections of your footage to help choose between repeated takes.
  • Voice synthesis: a text-to-speech provider, for AI Voiceover audio.
  • AI generation and assistants: third-party AI processing providers for editing decisions, media generation, and text tools.
  • Hosting and payments: our cloud hosts and payment processor.

4. AI model training

We do not use your uploaded footage, transcripts, or generated media to train our own AI models, including the files we keep as described in section 5. Content is sent to the providers above only to perform the task you requested and for the uses described in section 5, and we select providers on terms intended to prevent your content from being used to train their models where that control is available.

5. Retention and deletion

Finished videos are deleted from storage seven days after they are created. That deletion runs automatically on a schedule, so download anything you want to keep before the week is out. A small number of finished videos may still be stored after seven days; write to [email protected] and we will remove them. To make a repeat export of the same edit faster, we may also keep a cached copy of a finished video, its transcript and its edit details for 14 days after it is made, and then delete it automatically. When you move a video to Trash, you can restore it until its finished file reaches the seven-day limit above; Trash does not delete a video sooner or keep it longer. You can also permanently delete a finished edit at any time from the video editor on the website; that deletes the finished video, and the record of the job, including the text transcript of its speech, stays with your account data described below.

The footage and audio you upload for editing, in the video editor, the mobile app or AI Voiceover, are kept for at least 30 days after the most recent activity on that edit, and the working copies we make from them are kept for at least 30 days after they are made, so you can re-edit a video and so we can find and fix problems in the editor, and all of them are then deleted automatically, unless you let us keep them in the optional test set described below. We do not use them to train AI models (see section 4). A re-edit, or any other change to that edit, starts the 30 days again for the uploads, but not for the working copies. An upload that is never used in an edit is deleted automatically after 30 days. The caches we build from your footage to speed up editing (a processed copy of the video, its transcript and word timings, the edit plan and similar analysis results) are deleted automatically 30 days after they are made, even if you edit again; a later edit builds them again. One exception: the manual editor in the mobile app also prepares a cleaned copy of the speech in your recording and, when it can, a matching copy of the picture. We keep them in our database for about 3 days, and longer only while an edit made from them is still in progress. Copies of these files that we keep elsewhere to find and fix problems, on our own computers or in a separate archive folder in our storage, follow the same limit; we clear them in a weekly clean-up, so they can stay up to a week longer.

Deleting your account deletes the uploads, working copies and videos linked to your account. The caches and the cached copies of finished videos described above are not removed when you delete your account; they are deleted on the schedule described above, 14 or 30 days after they are made. A run we make ourselves to find and fix a problem in one of your edits is not linked to your account: we file it under our own account, so the uploads and working copies it uses or makes are not removed with your account. They are deleted automatically on the same schedule, the uploads at least 30 days after the most recent activity on that run and the working copies at least 30 days after they are made, and the record of that run, including the text transcript of its speech, stays in our own records. Words from your edits, such as the text transcript of what you say and when each word is said, may also be copied into our own test files that we use to check the editor. Some of those copies are saved in the history of our software and are not removed when you delete your account. On the website, pictures you add to AI Video Studio, and the scene images and clips it makes along the way, are kept in separate storage that is not removed with your account. Write to [email protected] before you delete your account if you want them removed. Whichever way content is deleted, we remove it from active systems and instruct our storage provider to delete the underlying objects; routine backups are cycled out on a rolling schedule.

The optional test set. When the app offers it, you can choose to let SayLessAI keep a few of your videos for up to 12 months, only to check the editor's quality. The choice is off unless you turn it on. If you turn it on, we may keep a few of your edits, with the footage you uploaded for them and the working copies we make from it, for up to 12 months, and use them only to check that the editor still edits them well, including by running them through the providers in section 3 again. We do not use them to train AI models. We keep about 150 of these videos at most, across all creators, plus videos we record ourselves. Ask us any time at [email protected] and we remove yours; deleting your account removes them too.

Your account data, including your email address, subscription records, and the record of the jobs you ran, is kept until you delete your account. After you delete your account, some records of how the apps and our systems ran are kept. Crash reports, the timing numbers described in section 1 and similar system records keep the account number they were written under. Sign-in and account-activity records keep the network address they were written from (this is separate from the two day marker described below) and, on some events, a device name or identifier, the first part of an email address, or a linked sign-in account name. Records of credits, refunds and subscription repairs that our staff made on your account keep the account number and the email address. We keep these records for security, reliability and running the service, and we do not use them to contact you or advertise to you. We do not delete them on a schedule today. You can close your SayLessAI account directly from the signed-in You tab or Settings by choosing Delete account; SayLessAI may ask you to sign in again before completing the deletion. If you cannot access that control, email [email protected] and we will help.

After a Sealed account is deleted, we remove the clear Gmail address and account link from the trial ledger. We retain a keyed, pseudonymous marker and the trial grant date for the lifetime of the Sealed trial program, solely to prevent the same mailbox from receiving repeated free trials. The marker is not used to contact you, advertise to you, or identify the mailbox in product or support views.

SayLessAI gives its free edits, free AI scripts and card-required free trial once per person. To keep it that way, we retain a keyed, pseudonymous marker of the sign-in identifiers and confirmed email address of accounts that use our AI video editor or AI scripts, and, for the card-required free trial, a keyed marker of the email address together with our payment processor's own fingerprint of the card (never the card number) and the trial's dates and subscription reference. These markers are kept after you delete your account, for as long as we offer that free use or trial to new accounts, solely to prevent the same person from receiving it again. To limit free uses per phone and per network, we also check the device identifier of the app you sign in on and keep a keyed marker of the network address an account signed up from, which we delete after two days. These markers are not used to contact you, advertise to you, or identify you in product or support views.

6. Support access

Authorized SayLessAI staff may access your account and media only when it is necessary to help with a request you raised, to investigate a fault, to find and fix editing problems while we keep your files (section 5), or to keep the service secure. Access is limited.

7. Presence and usage measurement

We measure how the product is used, including sign-ins, feature usage, render outcomes, and error events, so we can keep SayLessAI working and improve it. Inside the SayLessAI apps and on the website we also record a few account-level events in our own database, such as sign-up completed, upload started, Plans screen opened, first save and free uses used up, so we can see where people get stuck. These events stay in our own database and are not sent to advertising or analytics companies. They are separated from your account when you delete it. Analytics that are not strictly necessary run only after you accept them in our cookie banner. See our Cookie Policy.

For Sealed, operational records include sign-ins, mailbox connections, control changes, and deal-status updates linked to your account. We use them for app functionality, security, and support, not advertising or tracking.

8. Consented marketing examples

We show real SayLessAI edits as examples only when the creator who made them has given us recorded consent to publish that specific video. We copy the approved media into separate marketing storage, strip embedded location, device, and account metadata, and remove the public example if consent is later withdrawn. We never publish your footage as an example without that consent.

9. Your rights

You can access, correct, export, or delete your personal data. Contact [email protected] to exercise any of these rights.

10. Security

Data is transmitted over encrypted connections (HTTPS/TLS). Files are stored at long, random web addresses, and anyone who has the exact address of a file can open it until it is deleted. No system is perfectly secure, but we work to protect your content and notify you of material incidents as required by law.

11. Google user data (Sealed deal agent)

If you connect a Gmail account to our deal agent, Sealed by SayLessAI, we access it through Google's APIs with your consent, using two permissions: read (gmail.readonly) to detect and display brand deal conversations, and send (gmail.send) to deliver the negotiation replies Sealed writes for you.

We use this data only to provide the deal agent features: classifying scanned messages to identify deal mail, extracting offer terms, drafting and sending negotiation replies, and showing those conversations in your dashboard. To classify a message and write a reply, the content of that message is sent to a third-party AI processing provider, of the kind listed in section 3, which returns the classification, the extracted offer terms and the draft text. We do not use Gmail data for advertising, we do not sell it, we do not use it to train generalized AI or machine learning models, and humans do not read it except with your permission, for security purposes, to comply with the law, or when aggregated and anonymized for internal operations.

Sealed runs automatically once a mailbox is connected. Every queued reply waits on a countdown that you can cancel before it is sent, and disconnecting the mailbox stops all sending.

OAuth tokens are stored encrypted. Disconnecting your mailbox inside the product revokes our access, and you can also revoke it at any time from your Google Account security settings. Sealed's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.