Privacy notice

About this notice

Connected Media Inc operates Amorist, a fictional AI character service for adults. This notice covers our website and mobile apps. Features and service providers can differ by platform; the sections below explain those differences. Contact support@connectedmedia.co with questions or privacy requests.

Your account and preferences

We use Google Firebase Authentication for account sign-in. With email and password sign-in, Firebase processes your email address and password to authenticate you. We do not store your password in our own account database. If we enable other sign-in methods, the provider may also supply a name, profile picture and account identifier.

We save your confirmation that you are at least 18 and the versions of the Terms and Privacy notice you accepted. Age confirmation is a self-declaration, not identity or document verification. Adult accounts can choose fictional romance through their conversations; a separate romance-enable switch is not required.

If private favorite characters are offered, the characters you mark as favorites are saved privately to your account so we can show them to you again. Favorites are not shown to other people and are not used for public counts. We do not put your favorites into analytics events sent to Google Analytics, or into any advertising or attribution service. This feature may not be available on every platform or version.

Your browser stores sign-in state. The mobile app uses protected device storage for sign-in state. Signing out ends that local session. Service providers also process technical information, such as IP addresses and browser or device information, to deliver and protect the service.

Conversations and AI responses

We store your messages, AI replies, the characters you talk to, conversation dates and service records needed to show your history, apply access limits and avoid processing the same request twice. Avoid sharing highly sensitive information about yourself or another person.

If you report a conversation or reply, we save your chosen report reason and a reference to that conversation or reply to help assess service safety and accuracy.

For website character chat, we send your message, the character instructions and relevant recent conversation context to the Venice API and its inference providers to generate a response. This includes information you choose to put into your messages. We do not include sign-in credentials or payment-card records from our account and billing systems in these requests. Venice processes these requests under its own provider terms and privacy policy; this does not mean your history is absent from our service, where we store it for your account. Some other service versions may use Google’s paid Gemini API, whose paid API terms describe limits on training use and retention. We do not use your conversations to build a model-training dataset. Provider information is linked below.

Characters are fictional. Responses can be inaccurate and are not professional advice.

Optional website analytics

Optional website analytics is off until you allow it. You can change your choice at any time through Privacy choices. Your preference is stored in that browser; it does not automatically change choices on another browser or device.

We record limited actions, such as a landing-page visit, starting sign-in, opening a character, sending a message or opening checkout. Records include the action, screen, time, platform and a random session identifier. Our testing activity is marked separately. We do not put conversation text, character names or interests, email addresses, passwords or payment-card details into these analytics records.

When separately enabled and allowed under this notice, our first-party analytics measures observed time by screen and through checkout steps. We distinguish visible time with recent interaction from visible idle time and hidden or background time. Active engagement includes the initial visible period and up to 30 seconds after a click, key press, scroll or touch, or after the page becomes visible. We record bounded duration totals and a fixed screen category, not keys pressed, typed text, page text, raw addresses, payment details or a replay. A random visit identifier can continue across reloads in a browser tab; observed visits are not a count of people. Suspended devices, blocked requests, closing a page and our collection limits can leave gaps, so reported durations are observed and may be incomplete. These duration records stay in our first-party reporting and are not sent to Google Analytics or advertising providers. Earlier analytics choices do not automatically authorize this purpose: it requires a fresh choice under this notice. Withdrawing analytics stops duration collection as well.

If optional website heatmaps are enabled and you allow analytics under this notice, we collect coarse click positions and maximum scroll depth on public browsing and purchase-information pages. We group clicks into a 20 by 20 grid relative to the visible browser window and separate broad mobile, tablet and desktop sizes. We batch and limit samples, and our private operations dashboard shows aggregate counts. We do not record mouse movements, replay sessions, take page screenshots, read typed input or collect page text for heatmaps. Chat, private profile and workspace pages, input fields and dialogs are excluded. These first-party heatmap samples are not sent to Google Analytics or advertising providers. The same optional-analytics choice and browser withdrawal controls apply. Samples are incomplete and do not identify how many people visited or which page element was clicked.

Before sign-in, optional first-party analytics covers public browsing, purchase-information pages, sign-in steps and their observed durations when enabled. Google forwarding remains limited to the selected actions described below. Identifiers are pseudonymous: they do not directly name you, but they are not a promise of anonymity. Once you sign in, we may link activity records to your account in our own records.

