Privacy Policy - SecondBook

Effective Date: the Policy originally took effect on July 6, 2026; version 1.5 takes effect upon publication, and the publication date is shown in the "Last Updated" field
Last Updated: October 9, 2026
Version: 1.5
Clarification: October 11, 2026 — section 5.1 (see 9.2)
IMPORTANT: This Privacy Policy describes how we collect, use, store, and protect your personal data, and on what grounds we do so (Sections 1.3 and 3).

1. General Provisions

1.1. Data Controller

The data controller is Ilnur Stybayev, an independent developer acting as a private individual (not a legal entity), Almaty, Republic of Kazakhstan (hereinafter referred to as "Company", "Operator", "we", "us" — in all cases meaning this independent developer). 2ndBook is a non-commercial tool that lets users find and contact each other directly. The operator is not a party to any transaction between users, does not hold, transfer or retain funds, and charges no commission. All data protection requests are accepted by email: support@secondbook.kz; no postal address for correspondence is published.

1.2. Applicable Law

Personal data processing is carried out in accordance with:

1.3. Grounds for Processing and Consent

We process personal data on the grounds described in this Policy. Where the law requires separate consent, we ask for it separately; using the Service does not in itself replace such consent.

At registration you confirm, by ticking a box, that you accept the Terms of Service and this Policy; registration cannot be completed without it. This confirmation is recorded as your consent to the processing of personal data for the purposes and to the extent described in this Policy, in the cases where the law requires consent. We keep a record of it: which documents and which versions you accepted, the time, the IP address, browser or app details and the language of the documents. A new version of the documents is shown when you sign in to the app, with a request for your acceptance. Permission to access your location is requested separately — only when you yourself send your location to a chat (Section 2.1).

You may withdraw your consent at any time (Section 6.7). Withdrawal does not affect processing carried out on other grounds described in this Policy.

2. What Data We Collect

2.1. Data You Provide

Data Category Examples Purpose of Collection
Registration Data Name, email, phone number (in international format, with the country code) Account creation, sign-in, identification, contacting you
Profile Data Profile photo and cover, description, country and city (chosen from a reference list), district; gender and address — if you have provided them Showing your profile and the place where a book is handed over. The country is also used to apply rules that depend on the country. By default the city is visible to other users in your profile; you can hide it with the "Show city" setting if that setting is available in your version of the app. The district is never shown to other users. Your phone and email are shown to other users only in line with your visibility settings
"My addresses" Handover addresses you have saved: city, street and building, an address label Quickly choosing an address when arranging a transaction. Only you can see your saved addresses. When you arrange a transaction, the chosen address is copied into that transaction and becomes visible to its other party; editing or deleting a saved address does not change transactions already arranged
Transaction Data Contact name, phone and email, handover address or meeting place, chosen settlement method ("cash", "directly to the seller") Arranging the handover of a book between users. We do not collect or store bank card details: the Service does not process payments — settlement happens directly between users
Date of Birth Day, month, year of birth — optional and not verified against documents Book age labels: determining access to books labelled 16+/18+/21+ (without a date of birth such books are not shown) and restricting transactions in books that do not yet have an age label for users under 18 — see Section 8
User Content Listings, book photos and covers, reviews, text messages, voice messages and video in chat, uploaded book files, podcast audio and video with their transcripts Service functionality
Location in chat Coordinates of a place and, if you confirm it, its address Only when you yourself send your location to a chat: the app first shows an explanation and asks for the device permission. The location is stored as a message and is visible to the other participant. The address for the coordinates is determined by the geocoding service of your device's operating system. We do not track your location in the background
Reading Data Position in a book, time spent reading, books started and finished, reading-day streaks, bookmarks Syncing your progress across your own devices and showing your personal reading statistics
Verification Documents Only if you apply for bookshop-partner or legal-entity status: a passport or national ID card, a business/sole-proprietor registration certificate, articles of association and similar documents (the exact set depends on the form of registration). Full name, tax number or IIN, date of birth, address, country, date of issue and issuing authority are read automatically from the uploaded pages and stored Verifying the applicant's identity and their right to trade on the Platform. An ordinary user never needs these documents — not to register, and not to buy or sell a book

