Privacy

Updated October 9, 2026

Who is responsible

The data controller is AKurba, an EURL based at 2 rue Carnot, 78210 Saint-Cyr-l'École, France. For any question: hello@tellendar.app.

What the server keeps

• An anonymous device identifier. There is no account, no email address, no password. The first time it connects, the app creates a key on your iPhone that Apple ties to this app, on this phone. The server keeps the number of this key, its public part, a technical counter and the receipt Apple attaches to its proof. It also keeps the sessions the app opens (a fingerprint and an end date) and a random technical token. None of this says who you are.
• Your device: an identifier the app draws at random when it is installed, the generic name "iPhone", the platform, the dates of the first and last connection, and the notification token provided by Apple. This token is used to wake the app when your Google calendar changes or when it is linked from another device, to show a backup notification when an alarm tied to Google has to move, and to tell you when your subscription ends.
• The state of your subscription: the date it is paid until, the date it was last checked, and whether the end-of-subscription notice was sent.
• The number of sentence analyses made each month, and the number of trial analyses used, to keep an eye on costs.
• If you link Google Calendar: what is described below, and nothing more.
• If you report a parsing mistake: the conversation of that event, as described below.

The server keeps neither your events nor their titles, except those of an event you report a parsing mistake for.

What stays on your phone

Your events, their alarms and the history of your exchanges with the app are on the iPhone. Dictation is transcribed on the iPhone. When you change an event with a new sentence, only that sentence and the event concerned are sent for analysis (see below); your earlier exchanges stay on the iPhone. With each exchange, the app also keeps the answer of the model that read the sentence; it only leaves the phone if you report a mistake.

The iCloud backup

When iCloud is on for the iPhone, the app keeps in your iCloud space, at Apple, a copy of your events, their alarms and their links to Google Calendar, with two technical identifiers of the app. The history of your exchanges is not in it. This copy is used to get your events back after a reinstall or on a new phone. Tellendar's publisher has no access to it. You can erase it from your iPhone's iCloud settings, or with "Erase my data" in the app's settings.

Google Calendar

Linking Google Calendar is optional. You choose one or more calendars.

What Google data Tellendar accesses

Tellendar asks Google for the following, and nothing more:

• The list of your calendars ("calendar.calendarlist.readonly" scope): the name, color, time zone and identifier of each calendar, so you can choose which ones to follow. Your iPhone reads this list. When you change the calendars you follow, the server reads it again to check your choice, without keeping it. Tellendar never changes this list.
• The events of the chosen calendars ("calendar.events" scope): Tellendar reads them, and creates, changes or deletes the ones you create, change or delete in the app. Of each event, it uses the title, the date and time, the time zone and the repeat rule, as well as technical data: the identifier, the status and the date it was changed. Google sends the whole event to your iPhone, but the description, location and guests are ignored: Tellendar neither keeps them nor writes them back.
• The email address and identifier of your Google account ("openid" and "email" scopes): to show in the settings which account is linked. The address stays on your iPhone. The server receives it once, in Google's answer when you connect, and does not keep it. It only keeps a fingerprint of the identifier.

How Tellendar uses it

• Your iPhone is what reads and writes your events at Google. It reads the events of the chosen calendars and writes the ones you create, change or delete in Tellendar. A new event goes to the calendar you picked for new events, an existing event stays in its own. When you link Google Calendar, the app offers to send your upcoming events there; they only go if you accept. The colors and names of your calendars stay on your iPhone.
• What Tellendar also writes. On the events it creates, Tellendar turns off Google's default reminders, since Tellendar is what rings. On each event it writes, it stores a private mark, which Google Calendar does not show, with its own identifier for the event. It adds no guests. Nothing else is written at Google.
• The server keeps the authorization Google gives it, encrypted, to provide your iPhone with short-lived access. It also keeps the scopes you granted, an identifier of your Google account as a fingerprint, and the technical markers Google provides so the server is told about changes and can resume reading where it stopped. It keeps the list of calendars you follow: the identifier of a shared calendar is often someone's email address, so it is kept encrypted too, never in clear text. While you connect to Google, it keeps a temporary state for a few minutes.
• The server keeps an alarm index: for each event that has an alarm, the identifier Google gives it (a meaningless string of characters), the identifier of the alarm, its delay, and whether the event repeats. No title, no date.
• When Google reports a change, the server only asks Google for the identifier, status, time and change date of the changed events in the calendars you follow, never their title. It also does this read every six hours, in case a signal gets lost. It wakes the app with the identifiers of the changed events. If the app does not answer, it sends a notification to move the alarm. The time is only kept for that sending: five minutes normally, fifteen at most if Apple's notification service does not answer.

