Presentr Analyze
AboutHow it works
Caption Retiming
Re-sync SRT / VTT to any cut
Broadcast Compliance
Validate against delivery specs
Ad Break Detection
SCTE-35 / HLS markers
Loudness QC
R128 / BS.1770 measurement
AI Dubbing
Translate and dub your videos
Read Aloud
Text to speech, 48 languages
Languages
61 for subtitles, 48 for dubbing
PricingFree toolsBlogContactDeveloperSign InGet Started

Privacy Policy

Last updated: November 13, 2026

1. Who we are

Presentr Analyze ("we", "our", "us") is a media analysis and transcription platform operated by T3 Interactive LLC. This policy explains how we collect, use, and protect your personal information when you use our service at analyze.presentr.me and related domains.

2. Information we collect

Account information

When you register, we collect your name, email address, and a hashed password. If you sign in via Google OAuth, we receive your name, email, and Google account ID from Google.

Media and content you upload

When you submit a run, we store the source media file (video or audio), transcription results, translation outputs, analysis artifacts, and any metadata you provide. This content is stored on your behalf to provide the service.

Feature interest sign-ups

If you register interest in a feature we're considering (for example AI dubbing), we store your email address and answers; the referring page and any campaign (UTM) tags; your IP address and browser user agent; the time and number of submissions; and, if you're signed in, your account and, when you register from a run, that run and its languages. We use this to measure interest in the feature, to contact you about it, and to prevent abuse. Email hello@presentr.me to be removed.

Voice samples and cloned voices

If you add your own voice ("My voice"), we store your recording (up to 30 seconds), the name and language you give it, and a record of your consent: its exact wording, the time, your IP address and browser. The recording is sent to AssemblyAI, which creates a synthetic copy of the voice that we use only to read your own dubs and text aloud; we do not use it to identify you or for any other purpose. The synthetic copy is kept while you use it for dubs or read-aloud audio, and deleted after 60 days without use. Deleting the voice on the Voices page, or closing your account, deletes the recording and the synthetic copy straight away (if a service is briefly unavailable, we keep retrying every hour until both are gone). We keep the consent record for as long as we may need it to show that consent was given (up to three years after the voice is deleted).

AI apps you connect (ChatGPT, Claude and other agents)

You can connect an AI app or agent to your account, for example ChatGPT, Claude or a coding agent, so it can run Presentr Analyze jobs for you. When you approve a connection, we store the app's registration (its name and the address it signs in through), the access tokens we issue it (kept only as one-way hashes, never in readable form), when they were issued and last used, and your approval. The app sends us only the files, links or text you ask it to process, and receives the results and download links; we do not see your conversation with the app. Every paid job needs a quote first, and the app is instructed to show you the quote and ask before it starts the job.

A job started by a connected app expires 7 days after it was created: after that the app can't get new links to its files, and the files are scheduled for deletion a day later. A record of the job stays with your other runs until you delete it or close your account (see Data retention): what it was, its status, credits and dates, and results data stored with it, such as a transcript or translated text it produced. Files an app uploads but never uses are deleted after 24 hours. Text inside the files you send is returned to the app only as files, and we treat it as content, never as instructions. You can disconnect an app at any time under Settings → Connected apps, which revokes its access straight away.

Integration credentials

If you connect third-party integrations (Google Drive, Dropbox, YouTube), we store OAuth tokens on your behalf to access those services. We access only the scopes you explicitly grant.

Usage data

We collect standard server logs including IP addresses, request timestamps, and HTTP status codes for security and performance monitoring. Apart from the ad measurement described under Cookies, we do not use third-party analytics trackers.

3. How we use your information

  • To provide, operate, and improve the Presentr Analyze service
  • To process media files and return analysis results to you
  • To communicate with you about your account and runs
  • To detect and prevent fraud, abuse, or unauthorized access
  • To comply with legal obligations

We do not sell your personal data or use your media content to train AI models.

4. Third-party services

We use the following third-party services to operate the platform:

  • AssemblyAI — transcription and speech analysis; your media is transmitted to AssemblyAI for processing under their privacy policy. If you add your own voice, your recording is sent to AssemblyAI to create the synthetic copy, and the text it reads is sent to AssemblyAI to generate the audio.
  • Anthropic — reading the text in PDFs and images you submit (text extraction).
  • Anthropic — translation of transcripts and extracted text. If Anthropic can't translate a transcript, it goes through AssemblyAI's LLM Gateway, which also writes the analysis in our free YouTube and TikTok transcript tools: the gateway uses Claude on Amazon Bedrock, with OpenAI models as its backup. The gateway doesn't store the text it's sent or the answers; Amazon Bedrock doesn't store or log them, OpenAI models used through the gateway run with zero data retention, and AssemblyAI has opted out of training with these providers. When you dub a video or have text read aloud with one of our AI voices, the text is sent to AssemblyAI or OpenAI, depending on the language, to generate the spoken audio.
  • Amazon Web Services (AWS) — cloud infrastructure and file storage (S3).
  • Google — OAuth authentication and optional Drive/YouTube integrations.
  • Dropbox — optional source and delivery integration.
  • Stripe — payment processing, if applicable. We do not store card details.
  • Google Ads — a conversion tag that counts ad clicks that lead to a visit or signup (see Cookies).
  • Reddit — an ad pixel, only for visitors who arrive from a Reddit ad (see Cookies).

5. Data retention

We retain your account data for as long as your account is active. Run data and associated media files are retained until you delete them or close your account. You can delete individual runs and their artifacts from your dashboard at any time. Jobs started by a connected AI app are the exception: they expire 7 days after they were created and their files are scheduled for deletion a day later, while the job's record stays like any other run's (see AI apps you connect).

When you close your account, we delete your personal data within 30 days, except where retention is required for legal or billing purposes.

6. Data security

We use industry-standard security measures including encryption in transit (TLS), encrypted storage for credentials, and access controls. No system is perfectly secure; we encourage you to use a strong password and keep your API keys confidential.

7. Your rights

Depending on your location, you may have rights to access, correct, export, or delete your personal data. To exercise these rights, contact us at the address below. We will respond within 30 days.

8. Cookies

We use a session cookie to keep you signed in and a CSRF token cookie for security.

Our Google Ads tag lets Google count when a click on one of our ads leads to a visit or a signup. In the European Economic Area, the UK and Switzerland its advertising storage is turned off, so it sets no advertising cookies there. Elsewhere it may set Google advertising cookies (such as _gcl_au) for that count. We don't use it for personalised ads or remarketing.

If you arrive by clicking one of our ads on Reddit, we load Reddit's ad pixel on that visit and again if you sign up, so Reddit can count how many ad clicks led to a visit or a signup. It sets a Reddit advertising cookie (_rdt_uuid) on this site. We send Reddit no name, email or account details. Visitors who didn't come from a Reddit ad never load it.

9. Changes to this policy

We may update this policy from time to time. We will notify you of material changes by email or by posting a notice in the application. Continued use of the service after changes take effect constitutes acceptance.

10. Contact

Questions about this policy? Contact us at privacy@t3interactive.com or through our contact page.

© 2026 T3 Interactive LLC. All rights reserved.
Privacy PolicyTerms of ServiceContact