개인정보처리방침

English summary

New AICrush versions require Firebase sign-in to use the app. iPhone supports Google and Apple, while the web supports Google. Existing guest records are retained when that guest ID is linked to a provider; records from separate accounts are not automatically merged. An Apple-only iPhone account can connect Google in iPhone settings to use the same Firebase account on the web. When you chat, Zrindy authenticates your Firebase ID token and sends the selected fictional adult character, up to eight recent messages, and bounded memory and relationship context to an AI provider to generate a reply. Consent version 3 or later permits AWS Amazon Bedrock (US region, Google Gemma models), with OpenAI as a fallback. Earlier OpenAI-only consent never routes to AWS. Firebase ID tokens are not sent to AI providers. Bedrock uses a dedicated project with no input/output retention and does not train on your conversations. OpenAI may retain abuse-monitoring content for up to 30 days even when response storage is disabled. With your consent, generated replies and updated memory summaries are temporarily stored for retry recovery, become inaccessible after ten minutes, and are automatically deleted. Encrypted disaster-recovery backups may retain them for up to seven days. Apple processes purchases and subscriptions; Zrindy stores transaction identifiers, product IDs, subscription status, balances, and usage ledgers linked to the authenticated Firebase account. Older guest clients remain supported during the update transition. RevenueCat receives a one-way-derived purchase account ID and purchase metadata, never chat content, photos, names, or email addresses. Optional, default-off product analytics and explicitly submitted message feedback store account-linked event metadata for up to 90 days, without message text or photos. Encrypted, user-created backups restore only into the same account; users control their backup files and passwords. Account deletion also clears this device’s account records and product events. Authentication SDK operational data is separate from optional Zrindy product analytics. Google Sign-In may process account and device identifiers, sign-in usage and service information for authentication and service analytics, and use an approximate region inferred from the IP address for security and fraud prevention. Firebase Authentication processes SDK, app, operating-system and device-type diagnostics for SDK adoption analytics without linking those diagnostics to user or device identifiers. AICrush does not use phone-number authentication, location permission, precise location or iPhone ad tracking. The signed-out public introduction at aicrush.zrindy.com may show Google AdSense ads with non-personalized and restricted-data-processing signals. Google may process IP address, coarse region, browser/device information, cookies and ad interactions for delivery, measurement and fraud prevention. A certified Google consent message handles applicable regional choices; the public page provides a privacy-settings control. No AICrush account ID, email, transcript, memory, photo or custom character data is passed to advertising. Signed-in account screens and the legacy corporate-host app do not load advertising. Google site approval is required for serving ads. Zrindy does not sell conversation or account data. New app versions require Firebase sign-in. iPhone supports Google and Apple, while the web supports Google. After the cloud notice is acknowledged, completed transcripts and custom character text settings synchronize through account-scoped Google Firebase Firestore in Seoul until deletion. Own-account access is enforced; transmission and provider storage are encrypted, without end-to-end encryption. Pending requests, tokens, photos, notes, bookmarks and device-specific memory controls are not uploaded as transcript documents. Content-free deletion markers prevent stale clients from recreating erased records. Web exports are unencrypted text JSON without photos or authentication tokens. Web has no checkout, RevenueCat SDK, optional product analytics or message-feedback transmission. iPhone purchases can be consumed with the same linked Firebase account. Firebase Analytics separately measures signup, login, consent, reply and purchase flows using an app-instance identifier and limited device, usage and approximate-region metadata. It does not receive chat content, photos, names, email, Firebase account IDs, receipts or transaction IDs, and does not use IDFA, IDFV or ad personalization. This analytics collection is separate from the optional Zrindy server analytics switch. Purchase-level credit consumption and estimated AI costs are retained for refund operations: detailed records for up to 90 days and purchase aggregates for up to one year. Only accounts that separately opt in may have purchase delivery and consumption information sent to Apple for refund review; refusal does not limit purchases or chat, and withdrawal stops queued and future responses. Apple makes the final refund decision.