Raflio Privacy Policy
Version: 1.1 · Effective date: October 29, 2026 · Language: English
This document serves two purposes: it is a GDPR (EU General Data Protection Regulation) privacy notice for users in the EU/EEA/UK, and it summarizes the KVKK (Turkish Law No. 6698 on Protection of Personal Data) disclosure that applies to our primary market, Türkiye (see §11). By using the Raflio mobile application (the "App"), you acknowledge that you have read this policy.
§1. Data Controller
For the purposes of GDPR Art. 4(7) and KVKK art. 3, the data controller for personal data processed through this App (the "Controller", "we", "us", "our"):
| Field | Value |
|---|---|
| Legal name | Oğulcan Özkan — natural person (sole operator) |
| Contact channel | privacy@raflio.app (see §12) |
| Tax/Company registration no. | Not applicable — the controller is a natural person, not a legal entity |
| Address | Soğanlık Yeni Mahallesi, Orhan Kemal Sokak No:5, 34880 Kartal/İstanbul |
| Contact email | privacy@raflio.app |
| EU representative (if applicable, GDPR Art. 27) | Not appointed — see note below |
| KVKK VERBİS registration no. (if required) | Not required — see note below |
On the EU representative (GDPR Art. 27): Raflio v1 is published for the Turkish market and its interface is Turkish-first. An Art. 27 representative has therefore not been appointed. If the App is offered in EU/EEA storefronts on a non-occasional basis, a representative established in the Union must be designated in writing before that release and this section updated.
On VERBİS: Turkish Data Protection Board decision no. 2023/1154 exempts controllers with fewer than 50 employees and an annual balance sheet under TRY 100 million whose principal activity is not the processing of special-category data. Raflio falls within this exemption: it is operated by a single natural person and its principal activity is book tracking and recommendation.
§2. Scope
Raflio is a mobile app offering personalized book recommendations, a virtual bookshelf, book logging/rating, and (optionally) social features such as following other readers. This policy explains what personal data we process when you use the App, why, with whom it may be shared, how long it is kept, and what rights you have.
This policy covers only the App itself. It does not cover the App Store's or Google Play's own data practices, which are governed by Apple's and Google's respective privacy policies.
§3. What Personal Data We Process
Each category below is only created when you actually use the corresponding feature.
§3.1 Data Stored Locally on Your Device — Your Bookshelf
When you add a book, rate it, change its reading status (read/reading/DNF/unread), position it on your virtual shelf, or add a private note, this data is stored primarily on your device:
- Your shelf list, ratings, reading status, shelf/row/position placement
- 🔒 Your private notes — visible only to you, never shown to any other user or in any server-side public view
- Free-text labels you attach to books yourself
How it is protected: this data is stored on your device encrypted with AES-128 (via react-native-mmkv's encrypted storage mode). The encryption key is not stored alongside the data — it lives in your operating system's own secure enclave: Keychain on iOS, Keystore/EncryptedSharedPreferences on Android. This means that even if your device is lost, stolen, or its lock is bypassed, your shelf data and private notes cannot be read as plain text.
§3.2 Account Information
When you create an account (email/password, Google sign-in, or Sign in with Apple), we process:
- Your email address (if you registered by email) or the identity token your provider (Google/Apple) shares with us — we never see your password
- Your internal system identifier (a UUID) — all other data is linked to this identifier, not to your email address
- Information you choose to show on your profile: username (
@handle), display name, a short bio, an avatar color (a color code, not a photo), your chosen shelf theme, and a privacy toggle controlling whether your profile is public or followers-only
Your session tokens are stored in your device's secure vault (iOS Keychain / Android Keystore) and are never kept as plain text.
§3.3 Shared Book Catalog Entries
If a book you're looking for isn't in our catalog, you may add it by typing its title and (optionally) author. This is catalog data, not personal data about you, but it works as follows and you should be aware of it:
- The title/author you enter is added to our shared, public book catalog and becomes searchable by every other user
- The entry itself does not display who added it to other users, but our system does internally record who submitted it, for abuse prevention and moderation review
- Submitted text goes through length and character validation to prevent technical abuse (e.g. spreadsheet formula injection); invalid input is rejected
§3.4 Social Features and User-Generated Content
If you use social features (following another user, posting a public review, blocking someone, reporting content), we process:
- The identities of users you follow / who follow you
- Your public reviews (
review) — shown on the book's detail page, visible to anyone. 🔒 This is different from your private notes in §3.1 — your notes are never public; your reviews always are - The identities of users you block (visible only to you)
- When you report content/a user: the reported content, your selected reason (chosen from a predefined category list), and the report timestamp — reviewed by our moderation process
If you set your profile to private, your shelf and reviews are visible only to followers you approve.
§3.5 Analytics (Usage) Data
We plan to use a product analytics tool called PostHog to improve the App. Once enabled, it will collect: which screens/features you use (e.g. "you rated a book", "a recommendation row was shown"), technical information such as device/OS/app version, and your internal system identifier (UUID). Book titles, author names, the text of your notes or reviews, and your email address are never sent to this tool — only the book's internal ID (book_id) and fixed, predefined category values (enums) are processed.
📌 Current status (as of this policy's effective date): the PostHog software component is bundled with the App but is disabled at the network level — it sends nothing. In development builds, these events are only logged to the developer's own local console; in production builds the call is a silent no-op. In other words, no data is currently actually collected via PostHog. When this tool is enabled, this policy will be updated and the change will be announced in-app and/or via a store listing update.
§3.6 Crash and Diagnostic Data
Crash reporting is OFF in v1 — no diagnostic data leaves your device, not even when the App crashes. The App contains Sentry code, but no connection address (DSN) is shipped in the production build and the crash reporting code is explicitly disabled.
If this is ever enabled, it would collect: a technical description of the error (stack trace), device model, OS version, and app version. Your email address and IP address are automatically stripped before such data is sent (a verified filtering step in our code). Any such change would be announced under §11.
§3.7 Purchase Data
Premium is a one-time purchase (not a subscription). It is processed directly through Google Play Billing — your payment/card details never reach us. To check whether Premium is unlocked, the App asks the Google Play service on your device (at launch and when the App comes to the foreground); this query does not go to us or to any third party we have chosen. There is no intermediary purchase service. Google processes data in this process under its own privacy policy, as part of your Google Play agreement with Google.
Google Play sends us sales reports containing the order number, date, product, amount, currency and country/region. We use these only for accounting/tax obligations and to answer refund requests, and we do not link them to your shelf or in-app behaviour (we hold no data that would allow it).
§3.8 AI-Assisted Catalog Enrichment — a Process Your Personal Data Never Enters
Catalog metadata such as book summaries and categories are generated in a batch, server-side process using the Google Gemini model (with Anthropic Claude as a fallback provider). Only the book's title and author (catalog data) are sent to this process.
🔒 Clarification: this process has nothing to do with your personal data. Your notes, reviews, ratings, reading history, taste profile, or any identifying information are never sent to these AI providers. The personalized recommendation calculation (which book fits you) runs entirely on your own device and is never sent to any server or AI provider.
Some factual catalog fields (publication year, page count, publisher) may also be supplemented from Open Library, an open data source; this source contains no personal data, only public book information.
§3.9 Backup and Export Data
When you export your shelf as CSV/JSON (this feature is free for everyone), the resulting file includes all of your shelf data, including your private notes and reviews. This file is created temporarily on your device and shared by you, through the share sheet you choose — we do not see where it goes, and it is never sent to our servers. The file may remain briefly in your device's temporary/cache storage after sharing.
§3.10 Notifications
The App sends no notifications — neither local reminders nor server push; it does not ask for notification permission and collects no push token. It also sends you no commercial electronic messages (SMS, email, calls); we do not collect your contact details for that.
§3.11 What We Do Not Collect
To be explicit — the App never requests or collects: your location (GPS), camera/photos, microphone, contacts, biometric data (fingerprint/face data stays within your device's own OS and is never shared with us), advertising identifiers (IDFA/GAID), or third-party ad tracking data. The App contains no advertising.
§4. Purposes of Processing
Your personal data is processed to:
- Create and authenticate your account and maintain your session
- Sync your shelf, ratings, and reading status across your devices (if you use more than one)
- Provide personalized book recommendations (computed on your device)
- Operate social features (following, reviews, activity feed)
- Protect the platform from abuse (spam, harassment, inappropriate content); review reported content and remove it or suspend accounts when warranted
- Manage subscriptions and purchases
- Detect and fix bugs (crash reporting)
- Improve the product using aggregated usage trends (once §3.5 is enabled)
- Comply with legal obligations and respond to lawful requests
§5. Legal Basis (GDPR Art. 6)
| Data category | GDPR Art. 6(1) basis |
|---|---|
| Account, shelf, sync data | (b) performance of a contract with you |
| Social features, public reviews | (a) your consent (you choose to use these features) |
| Security, abuse prevention, crash monitoring | (f) our legitimate interest, balanced against your rights |
| Purchase records (Google Play sales report) | (b) performance of a contract and (c) legal obligation — tax records |
| Analytics data (once enabled) | (a) consent or (f) legitimate interest — to be stated explicitly in this policy once analytics is enabled |
§6. International Transfers and Processors
We use the following service providers (processors) to operate the App. None of them may use your data for their own purposes — they process it only on our instructions, to provide the stated service:
| Provider | Role | Data involved | Location |
|---|---|---|---|
| Supabase | Database, authentication, server-side functions | Account, shelf, social data | Not active in v1 — EU, Frankfurt (eu-central-1) when enabled |
| Sentry | Crash/error monitoring | Technical error data (email/IP stripped) | Not active in v1 — EU, Sentry European data region (de.sentry.io) when enabled |
| PostHog | Product analytics | Usage data described in §3.5 | Not active in v1 — EU region (eu.i.posthog.com) when enabled |
| Google (Gemini API) | Catalog enrichment (book title/author only) | Catalog data, not personal data | Google global infrastructure (including the US) |
| Anthropic (Claude API, fallback) | Catalog enrichment (book title/author only) | Catalog data, not personal data | Anthropic infrastructure (US) |
| Apple / Google (store) | Payment processing | Payment details (never reach us) | Apple's/Google's own policy |
In v1, the App sends NO data to us or to any service provider we have chosen. The only external contact is with the Google Play service on your device when you buy and verify Premium (§3.7) — that relationship is between you and Google. No crash report is sent either. Your shelf, ratings, notes and search queries stay on your phone; the app does not contact a server for anything else, including the catalog, which is bundled inside the app.
Clarifications about the table above:
- Sentry is not configured in v1. No crash report is sent (see §3.6). The row remains so the disclosure is ready when the feature ships.
- Supabase is not configured in v1. The app contains Supabase code, but no connection credentials are shipped in the production build and the app runs entirely locally. There is no account creation, sign-in or server sync in v1. The row remains so the disclosure is ready when the feature ships.
- PostHog is not active in v1. It is not used anywhere in the app's code, so no data reaches that provider. The row is here so the disclosure is ready when the feature ships — not because it is running today.
- There is no purchase intermediary (from 1.0.2). RevenueCat, used in earlier versions, was removed; purchases and verification run directly through Google Play Billing. Payment and card details are handled by Google Play and never reach us.
- Only a book's title and author are sent to Google/Anthropic — not by the App, but by us when preparing the book descriptions in the catalog. No account, shelf, rating or social data is sent on that path, so it does not involve an international transfer of personal data.
International transfers: in v1 we do not transfer personal data abroad (providers marked "not active" above are not used). If a provider is introduced later, the transfer will follow KVKK Art. 9 (including standard contracts and notification to the Board) and GDPR Chapter V, and this policy will be updated BEFORE that happens.
We never sell your data or share it with third parties for their own advertising purposes.
§7. Retention
- Account and shelf data (accounts do not exist in v1, see §2): once accounts exist, retained while your account is active. When you delete your account (§9), your associated shelf, social relationships (follows/blocks), and report records are automatically deleted at the database level (verified: cascading deletion is configured on account deletion).
- Local device data: retained on your device until you delete it (Settings → "Delete my data") or uninstall the App.
- Purchase records (Google Play sales report, §3.7): kept for the period required by Turkish tax law (Tax Procedure Law Art. 253 — 5 years), then deleted.
- Shared catalog entries (§3.3): a book's presence in the catalog is not tied to your personal account — deleting your account does not necessarily remove a book you added, since it is now a shared, public catalog record with no personal attribution shown to other users.
- Analytics data (§3.5): none is collected in v1 — the analytics tool is not wired into the code. Once enabled, raw person-linked event data will be retained for 90 days, after which only aggregate counts that cannot be linked to a person are kept.
- Crash/error logs: not collected at all in v1 (§3.6). If enabled, they would be subject to Sentry's default retention policy.
§8. Security Measures
- Your shelf data and private notes are encrypted on-device with AES-128; the encryption key is stored in your OS's hardware-backed secure vault (iOS Keychain / Android Keystore), separately from the data itself.
- *(When accounts arrive — v1 has no server:)* On the server, every database table is protected with row-level access control (Row Level Security) — it is structurally impossible at the database layer for one user to read another user's private notes, not merely a choice made in app code.
- All network traffic is encrypted via HTTPS; unencrypted (http://) connections are not used.
- Your session tokens are stored in your device's secure vault, never as plain text.
- Rate limiting is applied to abuse-prone endpoints.
- When you block a user, that user's content becomes completely invisible to you at the database query level.
No system is 100% secure. We take reasonable technical and organizational measures but cannot guarantee absolute security.
§9. Children's Data
Raflio includes user-generated content (reviews, profiles, following) and is therefore not directed at children under 13, and the "Kids" store category has not been selected. If we learn we have inadvertently collected data from a child under 13, we will delete the account. If you are a parent/guardian and believe your child has provided us with information, contact us using §12.
§10. Your GDPR Rights
If you are in the EU/EEA/UK, you have the right to: access your data (Art. 15), rectify it (Art. 16), erase it / be forgotten (Art. 17), restrict processing (Art. 18), data portability (Art. 20 — already fulfilled by the free export feature in §3.9), object to processing (Art. 21), and lodge a complaint with your national supervisory authority.
§11. KVKK Notice for Users in Türkiye
Since Türkiye is our primary market, users there are additionally entitled to the rights under KVKK art. 11, including the right to: learn whether your data is processed; request information about it; learn its purpose and whether it is used accordingly; know third parties it is transferred to (domestically or abroad); request correction of inaccurate data; request erasure/destruction once the conditions of KVKK art. 7 are met; request that such correction/erasure be notified to third parties the data was transferred to; object to a result that is to your detriment arising solely from automated analysis; and claim compensation for damages arising from unlawful processing. The full Turkish-language disclosure is provided in the Turkish version of this policy (raflio.app/gizlilik), which governs for Turkish-language users and in case of conflict.
§12. How to Contact Us / Exercise Your Rights
- Email: privacy@raflio.app
- In-app: Settings → "Delete my data" (the data on this device, see §12.1)
You may also send written requests to Soğanlık Yeni Mahallesi, Orhan Kemal Sokak No:5, 34880 Kartal/İstanbul. Under the Turkish Communiqué on the Procedures and Principles of Application to the Data Controller, an email address previously notified to the controller is a valid application channel alongside written application, registered electronic mail (KEP), secure electronic signature and mobile signature.
We will respond to verified requests within the timeframe required by applicable law (generally within 30 days under KVKK; without undue delay and within one month under GDPR).
§12.1 Data Deletion
Raflio (v1) has no accounts and the App sends us no data. Your data is on your device:
- Data on your device (your shelf, ratings, reading statuses, reviews, quotes and settings): Open Raflio → the gear icon on the bookcase screen (Settings) → "Delete my data" → confirm. All Raflio data on this device is deleted immediately and permanently; this cannot be undone. Uninstalling the app has the same effect. This data never reaches us, so we hold no copy of it. Backup files you exported yourself are under your control; you delete those yourself.
- Purchase record: the purchase itself is tied to your Google account and Google Play's order record is subject to Google's policy. The sales-report record we hold must be retained under tax law (§7); it cannot be deleted early but is used for no other purpose. Questions: privacy@raflio.app.
§13. Cookies
Raflio is a mobile app and does not use browser cookies. The web page hosting this policy (raflio.app) serves static text only — no tracking cookies, pixels or analytics scripts. As with any static hosting service, the hosting provider may briefly retain IP addresses in server access logs for security and abuse prevention; those logs are not read by Raflio, are not linked to your in-app account, and are not processed by us in any way.
§14. Changes to This Policy
We may update this policy from time to time — in particular when the analytics tool in §3.5 is enabled, or when new features are added. We will notify you of material changes in-app. The current version is always identified by the version/date at the top of this document.
§15. Summary Contact
raflio.app/privacy · raflio.app/gizlilik · privacy@raflio.app