Blobodoro

Privacy Policy

Last updated 9 November 2026

Concurrent Space Ltd (“we”, “us” or “our”) provides Blobodoro. We are responsible, as the “controller”, for the personal information that we and the providers working for us receive. You can contact us at blobodoro@concurrent.space. This policy covers Blobodoro 2.0 for iPhone and this website.

1. Your save, on your phone and in iCloud

Blobodoro keeps your focus sessions, activity names, fish, fish names, achievements, shells, coins, pearls and settings in a single save file on your phone, which we never receive. Your iPhone’s own backups, whether to iCloud Backup or to a computer, include this file, and this policy calls them device backups. Blobodoro 2.0 has no accounts and no sign-in.

If you used Blobodoro 1.x on the same phone, Blobodoro 2.0 will copy your 1.x data into the new save without sending that data anywhere, and will leave the original 1.x data on your phone.

We will back up your save to your own iCloud account using Apple’s CloudKit, unless you turn off iCloud backup in Blobodoro’s Settings. The backup also includes the app version and a summary of your save, such as how many fish you have. Apple stores your backup in your iCloud storage under Apple’s privacy policy, and we have no access to it. We back up your save so that you can restore your progress on a new phone or after reinstalling Blobodoro, and our legal basis is our legitimate interest in keeping your progress safe. If you restore a backup, we will also restore your choice about sharing usage data.

If you allow notifications, Blobodoro will schedule focus and break reminders on your phone, and we don’t send push notifications. While the tank is on screen, Blobodoro reads your phone’s motion sensor so that the shells roll when you tilt the phone. iOS does not ask your permission for the motion sensor, and the motion readings stay on your phone.

Deleting Blobodoro will remove the save from your phone, but your backups and any information already sent to the providers below will remain. If you turn off iCloud backup, we will stop backing up your save, and your existing backups will stay in your iCloud account until you delete them in your iPhone’s Settings. To delete them, open Settings, tap your name, then iCloud, then Storage, then Blobodoro: Pomodoro Timer, and tap Delete Data from iCloud. This will delete every Blobodoro backup in your iCloud account, and Blobodoro will only make a new backup if you turn on iCloud backup again.

2. Usage data and error reports

The first time you open Blobodoro, we will ask whether you want to share usage data and error reports. We send nothing to PostHog or Sentry before you answer, or if you choose No thanks. You can change your answer at any time in Settings, under Share usage data. This choice does not cover purchase processing, which section 3 describes.

If you choose Share, we will send usage events to PostHog, our analytics provider, and error reports to Sentry, our error reporting provider. A usage event records something you did in Blobodoro, such as finishing a focus session or catching a fish. Each usage event holds only counts, yes-or-no values and fixed categories, and never includes the names you type. Each usage event also contains the app version, the iOS version, your screen size, the time and a random identifier for that use of Blobodoro.

PostHog gives your installation a random identifier so that we can count records from the same phone together. This identifier does not contain your name, but it does link your records to your installation. PostHog also works out your approximate location, such as your country, region and city, from your internet address, and our PostHog project then discards that address. If you used Blobodoro 1.x, your first records also include counts of what Blobodoro copied from 1.x, such as how many focus sessions and fish.

We will send an error report to Sentry when an error happens in Blobodoro, when Blobodoro crashes or stops responding, and when iOS closes Blobodoro. Each report contains the error’s message, the place in Blobodoro’s code where the error happened, the app version, the iOS version, your phone’s model, its memory and storage figures, its screen size, its language and time zone settings and the time. Error reports do not contain screenshots, a recording of the screen or the names you type. Each report also contains a random identifier kept in your save, so that we can count reports from the same save together. We tell Sentry not to record your internet address, and we have set our Sentry project not to store it.

We use usage data to understand how people use Blobodoro so that we can improve it, and we use error reports to find and fix faults. Our legal basis for both is your consent. If you turn sharing off, we will stop sending data to PostHog and Sentry, discard any usage events not yet sent, and delete both identifiers from your phone. If you turn sharing on again, you will get new identifiers.

PostHog stores usage data on its servers in the European Union, in Frankfurt, Germany. PostHog keeps usage data for the period set for our PostHog project and as its legal obligations require.

Functional Software, Inc. runs Sentry, which stores error reports in the United States. Sentry takes part in the EU-U.S. Data Privacy Framework and its UK Extension, which protect this transfer, and Sentry’s data processing terms also include standard contractual clauses with the UK addendum. Sentry keeps error reports for the period set for our Sentry project and as its legal obligations require.

3. Purchases

Apple takes your payment for Premium and pearls, and handles subscriptions, cancellations and refunds. We do not receive your name, your Apple Account details or your payment card details.

RevenueCat processes purchases for us. When you open Blobodoro or come back to it, when you open the Premium screen, and when you buy something or restore purchases, RevenueCat will receive a random app user identifier, your App Store purchase records, and technical information about Blobodoro and your phone. RevenueCat uses this information to confirm your purchases, to check whether you can have a free trial, to tell Blobodoro whether you have Premium, to add pearls you buy, and to give us purchase statistics. We send this information whether or not you share usage data, because Blobodoro cannot sell or restore Premium without it. Our legal basis is that we need this processing to provide what you buy.