2.2. Data Collected Automatically

Data Category Examples Purpose of Collection
Technical Data IP address, device type, operating system, browser, app version; technical logs of requests to the server Operating the service, security, diagnosing errors
App error reports Description of the error, screen, app version, platform and device Finding and fixing errors
On-device authorization token Session Bearer token (not a cookie) Authentication in the app and web app — see Section 7
Push notification data Firebase Cloud Messaging (Google) device token, platform (iOS / Android / web), device name Delivering notifications about messages, transactions and moderation. Notifications can be turned off in profile settings or in your device settings
Session data List of active sessions: device, platform, app version, sign-in time and last activity Account security and the ability to end another session
Records of acceptance of documents Which document and which version of it you accepted, the time, IP address, browser or app details Evidence of which version of the documents you agreed to
Records of checks of books against official lists The book and its title, the owner's account, the matched list entry, the decision taken and its time, counted repeated attempts. For the check, the text of an uploaded book file may be read automatically — on our server, without passing it to third parties Applying the rules on prohibited materials (Terms of Service, 3.4) and reviewing requests

We do not determine your location from your IP address.

2.3. Data from Other Sources

We may receive data from the following sources:

3. Purposes of Personal Data Processing

We process your personal data for the following purposes:

3.1. Contract Performance

3.2. Legitimate Interests

3.3. With Your Consent

3.4. Legal Requirements

4. Sharing Data with Third Parties

4.1. Categories of Recipients

We may share your data with the following categories of recipients:

Recipient Purpose of Sharing Data Shared
Other Users Completing transactions, communication Name, photo, city (unless you have hidden it), rating and reviews, public content; to the other party of a transaction — the contact details and handover address given in that transaction; phone and email — in line with your visibility settings
Hosting provider (Republic of Kazakhstan) Hosting the Service's server, database, file storage and backups Data stored in the Service
Google (Firebase Cloud Messaging, Firebase Crashlytics) Delivering push notifications and collecting app crash reports Device token, platform, notification text; on a crash — technical data about the device and the circumstances of the crash
Sentry (Functional Software, Inc.) Collecting server error reports On a server error — a description of the error and where in the program it occurred, the request address, headers and body, and the values the program was processing at the moment of the error. IP addresses, cookies and authorization headers are not sent; passwords, tokens, codes and email addresses are masked automatically. A report may contain other data being processed at the moment of the error, such as an account number or the text of a request
Email provider Sending emails (confirmation codes, service notices) Email address and the text of the email
Telegram Signing in with Telegram and delivering notifications — if you have connected Telegram Telegram identifier, text of the notification
Telegram — the Operator team's private work chat Work of moderators and support: notices about moderation cases, support requests, feedback and failures that need a person's attention. Sent whether or not you have connected Telegram The number of the case, request, listing, message, chat or account; the book title; the category and reason of the check; a short excerpt of a support request or feedback; technical details of an error (request address, account number, error description). For a picture that the automated check held until a moderator decides: which picture it is (avatar, cover, logo), the category, the model's explanation and the text recognised in the picture and in a QR code (up to 120 characters each). If every category of such a picture is spam, weapons, fraud, contact details with a prohibited offer, the model being unsure, a match with the list of prohibited materials, legal risk or an unreadable picture, the picture itself is sent as well. If sexual content, harm to children or human trafficking is suspected, only the case number, which picture it is and the category are sent — never the picture, its text or the model's explanation
Government Authorities Only in the cases and in the manner established by law To the extent of a lawful request

We do not pass data to third-party analytics or advertising services.

4.2. Cross-Border Data Transfer

