Return to home

Last updated: 2 November 2026

Privacy Policy

This policy explains which data are processed when you use Sakin, which stay on your device, and how your choices are protected.

Summary: Your blocked app list and screen observations stay on your device. Account and reading data, room sharing, notification delivery, and server feature measurements are explained below. The mobile app does not use advertising tracking. Website and checkout measurement are explained separately.

1. Scope and data controller

This policy applies to the Sakin iOS and Android apps, physical Sakin bookmark, sakinayrac.com website, online orders, and account and synchronization services at api.sakinayrac.com.

Sakin is the data controller under Turkish Personal Data Protection Law No. 6698 (KVKK). Send questions and requests to [email protected].

2. Account and authentication data

  • Account details: When you create an account, we process your name, email address, Firebase user ID, sign-in provider, account timestamps, and any profile photo link supplied by the provider.
  • Sign-in providers: Firebase Authentication provides email/password, Sign in with Google, and Sign in with Apple. We do not store your password on the Sakin server.
  • Security data: Firebase Authentication can process technical data to protect authentication and prevent misuse. These can include your IP address, platform/SDK details, and Firebase app ID.

3. App data synchronized with your account

  • Library: Book titles, authors, reading status, optional ISBNs, and cover links are stored to synchronize with your account.
  • Reading history: Session start and end times, duration, optional target duration, session type, and linked book ID are processed for statistics and synchronization.
  • Physical bookmark: The NFC tag ID is sent to api.sakinayrac.com to verify your access to a registered Sakin bookmark. The verification is stored with your account and its time. The same bookmark can be verified by more than one account. This does not merge accounts or give another account access to your library, reading history, or private room memberships.
  • Private rooms and book clubs: The server stores room names, hosts, memberships, room settings, shared books, page and edition details, reading progress, and margin notes you share. Session links to rooms or invitations, start and end times, weekly total reading time, and active days are processed to provide these features. Blocking and reporting process the relevant user IDs, your selected reason, and any details you enter.
  • Information visible to room members: Other room members can see your display name, profile photo if present, whether you are reading now, whether you are using your bookmark, and your recent reading status. If you do not hide your book, its title, author, and cover link are visible. Book clubs share your page, edition page count, and progress. A margin note becomes readable when the other member reaches the required reading progress.
  • Room privacy and reminder preferences: Your choice to hide your book or receive room notifications, edition page count, and shared reading reminder preferences are stored on the server with your account. Hiding your book does not hide your display name, reading status, or book club page progress. You can change these preferences in the app, leave a room, and block another member.
  • Invitation links: The invitation ID, creator account, related room or session, duration, expiry time, and accepting accounts are stored. People with the link can see the inviter’s display name, the room name and type if present, reading status, and invitation duration. Book details appear only if you choose to share them in the invitation and your book privacy settings permit it. Accepting an invitation can create a record linking you to the inviter. Eligible invitations can also include a friend discount code.
  • Book search: Your search text is sent through the Sakin API to Google Books to obtain results. We do not intentionally store search history.

4. Data that stay on your device

  • Website purchase draft: The product quantity, gift option, and gift note are kept in the browser tab session so that a page refresh does not remove them. When you select Buy, these details are sent to Shopify for checkout.
  • Focus settings: Your weekly target, personal reading reminder days and times, active Shield status, and remaining session-ending allowances without the bookmark stay on your device. Room and shared reading reminder preferences are stored on the server as explained above.
  • Apps to block: Selected app packages stay on your Android device. Family Controls selections stay on your iOS device. These lists are not sent to the Sakin server.
  • Android app observations: While Shield is active, foreground app IDs and notification events are processed on the device only for immediate blocking. They are not recorded or sent to the server.

5. Permissions and device features

A feature may not work without its permission. You can switch off Android Accessibility and notification access in system settings at any time.

  • NFC: Used to verify the physical bookmark and start or end a reading session.
  • Android Accessibility service: During a session you start, Shield Mode uses window-change events and app package IDs to detect selected apps in the foreground. It does not read screen text, passwords, messages, images, touches, or the view tree. The service is configured with canRetrieveWindowContent=false.
  • Android notification access: Optional. It works on your device to silence notifications from selected apps during an active session. Notification content is not sent to Sakin or stored permanently.
  • iOS Screen Time: Apple Family Controls / Screen Time temporarily restricts selected apps on your device during an active reading session.
  • Notification permission: Used for personal reading reminders, timed session alerts, and the room and shared reading notifications you choose. Room notifications can tell you when a member starts reading or a planned reading time begins. We do not send marketing notifications. You can switch off notification permission in system settings.
  • Remote notification delivery: To deliver notifications, the Sakin server processes the device push token, your account, platform, and delivery channel. iOS uses Apple Push Notification service (APNs) and its environment setting. Android uses Google Firebase Cloud Messaging (FCM), a random installation ID, and a registration revision number. The installation record prevents an old request from sending notifications for an account you have signed out of. The push token, notification content, and account and room IDs needed for delivery are sent to the relevant provider. Delivery and read status are stored on the server.

