Riffanta - Privacy Policy
Last Updated: October 26, 2026
Riffanta (package name: com.riffanta.aimagic) is operated by GiggTech LLC. Handling your information responsibly matters to us, and this Privacy Policy lays out what the App gathers, why it gathers it, and how that information is protected while you create with Riffanta ("Riffanta" or "the App").
Installing and using Riffanta means you accept this Privacy Policy. If anything below does not sit right with you, please stop using the App.
1. What the App Collects
A plain-language picture first — much of what powers Riffanta never reaches our servers at all:
What stays off our servers:
- No Sign-Up, No Personal Details: There is no account to create and no email address, name, or other personal detail to hand over. The moment you first open the App, an anonymous guest session is set up on your device and you can start creating immediately.
- Your Creations Stay Yours: The images and videos Riffanta produces for you are not permanently collected, stored, or shared on our side.
- No Real-World Identity: We never ask for — and never collect — identifiers like your name, email address, or home address.
What the App does handle:
- Device Identifier: The service needs a stable, non-personal handle for your device. We build one by combining the Android-supplied ANDROID_ID with the App's package name and running the pair through a one-way MD5 hash — the output cannot be linked back to you. If ANDROID_ID is not available, a random UUID persisted on the device takes its place. A Firebase Installation ID acts as an additional anonymous marker for service operation. Where an install is traced to one of our direct Meta campaigns, a Facebook SDK anonymous device identifier is used as well (Section 7 explains).
- Guest Session: That device handle automatically seeds an anonymous guest session on first launch. It keeps convenience features working — your creation history, for example — without any registration, and it contains nothing personally identifiable.
- Device Information: Basic technical facts about your device (such as model, operating system version, screen resolution, language, and timezone) help us keep the App running well across the very different devices our users hold.
- Usage Data: We note which features you use and how often, which tells us what to improve and where your preferences lie.
- Advertising Identifier: Your Google Advertising ID (GAID) may be read for advertising attribution. When "Limit Ad Tracking" or "Opt out of Ads Personalization" is switched on, we skip it. You can reset the ID whenever you like in device settings.
- Audio Data: Choosing the in-app recorder means we receive the audio you capture with the microphone — captured only while you are actively recording and used only as custom audio (for example, background music) for the AI video you request. Section 3 has the full picture.
- Push Notification Data: Notification identifiers let service messages (such as generation progress) reach your device. Turn notifications off at any time in settings; the App's core features do not depend on them.
2. When You Upload Photos or Videos
Some creation modes begin with a photo or video you provide. Here is the life cycle of that file:
- What It Is Used For: The upload drives the generation — the styled image or video is computed from the media's attributes. Files travel to our servers over an encrypted connection.
- Short-Lived Processing: Both the upload and the generated result sit on our servers only while processing requires, then are deleted automatically.
- Nothing Kept: We hold no permanent copy of what you upload, and no personal details attached to it.
3. In-App Audio Recording
An optional recorder inside Riffanta lets you capture a brief clip (at most 5 seconds) and attach it as custom audio — background music, say — to an AI video:
- Permission on Demand: The microphone permission is requested at runtime, only at the moment you use the recording feature, and you may deny or revoke it whenever you like in device settings.
- When Recording Happens: Only your explicit action starts the microphone, only in the foreground, and only for the clip you are recording. Nothing listens in the background.
- Purpose: The clip serves as an audio input — custom audio such as background music — for AI video generation.
- Upload: Once you confirm the recording, the file is uploaded over an encrypted connection and consumed during generation.
- Temporary Storage: Server-side copies exist only for processing and are deleted when processing completes.
- No Biometrics: Recorded audio is never used for voice recognition, speaker identification, or any other biometric analysis.
- Local Cache: During the recording session the clip is cached on your device; clearing the App's data in device settings wipes it.
4. Facial Data Processing
When a photo or video you upload contains faces, Riffanta processes a limited set of facial signals to power its AI image and video features:
- What Is Processed: Facial landmarks (eye, nose, and mouth positions) and feature details such as contours and proportions, drawn solely from media you voluntarily upload.
- What It Is For: Producing personalized, high-quality images and videos, keeping visual effects aligned correctly, and improving the accuracy of generated content.
- How Long It Stays: Processing happens on encrypted servers, strictly for generating your result, and the data is deleted automatically once that completes — usually within 24 hours.
- Sharing: None. Facial data is never shared with third parties.
5. Our Use of Data
The information described above goes toward:
- App Operation: Delivering the features you expect and keeping them working.
- Notifications: Service messages about your generation tasks and app updates.
- Improvement & Updates: Usage patterns steer bug fixes, refinements, and new features.
- Security: Defending against fraud, abuse, and unauthorized access.
- Attribution & Analytics: Learning how users find the App and how campaigns perform.
We do not sell, rent, or share your personal information with third parties for their own marketing.
6. Purchases and Subscriptions
When you buy credits or subscribe inside the App:
- Transaction Data: Purchase tokens, product identifiers, order IDs, and subscription status are collected so purchased content and services can be verified and delivered.
- Payment Processing: Google Play Billing handles every payment. Card numbers, billing addresses, and other financial details never pass through our hands — Google's privacy policy covers that side.
- Subscription Status: We record where a subscription stands (active, expired, cancelled) so premium access is granted correctly.
- Data Retention: Transaction records live as long as providing the service, meeting legal obligations, and resolving disputes require.
7. Third-Party Services in the App
Functionality, analytics, and user experience in Riffanta lean on these services:
- Google Play Services: App distribution, in-app purchases, and subscription management. Google's privacy policy governs the data Google Play collects.
- Google Play Billing: In-app purchases and subscriptions; purchase tokens and transaction data flow through Google Play.
- Firebase Analytics: Anonymous usage statistics and app-usage patterns; Firebase may gather device information, usage data, and anonymous identifiers. For details, see Firebase Privacy Information.
- Firebase Installations: Generates the unique, anonymous installation identifier used in service operation.
- Firebase Cloud Messaging (FCM): The transport behind the App's own push channel (generation status updates, service announcements). Notifications can be switched off any time in device settings. See Firebase Privacy Information.
- Google Play Install Referrer: Tells us how the App was installed (install attribution); used only for attribution and analytics.
- Google Advertising ID: Read for advertising attribution only, and never when "Limit Ad Tracking" is on.
- Facebook SDK (Meta): Reserved for measuring installs from our direct Meta (Facebook) campaigns. Out of the box it is disabled and fully dormant — no initialization, no reports — and it wakes only when an install is identified as a direct campaign. Once active it reports the install/activation event and an anonymous device identifier to Meta; that identifier also goes to our backend and pairs with Meta's server-side Conversions API for conversion measurement. Purchases are reported server-side only. No Facebook login, sharing, or deep links. Details: Meta Privacy Policy.
Each service maintains its own privacy policy for the data it collects — we encourage you to read them.
8. Marketing Attribution and Analytics
To understand our marketing and improve the service we may gather:
- Attribution Data: Install referrer information, advertising identifiers, and anonymous device fingerprints (device model, screen resolution, language, timezone, network type) used for marketing attribution.
- Direct-Campaign Attribution (Meta): Where an install is identified as coming from a direct Meta campaign, the Facebook SDK may activate to report the install/activation event and an anonymous device identifier to Meta for conversion measurement; every other install leaves it dormant and silent.
- Analytics Data: Anonymous usage statistics, feature interactions, and performance metrics through Firebase Analytics.
- IP Address: Your IP address may be collected temporarily for attribution; it is not used to identify you personally.
- Opt-Out: Limit ad tracking in device settings (Settings > Google > Ads > Opt out of Ads Personalization) and reset your advertising ID whenever you wish.
9. How Data Is Shared
We do not sell, trade, or hand over personal data to third parties for their own marketing. Anonymized, aggregated data may go to the Section 7 services, strictly for the purposes described here. Legal requirements or the protection of our rights may also warrant disclosure.
10. Safeguards
Safeguards we apply to your data:
- Transmission is encrypted (HTTPS)
- Server storage used for temporary processing is encrypted
- Access controls and security monitoring are in place
No system can promise perfect security. We take every sensible precaution, but anything sent across the internet carries some inherent risk.
11. How Long We Keep Data
Data lives only as long as the purposes in this policy require:
- Uploaded media, audio recordings, and facial data: Gone automatically after processing — typically within 24 hours.
- Device identifiers and session data: Around for as long as you keep using the App.
- Transaction records: Kept as applicable laws and dispute resolution demand.
- Analytics data: Held in aggregated, anonymized form.
12. Children
Riffanta is not aimed at children under 13, and we do not knowingly collect their personal information. Let us know if you believe a child's data reached us and we will delete it promptly.
13. Rights You Hold
Over your data, you hold these rights:
- Access & Control: Review what we collect; ask for corrections or deletion.
- Data Deletion: Email us (address below) to have your data deleted. Since images, videos, and personal information are not permanently stored on our side, there is little to manage — most of your data lives on your device.
- Opt-Out of Tracking: Limit ad tracking in device settings and reset your advertising ID at any time.
- Notification Settings: Push notifications can be toggled on or off whenever you like.
- Subscription Management: Google Play Store account settings are the place to manage or cancel subscriptions.
- Uninstall: Quit the App any time to end data collection; uninstalling wipes everything stored locally.
14. Cross-Border Processing
Processing may happen on servers outside your country of residence. Wherever your data goes, appropriate safeguards travel with it.
15. Policy Revisions
As our operations, features, or legal duties change, this Privacy Policy may be revised and the "Updated Date" at the top will move. Come back now and then to stay current.
16. Getting in Touch
Questions or concerns about this Privacy Policy or our data handling? Reach us:
Registered entity: GiggTech LLC
Email: venitademerevhh72@gmail.com