Fondly mobile Privacy Notice
Effective October 26, 2026 · Immutable version fondly.native-terms-privacy.2026-10-26.v1
Scope and operator
Loma Studios LLC operates Fondly. This notice describes the Fondly iOS and Android fictional AI character and story experience. It replaces the earlier local quiz-card description for this experience. Website analytics and website purchase rules remain separate. Contact support@amorist.ai for questions, privacy requests, or deletion assistance.
Account, storage, and service records
Google Firebase Authentication processes account sign-in, including your email address and password for email sign-in. We do not store your full password in our account database. For the native age check, the date of birth you enter is sent to our service to check whether you are at least 18. We do not retain that date or a fingerprint derived from it. We store the resulting adult self-declaration and its time, accepted legal versions, and separate permission choices. This age check relies on the information you enter and is not identity verification. If Google or Apple sign-in is made available and you choose it, that provider processes the sign-in request and the profile information you allow it to return, such as a name, email address, and provider account identifier. Provider security and technical records can include device or app information and IP-derived general location. We do not request access to your contacts, phone number, or precise location for sign-in.
The app uses protected device storage for sign-in state, random installation identifiers, and permission preferences. Our service stores your profile, messages and AI replies, conversation references and dates, favorites, private fictional character details, personas, and saved memory so you can use those features across sessions. Operational records help prevent duplicate actions, apply limits, investigate reports, and secure the service. Providers also process technical connection information such as IP addresses, app or operating-system information, and request logs.
We retain your chosen profile name, optional profile selections, saved in-app search terms, story-mode preferences, and records of notices and permissions. Searches can be shown again as your recent searches. Favorites, personas, saved memory, and story preferences customize discovery and generated stories. Exact native birth dates are not retained; an adult age bracket can be retained when you choose it.
AI generation and safety review
Venice.ai and its inference providers process text to generate AI responses and check content safety. The text needed for the request can include your messages, relevant recent chat history, fictional character details, personas, saved memory, and generated responses. Opening saved content can require a safety check before it is displayed. Your sign-in email from account records, purchase details, and notification tokens are not included in these AI requests. Information you choose to type into a conversation can still be part of the submitted text; avoid highly sensitive information about yourself or another person.
The app asks separately for permission to share this text with the AI service. Declining or withdrawing that permission pauses AI features and saved content that requires an AI safety check; public browsing remains available. Requests already sent cannot be recalled. AI permission does not authorize optional analytics, advertising measurement, or notifications. We store account conversation history; no promise of zero provider retention or automatic deletion of every provider copy is made. We do not use your conversations to build a model-training dataset.
Reports and account deletion
When you report an owned conversation or AI reply, we store the reason, the conversation or reply reference, and service records needed to assess the report. Filing a report does not require AI-sharing permission and does not itself send the reported text to an AI provider. Authorized service operators can inspect reports and relevant content to assess safety and respond.
Account deletion removes the active account, stored conversations, favorites, private workspace content, and account-linked usage records through the service’s deletion process. Necessary billing, fraud-prevention, security, and legal records can be retained separately. Provider logs and backups may follow different retention cycles; deletion is not a promise that every provider copy disappears immediately. Account content remains while you keep the account unless deleted through the available controls. Contact support for applicable access, correction, portability, or deletion requests; a self-service data export is not included.
Store purchases and test records
Apple App Store or Google Play processes native payments. We use a store-issued purchase reference, an opaque account binding, product and period information, verified purchase or reversal status, and related delivery records to verify benefits, restore eligible purchases, and prevent duplicate delivery. We do not receive your full payment-card number from the store. Required transaction and reversal records may remain after account deletion for accounting, refunds, fraud prevention, and legal obligations.
Store testing may use separately identified test purchase facts, test memberships, and test balances. Test receipts and debug changes are not recorded as real customer revenue or added to live paid balances. Testing does not itself authorize optional measurement.
Optional notifications and device access
Notifications are optional. If you turn them on, the app requests the operating system’s permission and registers a random installation identifier, platform, device push token, permission state, and related registration information with our service. Apple Push Notification service delivers iOS notifications; Google Firebase Cloud Messaging delivers Android notifications. Notification content and technical delivery information are processed by those providers. Notifications may appear on your lock screen; use system settings to control previews.
Turn notifications off in the app or system settings. The app asks our service to withdraw its registration and stops requesting delivery; a notification already handed to a provider may still arrive. Permission or registration failures can prevent delivery. This app does not need your microphone, camera, contacts, precise location, or photo-library access for its current native features. Tapping support opens your email app so you can choose what to send; it does not automatically send an email.
Optional native usage measurement
Native optional measurement starts off. If it is made available, the app shows its current provider notice and asks for a separate per-account choice before enabling it. A general legal acceptance, AI permission, notification permission, or an earlier website choice does not grant this choice. You can decline or withdraw in Settings. Fresh service configuration and current permission are both required. Optional product-usage analytics and advertising attribution are separate purposes. Choosing usage analytics does not itself authorize advertising data sharing or personalization.
When separately enabled and allowed, Google Analytics for Firebase can receive generic app actions and screen categories, event times, app and device technical information, pseudonymous SDK installation or session identifiers, and general location derived by Google from a masked IP address. The SDK does not need permission to use the device’s precise Location Services to derive that general location. Its SDK may also collect automatic technical, app-session, and store-purchase events. Our selected event payloads do not include chat text, character names, interests, saved favorites, account email, direct account identifiers, passwords, or payment-card details. We may retain an internal link between the permission and your account to honor withdrawal; pseudonymous does not mean anonymous.
A separately configured server integration may associate provider-confirmed native purchases or refunds with the original permitted app context, including a generic product category, transaction reference, verified customer-paid or refunded amount, and currency when verified. Missing evidence can omit an event. SDK automatic events and store-test data are not a billing statement or a verified financial ledger. Testing, debug activity, and duplicate reports must remain separate from customer financial reporting. No purchase or revenue is inferred from opening checkout or returning to the app.
Withdrawing closes app collection and requests cancellation of unsent server events. Offline devices, provider processing, or an in-flight request can delay completion; already sent information cannot be recalled. SDK reset or permission withdrawal does not automatically erase all previously received Google data. Contact support about applicable requests. Provider retention and processing rules apply; we do not promise a fixed universal deletion period for optional native measurement.
Optional advertising attribution and sharing
Optional advertising attribution and sharing start off. If offered, the app presents a separate notice naming Singular and any advertising providers for the proposed purpose, and asks for your choice before enabling that purpose. On iOS, this app also requires authorization through Apple’s tracking permission before starting this optional device-level attribution or advertising sharing. Declining or an unavailable permission keeps it off and does not block the app. General legal acceptance, AI permission, notifications, and product-usage analytics do not grant these permissions. A changed provider connection does not override your choice; materially different purposes or recipients require an updated notice and choice.
With your applicable permission and a configured connection, Singular provides mobile attribution: measuring how people find and use Fondly. Starting its SDK sends an initial app session and can begin install attribution. It can process app opens, store visits, installation or session identifiers, device and app technical information, operating-system version, connection IP address, and general location inferred from that information. Available platform identifiers can include an app-scoped device identifier; an advertising identifier is used only where the app supports it and the required permissions allow it. IP addresses and pseudonymous identifiers remain personal data. We do not send Singular your messages, conversation history, character choices, personas, memories, interests, account email, or direct account identifier.
When this attribution purpose is permitted and the server integration is configured, we can also send Singular provider-confirmed purchase or refund records linked to a Singular-generated attribution identifier. A record can include the generic product, store transaction reference, event time, and actual verified amount and currency when known. An app-reported price or event does not establish a paid or refunded amount. Missing money information remains unavailable. Test, debug, and internal activity do not become real customer revenue. We keep attribution reporting separate from the original store payment records and avoid treating duplicate reports or parallel provider delivery as additional purchases.
Singular partner postbacks are disabled for this integration. We do not use an iOS tracking denial as permission to start alternative device-level matching or fingerprinting. Any later partner forwarding or materially different use of identifiers requires review, disclosure, and the applicable permission before it is enabled. Platform-generated aggregate attribution reports may be processed only where supported and permitted; this does not authorize device-level tracking for someone who declined.
A separately permitted server integration can send app opens, store visits, and provider-verified purchases to the Meta, TikTok, or Google destination named in its notice. A selected record can include a random installation identifier, app and operating-system versions, generic purchase product, verified amount and currency when known, transaction reference, and event time. A Firebase app-instance identifier is available to Google only when you have also independently allowed product-usage analytics. These selected server payloads exclude account email, direct account identifiers, advertising identifiers, IP addresses, and private conversation or workspace content. Allowing one optional measurement purpose does not by itself enable another.
You can withdraw the relevant permission in Settings. We stop future app collection for that purpose and cancel unsent server events when withdrawal is confirmed. An offline device or an in-flight request can delay completion; already sent information cannot be recalled. Stopping collection does not automatically erase earlier provider records. Contact support about applicable deletion or access requests. Provider processing and retention rules apply. Store-test, internal testing, and debug activity are excluded from real customer advertising and financial reporting. A delivery acknowledgment or an SDK event does not prove an attributed conversion, payment, or revenue. Missing payment amounts remain unavailable rather than being replaced by a catalog price.
Service providers and changes
Firebase provides authentication and service infrastructure. Venice and its inference providers process allowed AI requests. Apple and Google provide store and push services where used. Singular processes permitted attribution information on our behalf, with forwarding restrictions for this integration. Meta, TikTok, and Google process advertising records only for the separately disclosed and permitted integration. Providers may process information in more than one country under their own terms and privacy policies. We will version material changes to this mobile notice and ask for updated choices where required.
RevenueCat and current optional services
RevenueCat processes account-linked purchase history, transaction identifiers, products, periods, status, restores and refunds for subscription management, verification and purchase analytics. Customer records can include a transaction country or a country inferred from the last-seen IP address. RevenueCat states that it drops that IP address after determining country. Apple and Google process payment details; we do not receive full payment-card or bank-account details.
At this notice’s effective date, optional native usage analytics, advertising attribution, paid ad serving and push delivery are disabled by service controls. They are not enabled by accepting these terms or by granting AI permission. Each optional purpose requires its own current disclosure and permission before collection can begin.
For current Fondly support and privacy information, visit https://amorist.ai/fondly/support/ and https://amorist.ai/fondly/privacy/.
Combined document SHA-256: 9acd86a8fe1f83c0302a49d36b358a44680f45b9a4d854ff9f84ac804618476e
- Fondly mobile Terms v1
- Fondly mobile Privacy Notice v1
- Firebase privacy
- Google partner information
- Venice privacy
- Apple privacy
- Google privacy
- Meta privacy
- TikTok privacy
- Singular privacy
- Singular terms
© 2026 Loma Studios LLC · support@amorist.ai