impressia← Back to Studio
Operational template

Privacy Policy

This notice explains the data used to run Impressia accounts, paid beta orders, video generation and abuse prevention.

Controller details pendingEffective 14 August 2026

Data we handle

  • Google-authenticated account identifiers, email, display name and avatar.
  • Prompts, generation settings, reference URLs, task status and error details.
  • USDT order amount, product, expiry, public receiving address and transaction ID.
  • Generation-unit balance and an auditable record of grants, reservations and use.
  • Security information such as timestamps, coarse country, IP-derived controls and request identifiers.

Never send us a wallet private key, seed phrase or password. Impressia does not need or request them to verify an incoming blockchain transaction.

Why we use it

We use data to authenticate you, create and deliver requested videos, verify payment, maintain balances, prevent duplicate crediting, secure the service, enforce policies, provide support and meet accounting or legal obligations.

Where required by law, processing relies on performance of the service contract, legitimate interests in security and operations, compliance with legal duties, or consent for a specific optional feature.

Service providers

Data may be processed by Google for sign-in, Supabase for authentication and database services, BytePlus ModelArk or another disclosed model provider for generation, and TRON/TronGrid infrastructure for public blockchain verification. Their processing and locations are governed by their own terms and our applicable service arrangements.

A submitted prompt and reference URL may be sent to the selected generation provider. A transaction ID and public wallet addresses are already visible on the public blockchain.

Temporary video delivery

Generated videos are currently delivered through a provider-hosted link that normally expires in about 24 hours. Impressia does not save a separate copy in local or object storage and cannot recover the file after expiry. Task metadata, including status and the expired link record, may remain in your private history for account operations, security and support.

Retention and deletion

We keep account, task and unit-ledger records only as long as reasonably required for the service, fraud prevention, dispute handling and applicable accounting or legal duties. Immutable financial records may need to be retained even after an account request, while direct identifiers are restricted or removed where lawful.

You can request access, correction, deletion or export by contacting support. We may need to verify the request and may retain information where law requires it.

Cookies and security

Impressia uses essential session storage and cookies needed for authentication and security. The paid beta does not require advertising cookies. We use access controls, server-side secrets and account-scoped records, but no online service can promise absolute security.

Your choices

You may sign out at any time and avoid submitting optional reference URLs. For a privacy request or complaint, email support@impressia.ai. Depending on where you live, you may also have the right to complain to a data-protection authority.

Do not include sensitive personal information in a generation prompt.

Contact support →