Tellerino

Juridisk · Opdateret

Privatlivs­politik

Denne tekst findes på tysk og engelsk. Nedenfor finder du den engelske version; det er den tyske version, der gælder: læs den tyske version.

1. Controller

Jan Colak
Jürgen-Töpfer-Straße 4
22763 Hamburg, Germany
Email: support@tellerino.app

2. What data we process

We process account, household, subscription and AI data in order to provide the app and its features (Art. 6(1)(b) GDPR – performance of a contract). Where a different legal basis applies, it is stated with the respective item.

  • Account: If you sign in with email, we store your email address and password (encrypted), plus the name or nickname you enter when registering. The members of your household see it, for example in notifications; you can change it in Settings under “Account”.
  • Sign in with Apple or Google: If you sign in with Apple or Google, the provider gives us your email address and your name; we don’t store a password in that case. With Apple, you decide whether to share your name and whether to hide your email address – then we only receive an anonymous relay address from Apple. Google also transmits the address of your profile picture, which we don’t use. The members of your household see the name we receive, as described above.
  • Household data: shopping list, meal plan, recipes, ratings, uploaded photos and the household settings (such as meals, number of people and excluded ingredients) – shared with the members of your household.
  • Sharing the shopping list by link: If you share your shopping list by link, anyone who has the link can, without the app and without an account, see the list’s item names, quantities and notes, the categories and the ticked-off status in a browser, and can tick items off or reopen them. They do not see your household’s meal plan, recipes, names or members. Only if you expressly allow it does the page also offer the person the option to join the household; to do so it hands them your household’s invitation code. The link expires after 30 days at the most and ends at the latest with the household; you can withdraw it at any time in the app’s Settings. On our server we only store a hash of the link, not the link itself. You decide who you share the link with. The legal basis is performance of a contract (Art. 6(1)(b) GDPR). What happens when the page is opened in the browser is described in the section “Website (tellerino.app)”.
  • Camera, photos and videos: the app accesses your camera or photo library only when you take a recipe photo, select one from your gallery or select a saved video for import. No other photos or videos are read; access occurs solely when you trigger it.
  • Clipboard: If you don’t have a household yet, the app checks once at first launch whether the clipboard contains an invitation or gift code that you copied on our website before. The content stays on your device; the app only sends a recognised code that you accept to our server to redeem it.
  • Home screen widget: To keep the Tellerino widget for the home screen up to date, the app on iPhone and iPad stores the planned dishes for the next few days and the next open items on your shopping list in a storage area shared by the app and the widget on your device. This data does not leave your device. When you sign out, delete your account or leave the household, the app resets the widget.
  • Notifications: If you switch on “Household updates” in Settings under “App”, the app registers your device with Expo’s push service (650 Industries, Inc., USA), and we store the push token (an address through which notifications reach your device) together with the platform and app language. When another member adds something to the shopping list or someone joins your household, our server sends the notification via Expo, which delivers it via Apple or Google. The notification contains the member’s name and the item, for example “Anna added milk to the list”. If you switch notifications off or sign out, we delete this device’s push token. The legal basis is Art. 6(1)(b) GDPR.
  • App updates: At launch, the app asks Expo’s update service (EAS Update, 650 Industries, Inc., USA) whether a newer version of the app content is available and downloads it if so. This transmits your IP address, a random identifier of this installation, the platform, the app version and the update channel, but no account or household data. The legal basis is our legitimate interest (Art. 6(1)(f) GDPR) in delivering bug fixes quickly.
  • Protection against abuse: So that only the genuine Tellerino app can use our server functions, it verifies itself through Firebase App Check: on Apple devices with Apple’s App Attest, on Android with Google’s Play Integrity. Apple or Google confirm that the request comes from the unmodified app on a real device; technical characteristics of the device and app are checked, not names or email addresses. The legal basis is our legitimate interest (Art. 6(1)(f) GDPR) in protecting our services against abuse.
  • Subscription management: So that the app knows your subscription status and can unlock Tellerino Pro, it transmits your user identifier (a random string) and, after a purchase, your purchase status to RevenueCat (USA). Your payment details remain with Apple or Google. Your display name is shown to the other members of your household when Pro is active through you (“Pro via …”); product and price are not shared with them; so that the app knows until when Pro applies, the household technically only receives the end date of the current period.
  • Use of the AI features: links, photos and text that you enter or share with Tellerino are transmitted to OpenAI (USA) for recipe recognition or creation; for video file import, the following item also applies. For recipe ideas and automatic week planning, our server also sends the household settings needed for this (such as the meal, number of people, the desired mix of dishes with meat, fish and vegetarian dishes, and excluded ingredients) and the names of recently saved or poorly rated recipes, so that nothing repeats. No account data is sent along with them.
  • Video file import: If you select a saved video from your library in the app, the app first uploads the file to Google Firebase file storage (EU region). Our server separates the audio track and a few individual frames from it and transmits them to OpenAI (USA): the audio track for conversion into text (transcription), the transcript and the frames for recipe recognition. The video file is deleted after processing; if it is left behind, for example after an interruption, the storage service deletes it automatically after one day at the latest. The audio track may contain voices and background sounds, so only select videos that you are entitled to use for this. No account data is sent along. The legal basis is performance of a contract (Art. 6(1)(b) GDPR).
  • Recipe links: when recognising a recipe from a link, our server automatically retrieves the content of the web page at the address you entered (including any preview image) in order to extract the recipe from it.
  • Direct requests from your device: the app loads some content directly, without going through our server: depending on the recipe, recipe images come from Pexels, from the website the recipe comes from, or as a preview image from YouTube. If a recipe website blocks our server, the app loads the page once itself and sends its content to our server for recognition. The respective provider sees your device’s IP address and the usual technical details such as operating system and app version; what it stores is up to that provider.
  • Crash reports: in the event of a technical error we automatically transmit an error report (affected feature, device type, app version) to Sentry so that we can fix problems. No names, email addresses or IP addresses are transmitted – only your pseudonymous user identifier (a random string), so that related reports can be linked. This processing is based on our legitimate interest (Art. 6(1)(f) GDPR) in a functioning app and cannot be switched off.
  • Usage statistics: only if you expressly consent do we use the PostHog service to record, in pseudonymised form, how the app is used. We record: app openings, which features are used and how often (for example whether the recipe ideas feature was used), individual milestones (household created or joined, setup completed, item added to the list, recipe saved, week planned, invitation sent, list shared by link, Pro offer shown, closed or purchased, gift code redeemed, email address confirmed or confirmation postponed) and the number of people in your household. For the Pro offer we also record the prices shown with their currency, the plan chosen, whether a purchase was cancelled or failed, and the country of your store account (for example DE). Every event includes the platform (iOS, Android or web). Your user identifier (a random string) is transmitted so that related events can be linked; no names, email addresses, recipe content or details about other household members are transmitted. The legal basis is your consent (Art. 6(1)(a) GDPR), which you give or decline when first starting the app and can withdraw or grant at any time in Settings under “Improve the app”.
  • Attribution of Apple ads (iPhone only): Only if you consent does the app on iPhone check whether you came to Tellerino through an ad in the App Store. You are asked together with the usage statistics, after your first sign-in or in Settings under “Improve the app”; an earlier consent whose notice did not yet mention this attribution does not count for it. For this, iOS creates a short-lived attribution code (valid for 24 hours) at the app’s request, which the purchase SDK sends to RevenueCat (USA) together with your user identifier (a random string). RevenueCat uses it to ask Apple and stores the answer with your subscription record: whether an ad was attributed and, if so, campaign, ad group, search term, country, whether it was a first download or a redownload, and whether the ad was tapped or only shown. The app does not use an advertising ID (IDFA) for this. This lets us see which ads lead to trials and subscriptions. The legal basis is your consent (Section 25(1) TDDDG, Art. 6(1)(a) GDPR). If you withdraw it, the app stops sending attribution codes from the next app launch at the latest. Once attribution has been switched on during an app session, it technically stays on until the app is closed; if you sign out and sign in with a different account during that time, the code may therefore also be sent for that account. To avoid this, close the app completely once after signing out. The app cannot remove an attribution that has already been stored; it is deleted together with your subscription record at RevenueCat when you delete your account, or on request to support@tellerino.app.

