Readimus Privacy Policy

Effective date: 5 October 2026 Last updated: 5 October 2026

This Privacy Policy explains what personal data Readimus collects and uses, why we process it, who may receive it, and what rights users have.

This Policy applies to the Readimus application, website, and other services (together, “Readimus” or the “Service”).

1. Who Is Responsible for Your Data

The controller of your personal data is Gaisar Davletkildin, an individual operating Readimus from Serbia (the “Operator,” “we,” “us,” or “our”).

For questions about personal data or to exercise your rights, email privacy@readimus.com.

2. Data We Process

Depending on how you use Readimus, we may process the following categories of data.

2.1. Account and Profile Data

email address;
your password in a protected form, as processed by the authentication system;
full or display name;
username;
profile description and avatar;
internal user identifiers;
privacy and community settings; and
dates relating to account creation and changes, email confirmation, and account sign-in.

We do not receive your password in plain text and cannot view it.

2.2. Guest Access Data

When you use guest mode, Readimus creates a technical anonymous account and associated internal identifiers and session data. That account does not contain your real email address, name, or username unless you choose to convert it into a standard account.

2.3. Book and Reading Data

books in your library and lists;
reading status and reading start and finish dates;
ratings, likes, and the history of changes to your reading activity;
lists you create, including their titles, descriptions, and visibility settings;
book, author, cover, and edition information that you add or suggest; and
search queries, ISBNs, and book identifiers from external sources.

2.4. User and Social Content

reviews, comments, and spoiler labels;
book notes and images attached to them;
reading activity posts and reactions to them;
follows, followers, and follow requests;
users you have blocked;
reports, selected report reasons, information submitted with reports, and a copy of the reported content saved at the time of the report; and
information about moderation measures and requests to review decisions.

2.5. Communications With Us

When you contact us, we may process your email address, name, the content of your message, attachments, and information needed to respond or investigate an issue.

2.6. Technical Data

When the Service operates, we and our infrastructure providers may automatically process:

IP address;
information about your browser, application, device, and operating system;
the date, time, and outcome of a network request;
account and session identifiers and authentication tokens;
technical logs, error information, and security events; and
your selected language and limited network information needed for the application to function.

When the application crashes or hits an error, it sends a crash report to our error-monitoring provider, Sentry (see Section 9). A report contains technical information: the error message and stack trace, the application version, the device model and operating system version, the names of the screens you visited shortly before the error, the method and address (without query parameters) of a failed network request, an account identifier, and whether the account is a guest account. We configure reports not to include your name, email address, IP address, screenshots, or screen recordings, and we do not intentionally include the text of your notes, reviews, or comments. Because a report carries your account identifier, it is linked to your account. Crash reports are sent only from the released application, not from development builds.

As of the date of the latest update, Readimus does not use separate SDKs for advertising tracking or push notifications. Usage statistics are described in Section 2.7.

2.7. Usage Analytics

To understand how Readimus is used and to improve it, the application sends anonymous usage statistics to our analytics provider, PostHog (see Section 9). The statistics contain: a random identifier generated on your device when you install the application (it is not linked to your account, and it changes when you reinstall the application or delete your account); events that describe what you do in the application, such as which screens you open, that you added a book or changed a reading status, or that you opened the application; whether you are using guest mode; the application language; and the application version and platform. They do not include your name, email address, username, account identifier, the text of your notes, reviews, comments or search queries, the titles of books, or your IP address. We do not link this data to your account and do not use it for advertising. Statistics are sent only from the released application, not from development builds. If several people use one device, or you sign out and sign in to another account, the statistics from that device are not separated.

3. Device Permissions and Local Data

If you choose to upload an avatar, a note image, or a book cover, the application may request access to your camera or photo library. Access is used only after your action and only to the extent necessary for the feature you selected. You can revoke permission in your device settings.

Readimus stores session data, cached books and search results, a profile snapshot, interface settings, and a random identifier used for usage statistics (Section 2.7) together with statistics waiting to be sent on your device. This helps keep you signed in and makes the application work faster. Local data may remain until you sign out, clear the application’s data, or uninstall the application, unless a shorter retention period applies to a particular record.

4. Where We Obtain Data

We obtain data:

directly from you when you register, complete your profile, publish content, or contact support;
automatically when you use the application or website;
from your interactions with other users;
from Google Books, ISBNDB, and other lawful sources of book information; and
from app stores and infrastructure providers where necessary to operate, secure, or support the Service.

5. How We Use Data

We use personal data to:

create and maintain accounts, confirm email addresses, and restore access;
provide guest mode and convert a guest account into a standard account;
maintain your library, reading diary, lists, notes, and other selected features;
display your profile and content in accordance with your privacy settings;
provide follows, user blocking, comments, reactions, in-app notifications, and other community features;
search for books and maintain the quality of the book catalog;
receive and review reports, moderate content, and review decisions;
respond to user communications;
protect users and the Service and prevent spam, fraud, unauthorized access, and circumvention of restrictions;
understand, in aggregate and without identifying you, how the Service is used, and improve it;
diagnose technical problems and maintain the reliability of the Service; and
comply with legal obligations and protect legal rights.

We do not use personal data for third-party advertising and do not sell it. Readimus has no paid features, subscriptions, in-app purchases, or payment data processing. We use email only for service messages related to your account, security, support, and operation of the Service, not for promotional mailings.

6. Legal Bases for Processing

Where applicable law requires us to identify a legal basis, we rely on one or more of the following:

performance of a contract — to create your account and provide features you request under the Terms of Use;
legitimate interests — to maintain security, prevent abuse, moderate the community, improve the reliability of the Service, understand how it is used so that we can improve it, and protect our legal rights, provided those interests are not overridden by your rights and freedoms;
legal obligation — where data must be processed or retained to comply with the law or a lawful request from a competent authority; and
consent — where consent is required for a particular optional activity. You may withdraw consent without affecting the lawfulness of processing that took place before withdrawal.

Account data identified as required is necessary to create a standard account. Without it, the relevant features may be unavailable.

7. Data Visibility and Public Content

Your username, display name, avatar, profile description, reviews, comments, public lists, social connections, and reading activity may be visible to other users depending on the type of content, your profile settings, and the community features you enable.

Your email address, password, access tokens, private notes, and note images are not intended for public display.

Do not add information to your profile, review, comment, or other public material that you do not want to disclose. Other people may copy or retain content that has already been published independently of Readimus.

8. Book Search and External Sources

When you search external book databases, your search query, an ISBN, or a book identifier may be sent through Readimus infrastructure to Google Books or ISBNDB. Readimus does not intend to send your name or email address to these services as part of such a request.

Search results and search query keys may be temporarily cached on the server to speed up search and keep it working when an external source is temporarily unavailable. Search results are normally current for 7 days and may be retained for up to another 30 days as a fallback if a source fails. Information about an individual book is normally current for 30 days and may be retained for up to another 30 days. An expired cache entry may be removed the next time the cache is updated. This cache is shared among users and is intentionally not associated with a particular account.

9. Who We Share Data With

We share data only to the extent necessary for the purposes described in this Policy with the following categories of recipients:

Supabase — authentication, database, file storage, and server-side functions;
Google Books and ISBNDB — book search and retrieval of book metadata and covers;
Sentry (Functional Software, Inc.) — collection and analysis of crash and error reports, described in Section 2.6;
PostHog (PostHog, Inc.) — collection and analysis of anonymous usage statistics, described in Section 2.7;
Vercel — temporary hosting for the website and account-related pages; this Policy will be updated if the hosting provider changes;
email delivery and communications providers — delivery of service messages and handling of communications;
professional advisers and contractors who need access to provide services and are required to maintain confidentiality;
public authorities, courts, and other persons where disclosure is required by law or necessary to protect rights, safety, the Service, or its users; and
a successor to the Operator if Readimus is transferred to a company or another owner in accordance with applicable law.

We do not share personal data with data brokers and do not sell it.

Apple and Google may independently receive technical data and app store account information when you download or update the application. Their own policies govern that processing. Readimus does not ordinarily provide them with your profile data or User Content for application distribution.

10. International Data Transfers

Readimus is available to users worldwide and is operated from Serbia. Our service providers and their subprocessors may process data in other countries. The primary region of the Supabase project is Central Europe (Frankfurt, Germany). Crash reports are stored in Sentry’s European Union region; Sentry’s operator is a company based in the United States. Anonymous usage statistics are stored in PostHog’s European Union region; PostHog’s operator is also a company based in the United States.

