Alkando

Politique de confidentialité

Pour l’instant, ce document est en anglais.

Version 1 Mis à jour 5 November 2026

This policy explains what data the Alkando app for iPhone and iPad and the account page at alkando.app/account process, why, who receives it and what rights you have. An Android version is in preparation; we will update this document before it is released.

1. The short version

  • Alkando works without an account and without an internet connection. By default your tasks, goals, habits, notes, photos and recordings stay on your device.
  • Data goes to the cloud only if you turn sync on yourself: to your own iCloud or to an Alkando account.
  • Buying Premium requires an account, because access is tied to the account. The rest of the app works without one.
  • We use no advertising tools or in-app behaviour analytics, we do not track you across apps, and we do not sell data.
  • Premium access is handled for us by RevenueCat, a US company. The app connects to it only when you have an account and are signed in (section 4.8 describes one exception).
  • Regardless of whether you have an account, the app connects to the internet to download current content and settings (for example the FAQ and this document). See section 4.1.
  • You can delete your account and data at any time in the app: Settings, Privacy & consents, Delete account & data. Deleting your account also requests deletion of the purchase record at RevenueCat, but we do not guarantee the result (section 12).
  • An account without Apple sign-in can also be deleted at alkando.app/account, and in the app and on the website you can choose deletion in 30 days (section 12.2).

2. Who is responsible for your data

The data controller is J20 Labs, the maker of the Alkando app ("we").

For any matter concerning personal data, write to support@alkando.app.

We have not appointed a data protection officer because the law does not require us to.

3. Data that stays only on your device

Until you turn sync on, everything you enter is stored only in your device's memory. We have no access to it and cannot read or recover it.

This includes:

  • tasks, subtasks, goals, projects, categories, tags, templates and habits,
  • completion history, statistics, XP and HP points, streaks, focus and Pomodoro sessions,
  • activity entries (for example workout, running, water), if you use them,
  • your nickname, full name and avatar photo,
  • saved places with their address and coordinates,
  • attachments: photos, voice notes, files, links and location markers,
  • settings, the in-app event log and the fair-play log.

Attachments, places, your avatar, subtasks, activity entries and templates are never sent to the cloud, even when sync is on.

Local data may be included in the backup of your whole device made by iOS (iCloud or a computer) if you have it enabled. You manage this in system settings.

You can type anything into text fields. Please do not enter sensitive data (for example about health) or other people's data unless necessary, especially if you use sync.

4. Data we process

4.1 Downloading content and settings

On launch the app connects to Firebase Remote Config (Google) to download current content: the FAQ, legal documents, what's-new information, contact details and feature settings. This happens even if you have no account.

  • Data: a random installation identifier assigned by Firebase, IP address, basic technical data about the app and device. None of your content is sent.
  • Purpose: delivering the current version of the app and its content.
  • Legal basis: our legitimate interest in maintaining and updating the service (Article 6(1)(f) GDPR).

4.2 Account

An account is optional. You need one only to buy and use Premium. You can create one with an email address, with Apple, or with Google, in the app or at alkando.app/account. On the website the sign-in session is saved in your browser until you sign out.

When you sign in with an email address, you do not type a password. We send a 6-digit code to that address, valid for 10 minutes and for one use. If you do not have an account yet, the correct code creates one and confirms the address. A code also signs you in to an Apple or Google account with the same address. If your account had a password, the first sign-in with a code replaces it with a random one that nobody knows and ends earlier sessions. Resend sends the code, and Cloudflare handles the sign-in and receives your email address and IP address. At Cloudflare we do not store your email address, IP address or the code in readable form: we keep their hashes and attempt counters for up to 48 hours.

An account created earlier with an email address and password requires confirming the address, with the link in a message sent by Firebase or by signing in with a code. Until you confirm you cannot turn on the copy in your Alkando account or buy Premium; the rest of the app works as usual.

  • Data: email address, name (or the name given at registration, if you give one), user identifier, sign-in method, password in protected form, IP address and technical sign-in data. With Google sign-in we also receive the address of your profile picture. With Apple sign-in you can hide your email address.
  • Source: you and, depending on the method, Apple or Google.
  • Purpose: signing in, tying Premium to your account and providing sync across devices.
  • Legal basis: performance of the contract for using the app (Article 6(1)(b) GDPR) and, for sign-in attempt limits and the IP address, our legitimate interest in protecting accounts against abuse (Article 6(1)(f) GDPR).

