Privacy Policy
Last updated: 2026-11-19
This policy explains what the Tomely app (iPhone, iPad, Apple Watch, Android phones and tablets, and widgets) and the website readtomely.app collect, why, who receives it, how long we keep it and what your rights are.
Short version: what you log in Tomely stays on your iPhone or iPad. We have no account system and no servers that receive your logs. We collect a small amount of technical data to run subscriptions, fix crashes and understand how the app is used. We don't sell personal data. While usage analytics is on, the app tells Meta (Facebook and Instagram) when it is installed, opened and subscribed to, so we can measure our ads; what you log is never part of it, and you can turn it off in Settings. The only exception is a problem report: if you send one from Settings, what you write or attach reaches us.
Who is responsible
Pediaca, LLC, 1111B S Governors Ave, Ste 81429, Dover, DE 19904, USA ("we", "us"), is the controller of the personal data described here. Contact for anything about privacy: hello@readtomely.app. More company details in our Legal notice.
Privacy contact. Santiago Gonzalez Fernandez, our founder and manager, is responsible for privacy and answers every request sent to the contact above. Where a law asks for a designated person, he is that person: the "encarregado" under Brazil's LGPD, the person in charge of the protection of personal information under Canadian and Québec law, the data protection officer under Singapore's PDPA, the information officer under South Africa's POPIA, the representative for Peruvian territory under Peru's data protection regulation, and the contact for requests under the laws of India, Chile, South Korea, Japan and Mexico. We have not appointed a GDPR data protection officer because our activities don't require one.
Countries where the app is offered
Tomely is not offered in some countries whose laws require a local representative, a paid registration or licence, or local data storage that we don't have yet: the European Union and the European Economic Area, the United Kingdom, Turkey, Russia, Belarus, Kazakhstan, Uzbekistan, Saudi Arabia, Egypt, Serbia, North Macedonia, Albania, Bosnia and Herzegovina, Montenegro, Kosovo, Moldova, Ecuador, Vietnam, Nigeria, Ghana, Uganda, Rwanda, Tanzania, Zambia, Zimbabwe, Morocco, Algeria, Mauritius and mainland China. We don't accept waitlist sign-ups from those countries. If you visit this website from one of them, this policy explains what happens with that visit.
What stays on your device
Everything you log in Tomely is stored only on your iPhone or iPad (and on your Apple Watch, if you use it). We can't see it, and deleting the app deletes it.
It is included in your device's own backup (iCloud or computer) if you have backups turned on; that backup is handled by Apple and you, not by us. You can export your books, sessions and quotes at any time, free, and delete everything from the app (both in Settings → Export & delete).Android and Google Play
Tomely is also offered for Android phones and tablets through Google Play. Everything in this policy applies to the Android app too; this section explains what is different there.
- What you log stays on your Android device, in the app's private storage. We can't see it, and uninstalling the app or clearing its data deletes it.
- If you turned on Android backup, the app's data may be included in your backup to your Google account; that backup is handled by Google and you, not by us.
- Purchases are made with Google Play Billing. Google processes the payment and your Google account under Google's privacy policy; we never see your payment details or your Google account email. RevenueCat (USA) receives the purchase token, order ID, product, dates and status from Google, linked to the random app user ID, to unlock and restore what you paid for. While usage analytics is on, RevenueCat also receives the Android Advertising ID and Meta's anonymous ID, to report subscriptions to Meta.
- The Android app doesn't access the Android ID and doesn't include Firebase. It includes Meta's SDK to measure our ads, which, only while usage analytics is on, can read the Android Advertising ID (see "Meta (Facebook and Instagram) ad measurement"). It has no equivalent of Apple Ads attribution. Analytics and crash reports work as described above, with the same choices in Settings.
- If you allow notifications, reminders are scheduled on your device (and restored after a restart); nothing about them is sent to us.
- The camera is used only when you scan a barcode or a page. Barcode scanning and text recognition run on your device with Google ML Kit models included in the app; the images are not sent to us or to Google. As part of ML Kit, Google may receive technical metrics about how these features perform (not your images or text), under Google's privacy policy.
Meta (Facebook and Instagram) ad measurement
We advertise Tomely on Facebook and Instagram. To know which ads bring people who install and subscribe, and so Meta can show our ads to people likely to enjoy Tomely, the app includes Meta's software development kit (SDK) for app events. While usage analytics is on, it sends Meta that the app was installed and opened, that you finished the first-time setup and, once, that you used its main feature for the first time (never what you did in it), an anonymous ID that the SDK creates on your device, technical details (device model, OS and app version, language, time zone) and your IP address. RevenueCat also tells Meta when a free trial starts, a subscription starts or renews, or you make a purchase (product and price), with that anonymous ID and Apple's IDFV, so Meta can match it to the ad. The SDK itself doesn't log your purchases.
On iPhone and iPad, iOS asks you once whether Tomely may track you. Only if you choose Allow does Meta also receive Apple's advertising identifier (IDFA). If you choose Ask App Not to Track, Meta doesn't get the IDFA and measures our ads only with Apple's privacy-preserving methods (Aggregated Event Measurement and SKAdNetwork). You can change your answer anytime in Settings → Privacy & Security → Tracking.
On Android, while usage analytics is on, Meta may also receive your device's Android Advertising ID (you can reset or delete it in your phone's settings, under Google → Ads) and the install referrer that says which ad led to the download.
What you log, read, listen to or write in Tomely is never sent to Meta, and neither is your name or email. If you turn off usage data in Settings (or, in the EEA, UK and Switzerland, don't agree to it), the app sends nothing to Meta and doesn't ask to track you.
Meta Platforms, Inc. (USA) and Meta Platforms Ireland Ltd. use this data as independent controllers under Meta's Privacy Policy, including to measure and deliver ads. In the EEA, UK and Switzerland, we and Meta are joint controllers for collecting and sending it (Meta's Controller Addendum); you can exercise your rights with us or with Meta. We don't receive anything back from Meta about you, only aggregated ad results. facebook.com/privacy/policy
Book search and covers
To find books and covers, the app sends your search text, a book's ISBN, or a book's title and author directly from your iPhone or iPad to public book catalogs: Open Library (Internet Archive, USA) and, if nothing is found there, Google Books (Google, USA). After you import a library, the app does this in the background for books without a cover. Like any web request, these services see your IP address. We don't send them any identifier of you, and they process the request under their own privacy policies.
What we collect, why and on what basis
The "legal basis" column applies if you are in the European Economic Area, the UK or Switzerland (GDPR / UK GDPR); the purposes are the same everywhere.
| Data | Why | Legal basis | Who receives it | How long |
|---|---|---|---|---|
| Purchases: a random app user ID created on your device, Apple's identifier for vendor (IDFV), purchase and subscription history and receipts, approximate country. | Unlock what you paid for, restore purchases, prevent fraud, handle refunds and accounting. | Contract (art. 6(1)(b)); legal obligations (art. 6(1)(c)). | RevenueCat (USA), Apple | While you have purchases with us and up to 3 years after your last transaction. |
| Usage analytics: events such as screens viewed and features used, app version, device model, OS, language, time zone and approximate country, linked to the random app user ID. For some sessions, also a recording of how you use the app's screens (session replay): taps, scrolling and what the app itself shows, such as buttons, menus, titles, images and prices, so we can see where the app is confusing and improve it. What you type, your own content (for example notes and names), your email, your support ID and other long IDs or numbers, and system views embedded in the app are hidden on your device before anything is sent, and some screens with private content are not recorded at all. Recordings are kept up to 30 days. You can stop them by turning off usage analytics in the app's settings. | Understand what works, improve the app and measure which channels bring people. | In the EEA, UK and Switzerland: your consent (art. 6(1)(a)), asked in the app. Elsewhere it is on by default and you can turn it off in Settings. | PostHog (USA) | Up to 12 months. |
| Crash and performance reports: error details, device model, OS and app version, a random installation ID, with personal data removed. | Find and fix bugs and crashes. | Legitimate interest in a working, secure app (art. 6(1)(f)). You can object at any time. | Sentry (USA) | Up to 90 days. |
| Problem reports (only if you send one from Settings → Report a problem): your message (up to 4,000 characters); your email address, if you add it; a screenshot or photo, if you choose to attach one (re-encoded without its metadata or location); the app version, OS, device model and, if there was one, the ID of the last error in that session. If crash reports are off, the app offers to send the report by email instead (see "Emails you send us"). | Understand and fix the problem you report, and reply to you if you left an email address. | Doing what you ask us to (art. 6(1)(b)) and our legitimate interest in fixing the app (art. 6(1)(f)). Nothing is sent until you tap Send. | Sentry (USA) | Up to 90 days. If we reply by email, that conversation is kept as described for emails you send us. |
| "How did you hear about us?" Optional answer (for example a platform or a creator's handle). | Know which channels and creators bring people. | Legitimate interest (art. 6(1)(f)); the question is optional and you can skip it. | RevenueCat, PostHog (USA) | Same as purchases / analytics. |
| "What stopped you?" (only while usage analytics is on): if you close the subscription screen without subscribing, the app may ask you once why, with fixed options (for example "Too expensive for me"). Optional. | Understand why people don't subscribe and improve the offer. | Same as usage analytics. | PostHog (USA) | Same as usage analytics. |
| Optional written answers to that question (only while usage analytics is on): after you pick an option, the app may offer a box to explain in your own words (up to 280 characters). It is sent only if you choose to write something. Please don't include your name, email or other personal details. | Understand why you don't continue and what to improve. | Same as usage analytics. | PostHog (USA). Linked to the random app user ID, never to your name or email. To have it deleted, tap Request data deletion in Settings: it opens an email with your support ID. | Same as usage analytics. |
| Apple Ads attribution (only while usage analytics is on): a one-time token from Apple's AdServices framework. RevenueCat exchanges it with Apple to learn whether the download came from an Apple Ads ad and, if so, the campaign, ad group and keyword, and stores that with the random app user ID. It doesn't contain the IDFA or require permission to track. | Measure which Apple Ads campaigns bring people who subscribe, compared with what they cost. | Follows usage analytics: in the EEA, UK and Switzerland, your consent (art. 6(1)(a)); elsewhere it is on by default, and if you turn off usage data in Settings it stops from the next launch. | RevenueCat (USA), Apple | Same as purchases. |
| Meta ad measurement (only while usage analytics is on): app installed and opened, first-time setup finished and first use of the main feature (once), an anonymous SDK ID, device and app details, IP address; free trial, subscription and purchase events from RevenueCat with that ID; Apple's IDFA only if you allow tracking; on Android, the Android Advertising ID. | Measure which Facebook and Instagram ads bring people who install and subscribe, and help Meta show our ads to people likely to enjoy the app. | Follows usage analytics: in the EEA, UK and Switzerland, your consent (art. 6(1)(a)); elsewhere it is on by default and you can turn it off in Settings. The IDFA only with your permission in iOS. | Meta Platforms (USA, Ireland), RevenueCat (USA) | Meta keeps it under its own policy (see below). |
| Meta ad attribution on Android (only while usage analytics is on): if you installed the app from Google Play after tapping an ad on Facebook or Instagram, Google Play passes an encrypted install referrer. We decrypt it on our server to learn the campaign, ad set and ad, and store them with the random app user ID. It contains no advertising ID and nothing about what you do in the app is sent to Meta. | Measure which Meta ads bring people who subscribe, compared with what they cost. | Follows usage analytics: in the EEA, UK and Switzerland, your consent (art. 6(1)(a)); elsewhere it is on by default, and if you turn off usage data in Settings it stops from the next launch. | Our server (Vercel, USA), RevenueCat and PostHog (USA) | Same as purchases / analytics. |
| Emails from the app (optional, only if you tick the box and confirm): your email address, language, the random app user ID, proof of consent (date, text shown, where in the app), your subscription status from RevenueCat, and whether you open or click our emails. | Send the emails you asked for (trial reminder, news and tips) at the right time, and know which ones help. | Your consent (art. 6(1)(a)); you can withdraw it from any email. | Loops (USA), RevenueCat (USA) | Until you unsubscribe; then we keep only what proves the unsubscribe, up to 3 years. |
| Reading Buddy Pass (optional, only if you ask for passes and tick the box): your email address, the random app user ID (Support ID), language, platform and app version; your passes and when they were opened (time, device type, approximate country) and redeemed. For a friend who redeems a pass: the random app user ID and offer code that RevenueCat reports, and whether their first payment went through. We never receive your friend's email address. | Email you your passes, and tell you about and give you the free month you earn when a friend subscribes. | Doing what you ask for (art. 6(1)(b)); for the emails about the month you earn, your consent given by ticking the box (art. 6(1)(a)), which you can withdraw at any time; for a friend's redemption, our legitimate interest in running the passes fairly (art. 6(1)(f)). Not offered in the EEA, UK or Switzerland. | Our server (Vercel, USA), RevenueCat (USA), Google Workspace (email, USA) | Up to 12 months after your passes expire. The emails we send you are kept like the emails you send us. |
| Waitlist (website): your email address; how you found us (link, campaign or creator, referring site); the language of the page and of your browser; approximate country. | Email you when the app is available and send you occasional news about the app. | Your consent (art. 6(1)(a)). | PostHog (USA) | Until you unsubscribe, and at most 12 months after the app launches. |
| Website visits: pages viewed, clicks on creator and beta links, referring site, device type and browser (user agent), approximate country. No cookies: to count unique visits to the site and to beta links we keep a one-way code computed from your IP address and browser that changes every day, never the IP address itself. Where on the page you click and how far you scroll (heatmaps), without anything you type. | Know which pages and links work. | Legitimate interest (art. 6(1)(f)). | PostHog (USA), Vercel (hosting, USA) | Analytics up to 12 months; hosting logs a few days. |
| Emails you send us: your address and what you write. | Answer you and keep a record of support requests. | Legitimate interest (art. 6(1)(f)); contract, if it is about a purchase. | Cloudflare (email forwarding), Google Workspace (mailbox) (USA) | Up to 3 years after the conversation ends. |
We never put the content of your logs in analytics or crash reports. A problem report contains only what you write or attach yourself, and is sent only when you tap Send; analytics only learns that a report was sent, never its content or your email address. Your IP address reaches our providers with every request, as on any network connection; they use it to estimate an approximate country and to protect their services. We don't make decisions about you based solely on automated processing, and we don't build profiles for advertising.
Providing this data is not required by law. Purchases need the purchase data; everything else is optional or can be turned off, and the app works without it.
Waitlist and early access
When you join the waitlist we store your email address. We use it only to tell you about the launch, send you occasional news about the app and shape the app. We don't sell it, share it with advertisers or set cookies to collect it. To unsubscribe and delete it, reply to any of our emails or write to hello@readtomely.app; we remove it within 30 days. Withdrawing consent doesn't affect what we did before.
Emails from the app
Tomely may offer, after you've used it, to send you emails: a reminder before your free trial ends, and now and then news and tips. It's optional, nothing in the app depends on it, and we don't offer it in the EEA, UK or Switzerland.
We only add you if you tick the box (it starts unticked) and then confirm with the link we email you (double opt-in). We keep proof of that consent: the date, the language, where in the app you agreed and the exact text you saw.
On our website's daily book game you can also ask to get the game by email. It works the same way (unticked box, confirmation link, proof of consent, one-click unsubscribe) and we don't offer it in the EEA, UK or Switzerland. There's no app account behind it, so we give that contact a random ID and don't link it to RevenueCat.
To send the right email at the right time (for example, not reminding you about a trial you already cancelled), we link your email to the random app user ID and keep your subscription status from RevenueCat (trial, active, cancelled, expired, billing issue, plan). Loops (Loops.so, Inc., USA) stores this and sends the emails on our behalf as our processor. We count opens and link clicks to know which emails help; Tomely's emails never contain ads from third parties.
Your email address is never sent to our analytics (PostHog), crash reports (Sentry), RevenueCat or Meta, and is never used for advertising or to build ad audiences. Analytics only learns that you asked for emails, not the address.
Every email has a one-click unsubscribe link. To delete your email address and contact record, write to hello@readtomely.app; we remove it within 30 days.
Reading Buddy Pass
Tomely may offer you Reading Buddy Passes: 3 links to share with friends who read. Each one gives a month of Tomely Plus free, and you get a free month when a friend subscribes with one. It's optional, and we don't offer it in the EEA, UK or Switzerland.
If you ask for passes, the app sends our server the email address you type, the random app user ID (your Support ID), your language, your platform (iPhone or Android) and the app version, only after you tick the box (it starts unticked) and tap Send. We check with RevenueCat that the ID exists and keep a private record on our server (Vercel, USA) with your email, ID and language, your passes and when they expire, and whether each one was opened and redeemed. A person reviews each request and emails you the links from our mailbox (Google Workspace). Later we email you when you earn a month.
We never receive your friend's email address or name: you share the link yourself. When someone opens a pass link we record the time, the type of device and the approximate country, never the IP address. When they redeem it, RevenueCat tells us the random app user ID of their account, the offer code redeemed and, later, whether their first payment went through or was refunded. We use this only to give you your month, as an extension or a promotional month through RevenueCat or a reward code from Apple. We don't tell you who redeemed it.
Your email address is used only for your passes and the month you earn. It's never sent to our analytics (PostHog), RevenueCat or Meta, never used for advertising or marketing, and it doesn't sign you up for the app's other emails, which are a separate, optional choice.
To stop these emails, reply to any of them or write to hello@readtomely.app. We keep the record up to 12 months after your passes expire, to give you the month you earn and handle refunds, and then delete it. To delete it sooner, write to hello@readtomely.app; we remove it within 30 days, and a month not yet given is then lost.
Cookies and tracking
The website sets no cookies and doesn't store anything on your device for analytics. The app includes Meta's SDK to measure our Facebook and Instagram ads (see "Meta (Facebook and Instagram) ad measurement" above) and, on iPhone and iPad, asks you once whether it may track you: it uses Apple's advertising identifier (IDFA) only if you allow it. It contains no other advertising SDK, and the website has no Meta pixel. Under some US state privacy laws, sending identifiers and app events to Meta for ads can count as "sharing" or "targeted advertising"; you can opt out at any time by turning off usage data in Settings. We don't sell personal data, and we honor Global Privacy Control signals on the website.
Apple Ads. While usage analytics is on, the app requests a one-time attribution token from Apple's AdServices framework so we can tell whether the download came from an Apple Ads campaign (see the table above). It doesn't use the IDFA, Apple doesn't require permission to track for it, and we don't send Apple what you do in the app (for Meta, see "Meta (Facebook and Instagram) ad measurement").
Service providers and international transfers
We use these providers as processors, under contracts that only let them use the data to provide their service to us: RevenueCat, Inc. (purchases), PostHog, Inc. (analytics and waitlist), Functional Software, Inc. — Sentry (crash reports and problem reports), Vercel Inc. (website hosting), Cloudflare, Inc. (DNS and email forwarding) and Google LLC (Google Workspace email). Apple (App Store) and Google (Google Play) process purchases as store operators under their own privacy policies.
We and these providers are in the United States. When the law of your country restricts transfers of personal data abroad, we rely on: for the EEA, the EU-US Data Privacy Framework where the provider is certified, and otherwise the European Commission's Standard Contractual Clauses (with the UK Addendum and Swiss amendments where applicable); for Brazil, the safeguards permitted by the LGPD; and for Japan, the measures described in "Japan" below. You can ask us for a copy of the relevant safeguards.
Your rights
Depending on where you live, you can ask us to: confirm whether we process your data and give you a copy; correct it; delete it; restrict or object to its processing; receive it in a portable format; and withdraw any consent at any time (without affecting earlier processing). Most of your data is on your device, where you control it directly.
How to exercise them: write to hello@readtomely.app. Because we don't have accounts, to find data linked to the app we need the support ID shown in the app (Settings → Support) or, for the waitlist, the email address you used. We may ask for information to confirm the request is yours. We answer within one month (15 days for a confirmation or copy under the LGPD; 45 days under US state laws), extendable where the law allows, and for free. If we refuse a request, we explain why and how to appeal: reply to our answer with "Appeal" and we will review it within 45 days. You also have the right to complain to a data protection authority (see below), and we would appreciate the chance to address your concern first.
We never discriminate against you for exercising your rights.
Region-specific information
European Economic Area, UK and Switzerland. You can complain to the data protection authority where you live or work, for example the Information Commissioner's Office (ico.org.uk) in the UK. The legal bases are in the table above. Where we rely on legitimate interests, you can object at any time.
Brazil (LGPD). In addition to the rights above, you can ask for anonymization, blocking or deletion of unnecessary data, information about the entities we share data with, and information about the possibility of not giving consent and its consequences. You can also petition the National Data Protection Authority (ANPD).
Mexico (LFPDPPP). You can exercise your rights of access, rectification, cancellation and opposition (ARCO), revoke your consent and limit the use or disclosure of your data by writing to the contact above with your name, the right you want to exercise and the data concerned. We answer within 20 days. If you are not satisfied, you can go to the competent Mexican data protection authority.
Japan (APPI). The business handling your personal information is Pediaca, LLC, 1111B S Governors Ave, Ste 81429, Dover, DE 19904, USA, represented by Santiago Gonzalez Fernandez. Your data is provided to the processors listed above in the United States, a country that has no comprehensive federal data protection law (information on its system is published by Japan's Personal Information Protection Commission); each provider is bound by contract to protect it at a level equivalent to the APPI. Our security measures include: limiting what we collect, encryption in transit, access restricted to the person responsible with two-factor authentication, removal of personal data from crash reports, and contracts with every provider. You can request disclosure, correction, suspension of use or deletion through the contact above.
United States. Residents of California, Colorado, Connecticut, Virginia, Texas, Oregon and other states with privacy laws have the rights described above, including the right to opt out of the sale of personal data, targeted advertising and profiling — we don't sell personal data or build profiles, and the only targeted advertising is the Meta ad measurement described above, which you can opt out of in Settings. In the last 12 months we collected the categories described in the table (identifiers, commercial information, internet or other electronic activity, approximate geolocation), for the purposes stated, from you and your device, and disclosed them only to the service providers above and, for ad measurement, to Meta.
Canada. Our privacy contact above is the person in charge of the protection of personal information (also under Québec's Law 25). Your information is processed in the United States by the providers listed above. You can complain to the Office of the Privacy Commissioner of Canada or, in Québec, to the Commission d'accès à l'information.
South Korea (PIPA). To provide the app, the data in the table above (purchase data, and analytics and crash data where they are on) is transferred over the network, each time you use the app, to the providers listed above in the United States, for the purposes and periods stated in the table. You can refuse by turning analytics off in Settings and not making purchases; the app keeps working, except for purchases.
India (DPDP Act). Send requests and grievances to the contact above. If you are not satisfied with our answer, you can complain to the Data Protection Board of India.
Argentina (Law 25,326). You can exercise your right of access free of charge at intervals of no less than six months, unless you show a legitimate interest (art. 14(3)). The Agency for Access to Public Information (AAIP), as the supervisory authority of Law 25,326, handles complaints from anyone whose data protection rights are affected.
Other countries. In Chile, Colombia, Peru, Uruguay, South Africa, Singapore, Australia, New Zealand and elsewhere you have the rights described above and can complain to your national data protection authority (for example Colombia's Superintendencia de Industria y Comercio, Peru's Autoridad Nacional de Protección de Datos Personales, South Africa's Information Regulator, Singapore's Personal Data Protection Commission or Australia's OAIC).
Children
Tomely is for people aged 16 and older. It is not directed to children under 13 and we don't knowingly collect personal data from children. If you believe a child has given us personal data, write to us and we will delete it.
Security
We collect as little as we can, keep your logs on your device, use encrypted connections, restrict access to our provider accounts and require two-factor authentication. No system is perfectly secure; if a breach affects your data, we will notify you and the authorities as the law requires.
Changes
If this policy changes in a meaningful way, we will update the date above and tell you in the app before the change applies. If a change requires your consent, we will ask for it.
Language
This policy is written in English and offered in other languages for convenience. If the versions differ, the English version prevails, except where the law of your country requires the version in your language or where it is more favorable to you.
Contact
Pediaca, LLC · 1111B S Governors Ave, Ste 81429, Dover, DE 19904, USA · hello@readtomely.app