Effective Date: September 1, 2026 • Version 6.0 (Global: GDPR, CCPA/CPRA, KVKK & Google Play Compliant)
Privacy Policy
Your privacy is of paramount importance to us. This Privacy Policy outlines how Ryuko AI (referred to hereinafter as the "Service", "App", or "Platform") collects, encrypts, processes, stores, and permanently purges user data. This disclosure has been meticulously drafted to satisfy all legal requirements set forth by the EU General Data Protection Regulation (GDPR), the California Consumer Privacy Act as amended by the CPRA (CCPA/CPRA), the Turkish Law on Protection of Personal Data (KVKK No. 6698), and the Google Play Store Developer User Data Policies worldwide.
Independent Individual Developer Status (Non-Corporate): Ryuko AI is developed, published, and maintained exclusively by an independent, individual software developer (a natural person). We are not a corporation, limited liability company (LLC), enterprise conglomerate, or venture-backed entity. We operate strictly as an independent creator. For all privacy, encryption, or account data deletion requests worldwide, contact us at support@ryukoai.net.
1. DATA CATEGORIES AND COLLECTION PRINCIPLES (DATA MINIMIZATION)
We strictly adhere to the principle of data minimization. We only collect the minimal personal data parameters necessary to deliver our AI conversational roleplay features. The categories of data processed include:
A. Information You Provide Directly
- Authentication Information: Your email address, encrypted authentication password, user display name, profile avatar URL, and optional user biography (bio).
- Public Profile Data: If you publish characters or set up a public profile, your display name, username, avatar and published characters become visible to other users.
- Fictional Inputs & Settings: Characters designed by your account, customized character descriptions, background lore prompts, and UI configuration settings.
- Age & Demographics: Your declared birth date (used solely to verify the 18+ legal majority threshold to unlock or restrict mature roleplay features).
B. Information Collected Automatically
- Encrypted Chat Logs: All chat message history, conversational turns, episodic memory records, and facts derived from your discussions with AI agents. Chat messages are encrypted at rest with server-held keys and are decrypted server-side solely to generate AI responses.
- Device Identifiers & Telemetry: Operating system version, device model, local language settings, temporary IP address (utilized solely for rate-limiting, DDoS prevention, and API key theft protection), and Firebase App Check / Google Play Integrity safety tokens.
- Push Notification Token (FCM): A Firebase Cloud Messaging device token is collected to deliver in-app push notifications (e.g., new direct messages, social activity alerts). This token is stored server-side solely to route push messages to your device and is permanently deleted upon account deletion or app uninstall.
- Online Presence & Activity Status: Your real-time online/offline status is stored in Firebase Realtime Database and may be visible to other users you have exchanged messages with. This data is ephemeral and is automatically cleared upon disconnection or session expiry.
- Social Graph (Follow / Follower Data): When you follow or are followed by another user, this relationship record is stored in your Firestore profile sub-collection. This data is used exclusively to power social features (activity feeds, group DM member lists) and is permanently deleted upon account deletion.
- Direct Message (DM) Metadata: Direct message threads are stored in Firestore with message content encrypted using AES-256-GCM. Message content is decrypted on our servers solely to deliver messages and operate the Service; metadata (participant list, timestamps, unread counts) is stored unencrypted for message delivery purposes only.
- Content Reports Submitted: If you submit a report against another user, character, message, or post, the report record (reporter UID, target ID, reason text, timestamp) is stored in our Firestore moderation queue for review purposes only and is never shared publicly.
- Firebase Analytics: Aggregated, anonymized in-app usage events (screen views, feature engagement metrics) are collected via Firebase Analytics to improve service quality. This data contains no message content or directly identifiable personal information.
- Stability and Crash Logging: System performance metrics and crash logs processed via Firebase Crashlytics. Crash reports may include your user ID so we can investigate and follow up on reported issues.
C. Financial Transaction Data
- When you make a transaction on Google Play Store or Apple App Store, we receive an anonymous digital receipt token confirming transaction status (tokens bought, subscription tier active). WE DO NOT STORE OR PROCESS YOUR DEBIT/CREDIT CARD NUMBERS. All payments are processed directly and exclusively by Google LLC or Apple Inc.
D. Device Permissions & On-Device Local Storage
- Photo Library / Camera Access: When you upload or update a profile avatar or character image, the app requests access to your device's photo library or camera. Selected images are compressed and uploaded to Firebase Storage under your account. No images are accessed or transmitted without your explicit action.
- Storage Write Access (Gallery): The app may request permission to save images to your device's media gallery (e.g., saving shared character images). This permission is requested only when you explicitly trigger a save action and is never used passively.
- Local SQLite Cache (Drift): Chat messages and character data may be cached locally on your device in an SQLite database (powered by Drift) for offline access and UI performance. This local cache is stored exclusively on your device and is cleared upon logout or app uninstall.
- Secure Credential Storage: Authentication tokens and per-chat encryption keys are stored in your device's OS-level secure enclave (iOS Keychain / Android Keystore). Per-chat keys are issued by our servers over authenticated TLS; the master key never leaves our secret manager.
- UI Preferences: Non-sensitive UI settings (theme, language preference) are stored locally via shared_preferences and contain no personal data.
2. PURPOSE AND LEGAL BASIS FOR DATA PROCESSING
We process your data based on explicit international legal grounds:
| Data Type |
Processing Purpose |
Legal Basis (GDPR / CCPA / KVKK) |
| Email, UID |
Account creation, password resets, secure login, subscription tracking. |
Contract Performance (GDPR Art. 6(1)(b) / KVKK Art. 5(2)(c)) |
| Chat Logs & Memories |
Storing messages, executing vector memory, maintaining roleplay narrative consistency. |
Contract Performance (GDPR Art. 6(1)(b) / KVKK Art. 5(2)(c)) |
| IP Address, App Check Tokens |
Rate-limiting API usage, defending against malicious bot farms, preventing credit exploits. |
Legitimate Interest & Security (GDPR Art. 6(1)(f) / CCPA / KVKK Art. 5(2)(f)) |
| Crash & Diagnostic Logs |
Debugging code errors, fixing UI exceptions, optimizing performance on mobile devices. |
Legitimate Interest (GDPR Art. 6(1)(f) / KVKK Art. 5(2)(f)) |
3. DATA SECURITY & THE GOLDEN SHIELD OF AES-256-GCM
We implement enterprise-grade protection policies across the entire application:
- Database Encryption: All private chats, character prompts, and user data stored in our Google Firestore database are protected utilizing industry-standard AES-256-GCM encryption.
- ZERO SALE OR SHARING OF CHAT DATA: The Developer NEVER sells, leases, rents, trades, or shares your private conversations, messages, or roleplay prompts with third-party data brokers, advertising agencies, or marketing companies.
- AI Privacy Shield (Zero-Training Guarantee): When conversation context is sent to our enterprise inference pipelines (Google Cloud Vertex AI, OpenRouter enterprise endpoints), it is transmitted over secure TLS/HTTPS channels. Your private chats and prompts are NEVER used to train, retrain, or improve public foundational AI models (inference providers may retain transmitted context under their own published policies — see §6).
4. CALIFORNIA CONSUMER PRIVACY RIGHTS (CCPA / CPRA)
If you are a California resident, you are entitled to specific rights under the CCPA/CPRA:
- Right to Know & Access: You may request the categories and specific pieces of personal information collected about you.
- Right to Delete: You have the absolute right to request the permanent deletion of your personal data at any time.
- Do Not Sell or Share: We do NOT sell or share your personal information or sensitive personal data with third parties for cross-context behavioral advertising.
- Non-Discrimination: We will never discriminate against you (deny services or alter pricing) for exercising your CCPA/CPRA privacy rights.
5. GOOGLE PLAY COMPLIANT ACCOUNT DELETION (RIGHT TO BE FORGOTTEN)
Under GDPR (Art. 17), CCPA, and KVKK (Art. 11), you have the absolute right to be forgotten. You may delete your account and permanently purge all your data at any time through:
- In-App Deletion Path: Go to Settings > Oturum & Veri Yönetimi > Tap Hesabı ve Tüm Verileri Sil. This initiates an immediate, real-time automated deletion sequence.
- Web Deletion Portal: If the app is uninstalled, you can submit a deletion request via our Account & Data Deletion Portal Page or email support@ryukoai.net.
- Deletion Timeline: Your request is queued immediately in real-time; all custom characters, chat histories, vector memories, subscription associations, and authentication IDs are permanently and irreversibly wiped from the active Firestore database within 7 days of request.
6. THIRD-PARTY SUB-PROCESSORS & GLOBAL DATA TRANSFERS
We utilize trusted global enterprise infrastructure sub-processors to deliver the Service. Data may be stored and processed on servers located in the United States and the European Union under Standard Contractual Clauses (SCCs):
- Google Firebase & Cloud Platform: Cloud database storage (Firestore), User Authentication (Firebase Auth), Firebase Realtime Database (online presence), Firebase Storage (avatar/image uploads), and serverless Cloud Functions execution.
- Firebase Cloud Messaging (FCM): Push notification delivery service. FCM device tokens are transmitted to Google's servers solely to route push notifications to your device.
- Firebase Analytics: Aggregated, anonymized usage analytics to understand feature engagement and improve the Service. No message content is transmitted.
- Google Vertex AI & Enterprise LLM Providers (incl. OpenRouter): Large language models used for generative text inference. Conversation context is transmitted over TLS-encrypted channels solely to generate AI responses and is not used to train models; provider-side retention is governed by each provider's published policy.
- Firebase Crashlytics: Diagnostic performance and memory exception monitoring.
- Google AdMob: Serving non-personalized or contextual advertisements exclusively on the Free tier. AdMob may collect device advertising identifiers as described in Google's Privacy Policy.
7. CHILDREN'S PRIVACY RATING (18+ AGE REQUIREMENT)
The Service is strictly rated 18+ and does not knowingly target, collect, or process information from children or minors under eighteen (18) years of age (in compliance with COPPA, GDPR-K, and Google Play Families Policies). If a parent or guardian discovers that an individual under 18 has created an account, contact us immediately at support@ryukoai.net. We will permanently delete all associated credentials and message history within 48 hours.
8. COOKIES, LOCAL STORAGE & ESSENTIAL DEVICE DATA
The web pages of the Service do not use tracking cookies, advertising cookies, or third-party analytics scripts. The only client-side storage employed consists of two browser localStorage entries: ryuko_lang, which remembers your interface language preference between visits, and ryuko_theme, which remembers your light/dark reading-theme choice on pages offering it. These entries never leave your device, contain no personal data, and can be erased at any time by clearing your browser's site data. The mobile application stores authentication tokens in OS-level secure storage and chat content in an encrypted local cache, as described in Section 1.
9. FORCE MAJEURE & INDIVIDUAL DEVELOPER LIABILITY SHIELD
While the Developer deploys high-grade security (including Firebase IAM rules, App Check attestation, and AES-256 encryption), no storage or internet transmission system is completely invulnerable. The Service is hosted on third-party Google Cloud infrastructure. In the event of a global cloud outage, zero-day infrastructure security exploit, or unauthorized third-party breach beyond the reasonable control of an individual developer, the Developer’s liability is strictly limited to the deletion and remediation of affected database entries upon request. The Developer (as a natural person) shall not be held personally liable for damages arising from third-party cyber-intrusion events.
10. CONTACT AND DATA PROTECTION DESK
For data audits, GDPR/CCPA/KVKK information requests, or deletion notifications:
11. DATA RETENTION PERIODS
We retain your personal data only for as long as necessary to deliver the Service or as required by applicable law. The following retention periods apply:
| Data Category |
Retention Period |
Deletion Trigger |
| Account & Profile Data |
Until deletion request |
Permanently purged within 7 days of verified request |
| Chat Logs & AI Memories |
Until deletion request |
Permanently purged within 7 days of verified request |
| Direct Messages (encrypted) |
Until deletion request |
Permanently purged within 7 days of verified request |
| FCM Push Tokens |
Active session |
Deleted on account deletion or uninstall detection |
| Online Presence / Status |
Session only (ephemeral) |
Auto-purged on disconnection |
| Social Graph (Follow Data) |
Until deletion request |
Permanently purged within 7 days of verified request |
| Moderation Reports |
90 days after resolution |
Auto-purged 90 days after report is resolved or dismissed |
| Crash & Analytics Logs |
90 days |
Auto-purged by Firebase after 90 days |
| IP Address Logs |
Minutes to hours (rate-limit window only) |
Short-lived rate-limiting counters; not used to build profiles |
| On-Device Local Cache |
Active installation |
Cleared on logout or app uninstall |