Privacy policy

Last updated 28 September 2026

The short version

• Your lists are stored on your devices and kept in sync through our servers in the European Union, so they reach your other devices, your watches and the people you share a list with.
• You don’t need an account. The app signs in with a random, anonymous ID. If you choose to sign in with Apple or Google (needed to share lists and to use the Mac app), we receive your name, your email address and the provider’s ID for you.
• On a shared list, every member sees its content, the names of the other members and who checked off each item.
• If you allow notifications, we store a notification token for each device so we can tell you when others change a shared list.
• When you make a list by voice, your speech is turned into text on your device or by the Pebble app’s dictation. We never receive audio. The text is sent to OpenAI to build the list and is not stored by us.
• Apple and Google handle payments. We use RevenueCat to know whether your subscription is active.
• We use Firebase Analytics and Crashlytics to understand how the app is used and to fix crashes.
• No ads. We don’t sell your data, and we don’t track you across other apps or websites. You can delete your account and its data from the app.

Who we are

Tasks for Pebble (“Tasks”, “we”, “us”) is an independent app for iPhone, Mac, Android, Apple Watch and Pebble watches. We are responsible for the personal data described here. You can reach us at hello@ovvio.studio.

On your devices

Your lists, their items, notes, sections, titles and subtitles, due dates, colours and icons are stored inside the app on each device you use: in a database on the iPhone, and in the app’s offline cache on a Mac or an Android phone. They are part of your device’s backups, like other app data.

The app asks for the microphone and speech recognition only when you first use voice, and listens only while you do. It asks before sending notifications. You can turn any of these off in your device’s settings; the rest of the app keeps working.

Your account

Anonymous by default

When the app starts, it signs in to Firebase Authentication anonymously. This creates a random user ID that isn’t linked to your name, email, phone number or Apple ID. The ID keeps your lists apart from everyone else’s, and it is also the ID RevenueCat uses for your subscription.

Signing in with Apple or Google (optional)

You can sign in with Apple or Google. It is required to share lists or join a shared list, and to use the Mac app. Signing in keeps the same account, so your lists, subscription and linked watches stay as they are. We then receive from Apple or Google:

• your name (Apple shares it only the first time, and only if you allow it);
• your email address (with Apple you can choose a private relay address instead);
• the provider’s user ID for you, and, from Google, your profile photo if you have one.

We use your name (and photo) to show members of a shared list who is who, and your email only to run your account; we don’t send you marketing. If you sign in on a device that already has lists under another anonymous ID, the two are merged into one account.

The apps also use Firebase App Check (with Apple’s App Attest or Google Play Integrity), which confirms that requests come from the genuine Tasks app on a real device. It doesn’t identify you.

Sync

Your lists are kept in Google Cloud Firestore, in the European Union (Firestore multi-region eur3; our server code runs in europe-west1, Belgium), so every device signed in to your account shows the same lists. For each list we store its title, subtitle, colour and icon, its items (text, whether they are done, who checked them off and when, due date, position and section), its sections and notes, and who created and last changed each of them. We also store, for you only, where each list sits: its order, home-screen section, whether it is archived, shown on your watches or muted.

Only you, your linked watches and the members of a list you share can read it. When something is deleted, it is marked as deleted so every device removes it, and the marked entry is erased 30 days later.

If you used Tasks 2.0 with a Pebble, the copy of your lists made for the watch then is kept, unchanged, as a backup and is deleted with your account.

Watches

Pebble

When you open Tasks on a Pebble that isn’t linked, it asks our server for a pairing code. We store the 6-character code with a random device ID, the watch model (for example “emery” for Pebble Time 2) and a scrambled (hashed) secret. A code lasts 10 minutes and works once. When you type it in the app, we record which account the watch belongs to, and the watch receives a private token. We store only a hash of that token, along with when the watch was linked and when it was last seen.

To stop people guessing codes, we count failed attempts per hour. These counters are keyed by a hash of the IP address or account ID, not by the address itself, and expire after an hour.

The Pebble doesn’t connect to the internet by itself. It talks to our server through the Pebble app on your phone, which also keeps the watch’s token and a cache of the lists it has shown, so it can display them quickly. Check-offs made while the phone is unreachable wait in that cache until they can be sent.

Apple Watch

The iPhone app links your Apple Watch for you: it asks our server for a private token and hands it to the watch. We store a hash of the token, the name of the watch and when it was linked and last seen. The watch reads and changes your lists through our server with that token.

Unlinking a watch (in the app’s settings, or from the watch) deletes its link and token straight away.

Shared lists

When you share a list, the app creates an invite link. We store the link’s random code, the list, who made it, when it expires (after 14 days) and how many times it has been used (up to 20). Anyone who has the link can see, on this website or in the app, the list’s title, colour and icon, the owner’s name and how many members it has. Turn a link off at any time from the list’s sharing settings.

Everyone on a shared list (up to 20 people) can see and change its content, and sees the other members’ names (and photos), who checked off each item and who made changes. What you add to a shared list is shared with its members; please don’t add anything you wouldn’t want them to see.

If you leave a list or are removed, it disappears from your devices; what you added stays in the list for the others. The owner can delete the list for everyone.

Notifications