If Google Analytics is turned on for the website and you allow analytics in this browser, Google Analytics stores and reads first-party cookies, including _ga and related _ga_ cookies, to distinguish browsers and sessions. We also store your analytics choice, the notice version it applies to, and a random identifier for that choice in your browser’s local storage. That identifier lets us honor a later withdrawal, is shared by this browser’s tabs, and is never sent to Google. Google’s website measurement tool then records limited visit, browser, device and technical connection information, and our servers may send selected actions you take in this browser, such as sign-up steps, a first reply, or checkout steps, that Google can associate with that visit through the same cookie-based client and session identifiers. For a web credit-pack checkout begun after you allow this version of optional analytics, we may also send Google Analytics provider-confirmed purchases and refunds associated with that checkout, including currency, verified customer-paid and refunded amounts, tax where known, a generic credit-pack category and a random-looking transaction reference. This helps us measure checkout outcomes and customer cash received and refunded; it is not a report of our profit or settlement proceeds. We keep the checkout’s original browser client identifier and permission snapshot for up to 90 days to associate later verified refunds with that same checkout, never with whichever browser most recently signed in. We do not attach a web session to server-confirmed financial events or claim they occurred during an active visit. Withdrawing optional analytics cancels this linkage and unsent events. Purchases begun without this permission, mobile purchases, subscription renewals and account-wide cancellation or expiry are not sent through this web measurement. A financial event may be omitted if we cannot verify its linkage, timing or amount; Analytics is not your billing statement. These identifiers are pseudonymous, not anonymous. We remove conversation references, character interests and extra URL details from page addresses and titles sent to Google, and we do not send Google Analytics your chat text, character names or interests (including any saved favorites), email address, direct account identifier or payment-card details. The website tag is set not to use Google signals or advertising personalization, we do not send Google hashed email or other user-provided data, and allowing analytics is not consent to advertising. To learn how Google uses information from sites or apps that use its services, see “How Google uses information from sites or apps that use its services” (https://policies.google.com/technologies/partner-sites), also listed under Provider information.

Google Analytics runs only when the website is configured to use it and you have allowed analytics in your browser. Until both are true, the website does not load it and our servers do not send it events. Advertising measurement, when enabled, has separate provider notices and choices. Analytics permission does not authorize advertising measurement. Mobile apps do not currently send optional analytics or advertising-attribution events. If we add mobile analytics or advertising attribution, we will explain the provider, information and choices before enabling collection.

The Google Analytics property is configured to retain event-level data for 2 months and user-level data for 14 months, with the user-retention period reset by new activity. These settings do not apply to every standard aggregated report and do not determine how long we keep account or conversation records.

Withdrawing permission clears unsent optional events in that browser and stops future optional events from it, including in its other open tabs. Where our servers send selected actions to Google Analytics, withdrawing also asks our servers to stop sending events that have not yet been sent. If your device is offline or our servers are unavailable when you withdraw, your browser keeps the request and retries it for a limited time; a retry is not guaranteed to arrive in time. A withdrawal cannot recall an event already being sent or information already received by us or Google, and we do not automatically delete information from Google Analytics when you withdraw or delete your account. Clearing browser storage resets your local preference. Contact us about applicable access or deletion requests for information already received.

Purchases

Available offers, prices, currency and billing periods are shown before checkout. The seller and payment recipient for website purchases is Jacob Gordon, trading through the Amorist service. Stripe processes website payments and payment-card details. Charges use the Amorist descriptor shown at checkout; one-time purchases may also show the shared CASINOAI statement prefix. Mobile purchases, when available, use the app store displayed at checkout.

Stripe processes billing information, including an address or location where required, to calculate applicable tax. We use your account identifier, original checkout and subscription references, verified amounts, currency, tax and payment status to deliver memberships, message credits, coins, diamonds and purchased content and to prevent duplicate delivery. We do not store your full payment-card number.

Purchases are linked to your service account so we can restore or verify them. We retain the original purchase, credit-delivery and reversal records needed for accounting, tax, fraud prevention, refunds and legal obligations, including after account deletion where necessary. Manage a subscription through its original payment provider. Deleting your service account does not automatically cancel a provider-managed subscription.

Mobile device access

Current mobile app features do not request your microphone, camera, contacts, precise location, photo library, notifications or advertising identifier. The app does not automatically send an email when you tap Support; it opens your email app so you can choose what to send.

The app keeps sign-in state in protected device storage. Conversation and profile data are loaded from the service; there is no app-managed offline conversation library in this version. Device operating systems and app stores can separately process information under their own policies.

Deletion and retention

You can request account deletion in Account → Delete account. When deletion completes, we remove the active account, stored conversations, saved favorite characters (where offered), and account-linked usage and optional analytics records. Necessary billing records may be retained separately. Provider logs, backups and records required for security or law may follow different retention cycles. Deletion does not guarantee that every provider copy disappears immediately.

Account and conversation records remain available while you keep your account, unless you delete a conversation or request account deletion. We do not promise a fixed deletion schedule for required financial or security records. We retain those only for the purpose that requires them.

Where applicable, you can request access, correction, deletion or portability of your personal information, or raise a privacy concern. A self-service data export is not included in this version; contact support@connectedmedia.co for requests.

Service providers and changes

Firebase supplies account authentication, hosting and database infrastructure. Enabled AI and payment providers receive the information needed to perform their functions. Provider infrastructure may process information in more than one country.

We will keep this notice aligned with the service. We will tell you about material changes as appropriate and identify the updated version and effective date.

Provider information

How Google uses information from sites or apps that use its services

Google paid Gemini API terms

Firebase privacy information

Google Analytics retention information

Stripe privacy policy

Venice API privacy information

Venice privacy policy

Separate advertising privacy notice

Contact

Contact Connected Media Inc at support@connectedmedia.co.