Avocadio Privacy Policy
This page describes how Avocadio processes account, generation, billing, analytics, and support data. It is the public privacy policy linked from the app and store metadata.
Data We Process
- Auth and account details such as sign-in provider, display name, and session identifiers.
- Video prompts and generation request metadata needed to run the product.
- Generated media, history, save/share references, and playback state.
- Credits, IAP verification metadata, and entitlement state.
- Analytics events and backend logs used for reliability and product analysis.
- Support messages and contact details submitted by the user.
AI Processing and Safety Screening
When you choose to create a video, Avocadio sends the selected or uploaded image, the prompt or motion text you entered, and the generation inputs required for the request to Google Cloud Vertex AI / Veo. Avocadio also uses Google Cloud Vision SafeSearch to screen visual inputs and generated outputs for prohibited or unsafe content. This processing is used only to create the requested video and to apply safety controls. Avocadio does not send prompts, images, generated media, or moderation classifications as analytics event properties.
Face Data
Uploaded photos and generated videos may contain a person's face. Avocadio processes this media only to provide the requested image-to-video feature and to run automated safety screening. Based on the current implementation, Avocadio does not perform facial recognition, identity matching, biometric profiling, face-mesh or facial-landmark extraction, embeddings, or persistent face-template creation.
Media may be sent to Google Cloud Vertex AI / Veo for generation and Google Cloud Vision SafeSearch for safety screening. Avocadio does not use face data for advertising, identification, profiling, or model training, and does not include images, faces, generated media, or moderation results in analytics events. Processing copies and generated outputs are stored only as required for the generation and history flows. Exact provider-side retention and backup windows are controlled by those providers and are not configurable by Avocadio; users may request account deletion from Settings and can contact support for deletion requests.
Storage and Retention
Generated assets and history may be retained for product continuity until the current retention policy removes them or the account lifecycle policy changes. Backend logs may also be retained for operational security, debugging, and abuse prevention.
Account Deletion
Users can request account deletion from Settings. The current implementation clears the authenticated session and removes the auth account record. Additional history, billing, and asset retention rules are handled separately according to the release policy.
Contact
Support: Avocadio Support page