If you signed in to an account in Blobodoro 1.x, your app user identifier at RevenueCat may still be the identifier of that account, which keeps your earlier purchases working. RevenueCat stores purchase information in the United States, and RevenueCat’s data processing terms protect this transfer with standard contractual clauses with the UK addendum. RevenueCat keeps purchase records while we use RevenueCat, so that Restore purchases keeps working.

4. App updates

When you open Blobodoro, we will ask Expo, our app update provider, whether a small update is available. The request contains a random identifier for your installation, your phone’s operating system, the app version, which update you are running and your internet address. Expo uses this information to deliver updates and to count how many installations use them. Our legal basis is our legitimate interest in fixing faults quickly. Expo is based in the United States and takes part in the EU-U.S. Data Privacy Framework and its UK Extension. Expo keeps this information only as long as Expo reasonably needs it, as Expo’s privacy policy explains.

5. Apple

Apple receives information under Apple’s privacy policy when you download Blobodoro, when you pay, and when you rate Blobodoro from Apple’s rating prompt. If you turned on Share with App Developers in your iPhone’s settings, Apple also shares crash reports and usage statistics with us, and these reports and statistics do not identify you. Apple also stores your iCloud backup, as section 1 explains.

6. Blobodoro 1.x

We still hold the accounts, email addresses and cloud backups from Blobodoro 1.x at Supabase, but Blobodoro 1.x can no longer reach them and we don’t use them. We will delete them all by 3 May 2027, and you can ask us to delete yours sooner. Until then, our legal basis is our legitimate interest in deleting this data carefully. Supabase stores this data in the United States under standard contractual clauses with the UK addendum.

Blobodoro 1.x also showed ads from Google AdMob and sent crash reports to Sentry. Blobodoro 2.0 has no ads, and we send 2.0’s error reports to Sentry only if you choose Share, as section 2 explains. To find out what data Google collected through those ads, read Google’s privacy policy.

7. This website

Vercel hosts this website and counts page visits with Vercel Web Analytics, which does not use cookies. When you visit, Vercel also uses your internet address to send you the pages and to keep the website safe, and keeps a short record of each visit. Our legal basis is our legitimate interest in running the website and knowing which pages people read.

8. Sharing and how long we keep information

We share your information only with the providers this policy names, or when the law requires us to. RevenueCat, PostHog, Sentry, Expo, Supabase and Vercel process your information for us under data processing agreements. Apple, and Google for the 1.x ads, handle your information under their own privacy policies. We don’t sell your information, use it for advertising, or use it to track you across other companies’ apps and websites. We don’t make decisions about you by automated means that have legal or similarly significant effects.

We keep information for these periods:

  • Your save stays on your phone until you delete Blobodoro, in your iCloud backup until you delete that backup, and in your device backups until you delete them.
  • PostHog keeps usage data, and Sentry keeps error reports, for the periods section 2 gives.
  • RevenueCat keeps purchase records while we use RevenueCat.
  • Expo keeps update checks for as long as Expo reasonably needs them.
  • We keep the 1.x accounts and cloud backups at Supabase until 3 May 2027 at the latest, and we will delete yours sooner if you ask us to.
  • Vercel keeps records of website visits for a short time, as Vercel decides.
  • We keep emails you send us only as long as we need them to answer you.

9. Children

Blobodoro is rated 9+ on the App Store in most countries, has no accounts and does not ask your age. We send nothing to PostHog or Sentry unless you choose Share in Blobodoro, and if you are under 13, only a parent or guardian may choose Share for you. Ask a parent or guardian before you buy anything in Blobodoro.

10. Your rights and contact

Depending on where you live, you may have the right to access, correct or delete your personal information, to receive a copy of it, to restrict or object to how we use it, and to withdraw your consent at any time. Withdrawing consent does not affect data we sent before you withdrew it.

Blobodoro has no accounts, so we usually cannot find your usage data or error reports from your name or email address. To stop sharing usage data and error reports and to delete both identifiers, turn off Share usage data in Settings. To ask about your purchase records, email us with your App Store order ID, which is in the receipt from Apple. You do not need to give us any information to use Blobodoro, apart from the purchase information in section 3 if you buy something.

To use your rights, email blobodoro@concurrent.space. You can complain to us by email. You can also complain to the UK Information Commissioner’s Office (ICO) at ico.org.uk, or to the data protection authority where you live.

If you email us, we will use your email address and your message only to reply to you. Our legal basis is our legitimate interest in answering you.

If we change this policy, we will update the date at the top of this page and give any notice the law requires.

Concurrent Space Ltd, registered in England and Wales, company number 16800102. 71-75 Shelton Street, Covent Garden, London WC2H 9JQ, United Kingdom.