Privacy Policy

Version: 2026-10-14

In short. This policy explains how we, the provider of Readerr, use personal data for our own purposes: your Account, our website, our emails and the Pronunciation Dictionary. We use it to run the service, keep it secure and, only if you agree, to measure our website and send you marketing. We do not sell personal data and we do not use it for advertising. Article texts and Listener data that we process for Customers are covered by the Customer's own privacy notice and our Data Processing Agreement, not by this policy. You can write to us about your data at any time at [email protected]. We update this policy as Readerr changes; the version date shows the current one (section 17).

1. Who we are

1.1. The controller of your personal data is IT Busters Marcin Rybak, a sole proprietorship registered in Poland, ul. Bolesława Chrobrego 12, 38-400 Krosno, Poland, NIP 6842342603, REGON 368728920 ("we", "us"). We provide the Readerr service ("Readerr"). More details: Legal notice.

1.2. Contact for all privacy matters: [email protected]. We answer in English and Polish.

1.3. We have not appointed a data protection officer. We are not required to have one. Write to the address above instead.

1.4. Terms written with a capital letter (for example Account, Customer, Player, Listener, Pronunciation Dictionary, Trial, Grace Period, Plan, Top-up, Link) have the meaning given in our Terms of Service.

2. What this policy covers and what it does not

2.1. This policy covers personal data that we process as a controller, that is, for purposes we decide ourselves:

a. the Accounts of our Customers and the people who sign in to them;
b. our website readerr.app, including the contact form, the blog and the customer panel at readerr.app/app;
c. emails we send;
d. the Pronunciation Dictionary (section 6);
e. security, abuse prevention and the handling of legal requests.

2.2. This policy does not cover data that we process on behalf of our Customers. In that case the Customer is the controller and we act as its processor under our Data Processing Agreement. This includes:

a. the text and titles of articles that a Customer sends us, and any personal data in them (for example people named in an article or its author);
b. the Audio we create from those articles and store for the Customer;
c. data about Listeners on the Customer's website: the requests their browsers make to download the Player and the Audio, and the listening statistics the Player sends after they press play.

2.3. If you are a Listener or a person named in an article, please read the privacy notice of the website where you heard the Audio. We give Customers a template for that notice: Publisher privacy notice. You can also write to us. We will pass your request to the right Customer or help it answer.

2.4. The one exception to section 2.2 is the Pronunciation Dictionary. We keep it for our own purpose, so we are its controller. Section 6 explains it.

3. Where your data comes from

3.1. From you. When you sign up, sign in, use the customer panel, fill in the contact form or write to us.

3.2. From your website. When you connect a website to Readerr, the integration you use (for example our WordPress plugin or our API) sends us the site's domain and technical details of each request (for example the plugin's User-Agent, which names the plugin, WordPress and PHP versions).

3.3. From Link. When you buy a Plan or a Top-up, Link tells us the result: identifiers of your customer record and subscription, the Plan and billing interval you chose, the subscription status and the end date of the paid period.

3.4. From your browser. Your IP address and browser details when you visit our website, and cookies as described in our Cookie Policy.

3.5. From articles. For the Pronunciation Dictionary only: fragments of text found in articles that Customers send us (section 6).

4. What we use your data for

4.1. The table below lists each purpose, the data, the legal basis under the EU General Data Protection Regulation (GDPR) and how long we keep the data. "Account deletion" means the moment we carry out the deletion of your Account (section 5.6).