Who receives it

Your Google data is not sold, not shared and not passed on to anyone. It is not used for advertising, and nobody here reads it. There is one case, which you control: when you change a Google event with a sentence and your iPhone cannot analyze that sentence itself, the title, dates and times, repeat rule and alarms of that event go with the sentence to Mistral AI, only for that analysis, and only if you have agreed to it (see How your sentences are understood). It is never used to train models.

When you unlink in the app, everything the server kept about your link to Google is erased, and the authorization is handed back to Google. One exception: if another iPhone with Tellendar is still linked to the same Google account, the authorization is not handed back, because Google would also take it away from that iPhone. The events that came from Google leave your iPhone; they stay in your Google calendar. You can also remove the access from your Google account, at myaccount.google.com/connections.

Tellendar's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. This information is only used to show and set your events and alarms.

How your data is protected

• Encrypted in transit. All exchanges between the app, the server and Google go through HTTPS (TLS).
• Google access encrypted at rest. The authorization given by Google is encrypted in the database with XChaCha20-Poly1305. The key is not in the database: it is kept apart, in the server's configuration. A copy of the database is therefore not enough to use it. Each authorization is also tied to its owner: it cannot be copied over to someone else.
• Nothing that identifies you. The identifiers of the calendars you follow are encrypted the same way, and tied to their owner too. The identifier of your Google account is only kept as a SHA-256 fingerprint. The server keeps no event title, no description and no email address.
• Only the Tellendar app. The server only answers the real Tellendar app on a real iPhone, which Apple attests (App Attest). Nobody else can ask it for access to your calendar.
• Limited access. Only Tellendar's publisher runs the server and the database. They are hosted by Clever Cloud in Paris, which only processes this data on the publisher's behalf.
• On your iPhone, your events are stored in the app's private space, protected by the iPhone's encryption.

The technical log

The app notes on your phone what it does: an alarm set, a sentence analyzed, a backup written, a server error. Dates, numbers and codes; never a sentence you dictated, never an event title, never an address. The last few hundred lines are kept, the oldest are overwritten.

This log stays on the phone. It only leaves if you send it, with "Report a bug" in the app's settings. You describe what happened, and you can see the whole report before sending it. If the app closed by itself or froze, iOS gives it a report; the app only keeps a summary of it (versions, type of error), on the phone, and this summary goes with the report.

The report also contains the app's installation identifier, the iPhone model, the iOS and app versions, the language, the state of the subscription, of alarms, of Google Calendar and of the backup, and the number of events. With the installation identifier, support can find your device on the server.

Your message, the report, the screenshots you choose to attach and your email address, if you give it, go through the server, which forwards them through Brevo to the support address. Cloudflare then routes this email to the publisher's mailbox. The server keeps none of it. Screenshots and the address are optional; the address is only used to reply to you.

The server, for its part, writes one line per request: the time, the method and route called, the result, the duration and a random identifier. This identifier shows in the app's error message, so you can give it to support and they can find the line. When an error occurs with Google, or a device goes past a threshold of analyses, the server also notes the device's anonymous identifier; in the second case, an alert goes to the publisher through Brevo. Like any host, Clever Cloud sees the IP address of requests.