3. Service providers and other recipients

These service providers process data on our behalf:

  • Google Firebase (sign-in, database, file storage, server functions, App Check and hosting of this website and the web app; the provider is a US company). The database, file storage and server functions run in the EU; Google processes sign-in (Firebase Authentication) exclusively in the USA.
  • OpenAI (AI recipe features, including transcription of the audio track in video file import, USA)
  • RevenueCat (subscription management and, only with consent, attribution of Apple ads; USA)
  • Expo (delivery of notifications and app updates; 650 Industries, Inc., USA)
  • Sentry (crash reports; EU region, operated by Functional Software, Inc., USA)
  • PostHog (app usage statistics, only with consent, and individual website events; EU region)
  • Cloudflare (website visitor statistics; Cloudflare, Inc., USA)
  • Pexels (recipe photos: our server only transmits a search term; the app loads the photo it finds directly, see section 2)
  • Google’s YouTube Data API (reading video descriptions for YouTube links)

In addition, where you use the respective feature, data is received by Apple and Google as operators of the app stores, of Sign in with Apple and Google sign-in, of the authenticity check (App Attest, Play Integrity) and of notification delivery, and by recipe websites and YouTube when the app loads images or pages directly.

Where data is transferred to the USA, the transfer is based on the EU-US Data Privacy Framework where the respective provider is certified under it, and otherwise on EU standard contractual clauses.

