Privacy draft · not operative
Privacy behavior must match the running system.
A pre-launch description of the implemented data lifecycle. Controller identity, legal bases, contact routes, subprocessors, and jurisdiction-specific notices remain to be completed.
Privacy draft · not operative
This is an engineering-facing draft, not an operative privacy notice. Before launch, the deployment operator and qualified privacy counsel must verify every data flow, publish the controller identity and contacts, select legal bases, list subprocessors and transfers, and adapt the notice to applicable law.
Data the product is designed to process
The service processes account identifiers and profile settings; uploaded audio or video; derived playback media, waveforms, transcripts, patches, translations, exports, and AI outputs; job and error metadata; quota usage; billing identifiers and subscription state; and security records needed to protect the service.
Payment card details are handled by the configured payment provider and are not intended to be stored by Echoryte.
Service providers and processing boundaries
Media may be sent to a compatible speech provider, transcript excerpts may be sent to configured translation or AI providers, and operational data may be processed by hosting, storage, queue, email, observability, and payment services.
The final deployment must publish the actual, current subprocessor list and transfer safeguards; this repository does not guess them.
Retention, export, and deletion
Unclaimed trial objects and trial metadata are designed to expire after 24 hours. Deleted account files enter a 30-day recovery window before durable deletion work removes objects, provider jobs where supported, and database records.
Account owners can request a portable export. Export artifacts have their own short download expiry and are removed by background cleanup.
Cookies, local storage, and rights
The product uses Secure HttpOnly cookies for authentication and trial access, plus necessary client storage for durable editing and upload recovery. Optional analytics and marketing consent behavior must be documented only after the selected tools and consent mode are configured.
A monitored privacy contact and jurisdiction-specific rights workflow must be tested before public launch.