This page explains how Otter Studio (otter-ai-video.com) currently processes member, social sign-in and video creation data.
Data we process
- Member data: member ID, username, email (which may be empty when not provided by the social platform), account status, permissions and quota. Local passwords are stored as hashes, never as plain text.
- Social sign-in: the Google or Facebook provider, account identifier and email supplied by the platform. The consent screen may list name and photo permissions. Otter currently does not store social names or photos as member fields or request friend lists, posts or photo libraries.
- Creation data: your prompts, reference images or image URLs, generation settings, task status, provider task identifiers, and returned usage, cost and result data.
- Security and operation data: login sessions, short-lived authorization verification data, administrator audit records, and connection or error information that may be recorded by servers.
How data is used and transmitted
This data supports registration, sign-in, account linking, task creation and lookup, usage reporting, member management and service operations. For video generation, Otter API sends prompts, reference images and generation settings to the configured video provider (currently Blue River). The provider may process this content under its own data policies. Avoid submitting personal or confidential data you do not want the provider to process.
Google and Meta handle sign-in and authorization on their platforms. Otter uses verification results to create or identify members. Provider access tokens and ID tokens are used only for server-side verification, are currently not stored in the member database, and are not returned to the member interface.
Cookies and safeguards
This site uses necessary login cookies and short-lived OAuth verification cookies. The production site uses HTTPS and Secure, HttpOnly, SameSite=Lax session cookies. Provider and social application secrets in the admin interface are encrypted by the API. These measures protect sign-in and operations. Your language preference is saved locally in your browser.
Retention and deletion
Member and creation records are retained for use and management across devices. Sessions and OAuth verification data expire; server logs rotate according to operational settings. You can follow theData deletion instructionsto request account and data deletion. The administrator first confirms your identity and the scope of your request. Revoking Google or Facebook authorization does not automatically delete your Otter account.
Content already sent to a video provider, or data retained independently by that provider, does not automatically disappear when local Otter records are deleted. We will explain what can be handled; you may need to contact the provider separately.
Contact and corrections
To learn about, access, correct or delete your Otter data, contact teco.li.email@gmail.com. Do not send passwords, verification codes or platform secrets by email. This policy will be updated to reflect actual service features. The update date is shown on this page.
Top-ups and payment data
We retain top-up orders, payment amounts, credited USD, NewebPay transaction identifiers, and video-generation USD charges with their model rates. NewebPay hosts the payment page; Otter does not store full card numbers or security codes. USD is credited only after verification of a payment notification. Test payments do not add real credits.
USDT-TRC20 payments
For USDT top-ups, we retain the assigned receiving address, order expiry, exact payment amount and blockchain transaction ID, and use TronGrid to verify transfers. Blockchain addresses and transfers are public records that Otter cannot delete. Otter does not store member or receiving-wallet private keys.