How your sentences are understood

When your iPhone has Apple Intelligence, the sentence is first analyzed on the iPhone. If your iPhone does not have Apple Intelligence, or if it cannot analyze the sentence, the sentence is sent to Tellendar's server, which passes it on to Mistral AI, a French company. This only happens if you have agreed to it.

What goes: the sentence, the date and time, the time zone and the language. For a change, the event as it stands goes too: its title, dates and times, repeat rule and alarms. Your earlier exchanges and your other events do not go. The server passes no identifier of your device to Mistral. Mistral processes this data in the European Union and does not use it to train its models. The server does not keep the sentence: it only counts the number of analyses.

If your iPhone does not have Apple Intelligence, the app asks for your agreement the first time it opens. Otherwise, it asks at the first sentence that needs it. Your agreement stays on your iPhone. You can withdraw it in the app's settings, under "Analysis by Mistral AI"; you then create your events by hand when the iPhone does not understand the sentence.

Reporting a parsing mistake

When a sentence was misunderstood, you can report it from the event's card, with "Report a mistake" in its menu. The conversation of that event then goes: each of your sentences, the result of each analysis, the date, time, time zone and language at that moment, the event before and after, and the answer of the model that read the sentence (Apple or Mistral AI). The event as it stands and the app's versions go too. The report is stored without any device or subscription identifier.

Nothing goes without you. On the first report, the app says what goes and shows you the exact content before sending. The next ones go as soon as you tap "Report a mistake".

These reports are kept on the server, at Clever Cloud in Paris. With each new version of the app, they are read to find the mistake and add it to the tests, then deleted. The server erases them by itself at most 180 days after they were sent.

Providers

• Clever Cloud (France) hosts the server and the database, in Paris.
• Mistral AI (France) analyzes sentences when the iPhone cannot, if you have agreed to it.
• Apple delivers notifications, collects the subscription, hosts the iCloud backup and attests that the app talking to the server is really Tellendar, on a genuine iPhone.
• Google, only if you link Google Calendar.
• RevenueCat (United States) tracks the state of the subscription. It receives the random identifier the server gives your device, and your in-app purchases.
• Brevo (France) delivers the bugs you report to support, sends the publisher technical alerts and a notice for each sign-up to the waiting list, and keeps the waiting list.
• Cloudflare (United States) manages the domain names, serves this website, and routes the email sent to tellendar.app, including the bugs you report.

How long

The server keeps your data as long as you use the app. The "Erase my data" button, in the app's settings, erases everything the server keeps about your device, unlinks Google Calendar, and erases your events on the iPhone and the iCloud backup. It does not cancel a subscription: that is managed in the App Store settings.

If you delete the app without using this button, the server erases this data by itself after 12 months without a connection, if there is no subscription still running. To have it erased sooner, write to hello@tellendar.app. RevenueCat keeps your device's identifier and your purchases; to have them erased, write to the same address.

The host's backups, made every night, then disappear as they are renewed. The parsing mistakes you report are deleted once handled, and at most 180 days after they were sent.

Your rights

You can access, correct, export or delete your data, and object to its processing. Export and erasure are done in the app. For anything else, write to hello@tellendar.app. If the answer does not satisfy you, you can complain to the French data protection authority, the CNIL.

The waiting list

If you leave your email address on the home page, it is kept at Brevo, in Tellendar's waiting list. It is only used for two things: telling you when Tellendar comes out on the App Store, then asking for your opinion of the app. Nothing else, and it is never passed on to a third party. Each new sign-up is reported to the publisher by an email that contains the address. The list is deleted at most one year after the release. Each email contains a link to unsubscribe, and you can also ask at hello@tellendar.app.

This website

This website uses no cookies and does not measure traffic. It loads nothing from another service: its font and its video come from the site itself. Cloudflare receives your IP address in order to send you the pages, like any host. It also uses it to limit sign-ups to the waiting list, and keeps a technical log of the requests for the video and the waiting list.