#	Purpose	Data	Legal basis	How long we keep it
1	Creating your Account and letting you sign in	email address (a Gmail address is stored in one standard form, section 5.1), Account name, the date you accepted the Terms and the version you accepted, sign-in links and sessions (we store only a one-way hash of each)	contract, art. 6(1)(b)	sign-ups never confirmed: 7 days; sign-in link valid 15 minutes, session up to 7 days, technical records of both deleted 30 days after they expire; the rest until Account deletion
2	Providing Readerr and managing your Account	domains of your websites, the plugin, WordPress and PHP versions your integration reports, Plan, billing interval, subscription status, character usage history, Top-ups, API keys (stored as a hash), your messages to us about the service	contract, art. 6(1)(b)	until Account deletion
3	Payments (section 9)	identifiers of your customer record and subscription at Link, Plan, billing interval, subscription status, end date of the paid period	contract, art. 6(1)(b)	until Account deletion
4	Service emails (section 8)	email address, content of the message	contract, art. 6(1)(b)	the copies we keep follow row 2
5	Marketing emails (section 8)	email address, whether and when you agreed or withdrew, the version of the consent wording and where you gave it; as proof, a one-way hash of your email address	sending: consent, art. 6(1)(a); keeping the proof: legitimate interest, art. 6(1)(f): showing that we had your consent (art. 7(1))	email address: until you withdraw consent or until Account deletion; proof of consent: 3 years after you withdraw consent or your Account is deleted, whichever comes first
6	Keeping Readerr secure and limiting abuse of sign-in and the contact form	counters of requests per IP address and per email address (stored as a hash, or for the contact form held only in the server's memory), technical logs that may contain IP addresses, email addresses and error details	legitimate interest, art. 6(1)(f): protecting the service and its users	counters expire on their own after at most 1 hour; logs at most 30 days
7	Bot protection on the contact, sign-up and sign-in forms (section 7.4)	IP address and browser signals, sent to our bot-protection provider	legitimate interest, art. 6(1)(f): stopping automated abuse	we do not store them
8	Allowing only one Trial per domain	domain name of each website that has used a Trial, and when	legitimate interest, art. 6(1)(f): preventing abuse of free Trials	at most 3 years
9	Pronunciation Dictionary (section 6)	a fragment of text (which may be a person's name) and how to read it; for proposals our check refused (section 6.6), also the website the article came from and when the proposal was seen; for the block list (section 6.11), a one-way hash of the blocked fragment	legitimate interest, art. 6(1)(f): correct pronunciation in the service and protecting the Pronunciation Dictionary from manipulation; for the block list, legal obligation, art. 6(1)(c)	entries: no fixed period, deleted on a successful objection or erasure request; refused proposals: 90 days after the proposal was last seen, or earlier when the fragment is blocked or the Account is deleted; block list: for as long as we keep the Pronunciation Dictionary
10	Website analytics (section 7.2)	pages visited, clicks on a few buttons, approximate location, device and browser details, Google Analytics cookie identifiers	consent, art. 6(1)(a)	cookies: see Cookie Policy; data in Google Analytics: at most 14 months
11	Remembering your cookie choice	your choice (accept or reject analytics)	legitimate interest, art. 6(1)(f): respecting your choice	180 days
12	Answering the contact form and emails to [email protected]	name, email address, topic, message	legitimate interest, art. 6(1)(f): answering you; or steps before a contract at your request, art. 6(1)(b)	not stored in our database; the email stays in our mailbox for 1 year after the last message in the matter, or until Account deletion if you are a Customer and that is later
13	Handling Account deletion requests	email address in the request, the timing you chose (now or at the end of the paid period)	legal obligation, art. 6(1)(c) (right to erasure); contract, art. 6(1)(b)	email address removed once the deletion is done; a record without personal data stays
14	Handling privacy requests, complaints and legal notices, and keeping records of what we did	your request, our answer, contact details	legal obligation, art. 6(1)(c); keeping the records: legitimate interest, art. 6(1)(f): showing that we handled the request	3 years after we close the request
15	Establishing, exercising or defending legal claims	the data from rows 1-14 that relates to the claim	legitimate interest, art. 6(1)(f)	within the periods above
16	Record of administrative actions in Readerr	who did what and when	legitimate interest, art. 6(1)(f): security and accountability	personal data removed at Account deletion; the entry stays without it, except the proof of marketing consent (row 5)

4.2. You do not have to give us your personal data. Without an email address we cannot create an Account or send you a sign-in link. Marketing emails and website analytics are optional; saying no has no effect on the service.

4.3. Where we rely on legitimate interest, we have weighed our interest against your rights. You can object at any time (section 13.3).

5. Your Account and the customer panel

5.1. Sign-up. You sign up with your email address and an Account name. We send a link to confirm the address. If you do not confirm it within 7 days, we delete the sign-up. When you sign up, we record that you accepted the Terms of Service and the version you accepted. We also record whether you ticked the separate, optional box for marketing emails. One Gmail mailbox can be written in many ways (with or without dots, with a "+" suffix, or with googlemail.com); we store a Gmail address in one standard form, without dots and without the suffix, so that one mailbox holds only one Account. Emails we send to that form reach the same mailbox.

5.2. Sign-in without passwords. You sign in with a link we email to you. The link works for 15 minutes. After you sign in, a session keeps you signed in for up to 7 days. We store only a one-way hash of each link and session, never the link or session itself. If we add other sign-in methods, we will update this policy before they go live.

5.3. Limits on sign-in requests. To stop someone from flooding a mailbox or guessing links, we count sign-in requests per email address and per IP address. The counters are hashed and expire on their own after at most 1 hour.

5.4. Websites and usage. For each website you connect we keep its domain, its API key (as a hash) and how many characters it used. You see this in the customer panel.

5.5. One Trial per domain. A Trial can be used once per domain. To enforce this, we keep a register of the domains that have used a Trial. We keep each entry for at most 3 years. If the domain name contains your name, the entry is personal data.

5.6. Account deletion. You can ask for deletion in the customer panel, now or at the end of your paid period. We carry it out within 30 days of your request. An Account that has expired (after the end of the Grace Period) is deleted 30 days after the Grace Period ends. Deletion removes your Account from our database and the Audio files from our content delivery network. Backups expire as described in section 12.

6. Pronunciation Dictionary

6.1. What it is. Readerr keeps one shared Pronunciation Dictionary for all Customers. Each entry is a pair: a fragment of text and how to read it aloud, for a given language. For example, a proper name, a foreign word or an abbreviation, and its spelling for the voice. When the same fragment appears in a later article, Readerr reads it the same way. This makes the Audio more correct for everyone.

6.2. Why it may contain personal data. Some entries are names of people, because people are named in articles. A name, even without anything else, can be personal data.

6.3. What we store. Only the fragment, its reading and the language. An entry has no link to the article it came from or to the Customer that sent the article. We cannot tell from an entry where it came from. Refused proposals (section 6.6) are the one exception: we keep them for a limited time together with the website they came from.

6.4. Private individuals are kept out. We keep names of private individuals out of the Pronunciation Dictionary, within the limits described in section 6.5. They are used only to read the current article and are not kept after that article is ready. The Pronunciation Dictionary holds names of people who appear in public life (for example politicians, athletes, artists, public officials) and names that are not people's names at all. We also add some entries by hand.

6.5. How entries are selected. Entries are proposed by the large language model that prepares pronunciation for Customers (section 10.1 g). The same model judges whether a name belongs to a private individual, and such names are left out; when the model is unsure, the name is treated as a private individual's. Before a new entry is added, a second, separate request to the same provider checks that the proposed reading is plausible and not an attempt to manipulate the Pronunciation Dictionary; only entries it accepts are added. These checks are automated and work as far as is technically possible, so they can make mistakes. If the name of a private individual is kept by mistake, we delete it as soon as we learn of it, and you can ask us to (section 6.11).

6.6. Refused proposals. When the check described in section 6.5 refuses a proposed entry, we keep a record of the refusal: the fragment, the proposed reading, the language, the website whose article it came from, and when and how often it was proposed. We use these records only to spot and stop attempts to manipulate the Pronunciation Dictionary and to correct refusals that were wrong. We delete each record 90 days after the proposal was last seen, and earlier if the fragment is blocked (section 6.11) or the Account of that website is deleted. Names that the model judged to belong to private individuals are not checked and are not kept in these records.

6.7. Source of the data. The fragments come from articles that our Customers publish on their websites and send to Readerr to be converted into Audio. We do not collect them from anywhere else.

6.8. Legal basis. Our legitimate interest in reading names and words correctly in the service we provide to all Customers (art. 6(1)(f) GDPR). The entry is limited to what the voice needs: how to read the name. For refused proposals (section 6.6), our legitimate interest in protecting the Pronunciation Dictionary, and so the Audio of all Customers, from manipulation.

6.9. Who sees the entries. Only us, and the language model provider while it proposes and checks entries (section 6.5). The service applies an entry automatically when it prepares an article in which the same fragment appears; the result is heard only as pronunciation in the Audio.

6.10. How long. Entries have no fixed end date, because correct pronunciation stays useful. They stay after a Customer leaves, because they are not linked to any Customer. We delete an entry when you successfully object to it or ask for its erasure.

6.11. Your rights. If an entry concerns you, you can ask us whether it exists, object to it or ask us to delete it, by writing to [email protected]. Tell us the name and, if you can, the language. If you object, we delete the entry and make sure it is not added again. To do that, we keep a one-way hash of the blocked fragment (not the fragment itself) on a list used only to stop it from being added again (legal obligation, art. 6(1)(c) GDPR: complying with your objection or erasure request). The block applies to that exact spelling, in all languages; other grammatical forms of the name are separate fragments, so please list the ones you want blocked. We also delete any refused proposals with that fragment. Readerr may still read your name correctly in a new article that mentions you, but only while preparing that article.

6.12. Why we do not contact each person. Entries contain only a name and its reading, without any contact details or link to the source. We have no way to identify or reach the people concerned. That is why we inform them through this policy.

7. Our website

7.1. Cookies. Our Cookie Policy lists every cookie we use. The customer panel uses only cookies that are strictly necessary to sign you in.

7.2. Google Analytics, only if you agree. On the pages of readerr.app (not in the customer panel) we ask whether you accept analytics. We use Google Analytics 4, a service of Google, to see which pages help visitors and how many people start a Trial or play the demo. Until you click "Accept analytics", Google's script is not loaded and your browser sends nothing to Google. If you reject, nothing is sent. If you accept, Google Analytics sets its cookies and receives data about your visit (row 10 of the table). We turn off Google's advertising features: advertising storage, sending user data for advertising and ad personalisation are all set to "denied". We also turn off the sharing of Analytics data with other Google products and services. We keep the data in Google Analytics for at most 14 months. You can change your choice at any time with Cookie settings in the footer of the website. If you withdraw consent, we delete the Google Analytics cookies from your browser. Google describes how it uses data from sites that use its services at policies.google.com/technologies/partner-sites.

7.3. Contact form. The form asks for your name, email address, a topic and your message. We send the message to our own mailbox by email and use it only to answer you. We do not save it in our database. To stop spam, we limit the number of messages per IP address. The counter is held only in the server's memory, for at most 1 hour.

7.4. Bot protection. The contact form, the sign-up and sign-in pages and the page where you confirm a sensitive action use a bot-protection check from our network provider. The check runs in your browser and sends your IP address and technical signals about your browser to the provider, which tells us only whether the visitor looks human. We do not store this data. The provider processes these signals for us to run the check, and, as a separate controller under its own Turnstile privacy addendum, to improve its bot detection. The provider is listed on our Subprocessors page.

7.5. Blog audio. Some blog posts include the Readerr Player. On our blog the Player stores nothing on your device and sends no listening statistics. The Player script and the audio file are delivered from our content delivery network, which, like any web server, sees your IP address and browser details in order to deliver the file. We do not keep these requests.

7.6. Fonts and other resources. We host our fonts ourselves. The website does not load fonts, social media widgets or advertising scripts from other companies.

8. Emails

8.1. Service emails. We send you emails that are needed to provide Readerr: sign-in and confirmation links, notices about your Account, Trial, Grace Period, Plan and usage, notices about changes to our terms or subprocessors, and answers to your messages. You cannot switch these off while you have an Account, because the service needs them.

8.2. Marketing emails, only with consent. We send news and offers only if you ticked the separate, unticked box when you signed up, or later agreed in the customer panel. You can withdraw consent at any time: in the customer panel, with the one-click unsubscribe link in every marketing email, or by writing to us. Withdrawal does not affect emails sent before. To be able to show that we had your consent, we keep a record of when you gave and withdrew it, the wording version and a one-way hash of your email address for 3 years after you withdraw consent or your Account is deleted (row 5). The hash does not let us email you.

8.3. We send emails through an email delivery provider. It sends the emails from the EU, but keeps its account data, email metadata and logs in the United States (see section 11 and Subprocessors).

9. Payments

9.1. We sell Plans and Top-ups through Link (Sold through Link, LLC, a company of the Stripe group), which acts as the merchant of record. Link collects the payment, charges VAT, issues invoices and receipts, and handles refunds and disputes.

9.2. Link collects your payment details (for example card details and billing address) directly, on its own pages. Link is a separate controller of this data. Its privacy notice explains how it uses it: link.com/privacy. The Stripe Privacy Center, in its section on "Sold through Link", explains which Stripe company is responsible in your country: stripe.com/legal/privacy-center.

9.3. What we send to Link: your Account identifier, your email address and the Plan or Top-up you want to buy.

9.4. What we keep: the identifiers of your customer record and subscription at Link, the Plan, the billing interval, the subscription status and the end date of the paid period (rows 2 and 3). We do not store card numbers or bank details.

9.5. Link can show us details of your order (for example your name, billing country and tax ID, if you gave one) in its dashboard so we can help you. We do not copy them into our own database.

10. Who receives your data

10.1. We share personal data only as far as needed for the purposes in section 4. Recipients fall into these categories:

a. Service providers that process data on our behalf (processors): the provider of our servers and backups (EU), the provider of our content delivery network, file storage, bot protection and network security (all traffic to our website, customer panel and API passes through its network), the provider of email delivery (sending from the EU; email metadata and logs in the United States), and the provider of our mailbox for [email protected] (data centre in the EU). They may use the data only on our instructions. Their names, locations and the data each receives are on our Subprocessors page.
b. Google, as our processor for Google Analytics, only if you accepted analytics (section 7.2).
c. Link, as a separate controller, when you buy a Plan or a Top-up (section 9).
d. Public authorities and courts, when the law requires us to.
e. Our professional advisers (for example lawyers or accountants), who are bound by confidentiality, when we need their advice.
f. A buyer of our business, if we transfer Readerr to another company. We will tell you before that happens.
g. The provider of the large language model that prepares pronunciation (Google, under its terms for the paid Gemini API, as our processor): for the Pronunciation Dictionary, it proposes entries, judges whether a name belongs to a private individual and checks each new entry before it is added (section 6.5). It does not use the data to train its models.

10.2. The provider of the large language model receives the text of articles in order to prepare pronunciation. That is processing for Customers under the Data Processing Agreement, not processing of your Account data. The only part of it done for our own purpose is the selection of Pronunciation Dictionary entries (section 10.1 g).

10.3. We do not sell personal data and we do not share it for advertising.

11. Transfers outside the European Economic Area

11.1. We store our database, backups and Audio in the European Union.

11.2. Some providers are based in the United States or can process data there: the provider of our content delivery network, network security and bot protection (its network runs worldwide and carries all traffic to our website, customer panel and API), the provider of email delivery (email metadata and logs), the provider of our mailbox (its group companies in other countries, for example India, may access data for support), and Google as the provider of Google Analytics and of the large language model (for Pronunciation Dictionary entries, section 10.1 g).

11.3. For these transfers we rely on:

a. the EU-US Data Privacy Framework, where the provider is certified under it (European Commission adequacy decision of 10 July 2023); and
b. the Standard Contractual Clauses adopted by the European Commission (Decision (EU) 2021/914), included in the provider's data processing terms.

11.4. The Subprocessors page shows the safeguard for each provider. You can ask us for a copy of the safeguards at [email protected].

11.5. Link is responsible for its own transfers as a separate controller (section 9).

12. Backups, snapshots and logs

12.1. Database backups are kept for at most 30 days. Data you deleted, or that we deleted under this policy, disappears from backups when they expire.

12.2. Snapshots of our servers (stored in Finland) are kept for at most 30 days.

12.3. Technical logs of our servers are rotated and kept for at most 30 days.

13. Your rights

13.1. Under the GDPR you have the right to:

a. access your data and get a copy (art. 15);
b. rectification of inaccurate data (art. 16); you can correct most Account data in the customer panel;
c. erasure (art. 17); for your whole Account, use the deletion option in the customer panel;
d. restriction of processing (art. 18);
e. data portability for data you gave us under a contract or consent (art. 20);
f. object to processing based on legitimate interest (art. 21), see section 13.3;
g. withdraw consent at any time, without affecting processing before the withdrawal (art. 7(3)): for analytics with Cookie settings in the website footer, for marketing in the customer panel or with the unsubscribe link.

13.2. How to use your rights. Write to [email protected]. If you have an Account, write from its email address, or we may ask you to confirm the request through a link sent to it. We answer within one month. For complex or numerous requests, we can extend this by up to two more months; if so, we will tell you why within the first month. Using your rights is free, unless a request is clearly unfounded or excessive.

13.3. Right to object. Where we process your data on the basis of our legitimate interest (rows 6-9, 11, 12, 15 and 16 of the table, and the proof of consent in row 5 and the records in row 14), you can object at any time, on grounds relating to your particular situation. We will then stop, unless we have compelling legitimate grounds that override your interests, rights and freedoms, or we need the data to establish, exercise or defend legal claims. This applies in particular to entries about you in the Pronunciation Dictionary (section 6.11).

13.4. Complaint. You can lodge a complaint with a data protection authority. In Poland this is the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych), ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl. You can also complain to the authority in the EU country where you live or work, or where you think the breach took place. We would be glad if you wrote to us first, so we can try to fix the problem.

14. No automated decisions or profiling

14.1. We do not make decisions about you based solely on automated processing that have legal effects on you or similarly significantly affect you. We do not profile you.

14.2. Some checks run automatically, for example refusing a second Trial for a domain that has already used one (section 5.5), or pausing audio generation when your character allowance runs out. These follow fixed rules set out in the Terms and in our offer. If you think a check treated you wrongly, write to us and a person will review it.

15. Security

15.1. We protect personal data with measures that match the risk. In short:

a. all connections are encrypted (TLS);
b. sign-in links, sessions and API keys are stored only as one-way hashes;
c. our servers talk to each other over a private, encrypted network;
d. administrative access requires authentication and follows the principle of least privilege;
e. we record administrative actions;
f. we keep only what we need; for example, article texts are deleted once the Audio is ready;
g. we keep backups, apply updates and scan our software images for known vulnerabilities.

15.2. If a personal data breach is likely to result in a high risk to you, we will tell you without undue delay.

16. Children

16.1. Readerr is for people aged 18 or over. We do not knowingly collect data from children. If we learn that an Account belongs to someone under 18, we will delete it.

17. Changes to this policy

17.1. We may update this policy when the service, our providers or the law change. The version date at the top shows when it last changed.

17.2. If a change matters for Account holders, we will email them before it takes effect and explain what changes. We keep previous versions and will send them to you on request.