The Service's server, database, file storage and backups are hosted by a hosting provider in the Republic of Kazakhstan. Data may be transferred outside the Republic of Kazakhstan only to the recipients listed in Section 4.1 (Google, Sentry, the email provider; Telegram if you have connected it, and as the Operator team's work chat), to the extent stated there, under those providers' data processing terms and in the cases and in the manner permitted by law.

4.3. We Do NOT Sell Your Data

We do not sell users' personal data to third parties for their marketing purposes.

5. Data Storage and Protection

5.1. Retention Periods

When an account is deleted, personal data is deleted or anonymised in active systems according to the rules below; certain information is retained to a limited extent for the stated purposes; files are deleted asynchronously, and backups as they are replaced on schedule.

Data Category Retention Period
Account, profile, "My addresses", device tokens, sessions, records of acceptance, reading data While the account exists; deleted when it is deleted (see 6.3), with uploaded files handled as described below. An account cannot be deleted while you have an open transaction or an open dispute over a transaction — they must be completed first
Verification documents and the information read from them Until the application has been decided, the document files are kept; the document files are deleted 90 days after the decision on the application or its cancellation (approval, refusal or your withdrawal of the application, or, if the status is revoked, after the revocation). The verification result and the information read from the documents are kept while the account exists and are deleted together with it. While a confirmed legal entity, sole proprietor or author status is in force, the account cannot be deleted (Terms of Service, 11.2)
Transactions Transactions in which you were the buyer stay in the other party's history without a link to your account; your contact details (name, phone, email) and the handover address and city are removed from them when the account is deleted
Chat Messages As long as the conversation is active or either participant's account still exists; messages and attachments (photos, voice, video) you sent to others remain with the other participant after your account is deleted, without the sender's name
Reviews and ratings you left for other users Kept without the author's name after the account is deleted
Deleted book listings 30 days in "Archive" status (restorable by the owner), then permanent automatic deletion; when the account is deleted, they are permanently deleted together with it
Records of checks of books against official lists Decision records (account number, book title, list entry, decision and its time) are kept as an unalterable log for as long as a record is needed to review requests, protect rights and apply the rules in Section 3.4 of the Terms of Service; the need to keep them is reviewed periodically. After the account is deleted the log may keep its technical number, which is no longer linked to any profile in the Service. Counted repeated attempts are deleted together with the account
Uploaded files (photos, book files, documents) After the account is deleted, they are queued for deletion and removed from file storage automatically; if the storage is temporarily unavailable, the deletion is retried. The exception is a copy of a book cover that is shown in another user's order history
Sign-in log Records of sign-ins, session refreshes, sign-outs and password changes (account number, event, result, time) are kept for security for no longer than 180 days and then deleted automatically; details of revoked sessions are deleted 90 days after revocation. After the account is deleted the number in the remaining records is no longer linked to any profile
Technical logs and backups Server logs are overwritten as their limited size fills up. Backups of the database and files are kept for a limited time and replaced by newer ones on their own cycle; data deleted from the Service disappears from backups as they are replaced
Marketing Consents Until consent is withdrawn
Notices in the team's Telegram work chat Kept in the chat history. When you delete your account, the bot removes from the work chat the messages that carry your data — your support requests, your feedback and the review cards of your books and pictures; Telegram does not let a bot delete messages older than 48 hours, so their text and picture are replaced with a deletion mark. The text of these messages is also deleted from the Service's database. After a decision on a case, the picture in its card is replaced with a neutral placeholder. Messages about order disputes concern both parties and stay with the anonymised order when you delete your account; on request through support we delete any message in the chat that relates to you, including these. Copies sent before October 9, 2026 that cannot be linked to an account (the record they refer to no longer exists) are also deleted on request through support

5.2. Security Measures

The Service is built and run by one independent developer. We apply the following measures to protect your data:

5.3. Incident Notification

In the event of a data breach that may pose risks to your rights and freedoms, we will notify you and the competent authority in the cases and within the time limits established by applicable law. Where the GDPR applies, the procedure is described in Section 7 of the "GDPR" document.