Accounts are handled by Firebase Authentication (Google), which processes data in data centres in the United States.

4.3 Sync with an Alkando account

The copy in your Alkando account is a Premium feature. It works only if you turn it on and are signed in. Data is stored in Cloud Firestore (Google) in the European Union (location eur3: data centres in Belgium and the Netherlands).

  • Data: tasks (title, description, dates, status, priority, difficulty, icon), goals, projects with their stages and blocker note, categories, tags, habits and the days they were completed, statistics (XP, level, streaks, selected mode) and a random installation identifier used to add up XP from several devices.
  • Purpose: a copy of your data and its availability on your devices.
  • Legal basis: performance of the contract (Article 6(1)(b) GDPR).

Before data leaves your device, the app encrypts its content with a key that only your devices know (end-to-end encryption). The key is stored in the system keychain and moves between your Apple devices through iCloud Keychain or through a key code that you copy yourself. We do not have this key, so we cannot read the content of your tasks, goals, projects, categories, tags, habits or statistics. In addition, data is sent over an encrypted connection and encrypted on Google's servers.

Technical data remains visible on the server: the account identifier, the identifiers and number of documents, field names, data size and the time of saving.

If you lose the key on all your devices and do not have its code, the cloud copy cannot be read. Data on your device remains intact and you can create a new copy. Data saved to the cloud without encryption by earlier versions of the app is encrypted at the first sync and its unencrypted copy is deleted.

Turning sync off stops the cloud copy from updating but does not delete it. The copy is deleted only when you delete your account.

4.4 Sync with iCloud

If you choose iCloud, the same kinds of data as in section 4.3 are saved in the private database of your iCloud account (Apple CloudKit). The data does not go to an Alkando account in that case. This copy is free and needs no account.

Here too the content is encrypted on your device as described in section 4.3 before it reaches iCloud. We have no access to the contents of your private iCloud database. Apple stores this data under its own privacy policy. You can delete it in system settings: your name, iCloud, Manage Storage, Alkando.

4.5 Weather