6. Website and analytics

The mobile apps contain no ads or third-party analytics SDK. The sakinayrac.com website uses Google Analytics and Meta Pixel to measure page views and use. Under their settings, these services can process cookies, online identifiers, approximate location, and browser and device details.

The Sakin server records feature events with the account ID and time. These include room and invitation creation, invitation acceptance and completed sharing, session starts and completions, and bookmark verification. We use aggregate measures to assess invitation use and continued reading among accounts that read in rooms or alone. To measure purchases after invitations, the account email address can be matched to the email address on a completed, paid order. This server measurement is not used for advertising tracking.

To measure purchases from ChatGPT ads, the OpenAI click reference (oppref) in the ad link can be passed to the checkout cart. After a purchase, this reference, product amount excluding tax and shipping, and currency are sent to OpenAI ad measurement only when checkout analytics and marketing permission is given and data sharing is not rejected. We do not include names, email addresses, phone numbers, addresses, or order numbers in this transfer.

We use website and checkout measurements to assess ad performance. You can limit this processing through browser cookie settings and supported privacy controls at checkout.

If you choose to register for Sakin letters, Brevo processes your email address, confirmation, and subscription status to deliver the newsletter. Registration is complete after you confirm the link sent to your email address. You can withdraw permission at any time through the unsubscribe link in each newsletter.

7. Order, payment, and delivery data

  • Order details: We process your name, email address, phone number, delivery and billing addresses, product, quantity, amount, and order status. This lets us create and deliver orders, provide support, and meet legal record requirements.
  • Payment: Shopify secure checkout and its authorized payment provider, iyzico, process card payments. Sakin does not store full card numbers or card security codes in its systems.
  • Shipping: We share the name, phone number, address, order, and shipment details needed for delivery with Geliver and the contracted carrier.

8. Processing purposes and service providers

We process data to create accounts, provide secure sign-in, verify access to physical bookmarks, synchronize libraries and reading history, provide private rooms and invitations, apply notification preferences, measure feature use, perform requested book searches, provide support, and protect service security.

Firebase Authentication, Apple APNs, Google FCM, Google Books, Shopify, Brevo, iyzico, Geliver, contracted carriers, and hosting and technical infrastructure providers can process data to provide the relevant service. We do not sell your personal data or share them with data brokers. Section 6 explains website and checkout ad measurement and your choices.

Necessary data can be shared with competent authorities in response to lawful official requests.

9. Storage, security, and international transfers

Account, library, and session data are stored while your account is active. Communication and security records can be kept for a limited period as required for service security and legal duties.

When you delete your account, we delete the Firebase identity, Sakin profile, library, reading history, and bookmark link from active systems. Copies in normal backups leave the backup cycle within 90 days. Records that must be kept by law can be stored separately for the required period.

Account deletion also removes your room memberships, invitations you created, social sessions, page progress, margin notes, notifications, device tokens, blocking and report records, and account-linked feature events from the server. Rooms you host are deleted. Other accounts’ verifications of the shared bookmark and those accounts’ data are retained.

To prevent an old request from recreating a deleted room, the room creation request ID, account link, and technical validation record can remain after room deletion. This record is deleted when the account is deleted. The Android notification installation ID, latest revision number, and revocation status are retained with the account and push token links removed. This record prevents an old device request from restoring notification registration.

When the notification worker runs, server notifications older than 30 days and their delivery records are removed. This is not a general retention period for rooms, invitations, reading history, or feature events.

HTTPS encrypts data in transit. Firebase and other infrastructure providers can have servers outside Turkey. Suitable transfer mechanisms under KVKK and provider safeguards apply to these transfers.

10. Delete your account and data

In the Android app, go to Settings › Account › Delete account. If you cannot access the app, use the account deletion page.

11. Your rights

Under Article 11 of KVKK, you can ask whether your data are processed and request information about processing and its purpose. You can request correction, deletion, or destruction, and notification of recipients. You can object to an adverse result based only on automated analysis and claim compensation for damage from unlawful processing.

Send your request to [email protected], preferably from your account email address. We may need to verify your identity to protect your account. We respond to valid requests within the legal period, no later than 30 days.

12. Children’s privacy

Sakin is not designed for children under 13. We do not knowingly collect personal data from this age group. Contact us if you think such data are being processed.

13. Updates and contact

We can update this policy when the product or law changes. For significant changes, we update the date on this page and, when necessary, provide notice in the app or website.

Send privacy questions to [email protected].