Where applicable law requires safeguards for international data transfers, we use legally recognized mechanisms, such as an adequacy decision, standard contractual clauses, or other permitted safeguards.

11. How Long We Retain Data

We retain data only for as long as necessary for the relevant purpose, taking security and legal requirements into account.

standard account data and associated content are retained for as long as the account exists, unless a shorter or longer period is stated below;
abandoned guest accounts are automatically deleted after 30 days of inactivity;
data on your device is retained as described in Section 3;
the server-side book search cache is retained as described in Section 8;
support communications are normally retained for up to 2 years after the request is closed;
reports and moderation records are normally retained for up to 3 years after the report is closed;
technical logs are retained only for as long as reasonably necessary to maintain security, investigate incidents, and diagnose technical problems;
crash reports are retained by Sentry for 30 days and then deleted automatically;
anonymous usage statistics are retained by PostHog for up to 1 year and then deleted automatically; and
data remaining in backups is deleted through the normal backup rotation process within 7 days.

Some data may be retained for longer where necessary to comply with a legal obligation, maintain security, prevent repeated violations, resolve a dispute, or establish, exercise, or defend legal claims. At the end of the applicable period, the data is deleted or anonymized.

12. Account Deletion

You may delete a standard account through the application settings. When you do so, Readimus deletes the account, associated profile, library, lists, reviews, comments, social connections, notes, avatar, and note images, except for data that must be temporarily retained for the reasons described in Section 11.

Book information and covers added to the shared catalog may continue to exist as part of the shared book database if they are no longer associated with you and do not identify you.

Anonymous usage statistics (Section 2.7) are not linked to your account and are therefore not deleted together with it. When you delete your account, the application resets the random identifier on your device, so earlier statistics are not carried over to what you do next. Statistics already collected are deleted automatically when the period in Section 11 ends.

Files in backups may remain for a limited time until their scheduled deletion. If an individual file is not removed automatically because of a technical error, we may remove it after we discover the issue or receive a request from a user.

You can also request account and associated data deletion through our external Account deletion page.

13. Your Rights

Depending on applicable law, you may have the right to:

learn whether we process your personal data and obtain access to it;
correct inaccurate or incomplete data;
request deletion of data;
restrict processing;
object to processing based on legitimate interests;
receive data you provided in a portable format;
withdraw consent where processing is based on consent; and
lodge a complaint with a competent data protection authority.

To exercise your rights, email privacy@readimus.com. We may request information necessary to verify your identity and protect your account. We will respond within the period required by applicable law.

Because usage statistics are not linked to your account, we cannot find or delete the statistics of a particular person on request. The application currently has no setting to turn usage statistics off. If you object to this processing, email privacy@readimus.com and we will review your objection.

You may contact the Serbian Commissioner for Information of Public Importance and Personal Data Protection or, where applicable, the data protection authority in the country where you live or work.

14. Children’s Data

Readimus is intended for people aged 16 and older. We do not knowingly collect personal data from children under 16.

If a user has not reached the age of majority in their country, they may also need permission from a parent or legal guardian in accordance with the Terms of Use and applicable law.

If you believe that a child under 16 has provided us with personal data, email privacy@readimus.com so that we can review the situation and take appropriate action.

15. Automated Decision-Making

As of the date of the latest update, Readimus does not make decisions based solely on automated processing that produce legal effects for a user or similarly significantly affect them.

16. Security

We take reasonable technical and organizational measures to protect data, including access controls, database-level permission separation, secure data transmission, and authorization checks for account deletion.

No method of storing or transmitting data is completely secure. If you believe your account or data has been compromised, email support@readimus.com.

17. Changes to This Policy

We may update this Policy when Readimus, our data processing practices, or the law changes. The current version and the date of the latest update will be published on the Readimus website.

We will notify you of material changes through the application, by email, or by another appropriate method where required by law. If consent is required for new processing, we will request it separately.

18. Contact Us

For questions about this Policy or personal data, email privacy@readimus.com.

For general questions about Readimus, email support@readimus.com.