6. Your Rights

You have the following rights regarding your personal data:

6.1. Right of Access

You have the right to obtain confirmation of whether we process your data, as well as to receive a copy of your personal data.

6.2. Right to Rectification

You have the right to request correction of inaccurate or incomplete data about you.

6.3. Right to Erasure ("Right to be Forgotten")

You can delete your account in your profile settings or through support; data is deleted or anonymised according to the rules in 5.1. You also have the right to request deletion of your personal data if:

6.4. Right to Restriction of Processing

You have the right to request restriction of processing of your data in certain cases.

6.5. Right to Data Portability

You have the right to request a copy of your personal data in a readable format. We prepare this manually on request via support; a self-service automated export (e.g. a "download my data" button in the app) is not yet implemented.

6.6. Right to Object

You have the right to object to the processing of your data for direct marketing purposes at any time.

6.7. Right to Withdraw Consent

If processing is based on your consent, you may withdraw it at any time. Withdrawal of consent does not affect the lawfulness of processing prior to withdrawal.

6.8. Right to Lodge a Complaint

You have the right to lodge a complaint with the supervisory authority for personal data protection if you believe your rights have been violated.

6.9. How to Exercise Your Rights

To exercise your rights, you may:

We will respond to your request within 30 calendar days.

7. Cookies and Similar Technologies

SecondBook does not use cookies for tracking, analytics, or advertising. The web app and mobile apps use a device-stored authorization (Bearer) token, not cookies, to manage your session. Technical session cookies may only be set on internal administrative interfaces, not reachable by regular users. Because no non-essential cookies are used, no cookie consent banner is required or shown.

8. Users' Age and Age-Restricted Content

The Service is intended for users aged 14 and over (Terms of Service, 2.1). Users aged 14 to 18 use the Service with the consent of their parents or other legal representatives.

SecondBook is intended for users aged 14 and over. The date of birth is optional and is not verified. If the Operator becomes aware that an account belongs to a person under 14, access to certain features of the Service may be restricted until the circumstances are clarified. A legal representative may contact support@secondbook.kz to have such an account checked or deleted. Entering into transactions on your own requires full legal capacity (as a general rule, from age 18) or the consent of a legal representative (Terms of Service, 2.1).

8.1. How Age Restriction Works

Some books in the catalog carry an age rating (16+, 18+ or 21+). Access to such content (in the catalog, search, book detail, cover and images, gifting, exchange, lending, and the book card in chat) is determined by the date of birth the user has entered in their profile settings.

9. Changes to the Policy

9.1. Amendment Procedure

We may update this Policy. We announce material changes in the Service: the new version is published on the Platform and shown when you sign in to the app, asking for your acceptance.

9.2. Version History

Previous versions of the Policy are available upon request.

On October 11, 2026 section 5.1 of version 1.5 was clarified: copies in the team's work chat — your support requests, your feedback and the review cards — are now deleted together with the account; copies about order disputes stay after the account is deleted and, as before, are deleted on request through support; copies sent before October 9, 2026 that cannot be linked to an account are also deleted on request, as described in 5.1. The right to have any message in the chat that relates to you deleted on request is kept. This narrows the processing of your data and therefore needs no new consent (9.1).

10. Additional Information Where the GDPR Applies

Where the GDPR applies to the processing of your personal data (including the cases provided for in Article 3 of the GDPR), the additional provisions set out in the "GDPR" document apply. In brief:

10.1. Legal Bases for Processing

10.2. EU Representative and Contacts

SecondBook does not have a representative in the EU. Send questions about data processing under the GDPR to the Operator: support@secondbook.kz

11. Contact Information

SecondBook

City: Almaty, Republic of Kazakhstan (no postal address is published; requests are accepted by email)

Privacy Email: support@secondbook.kz

GDPR Requests Email: support@secondbook.kz

General Support: support@secondbook.kz

Website: secondbook.kz

© 2026 SecondBook. All rights reserved.