4. Storage period and deletion

Your data remains stored for as long as your account exists. You can delete your account yourself at any time in Settings. Shared household data remains with the household as long as someone is still in it; if you are the last member, we delete the household with all its data. Backup copies of the database expire after seven days at the latest. We delete video files from video file import after processing, after one day at the latest. Crash reports at Sentry only carry your pseudonymous user identifier. They are not removed individually when you delete your account, but are deleted automatically by the provider after 90 days at the latest. What exactly is deleted and what remains is explained at tellerino.app/da/account-deletion.

5. Your rights

Access, rectification, erasure, restriction of processing, data portability and objection, as well as the right to lodge a complaint with a supervisory authority. Contact: support@tellerino.app.

6. Data export (right to data portability, Art. 20 GDPR)

To receive a copy of your data in a common, machine-readable format (for example JSON), simply write to us at support@tellerino.app. We will process your request within 30 days and send the data to the email address of your account.

You can also export your recipes yourself: in the app, Settings → Account → Export my data creates a text file with your household’s recipes (name, servings, times, ingredients, instructions, source and notes). Use your device’s share menu to save it or pass it on to an app of your choice. The file is created on your device and only goes where you share it. For all other data, the email route applies.

7. Website (tellerino.app)

This website is hosted on Google Firebase Hosting. When you visit it, Google processes your IP address and, according to Google, keeps it in server logs for a few months to detect abuse. We set no cookies. Only if you choose a language yourself in the language menu does your browser remember that choice. Two services help us understand whether the site serves its purpose:

  • Cloudflare Web Analytics counts page views without cookies and without user profiles; your IP address is processed technically but not stored (provider: Cloudflare, Inc., USA). We do not use Cloudflare Web Analytics on the invitation and gift pages (tellerino.app/join/… and tellerino.app/gift/…).
  • We send individual events to PostHog (EU region), without a persistent identifier and without a profile: when you press a store button or the “Use it in your browser” link (which store or the web app, page language, position on the page and referral source such as “tiktok”), and on the invitation and gift pages when the page is opened, the code is copied or a store button is pressed. These events contain the page language, the device type (iOS, Android or computer), for a store button the store chosen and, when the page is opened, whether the address contained a code in a valid format – never the code itself. PostHog processes your IP address technically in the process.