To tell you when someone changes a shared list or joins it, each device where you allow notifications registers with Firebase Cloud Messaging (which uses Apple’s push service on iPhone and Mac). We store, per device, a random installation ID, the notification token, the platform, the app’s language and version. A notification contains the list’s title, the name of whoever made the change and what changed. Turn notifications off in your device’s settings, or mute a list in the app. When you sign out, the device’s token is removed.

Voice and AI

Turning speech into text

• On the iPhone, Tasks uses Apple’s speech recognition. Depending on your device and language, Apple may process the audio on the device or on its servers, under Apple’s privacy policy. The audio isn’t sent to us.
• On Android, Tasks uses the phone’s speech recognition service (usually Google’s), under that provider’s privacy policy. The audio isn’t sent to us.
• On the Pebble, Tasks uses the dictation built into the Pebble app. That service is not run by us; only the resulting text reaches Tasks.

Building the list

To build a list, we send OpenAI the text of what you said, the app’s language, and some context so the result fits your lists: the titles of your lists and, if you are inside a list, its title, its subtitle and the text of its items. Autocomplete sends the open list’s title, subtitle and items. Icon suggestions send the titles and subtitles of the lists that need an icon.

We pass this through our server to OpenAI’s API and return the result to your device. We don’t store the transcript or OpenAI’s answer, other than as the list items you end up with. OpenAI says that data sent through its API is not used to train its models by default and may be kept for up to 30 days to detect abuse (see OpenAI’s policies). Please don’t dictate sensitive information you wouldn’t want processed this way.

When a list is made from a watch, we also keep a short-lived undo record (the IDs of the list and the new items, not their text) so you can undo it. To enforce the fair-use limit of 50 voice requests a day, we keep a daily counter per account.

Subscriptions

Subscriptions are sold and billed by Apple through the App Store, or by Google through Google Play. We never see your payment card. We use RevenueCat to manage subscriptions: the app identifies itself to RevenueCat with your account ID, and RevenueCat receives the store’s purchase information for it (product, dates, renewals, country and currency). Our server asks RevenueCat whether that ID has an active subscription and remembers the answer (active or not, and until when) for a few hours. Sharing a list and joining one don’t need a subscription.

Analytics and crashes

Firebase Analytics (Google) receives events about how the app is used, for example that a list was created by voice, that a list was shared or that a watch was unlinked, along with an app-instance ID, device model, system version, app version, language and approximate country. It doesn’t receive the content of your lists, your name or your email. The app doesn’t ask to track you, and doesn’t use advertising identifiers.

Firebase Crashlytics (Google) receives crash reports and some error reports: the state of the app and the device at the time (model, system version, free memory and similar) and a technical trace. They don’t include your lists.

Our server keeps technical logs of errors (for example that a request failed and why), which Google Cloud keeps for about 30 days.

Who else is involved

When data leaves the European Economic Area, the providers rely on safeguards recognised under EU law, such as the EU–US Data Privacy Framework or the European Commission’s standard contractual clauses.

What we don’t collect

• No advertising and no ad networks. We don’t sell or rent your data.
• No tracking across other companies’ apps or websites.
• No contacts, photos, calendar, health data or location.
• No audio recordings.
• No phone number or password. No name or email address unless you sign in with Apple or Google.

Keeping and deleting

• Your lists are kept while you use Tasks. Deleted lists and items are erased from our servers 30 days after you delete them.
• Invite links expire after 14 days and can be turned off at any time.
• Pairing codes expire after 10 minutes and are deleted once used. Failed-attempt counters expire after an hour. Undo records are kept only to allow undo.
• Voice text is not stored by us; see Voice and AI for OpenAI.
• Analytics and crash data are kept by Google under Firebase’s retention settings.

To delete everything we hold about you, use Delete account in the app’s settings. It deletes your account, your lists and their placement, your watches’ links, notification tokens, open invite links, counters and subscription status, and removes you from lists shared with you. A list you own that has other members passes to the member who joined first; what you added to shared lists stays there for the others. If you signed in with Apple, the app also revokes Tasks’ access to your Apple ID. You can also write to hello@ovvio.studio; if you never signed in, tell us something that lets us find your account, such as the titles of a few lists. Your subscription itself is with Apple or Google: cancel it in your store account’s subscription settings.

Your rights

Depending on where you live, including under the EU and UK GDPR, you can ask us for a copy of your data, to correct it, to delete it, to restrict or object to how we use it, and to receive it in a portable format. We process your data to provide the app you asked for (our contract with you), and for analytics and crash reports on the basis of our legitimate interest in keeping the app working and improving it. You can also complain to your data protection authority; in Spain that is the Agencia Española de Protección de Datos (aepd.es).

Children

Tasks is not directed at children under 13, and we don’t knowingly collect data from them. If you believe a child has used Tasks and want their data removed, contact us.

This website

This website has no cookies, analytics or trackers. It is hosted on Firebase Hosting, which processes technical data such as IP addresses to serve pages. Fonts are loaded from Google Fonts, so your browser connects to Google to fetch them. When you open an invite link here, the page asks our server for the list’s preview; to limit abuse, the server counts these requests per IP address for an hour.

Changes and contact

If we change how Tasks handles your data, we’ll update this page and the date at the top. If the change is significant, we’ll say so in the app too.

Questions or requests: hello@ovvio.studio.