The weather tile is off by default. Once you turn it on and allow location access, the app sends your position rounded to about 1 km to Apple Weather (Apple's WeatherKit). Apple states that the location is used only to provide the forecast, is not associated with information that identifies you and is not tracked between requests.

  • Purpose: showing the weather forecast.
  • Legal basis: your consent, given by turning the feature on (Article 6(1)(a) GDPR). You withdraw it by turning weather off.

We do not store your position or a history of weather requests.

4.6 Places and location

The app asks for location access only "while using the app" and only when you start a feature that needs it (saving a place, the "my location" button, weather).

  • Saved places and their coordinates stay on your device.
  • Place reminders are carried out by iOS; the app does not record a history of your location.
  • When you search for an address or set a pin, the text you type, the map area and the pin coordinates are sent to Apple (Maps services) to return results. Apple processes them under its own privacy policy.
  • A location marker added to a task is saved as an Apple Maps link containing coordinates. It stays on your device and is included in the data export file.

4.7 Calendar and Reminders

Both integrations are off by default.

  • Exporting tasks creates a calendar and a reminders list named "Alkando" on your device and writes task titles, dates and (unless you turn this off) notes to them. If your calendar is connected to iCloud or another account, the system may sync these entries with that account.
  • Showing calendar events in the Day Plan reads the title, time and colour of events for display only. We do not store or send them.
  • Importing from the "Alkando" list in Reminders turns reminders into tasks in the app.

4.8 Purchases and subscription

Payment is handled by Apple. We do not receive your card or billing details. Buying Premium requires signing in, because access is tied to your Alkando account, not to your Apple ID. RevenueCat, Inc. (USA), our processor, checks for us which account has Premium.

When you are signed in, the RevenueCat library connects to that company on every launch of the app and sends:

  • a customer identifier derived from your account identifier,
  • the identifier for vendor (IDFV), IP address, store country, device model, system and app version, and the languages set on the device.

The customer identifier is not the account identifier itself, but we can derive it again from that identifier, so it is personal data in pseudonymised form.

Without an account the app does not connect to RevenueCat. The exception: after you sign out or delete your account, the library keeps running until the app is closed and may send the same technical data with a random anonymous identifier instead of the customer identifier. On the next launch without an account it no longer connects.

The purchase history of your Apple ID goes to RevenueCat:

  • when you buy and when you use "Restore purchases",
  • before a purchase, if your Apple ID has Alkando purchases your account does not yet know about. The app then sends them before you pay, to check whether they belong to another account,
  • when Apple passes a new transaction to the app, for example a renewal.

Purchase history includes transaction identifiers, the plan, dates and, among other things, the price, currency and store country. RevenueCat also receives notifications from Apple about renewals, expiry and refunds.

  • What we do not send: your email address, name or other profile data. We do not turn on advertising identifiers.
  • What we see: in the RevenueCat dashboard, the purchase history of a given customer identifier and aggregate purchase statistics.
  • What we give Apple: at purchase, the same customer identifier, which Apple attaches to the transaction as a token. This way Apple does not receive the account identifier itself.
  • Purpose: confirming the purchase, making Premium available on your devices, tying a purchase to one account, preventing abuse, and purchase statistics.
  • Where: in the United States (section 9).

Purchase data is not covered by the encryption in section 4.3, because RevenueCat has to read it. Apple also gives us aggregate sales reports that do not allow us to identify you.

  • Legal basis: performance of the contract when you buy or have Premium (Article 6(1)(b) GDPR), tax and accounting obligations (Article 6(1)(c) GDPR) and, for the connection after signing out, purchase statistics and preventing abuse, our legitimate interest in running and developing the paid service (Article 6(1)(f) GDPR).

4.9 Feedback and suggestions

In the beta version you can send us a rating and a suggestion. The form works without an account.

  • Data: rating, message text, app version and build number, platform, language and, if you provide it, your email address. We do not attach an account or device identifier to feedback.
  • Purpose: developing the app and possibly replying to you.
  • Legal basis: our legitimate interest in improving the app (Article 6(1)(f) GDPR); for the email address, your consent (Article 6(1)(a) GDPR).

Please do not include personal data in the feedback text. Feedback is not linked to an account, so deleting your account does not delete it. If you want submitted feedback removed, write to us and give the email address or the approximate date and content.

4.10 Contact and help

When you write to us, we process your email address and the content of your message in order to reply. In the Help centre you can choose to share diagnostic data: an identifier, app version, system version and device model. Nothing is sent unless you take that action.

  • Legal basis: our legitimate interest in handling requests (Article 6(1)(f) GDPR) and, where the matter concerns the contract, its performance (Article 6(1)(b) GDPR).

4.11 Messages from the makers of the app

The app currently shows no ads. In future the free version may show only our own messages (for example about new features). They do not use your data, and view counters are stored only on your device. The image for a message is downloaded from the internet, so the server it comes from sees your IP address. We will tell you in the app when this feature is turned on and update this policy.

4.12 Legal claims and legal obligations

In the event of a dispute we may process the data needed to establish, exercise or defend legal claims (Article 6(1)(f) GDPR), and where the law requires it (Article 6(1)(c) GDPR).

4.13 The alkando.app website

On the information pages of alkando.app we use Cloudflare Web Analytics to know how many people visit the site, where they come from and whether the site loads quickly. The tool does not store cookies or any other data in your browser and does not track you across websites. It does not run on the account page or on pages opened from links in emails.

  • Data: pages visited, the page you came from, country, device and browser type, page speed measurements and the IP address that Cloudflare receives when a measurement is sent.
  • We see only aggregate statistics, with no data about individual people.
  • Purpose: visit statistics and site speed.
  • Legal basis: our legitimate interest in developing the website (Article 6(1)(f) GDPR). You can object (section 11) or block the script from static.cloudflareinsights.com in your browser.

5. System permissions

The app asks for each permission only when you start a feature that needs it. You can revoke any of them in system settings.

  • Notifications: reminders about tasks, goals, habits and places, summaries, and a reminder that your trial is ending. All notifications are created locally on your device.
  • Location (while using the app): places and weather.
  • Calendar and Reminders (full access): the integrations described in section 4.7.
  • Camera: a photo as a task attachment or avatar.
  • Microphone: a voice note for a task.

Photos, recordings and files added as attachments stay on your device unless you share them with someone yourself.

6. Notifications and widgets

Notifications may contain the titles of tasks, goals and habits you entered, and place names. Widgets show task titles, your streak, level and XP. This content may be visible on the Lock Screen and Home Screen. You can limit notification previews in system settings.

7. What we do not do

  • We do not sell data or share it for advertising purposes.
  • We do not use in-app behaviour analytics, crash reporting or third-party advertising networks. The only statistics we see are purchase statistics in RevenueCat and aggregate visit statistics for the alkando.app website (section 4.13).
  • We do not use the advertising identifier and do not track you across apps or websites.
  • We do not compare you with other users. The fair-play mechanism compares your activity only with your own usual rhythm and runs only on your device.
  • We do not make decisions about you based solely on automated processing that would have legal or similarly significant effects.

8. Who receives data

We pass data only to parties without which the service could not work:

  • Google Ireland Limited and Google LLC: Firebase and Google Cloud services (sign-in, the sync database, content download) and Google sign-in. Google acts as our processor under a data processing agreement.
  • RevenueCat, Inc. (United States): handling Premium access and purchase history (section 4.8). RevenueCat acts as our processor under a data processing agreement and uses its own providers, mainly in the United States.
  • Cloudflare, Inc.: the server that handles sign-in with a code (section 4.2), account deletion and deletion in 30 days (sections 12 and 12.2), and visit statistics for the website (section 4.13). Cloudflare acts as our processor under a data processing agreement.
  • Plus Five Five, Inc., operating as Resend (United States): sending sign-in codes (section 4.2) and email notices about account deletion (section 12.2). Resend acts as our processor under a data processing agreement.
  • Vercel Inc. (United States): hosting of the alkando.app website, IP address and technical data when you visit the site. Vercel acts as our processor under a data processing agreement and, for data generated by the service itself, as a controller.
  • Apple Distribution International Limited and Apple Inc.: Apple sign-in, iCloud, the App Store, payments, Maps, weather forecasts (Apple Weather). Apple acts as a separate controller.
  • Apple (iCloud Mail), which hosts the support@alkando.app mailbox: only when you write to us.
  • Public authorities, where the law requires us to.

9. Transfers outside the European Economic Area

Some data is processed in the United States (in particular account data in Firebase Authentication). The transfer is based on the European Commission's adequacy decision for the EU-U.S. Data Privacy Framework, in which Google LLC participates, supplemented by standard contractual clauses.

The data described in section 4.8 is processed by RevenueCat and its providers in the United States. This transfer is based on standard contractual clauses adopted by the European Commission.

The data described in sections 4.2 (sign-in with a code), 4.13, 12 and 12.2 passes through Cloudflare's network, which may process it outside the European Economic Area. This is based on the safeguards in our data processing agreement: standard contractual clauses adopted by the European Commission and, to the extent covered by certification, the EU-U.S. Data Privacy Framework.

The alkando.app website is handled by Vercel, including in the United States. This is based on standard contractual clauses adopted by the European Commission.

Sign-in codes and email notices are handled by Resend and its providers, mainly in the United States. This is based on standard contractual clauses adopted by the European Commission and the EU-U.S. Data Privacy Framework.

We will provide a copy of the safeguards on request.

10. How long we keep data

  • Account data and data synced with an Alkando account: until you delete the account. After deletion Google removes it from its systems and backups within up to 180 days.
  • Purchase data and identifiers at RevenueCat: for the duration of our agreement with RevenueCat, or until deleted earlier. Deleting your account requests their deletion, and RevenueCat carries this out in a queue and gives no time limit (sections 12 and 12.2).
  • The sign-in token needed for this request in the app: on your device until the request is sent, if the first attempts fail. It is valid for about an hour.
  • The account identifier and deletion date at Cloudflare: until the deletion is carried out or cancelled. The account identifier needed to retry deleting the record at RevenueCat: up to 90 days from the deletion of the account.
  • Hashes of the email address, IP address and code, and sign-in attempt counters at Cloudflare: up to 48 hours after the last attempt.
  • Sending data for codes and notices at Resend: up to 30 days.
  • Website visit statistics at Cloudflare: detailed measurements up to 7 days, aggregate statistics up to 6 months.
  • IP addresses in sign-in logs: for a few weeks (under Firebase's rules).
  • Firebase installation identifier: until you uninstall the app or delete your data, then up to 180 days in Google's backups.
  • Feedback and suggestions: no longer than 24 months after the beta ends, or until you ask us to delete it.
  • Correspondence: for as long as needed to deal with the matter, and then until any claims become time-barred.
  • Local data: for as long as you keep it in the app. Tasks moved to the Trash are deleted automatically after 30 days.

11. Your rights

You have the right to:

  • access your data and receive a copy of it,
  • have data corrected,
  • have data deleted,
  • restrict processing,
  • data portability,
  • object to processing based on our legitimate interest,
  • withdraw consent at any time, without affecting the lawfulness of earlier processing.

You can exercise some rights yourself in the app: exporting tasks, goals and projects to a file (Settings, Privacy & consents, Export my data), turning off sync, weather and integrations, and deleting your account and data. You can also delete your account at alkando.app/account. For anything else write to support@alkando.app. We reply within one month at the latest.

If you believe we process data unlawfully, you can lodge a complaint with the President of the Personal Data Protection Office in Poland (ul. Stawki 2, 00-193 Warsaw) or with the supervisory authority in the country where you live.

Providing data is voluntary. Without an account you cannot buy Premium or use Premium features; all other features work without providing any data.

12. Deleting your account and data

The "Delete account & data" option (Settings, Privacy & consents):

  • deletes your account, all data synced with the Alkando account and the key it was encrypted with,
  • for Apple sign-in, revokes the link between the app and your Apple account,
  • requests deletion of your purchase record at RevenueCat through Cloudflare Workers (section 12.2),
  • clears the app's database and settings on the device.

With an account, you confirm it by typing the phrase shown. This cannot be undone. If you have no account, the same option clears local data.

A few things are outside the reach of this option and need action from you:

  • data in your iCloud: delete it in system settings (your name, iCloud, Manage Storage, Alkando),
  • the "Alkando" calendar and reminders list: delete them in the Calendar and Reminders apps,
  • attachment files and export files saved in the app's storage: they are removed when you uninstall the app,
  • submitted feedback: we will delete it at your request,
  • the record at RevenueCat, if the request fails: you will not see an error, and attempts are repeated. We do not guarantee that this record is deleted. To be sure it is gone, write to support@alkando.app from your account's email address. We will delete it manually within the time limit in section 11,
  • your subscription: deleting the account does not cancel it. You do that in your Apple account settings. If the subscription stays active and you keep using the app on that Apple ID, a record at RevenueCat may be created again.

A purchase stays with the account on which it was bought. As long as the record at RevenueCat exists, your Apple ID remains tied to it, so a new account on the same Apple ID will not take over the purchase. This also applies to the Lifetime plan.

12.1 Signing out and changing accounts

When you sign out you choose one of two options:

  • "Sign out": data stays on the device and in the cloud,
  • "Sign out and delete data from phone": tasks and the other data in section 3, attachments, export files, scheduled notifications and items exported to Calendar and Reminders are removed from the device. The cloud copy stays.

In both cases the theme, language, layout, notification settings and the encryption keys in the keychain stay on the device; without those keys you could not read your copy when you come back. Premium features come back when you sign in to the same account again.

If the device holds another account's data, the app sends nothing until you decide:

  • "Start with this account's data": the data on the device is deleted as described above, and the previous account's cloud copy stays,
  • "Add it to this account": the data goes to the cloud of the account you are signing in to. This cannot be undone, so do not choose this option if the data belongs to someone else,
  • "Sign out" or "Cancel": nothing is deleted or sent.

12.2 Deleting on the website and deletion in 30 days

At alkando.app/account you can delete an account created with an email address or with Google. An account with Apple sign-in can be deleted only in the app, because the website and the server do not revoke the link with your Apple account.

On the website you first sign in again (with a code from your email or Google) and type the phrase shown. Then you choose:

  • "Delete now": the account and the data synced with it are deleted right away. This cannot be undone,
  • "Delete in 30 days": this option is also in the app, again only for accounts without Apple sign-in. You can keep using the account, but the copy in your Alkando account stops and your data stays on your phone. The app and the website show the deletion date, and until that date you can cancel the deletion in either place. Once deleting has started, it cannot be cancelled.

Each of these options also requests deletion of the purchase record at RevenueCat. If this fails, you will not see an error, and the server keeps retrying in the background. We do not guarantee that this record is deleted: it may stay, for example if the request does not reach the server or the retry period ends (section 10). To be sure it is gone, write to support@alkando.app.

These options do not immediately clear data on your device or in iCloud and do not cancel a subscription. Once the account is gone, the app asks whether to keep the data on your phone. You delete data in iCloud in system settings (section 12), and the subscription in your Apple account settings.

Cloudflare Workers handles this for us. When you are signed in, the app and the website ask it for the deletion date, in the app on launch and when you return to it. With each such query and each request it receives your IP address and a sign-in token containing your account identifier and email address, as well as your name and picture address if the account has them. With "Delete in 30 days" it stores the account identifier and the deletion date. We do not save the token on a server and we do not turn on logs for this service.

When you delete your account or choose deletion in 30 days, we email you a notice that the deletion was scheduled, cancelled or carried out, from konto@alkando.app. These are sent by Resend, which receives your email address and the content of the notice and keeps sending data for up to 30 days. With deletion in 30 days your email address is also stored at Cloudflare, from the start of deleting until the notice is sent. If a notice is not sent, the deletion is still carried out.

  • Purpose: carrying out your deletion request and showing its date.
  • Legal basis: performance of the contract (Article 6(1)(b) GDPR) and giving effect to your right to erasure (Article 6(1)(c) GDPR).

13. Security

Connections to services are encrypted. The content of the cloud copy is additionally encrypted on your device with a key we do not hold. Access to cloud data is restricted by rules so that each user sees only their own data. The account identifier is stored in the system keychain. Local data is protected by device encryption and your passcode, so we recommend setting one. No system offers a complete guarantee; if a breach could seriously endanger your rights, we will inform you as the law requires.

14. Children

Alkando is intended for people aged 16 and over. We do not knowingly collect data from children below that age. If you are a parent or guardian and believe a child has given us data, write to us and we will delete it.

15. Additional information for people in the United States

This section supplements the policy for residents of the United States, including California.

  • Categories of data we collect: identifiers (email address, user identifier, installation identifier, identifier for vendor, IP address), name, content you create in the app and sync at your request, data about your progress in the app, data about your Premium purchase, feedback. Approximate location is passed to Apple (weather service) only after you turn that feature on and is not stored by us.
  • Purposes: running accounts, Premium and sync, delivering app content, handling requests, developing the app.
  • We do not sell personal information and do not share it for targeted advertising. We have not done so in the past 12 months.
  • We do not use sensitive data to infer characteristics about you.
  • You have the right to know what data we hold, to obtain a copy, and to request correction and deletion. We will not treat you worse for exercising these rights. Send requests to support@alkando.app; we may ask you to confirm that you own the account. You may act through an authorised agent.
  • The app does not respond to "Do Not Track" signals because it does not track users across services.
  • The app is not directed to children under 13 and we do not knowingly collect their data.

16. United Kingdom and Switzerland

If you use the app in the United Kingdom or Switzerland, you have rights equivalent to those in section 11 under local law. You can complain to the Information Commissioner's Office or the Federal Data Protection and Information Commissioner respectively.

17. Changes to this policy

We update the policy when the app or the law changes. The current version is always available in the app (Settings, Privacy & consents) and at alkando.app/privacy. We will tell you about significant changes in the app before they take effect.

18. Contact

J20 Labs
support@alkando.app