List page (tellerino.app/l/…): When you open a shared shopping-list link, Google Firebase Hosting and the server function that delivers the list process your IP address technically; the function’s logs are kept for about 30 days, and the retention period stated above applies to hosting. The link’s key sits after the “#” of the address, which your browser does not send to servers, and it only reaches the function in the request body – never in the address and never to PostHog. Your browser stores there (localStorage) the link key, a copy of the list you saw last (together with the time you last opened it) and ticks not yet transmitted, so that the list is available in the shop even without a connection and it is clear which list is meant when you start it from your home screen. This is strictly necessary for the service you asked for (§ 25(2) no. 2 TDDDG) and needs no consent. We set no cookies there either, and Cloudflare Web Analytics is not used there.

On the list page we send individual events to PostHog (EU region), without a persistent identifier and without the link key: when the page is opened (a state such as “valid” or “expired”, device type, page language and the rough number of items in bands such as “1–10”), the number of items ticked off when you leave the page, and when a store button, the “Use it in your browser” button or the “Plan along” button is pressed. Item names and household data are never transmitted. PostHog processes your IP address technically in the process.

The legal basis is our legitimate interest (Art. 6(1)(f) GDPR) in a working, secure and discoverable website.

8. Web app (app.tellerino.app)

Tellerino is also available as a web app in your browser at app.tellerino.app. You sign in there with the same account and see the same household data. For your account, household data, sharing the shopping list by link, the AI features, crash reports and usage statistics, section 2 applies, and section 3 for the service providers. In the web app you sign in with email or with Google; Google sign-in runs through a Google window in your browser. In mobile browsers (smartphone, tablet) and in Safari, the web app loads the files from Google needed for this as soon as the page is opened; in the process, Google receives your IP address and details about your browser. Sign in with Apple, purchases of Tellerino Pro, notifications and the authenticity check via App Check are not available in the web app.

Like this website, the web app is hosted on Google Firebase Hosting. For your IP address in the server logs, the section “Website (tellerino.app)” applies.

Storage in your browser: So that you stay signed in, your browser stores your sign-in (IndexedDB). So that the shopping list, meal plan and recipes appear quickly and even without a connection, the web app also keeps a copy of this data and of your household, as well as changes not yet transmitted, in your browser’s storage (localStorage). Drafts are kept there too (for example your answers from the setup and a recognised recipe that has not been saved yet), as well as pending invitation or gift codes, the key of a shared list link, settings such as language and appearance, your decision on usage statistics and markers for whether a tip has already been shown. When you sign out or delete your account, the web app removes the household and account data from this storage; what remains are device settings and markers for tips already shown, some of them with your random user identifier. This is strictly necessary for the service you asked for (§ 25(2) no. 2 TDDDG) and needs no consent. The Firebase library we use also places a technical entry with no link to you as a person in your browser’s storage as soon as the page is opened (the date and the library’s version numbers, no identifier). We set no cookies in the web app.

Only if you consent to usage statistics does PostHog also store a random identifier and events not yet sent in your browser. The basis for this is your consent (§ 25(1) TDDDG, Art. 6(1)(a) GDPR), which you can withdraw at any time in Settings under “Improve the app”. If you withdraw it or sign out, PostHog removes the identifier; a marker stays in your browser saying that nothing may be sent.

Error reports from the browser: The web app, too, sends an error report to Sentry in the event of a technical error, as described under “Crash reports” in section 2. Instead of details about the device, it may contain details about the browser and operating system, as well as the address of the web app page that is open and the pages visited most recently. In addition, your browser reports directly to Sentry when our security rules for the web app (Content Security Policy) block content from loading or would block it. Such a report contains the address of the page, the page visited before, the blocked address, the rule concerned and details about the browser and operating system, but no user identifier. Sentry processes your IP address technically in the process and does not store it. The legal basis is our legitimate interest (Art. 6(1)(f) GDPR) in a working and secure web app.