Cookie policy

Your analytics choice

Use Manage analytics on this page to allow or refuse usage measurement at any time. Not now means analytics is off. Closing a notice, browsing or starting a chat does not count as permission. Your choice applies to this browser; choose separately on another device.

Ariola stores your choice, policy version and date in local storage as chatw.analyticsConsent.v1, with no automatic expiry. When you enter chat, we also save that choice against your anonymous account. If browser storage is blocked, your choice still applies for the current visit but may not survive a reload.

Withdrawing permission stops future analytics collection and removes accessible Google Analytics cookies on this site. It does not undo information already sent to Google or delete the separate storage needed for chat and notifications. A material change to the analytics notice requires a new opt-in; previous refusals remain off.

Cookies: language and optional analytics

Ariola sets ariola_language when you choose a language. This first-party preference cookie contains a language code, not your nickname or account ID. It lasts 365 days and is renewed when your saved preference is restored or changed. You can change the language in the language selector or delete the cookie in your browser.

Only after you allow analytics, Google Analytics uses first-party cookies named _ga and _ga_* to distinguish browser visits and sessions. Ariola configures new analytics cookies to last up to 365 days from creation, without extending that period on each page load. Your browser may remove them sooner. Refusing analytics removes these cookies; accepting again can create new ones.

Analytics helps us understand screens visited and use of controls and features. It involves online identifiers and technical information about your browser and device. Advertising storage, advertising personalization and Google signals are disabled in the website configuration. We do not run an advertising pixel in the current website.

Preferences kept on your device

Ariola uses local storage for your chosen language (ariola.language.v1), theme (ariola.theme.v1), appearance and motion choices (ariola.atmosphere.v1, ariola.atmosphere-effects.v1 and ariola.chat-smoke-motion.v1), and dismissal of the App Store suggestion (ariola.app-store-badge.dismissed.v1). These remember the choices you make and have no automatic expiry. Change them using the corresponding control, where available, or remove them through your browser's site-data settings.

The local profile draft, chatw.profile.v1, remembers your nickname and any optional profile details. Per-account ariola.chat-experience.v1 entries remember your selected conversation, navigation state and unsent text drafts. These are stored by Ariola in your browser without automatic expiry. Editing your profile or draft updates them; clearing site data removes them.

Chat session, local message cache and delivery

When you enter chat, Google Firebase Authentication stores an anonymous sign-in session in browser storage so the same browser can reconnect to its account. This session persists across browser restarts. Clearing site data can end that session and may prevent you from returning to the same anonymous account.

Google Cloud Firestore also uses an IndexedDB database on your device to cache data the app has loaded, which can include public and private messages. The cache is not automatically cleared when you close the tab or browser; the SDK manages cache eviction without a fixed time limit. Use a trusted device for chat, especially for private conversations, and clear site data after using a shared device.

Firebase's SDK may also keep diagnostic dates and SDK-version information in firebase-heartbeat-database. It keeps at most 30 pending daily records, removes reported entries and retains the last reporting date, with no fixed expiry for the database. This supports Firebase service diagnostics and is separate from optional Google Analytics.

Ariola stores pending message delivery identifiers (ariola:send:* and ariola:image-send:*) to avoid duplicate sends after an uncertain response. Text delivery records include the submitted text and destination in their storage key. Successful delivery removes these records; unresolved attempts can remain until you clear site data. Image and audio allowance entries (ariola:image-allowance:* and ariola:audio-allowance:*) remember upload cooldowns without automatic storage expiry. If Spark Studio is enabled, pending redemption records (ariola:spark-purchase:v1:*) remain until resolved or cleared.

Temporary choices and browser notifications

Ariola keeps age confirmation (ariola:entry-age-confirmed) and dismissal of the notification prompt (ariola:notification-prompt-dismissed) in session storage. These normally last for the tab's session; browser session restoration can retain them.

Browser notifications require your explicit action and the browser's permission. Ariola and Google Firebase Cloud Messaging then use a push subscription, service worker and IndexedDB records to deliver alerts. Ariola's ariola-notifications-v1 database keeps notification settings and account-routing information; Firebase keeps messaging and installation identifiers. These records have no fixed browser-side expiry and can remain after permission is revoked. Use your browser's notification permissions to block alerts and its site-data controls to remove stored records.

Firebase Installations can also create an IndexedDB identifier when you accept analytics. The identifier may be shared with requested notifications, so withdrawing analytics does not automatically delete it. Google retains the server-side installation ID until deletion is requested through its service; this is separate from removing your browser's copy.

Providers and other services

Ariola manages its own preference and delivery storage. Google provides Firebase hosting, authentication, Firestore, file storage, functions, optional analytics and requested push messaging. Your browser vendor also operates the browser's push service. Hosting and service requests involve network information, including an IP address, independently of analytics consent.

Google Cloud Vision, Vertex AI and Google Cloud Translation process supported media safety checks, voice transcription and incoming-message translation on the server. Those functions are separate from optional website analytics and do not require an analytics cookie. The Privacy Policy describes this processing. Links to the App Store or other websites take you to providers with their own policies.

Clearing storage and contacting us

In your browser settings, look for site data for ario.la. You can delete cookies, local storage and IndexedDB records, or block storage. Clearing cookies alone may leave local storage and databases intact. Clearing all site data resets preferences and consent, removes drafts and cached data, and can interrupt chat or notifications.

Removing browser data does not delete messages or other records held by the service, and withdrawing analytics does not request account deletion. For privacy questions or requests concerning your service data, contact ⁨ariola.support@gmail.com⁩. This policy covers the website; native app storage is separate.