Contents
1ABOUT THIS POLICY
This Privacy Policy explains how Advia ("we", "us", "our") collects, uses, and protects your personal information when you use the Advia mobile application ("App"), available on the Apple App Store and Google Play. By creating an account or using the App, you confirm that you have read and understood this Policy.
If you do not agree, please do not use the App.
2WHAT ADVIA DOES
Advia is a marketplace and community platform connecting clients and businesses (buyers of influencer and advertising services) with bloggers and content creators. The App provides: user profiles for clients, bloggers, and businesses; a searchable catalog; in-app chat (including text messages, voice messages, photo attachments, and file attachments such as PDF documents); optional AI-powered chat translation (messages and voice notes may be automatically translated using third-party AI services, including OpenAI); a feed of posts, short videos (Reels), events, and temporary stories called AD's, with likes, comments, reposts, and follows; announcements (campaigns); order management; a rating and review system; identity verification for bloggers and businesses; creative and analytical tools, including an AI assistant; and subscription plans, credits, and other optional in-app purchases.
The App is not intended for users under 16 years of age (or the higher age of digital consent applicable in your country). By registering you confirm that you meet this requirement.
3INFORMATION WE COLLECT
3.1Account and authentication
Email address, Firebase Authentication user ID, and authentication method data (email and password, Google Sign-In where enabled, Apple Sign-In on iOS where enabled). Technical session identifiers and security tokens.
3.2Mandatory profile data
Display name, gender, date of birth (required to verify minimum age and enable full profile functionality), profile photo URL, internally assigned stable app username (format: advia_XXXXXXX), user role (client, blogger, or business), preferred app language, and notification preferences. Marketing notification consent is collected separately where required by law.
3.3Public profiles (blogger and business)
Information you voluntarily submit for your public profile: biography or company description, country and city, spoken languages, content category, website and social media links, services or products offered, indicative pricing, audience size, and aggregated rating and order counts as displayed in the App. Public profile information is visible to other users of the App.
3.4Chats and orders
Message content exchanged in the App, including text messages, voice messages (audio recordings), photo attachments, and file attachments (such as PDF documents). If you enable AI chat translation, message text and voice content submitted for translation may be sent to third-party AI providers (including OpenAI) to generate translations. We store translations alongside the original messages so they remain available in the chat history.
Order details: title, description, agreed price range, deadline in days, status timeline, links to completed work submitted by the blogger, and payment confirmation materials (such as receipt screenshots or PDF files) that the client may optionally attach to confirm payment. Conversation IDs and participant identifiers required for delivery and dispute context. Voice messages require access to your device microphone when you choose to record. Photos and files you attach are uploaded to our cloud storage for delivery to the other participant.
Important: Advia does not operate as a bank, payment service provider, or card acquirer. Financial settlements for collaborations are arranged directly between users. Advia does not hold, move, or guarantee funds unless a separate explicit payment integration is introduced and disclosed.
3.5Feed content and community activity
Content you publish: posts (text, photographs), videos and Reels, stories (AD's), events (title, description, date, place, address, city, price, links), captions, hashtags, a place label, selected music, and the media files themselves, which are stored in our cloud storage. Interactions: comments and replies, likes (stored as a list of user IDs on the post or comment), reposts, event interest ("going"), and follows (who follows whom). Your published content, comments, your name, your profile photo, and follow relationships may be visible to other signed-in users of the App. Stories are temporary and are removed automatically after a limited period.
3.6Views, activity, and achievements
When a video plays in the App for a short time (currently two seconds), we record one view for that post per person: we store your user ID under the post so that the same person is not counted twice, together with the total view count. The post's author sees only the totals, not who viewed. We also keep an activity list for each user (for example, "someone liked your post", "someone followed you"), which contains the name and profile photo of the person who acted, a short excerpt or thumbnail of the post, and the time. When a post or account reaches certain round numbers of views, likes, or followers, we create an achievement entry, show a congratulation screen, and may send a push notification.
3.7Personalization signals on your device
To suggest relevant videos (Reels), the App learns from what you do: what you watch to the end, skip, like, comment on, or repost, and the authors and hashtags involved, as well as which videos you have already seen. These personalization signals are stored on your device, are not sent to our servers, and are removed when you uninstall the App. The order of the general feed also uses public data such as freshness, likes, comments, and whom you follow.
3.8Announcements (campaigns)
Announcements you publish (title, description, budget, requirements, category), responses that bloggers submit, and the discussion attached to an announcement. Announcements and responses may be visible to other users of the App.
3.9Verification
Advia offers an optional but strongly recommended identity verification flow for bloggers and businesses, designed to reduce impersonation and fraud and to confirm genuine control of the declared account or company. For bloggers we process: the social platform selected (Instagram, TikTok, YouTube, or Telegram), the public username or handle on that platform, a contact email address for YouTube only (used solely to deliver a one-time verification code when the platform requires it), follower or subscriber counts you self-report or that are retrieved automatically, the verification request status (pending, code sent, confirmed, or rejected), generated one-time codes, attempt counts, and timestamps.
For businesses we process: company information you submit and supporting documents you upload (for example, registration documents or proof of control of official accounts), the request status, and the reviewer's decision. Uploaded documents are used only to review your request and are accessible only to you and our authorised administrators.
Verification confirms account or company control at the time of the request. It is not a commercial endorsement, a guarantee of audience authenticity beyond the checks performed, a financial recommendation, or legal advice. A verified badge may be revoked if evidence of misrepresentation is found. After successful verification a limited free period may be granted; its start date is derived from the verification date.
3.10Plans, credits, and purchases
We offer monthly subscription plans and other digital purchases (such as additional credits, event publication beyond the free allowance, and promotional placement). Transactions are processed entirely by Apple (StoreKit) or Google (Play Billing). We do not store your card details.
We receive and keep transaction identifiers, purchase tokens, product identifiers, subscription status and expiry dates, and confirmation from the store, which our server verifies with Apple or Google before activating a feature. We also store your plan level, credit balance and usage, the conversation used for your monthly free contact, and a purchase audit record that we retain for fraud prevention and accounting.
3.11Tools and AI features
When you use tools we process what you enter or select for that request: text and parameters sent to the AI assistant, creator search, script generator, and translation (which are processed by third-party AI providers, including OpenAI); links you provide to the media downloader (processed on our servers to retrieve the media); and a public social username you enter into the profile analyzer (processed on our servers and through a third-party provider of public social media data). We also store your usage counters for daily limits. The video editor works on your device: projects and media stay on your device unless you publish or share them, and the music library is downloaded from our storage. Saving an exported video to your photo library asks for photo library access.
Do not enter information you do not want processed by these services.
AI Studio (photo trends, AI video, stories and films, Free mode, Promo video, songs and music, voiceover, hooks and auto-editing) and the Auto captions, Shorts clipper and Content plan tools send what you choose for a request (photos, product photos and app screenshots, video frames, the audio track of a video, text, song lyrics and settings) to AI providers that process it on our behalf: Google Cloud Vertex AI (Gemini, Veo and Lyria models) and Runware, Inc., an AI generation platform that passes the request to the developer of the model used for it (for example Google — Gemini Omni and Veo, Alibaba — Wan, Kling, HeyGen and Pruna AI). Google Cloud processes requests in the European Union, except AI video generation and songs, which Google currently offers only through a global endpoint or in the United States. Runware and the model developers may process requests in the United States, the European Union and other countries, including China. If Runware is unavailable, the request is processed by Google Cloud instead. These providers use your content only to create the result you requested; Runware keeps generated files for up to 7 days to deliver them to us. Songs, covers and lyrics are saved in your account (My songs) and, like other results, are stored so you can open them again, until you delete them or your account.
Before your first use of an AI feature, the App asks for your consent to send your content to these AI providers for processing; you can withdraw this consent in Settings. Photos you choose may show faces and are used only as a likeness reference to generate the result you request; we do not create or store biometric templates or face-recognition data. Source files you upload for processing are deleted when the job finishes and, in any case, no later than 30 days after upload. Generated results stay in your account until you delete them or delete your account.
3.12Reports, blocking, and moderation
Reports you submit (the reported content or user, the reason, and an optional comment), the list of users you have blocked, and moderation records such as warnings, restrictions, and bans, including whether they were issued automatically or by our team.
3.13Push notifications
Device push token (APNs on iOS, FCM on Android), and your per-category notification preferences (messages, order updates, activity such as likes at round numbers, comments, follows, reposts and achievements, and marketing). Notifications may contain names, message excerpts, and counts. Notifications about your plan or free period are sent to accounts that have one.
3.14Device permissions
The App asks for access to your camera, photo library, and microphone only when you use a related feature (for example, attaching a photo, recording a voice message, or creating a video), and for notifications when you choose to receive them. We do not collect your precise device location; places you enter or choose for events and posts are text you provide.
3.15Technical and diagnostic data
Device model, operating system version, app version, anti-abuse and fraud-detection signals, and usage events (such as screens viewed) that may be collected through Firebase Analytics using an app instance identifier. We do not sell your personal data for money. Advertising is described in Section 3.17.
3.16Infrastructure and third-party services
The App is built on Google Firebase, including Firebase Authentication, Cloud Firestore, Cloud Storage, Cloud Functions, and Firebase Cloud Messaging. When you use AI features, the content you submit may also be processed by OpenAI and other third-party AI providers in accordance with their privacy policies. We use email delivery providers to send codes and service messages and internal administration tools (including messaging services used by our team) to review verification requests, reports, and purchases. Google's Privacy Policy and Terms of Service apply in addition to this Policy. Apple and Google also process data as part of account sign-in and in-app purchase flows under their own policies.
3.17Advertising
The App shows ads through Google AdMob: a native ad after every few Reels and small banners between posts in the feed. To show and measure ads, prevent fraud and, if you allow it, personalise ads, Google AdMob receives from your device your advertising identifier (Advertising ID on Android; IDFA on iOS if you allow tracking), approximate location derived from your IP address, device and app information, and your interactions with ads. Google processes this data as an independent controller under its own policy (policies.google.com/technologies/ads). In the European Economic Area, the United Kingdom, Switzerland and other regions where the law requires it, the App asks for your consent in a Google consent form before any ad is requested; on iOS it also shows Apple's tracking prompt. You can change your choice at any time: in Settings → Ad options (where the form applies), in your device settings (Android: Settings → Google → Ads; iOS: Settings → Privacy & Security → Tracking) or at adssettings.google.com. If you decline personalisation you still see ads, but they are not tailored to you. We do not give advertisers your name, email address, chats, photos or other content.
3.18Partner programme payouts
If you take part in the partner programme and request a payout, you enter the number of a Visa or Mastercard bank card and the cardholder's name. We store the full card number and name on our servers, in a database that the App and other users cannot read, and use them only to transfer your payout. We do not ask for or store the card's expiry date or CVV. You can remove the card in the App at any time, and it is deleted together with your account. Records of payouts made are kept for accounting without your name, username and card digits.
4HOW WE USE YOUR INFORMATION
We use your information to: create and manage your account; provide and improve all App features; deliver and store chat messages, voice messages, photos, and file attachments; provide optional AI-powered chat translation and other AI features; publish and display your content and interactions; count views and detect achievements; suggest relevant content; process and display announcements, orders, and reviews; operate the verification systems; deliver push notifications you have requested; verify purchases and activate entitlements, credits, and free periods; detect and prevent fraud, abuse, and policy violations; moderate content and act on reports; comply with legal obligations; and for legitimate business interests balanced against your rights (such as security monitoring and service analytics). We also use your advertising identifier and ad interactions to show and measure ads (Section 3.17).
5SHARING YOUR INFORMATION
Other users. Your public profile, published content, comments, likes on public content, follow relationships, ratings, and reviews are visible to other signed-in users of the App, and content you share outside the App is visible to whoever receives it.
Service providers. We share personal data only with processors strictly necessary to run the App (Google Firebase, Apple, Google, OpenAI and other AI providers when you use AI features, email delivery providers, and providers of public social media data when you use the profile analyzer or statistics). We do not sell, rent, or trade your personal data to third parties for their own marketing purposes. We may disclose data if required by law, court order, or to protect the safety of users.
Advertising partners. Google AdMob receives data from your device to show and measure ads, as described in Section 3.17. We never give advertisers your payout card details or your content.
6INTERNATIONAL DATA TRANSFERS
Your data may be processed on servers located outside your country of residence, including in the United States, due to our use of Google Firebase infrastructure and AI providers. Where required by applicable law, we rely on appropriate transfer mechanisms such as standard contractual clauses. AI video and song generation in AI Studio is processed by Google in the United States or through Google's global endpoint, and requests sent through Runware may be processed by Runware and the model developers in the United States, the European Union and other countries, including China.
7DATA RETENTION
We retain your personal data for as long as your account is active and as necessary for the purposes described. Views are kept as long as the post exists. Purchase audit records are kept for fraud prevention and accounting for as long as the law and our legitimate interests require. Upon account deletion, data is removed or anonymised as described in Section 8, subject to legal retention requirements and residual aggregated statistics.
8ACCOUNT DELETION — WHAT IS DELETED AND WHAT IS NOT
You may delete your account at any time from the App settings. After re-authentication (required by platform security rules), the following deletion sequence is executed:
What we DELETE:
- Your posts, reposts and stories, the media files attached to them, all comments under your posts, and the comments you wrote under other users’ posts.
- Your AI Studio data: generation jobs and prompts, generated videos, images and audio, and the files you uploaded for processing.
- Your Firestore user document (users/{uid}), which also removes your plan, credit balance, and settings stored in it.
- Your Firebase Authentication user record.
- Your blogger profile document(s), including any legacy documents where the profile references your user ID even if the document ID differs.
- Your public directory entry.
- Your profile photo object in cloud storage (avatars/{uid}.jpg or equivalent path).
- All verification request documents associated with your user ID.
- App-side subscription and entitlement records tied to your user ID (this does not affect Apple or Google billing records, which are governed by their own policies).
- Favorites where you are listed as the client.
- Reviews you wrote as the reviewing client (deleted by client ID).
- Your personal offer document keyed by your user ID, if present.
- Personal broadcast message rows stored under your user document.
- The email-to-role hint document used during registration, where applicable to your email address.
- Your device push token is revoked and the fcmToken field is cleared from your user document BEFORE the user document is deleted, so no further push notifications are sent to a deleted account.
- Local notification preferences, personalization signals, and broadcast read-state stored on your device by the App are removed when you uninstall the App.
What we DO NOT DELETE automatically (or only archive):
- Events and announcements you published, and likes you gave. Anything that remains after your account is deleted will be deleted or anonymised on request sent to advia.app.admin@gmail.com, no later than 30 days after we receive it.
- Chat message history is generally preserved for the other participant. Conversations are marked inactive or archived rather than erased, so that the counterpart retains a record of legitimate collaboration and dispute context. Name and avatar snapshots in conversation metadata may persist until updated by system rules.
- Reviews about you written by other users may remain where they do not fall within the client-review deletion path keyed to your client ID, or where retention is required by law or platform integrity.
- Purchase audit records kept for fraud prevention and accounting.
- Aggregated and de-identified analytics.
- Billing records held by Apple or Google under their own policies.
- Any data we are required to retain by applicable law.
9YOUR RIGHTS
Depending on your jurisdiction, you may have rights to access, rectify, erase, restrict processing of, or obtain a copy of your personal data, and to object to or withdraw consent for certain processing. Contact us at advia.app.admin@gmail.com. You may manage notification preferences in the App and in your device settings at any time, and you can reset your personalization by uninstalling the App.
10SECURITY
We implement appropriate technical and organisational security measures. You are responsible for keeping your login credentials confidential and for securing access to your device.
11CHANGES TO THIS POLICY
We may update this Policy from time to time. The effective date at the top will be revised. We will notify you through the App or by email when changes are material, where required by law.
12CONTACT
Advia
Privacy inquiries: advia.app.admin@gmail.com
Support: advia.app.admin@gmail.com