Privacy policy

Information we handle

• Account information from Google sign-in, including your account identifier, email address, name and profile image when supplied.
• Project settings, prompts, scripts, uploaded assets, generated voiceovers, videos, thumbnails, captions and review decisions.
• Usage, credit reservations, job status, error records and security logs needed to run and protect the service.
• If you purchase a paid service, customer and subscription identifiers, payment status and invoice information. Stripe handles payment details through its hosted payment pages.
• If you connect a social account, the account identifiers, granted permissions, authorisation tokens and publishing records needed for the connection you choose.

Why we use it

We use this information to sign you in, keep your projects available, produce the work you request, track usage, manage billing, troubleshoot failures and protect accounts. A publishing connection is used to carry out the actions you authorise for that account.

Do not include passwords, private keys or sensitive information about other people in prompts or uploads. Only provide material you are entitled to use.

Service providers and sharing

We use service providers for account sign-in, hosting, secure storage, website delivery and content processing. Creating content may send your prompts, scripts or narration text to AI services. Searching for stock media shares search terms with media providers. The information shared depends on the feature you use.

Google receives sign-in requests. If you connect a supported social account, that platform receives the content and metadata you authorise for its publishing workflow. Stripe processes payment information for paid services. Providers may process information outside your country under their own terms and privacy policies.

We may disclose information where required by law or necessary to investigate misuse and protect the service.

Cookies and local storage

Sign-in uses cookies to maintain your session. Browser storage may also retain interface preferences. Our website security and sign-in services may use cookies and request information for security and service delivery. Clearing cookies may sign you out; it does not delete your account or projects.

Connected accounts, including YouTube

Connecting a publishing account is separate from signing in. When you authorise it, the YouTube integration uses YouTube API Services to identify your channel, upload the video and associated metadata you select, and display available view, like and comment counts. We store the channel ID and name, the channel information Google returns, granted permissions, encrypted authorisation tokens, uploaded video IDs, links and API responses, and these statistics. These records support the connection, upload status and statistics you request. Google's handling of information is described in the Google Privacy Policy.

You can revoke AI FRRIP's Google access through your Google account connections. Where a connection exists in AI FRRIP, use its Disconnect control as well. Disconnecting immediately disables the connection and removes its saved YouTube channel information, video identifiers, API responses and statistics from AI FRRIP. We request Google revocation immediately and remove stored tokens; if that cleanup fails, retries and a retention limit remove the credentials within seven days. This does not delete videos already on YouTube. Application records of your own projects and actions remain, without the removed YouTube data.

YouTube data retention

We periodically check that the connection remains authorised and that retained videos still exist, and refresh stored channel information and API data. If we cannot validate the data, it is deleted before 30 days have elapsed since its last successful validation. Revocation detected through Google also disables the connection and removes its YouTube data. You may need to reconnect after access is removed.

Storage, retention and deletion

Project content remains available until you delete it or it is removed under the service terms. Project deletion queues cleanup of related application records and stored media; it is not instantaneous. Transaction, security and audit records can remain where needed for accounting, dispute handling or security.

See Data deletion for the available controls and their limits. Media downloaded by you or posted to another platform must be managed separately.

Privacy requests and changes

For help with access, correction, deletion or a privacy concern, visit Support.

We will update this page when practices change and show the revision date above.