- This policy describes the current version of Read Bro. When the app changes, this page changes too. Before a material change applies, we tell you as described in "Changes to this policy".
- We keep what the app needs to work: your account, your place in each book, your saves and highlights, and a record of how you use the app.
- We keep that record on our servers, which a cloud service provider hosts for us. Today, Read Bro uses no third-party analytics or advertising tools, does not access your advertising identifier and does not track you across other companies' apps or websites.
- You can delete your account in the app at any time. That removes your account and the data linked to it from our database straight away. A few limited records can remain for a short time, as explained below.
- Questions and requests go to readbro@foxnutstudios.com.
Who we are
Read Bro is made by Ameya Sahasrabudhe, an individual based in Bengaluru, Karnataka, India. In this policy, "we", "us" and "our" mean Ameya Sahasrabudhe.
We decide why and how your personal data is used, so we are responsible for it. Data protection laws have names for this role. Under the GDPR and the UK GDPR it is the "data controller". Under India's Digital Personal Data Protection Act, 2023 it is the "data fiduciary".
Write to readbro@foxnutstudios.com with any question, request or complaint about your personal data, wherever you live. Ameya Sahasrabudhe is also the grievance officer for India, and the person who answers questions about how your data is processed, at the same address.
What we collect
Your account
You can use Read Bro without signing in. During the first-run questions, the app creates a guest account on our server so that it can pick your first books. This happens before you choose whether to sign in. What we store after that depends on how you use the app.
- Guest account. Linked to an identifier for your phone that Apple gives to our apps. If Apple does not provide one, the app creates a random one. It is not your device's advertising identifier. A guest account has no name and no email address.
- Sign in with Apple. Apple gives us an account identifier and, if you choose to share them, your name and your email address (or an Apple private relay address). We also keep a token from Apple so that we can ask Apple to end Read Bro's access when you delete your account.
- Continue with Google. Google gives us an account identifier, your email address and your name. The current version does not keep your Google profile picture or any Google access token.
- Email sign-in. The current version does not offer email sign-in. For an account made with email in an earlier test version, we keep the email address and a one-way hash of the password, never the password itself.
For every account we also keep your display name if you set one, your time zone and language setting, and your sign-in method. We also keep whether you finished the first-run questions, when the account was created and last changed, and which version you see when we test 2 versions of a feature.
What you do in the app
- Your reading. The books you open, where you are in each one, how many words and minutes you have read, the chapters and books you finish, your daily goal, and your streak, including grace days and pauses.
- Your first-run answers. Why you want to read, the genres and moods you like, any favourite authors you name, and your daily goal. You can skip the questions about genres, moods and authors.
- What you keep. The books you save and the passages you highlight. For a highlight, we store the highlighted text itself and its place in the book, so that it appears on any phone where you sign in.
- Recommendations. The books we showed you, where we showed them, the reason we gave, and any "More like this" or "Not for me" you tap.
- Usage events. Records of set actions in the app. Examples are opening the app, reading or finishing a screen, starting or finishing a book, and seeing or tapping a recommendation. Others are searching, saving, highlighting, sharing, pausing a streak and answering the notification prompt. Each event records the time, your time zone and local date, the app version, the book, chapter or screen involved, and any feature test you are in. It also records a random session code that changes each time the app starts, and a few details about the action, such as how many seconds you spent on a screen. The app records events before you sign in as well. It keeps them on your phone for up to 30 days until it can send them to our server.
- Searches. The words you search for, including as you type, go to our server so that it can find books. Today, our server does not store them or write them to its logs. Our hosting provider's network logs may include them (see "Our hosting provider's logs" below). The search event records only how many characters you typed, how many books were found and the position of any result you open.
- Define. Definitions come from the dictionary on your iPhone. We record that you opened a definition, whether your dictionary had an entry and how long the word was, not the word itself. If you tap Search the web, the word opens as a web search in your browser.
- Share cards. Cards are made on your phone. We record that you made a card and which style you picked, not the passage.
- Reminders. Reminders are scheduled on your phone, not sent by our server. We record whether you allowed notifications, which reminders are scheduled and at what hour, and when you open one, not the text of the notification.
- Messages to us. If you write to us, we keep your email address, your message and our reply.
Technical data
- IP address and security counters. Your IP address is the internet address of your connection. To limit repeated sign-in and session requests, which protects accounts from attacks, our server keeps short-lived counters. They are keyed by a hashed form of your IP address and, for sign-in, a hashed form of your account identifier, device identifier, session token or email address. The server does not store the address or identifier itself. Each counter stops counting after its time window, which is 1 minute for IP addresses and up to 24 hours for email sign-in. Expired counters are deleted from time to time. A hash of a short value, such as an IP address, could in principle be matched back to the original, so we treat these counters as personal data.
- Server logs. For each request, our server logs the address of the page or data requested (not your search words), the result, how long it took and a random request identifier. Our logs are set up to leave out names, email addresses, passwords and sign-in tokens. A few kinds of log entry include an account's internal identifier, which is a random code, not your name or email address.
- App version. Requests from the app include the app's name and version.
- Our hosting provider's logs. Our hosting provider may record IP addresses and the addresses of requests in its own network logs, for security and to run its service. A request address can include the words you search for.
What we do not collect today
- Your location, contacts, camera, microphone, health or financial data.
- Your phone number or date of birth.
- Your advertising identifier.
- Payment details. The current version has no purchases or subscriptions.
- Crash reports from a third-party crash-reporting tool. If you have chosen in your iPhone's settings to share analytics with app developers, Apple may give us crash reports and combined usage figures that do not name you.
- Your photo library. If you save a share card, iOS asks your permission to add that one image. That permission lets the app add images, not read your photos.
If a future version needs any of these, we will update this policy first and, where the law or Apple requires it, ask for your permission in the app before we collect it.
How we use it
| Why we use it | What we use | Legal basis under the GDPR and UK GDPR |
|---|---|---|
| To run the app: sign you in, keep your place in every book, and keep your saves, highlights and streak on every phone where you sign in | Account details, reading, saves, highlights | Providing the app you asked for (our contract with you) |
| To count your streak and daily goal by your own midnight | Reading, time zone | Our contract with you |
| To choose books for you and show why each one was picked | First-run answers, reading, saves, highlights, recommendation feedback, books shown | Our contract with you, because picking books is a core part of the app |
| To show figures drawn from many readers, such as how many readers finish a book | Reading data from all readers, combined | Our legitimate interest in helping readers choose books. A book's finish rate appears only when at least 50 readers are counted, and these figures show totals only, not individual readers |
| To understand and improve the app, including testing 2 versions of a feature | Usage events, feature test versions, app version | Our legitimate interest in making the app work better |
| To keep the service secure and limit abuse | Security counters, server logs, sign-in records | Our legitimate interest in protecting you, other readers and the service |
| To send sign-in codes and password-reset emails, for email accounts | Email address | Our contract with you |
| To answer your messages and requests | Your email address and message | Our contract with you, and our legal obligations for rights requests |
| To meet legal obligations and deal with legal claims | Whatever the obligation or claim needs | Legal obligation, and our legitimate interest in defending our rights |
Where we rely on legitimate interests, we have weighed them against your interests and rights. You can object at any time. See "Your choices".
Under India's Digital Personal Data Protection Act, we use your data for the purposes above in 2 cases. The first is when you give it to us yourself for that purpose, for example when you sign in. The second is when you give your consent. You can withdraw your consent at any time, as described in "Your choices". Withdrawing does not affect what we did before.
Recommendations and feature tests are automated. They change which books and designs you see. We do not use them to make decisions with legal or similarly serious effects on you, such as decisions about money, work or access to services.
What you have to give us. You do not have to give us your name or email address. You can use Read Bro as a guest, and with Sign in with Apple you can hide your email address. The app needs a guest identifier or a sign-in to save your reading, and it records usage events as part of how it works.
Marketing. We do not currently send marketing emails or marketing notifications. If we start, we will ask for your permission where the law requires it, and each message will include a way to stop them.
AI. Read Bro does not send your personal data to AI services.
Your choices
- Use Read Bro as a guest. You do not need to sign in to read.
- Skip questions. You can skip the first-run questions about genres, moods and authors.
- Reminders. Reminders reach you only after you allow notifications. You can turn each reminder off in the app, in Settings, Reminders, or turn off notifications for Read Bro in your iPhone's Settings.
- Recommendations. Tap "Not for me" or "More like this" on a recommended book to steer what you see.
- Usage events. The current version of the app has no setting to turn usage events off. We record them because of our legitimate interest in running and improving the app. You can object at any time by writing to readbro@foxnutstudios.com. Where the law gives you that right, we will stop using your usage events for analytics and delete the ones we hold, or explain why we cannot. If we add a setting in the app, we will describe it here.
- Withdraw consent. Where we rely on your consent, for example for notifications, you can withdraw it at any time. Turn notifications off in your iPhone's Settings, delete your account in the app, or write to us.
- Stop collection. Deleting your account stops us collecting data linked to that account.
Who else handles it
Today, we do not sell your personal data and we do not rent it. We also do not share it for cross-context behavioural advertising. This term, used in US state privacy laws, means ads based on what you do on other companies' apps and websites.
These organisations handle personal data so that Read Bro can work:
| Organisation | What they do | What they receive |
|---|---|---|
| Cloud service provider | Hosts our servers and database in the United States. | The account, reading and usage data described in "What we collect", and our server logs, stored on our behalf. |
| Email delivery provider | Sends sign-in codes and password-reset emails for email accounts. The current version does not offer email sign-in. | Your email address and the message. |
| Email provider | Hosts our email inbox. | Messages you send us, including requests about your data and complaints, your email address and our replies. |
| Apple | Sign in with Apple. Confirms who you are. When you delete your account, we ask Apple to end Read Bro's access. | A sign-in code from Apple, and the token Apple gave us, sent back to Apple. If you chose to share analytics with app developers, Apple also collects crash and usage data and shares some of it with us. |
| Continue with Google. Confirms who you are. | What you approve on Google's sign-in screen. | |
| Web search provider | Only if you tap Search the web in Define. The word opens as a web search in your browser. | The word, from your browser, under the search provider's own privacy policy. |
Our cloud service provider and email providers handle personal data only to provide their service to us. They do so under their own published terms and privacy commitments. We choose providers that commit to protecting the data they handle. Apple and Google handle sign-in under their own privacy policies.
We may also disclose personal data if the law requires it, or where it is needed to establish, exercise or defend a legal claim.
If Read Bro is transferred to another person or company, for example a company we set up to run it, your personal data would move with it. We will tell you before that happens. This policy, or one that protects your data at least as well, will continue to apply.
If we add an organisation that receives personal data, for example to report crashes, take payments or show ads, we will add it to this page before it receives any of your data.
Where your data is stored
Our servers and database are hosted by a cloud service provider in the United States. If you use Read Bro from India, the European Union, the United Kingdom or anywhere else, your data is transferred to the United States and stored there. Data protection law in the United States may differ from the law where you live. Our email providers, Apple and Google may also process data in other countries. Each of them does so under its own published terms.
Some laws protect personal data sent out of the European Economic Area, the United Kingdom and Switzerland. For these transfers, we rely on our providers' published terms and privacy commitments, and we choose providers that commit to protecting the data they handle. Indian law currently allows transfers to other countries unless the Government of India restricts transfers to a particular country. Write to us if you would like more detail about these safeguards.
Before we move your data to another country or provider, we will update this section, and tell you if the change is material.
How long we keep it
- Your account and the data linked to it, including reading, saves, highlights, first-run answers, recommendation history and usage events, are kept for as long as your account exists. We may set shorter periods for some kinds of data, and if we do, we will update this section.
- A guest account you can no longer open, because you signed out as a guest or deleted the app, stays on our server with its reading data. It stays until you ask us to delete it or we remove it. It has no name or email address. We intend to remove closed and long-unused guest accounts automatically, and will state the period here when we do.
- Records of old sign-in sessions are kept in hashed form, marked as ended, until your account is deleted.
- Security counters stop counting after 1 minute to 24 hours, and expired counters are deleted from time to time.
- Server logs are kept for the period set by our plan with our hosting provider, and then deleted.
- Messages to us are kept for as long as we need them to deal with your message and any follow-up.
- Backups. We may keep backups of our database to recover from failures. If we do, data you delete stays in them until those backups are replaced. We keep any backup for no longer than 3 months, and use backups only to restore the service.
- Records the law requires. Where the law requires us to keep certain records for a minimum period, we keep them for that period and then delete them. For example, India's data protection rules will require some records of processing to be kept for 1 year.
Deleting your account
In the app, open the You tab, tap the settings gear, then under Account tap Delete account, and confirm with Delete. You do not need to contact us.
If you are a guest, you can do this too. Do it before you sign out or delete the app. Deleting the app on its own does not delete your account.
When you confirm, we:
- ask Apple to end Read Bro's access to your Apple Account, if you signed in with Apple,
- end all your sessions, on every phone,
- delete your account and the data linked to it from our database straight away.
This includes your sign-in details, preferences, first-run answers, reading progress, saves, highlights, streak, usage events, feature test versions and recommendation history.
The app then clears its copy of your data on your phone. If Apple cannot be reached at that moment, your account is still deleted. You can also remove Read Bro from Sign in with Apple in your Apple Account settings on your iPhone.
A few limited records can remain after deletion:
- a log entry that records that an account was deleted, with a shortened hash of the account's internal identifier instead of the identifier,
- earlier log entries that contain the account's internal identifier, until those logs are deleted,
- rarely, a record of a background task that holds the account's internal identifier and time zone, until we clear old task records,
- data in backups, if any, until they are replaced (see "How long we keep it"),
- messages you sent us, as described in "How long we keep it",
- records that Apple, Google and our email providers keep under their own policies,
- records the law requires us to keep.
Figures drawn from many readers, such as a book's finish rate, are worked out from the data that remains, so your data stops counting towards them once it is deleted.
If you cannot open the app, write to readbro@foxnutstudios.com from the email address on your account, or tell us your sign-in method and that email address. We may ask you to confirm the request before we act on it.
If you were a guest and have already signed out or deleted the app, we may not be able to tell which guest account was yours. It has no name or email address. Write to us and we will try to help.
Your rights
Depending on where you live, you may have some or all of these rights over your personal data.
- In India, under the Digital Personal Data Protection Act, you can:
- get a summary of your personal data, how we use it and who we have shared it with,
- have it corrected, completed, updated or erased,
- withdraw your consent,
- have your complaints dealt with,
- name someone to use these rights for you if you die or cannot act yourself.
- In the European Economic Area, the United Kingdom and Switzerland, you can:
- see your data,
- have it corrected or erased,
- limit how we use it,
- object to how we use it, including uses based on our legitimate interests,
- get a copy in a format you can move to another service,
- withdraw your consent at any time.
- Elsewhere, including some US states, you may have similar rights under local law. We will not treat you differently for using them.
How to use your rights. Delete your account in the app at any time. For anything else, write to readbro@foxnutstudios.com. Tell us what you would like and which sign-in method you use, and give the email address on your account. If you use Sign in with Apple with a hidden email address, give the address shown in the app under Account. We may ask you to confirm your identity before we act. If someone asks on your behalf, we may ask for proof that you agreed.
When we reply. We aim to acknowledge your request within 2 working days and to complete it within 30 days. If we need longer, we will tell you why, within the limits the law allows. Requests are usually free of charge. A copy of your data comes in a common electronic format.
Complaints
If you have a concern about how we handle your personal data, please write to us first at readbro@foxnutstudios.com. Ameya Sahasrabudhe is the grievance officer for India. We aim to acknowledge complaints within 2 working days and to resolve them within 30 days.
You can also complain to a data protection authority, whether or not you have written to us:
- in India, the Data Protection Board of India,
- in the European Economic Area, the data protection authority in the country where you live or work, or where you think the problem happened,
- in the United Kingdom, the Information Commissioner's Office (ico.org.uk),
- elsewhere, the authority that deals with data protection where you live.
Age
Read Bro is for people aged 16 and over. It is not directed at children, and some of the classics in it deal frankly with adult themes. The app does not ask your age. We rely on the App Store age rating and our terms of service. If we learn that we hold personal data about someone under 16, we will delete it. Parents and guardians who think this has happened can write to us.
Security
We use reasonable technical and organisational measures to protect your data. Today, these include:
- encryption in transit: traffic between the app and our servers uses HTTPS, and remote connections to our database are encrypted,
- your sign-in tokens are kept in your iPhone's Keychain, on that phone only,
- on our server, passwords, session tokens and email codes are stored only as one-way hashes,
- the token Apple gives us has to be sent back to Apple as it is, so it cannot be stored as a hash. We use it only to end Read Bro's access when you delete your account, and our logs are set up to leave it out,
- access to our servers and database is restricted and needs a login,
- limits on repeated sign-in attempts.
No online service is completely secure, so we cannot guarantee that unauthorised access will not happen. If a data breach affects your personal data, we will tell you and the relevant authorities as the law requires.
Tracking and Do Not Track
Read Bro does not currently track you across other companies' apps or websites, and it does not access your device's advertising identifier. No other company collects data about your activity across apps or websites through Read Bro today. Because of this, these web pages do not respond differently to a browser's Do Not Track signal.
If this changes, we will update this policy first, and we will ask your permission through Apple's App Tracking Transparency prompt before any tracking starts, as Apple requires.
This website
Today, the Read Bro pages on foxnutstudios.com set no cookies and use no analytics tools. Our web host may record visitors' IP addresses and requests in its logs, for security and to run its service. If you write to us from a link on these pages, see "Messages to us" above.
Changes to this policy
Read Bro will change over time, and this policy will change with it. We update this page whenever we change what we collect, why we use it, or who receives it, and we change the date at the top each time.
If a change is material, we will post it on this page with a new date before it takes effect. Examples are a new kind of data, a new purpose such as advertising, or a new kind of recipient. We will also tell you by email if we have your email address, or in the app where the app supports it. Where the law requires your consent, we will ask for it. We will ask for your consent before a material change applies to data we already hold.
For smaller changes, such as clarifications, we update this page and the date. Write to us if you would like an earlier version.
Contact
Ameya Sahasrabudhe, Bengaluru, Karnataka, India. Email readbro@foxnutstudios.com.
Grievance officer for India: Ameya Sahasrabudhe, at the same address.