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
- Account details: when you sign in with Google (through Firebase Authentication) we receive your account identifier, email address and display name, plus session identifiers.
- Video prompts, the photos you choose or upload, and generation request metadata needed to run the product.
- Generated media, history, save/share references, and playback state.
- Credits and purchase records: transaction identifiers, product, amount and entitlement state. We never receive or store your full card number.
- Technical data: IP address, browser/device type and request logs on our servers, used for reliability, security and abuse prevention.
- Analytics and advertising-measurement events (see the next section).
- Support messages and contact details you send us.
Website analytics and cookies
On avocadio.ai we use the tools below only with your consent. When you first visit, a banner asks you to Accept or Reject them. Until you choose, none of these tools is loaded and no cookie is set by them. You can change your choice at any time (see “Your choices”).
- Google Analytics 4 (Google Firebase Analytics), loaded from Google domains (for example googletagmanager.com and google-analytics.com). Purpose: measure page views and which features are used, for example which template is opened or whether a video is started. Data: event name, page, device/browser type, approximate location from IP address, and a random identifier stored in a cookie or local storage. Retention follows the data-retention setting of our Google Analytics property.
- Meta Pixel (Meta Platforms), loaded from connect.facebook.net. Purpose: measure the performance of our ads and understand visits that come from them. Data: page views and standard events, browser identifiers and cookies set by Meta, IP address and browser details.
- Meta Conversions API (server-to-server). Purpose: the same ad measurement, sent from our servers so that results are not lost to browser limits. Data: the event type (registration, purchase, video created), a hashed account identifier, and event details such as generation mode or duration. This does not include your prompts, photos, generated media or email address. It is sent only if you accepted analytics and advertising cookies. Your browser passes your choice to our servers with each request. If you rejected, or never chose, we do not send these events. For payment confirmations that reach us directly from the payment provider, we use the choice we last saved for your account; if there is none, nothing is sent.
None of these tools receive your prompts, images or generated media. We do not use advertising or analytics scripts other than those listed here on the website.
Your choices
Choose “Accept” or “Reject” on the banner. If you reject, Google Analytics and the Meta Pixel are not loaded on this browser, including on later visits, and our servers do not send server-side events to Meta. We remember your choice on this device and, when you are signed in, on your account. To change it, open Settings → Analytics preferences and choose again. You can also block cookies in your browser settings, which may stop the tools from working. If you use a different browser or device, make the choice there too. To ask us to delete data linked to your account, write to the address in the Contact section.
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.
Service Providers
We share data only with providers that help us run Avocadio: Google (Firebase Authentication, Google Cloud hosting and storage, Vertex AI / Veo, Cloud Vision, Google Analytics), Meta (Meta Pixel and Conversions API), and payment providers for the checkout you use (PayPlus, Paddle, Apple App Store, Google Play). Payment providers process your payment details under their own policies. Some of these providers are located outside your country, including the United States; where the law requires it we rely on the transfer mechanisms those providers offer.
Your Rights
Depending on where you live (for example the EU/UK, Israel or California) you may have the right to access, correct or delete your personal data, to object to or restrict some processing, to withdraw consent for analytics, and, in California, to opt out of the sale or sharing of personal information for advertising. We do not sell personal data for money. To use any of these rights, contact us at the address below; you can also delete your account from Settings.
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
Privacy questions and requests: support@avocadio.ai, or the Avocadio Support page.