Farenda
Home

Privacy Policy

Effective 22 November 2026, version 2026-11-22-2 (draft). Applies to the Farenda apps for iOS and Android, the web app, the account and family service and the website farenda.app. This is a convenience translation; the German Datenschutzerklärung is legally binding.

ControllerData and purposesGoogle dataData protectionPurchasesRecipientsChildrenDeletionTest programmeYour rights

1. Controller under the GDPR

Ilias Martis
c/o Impressumservice Dein-Impressum
Stettiner Str. 41
35410 Hungen
Deutschland
E-mail: info@farenda.app

No data protection officer is appointed because the statutory requirements for one are not met. Send privacy requests to the e-mail address above.

2. What data we process and why

Account and sign-in

When you sign in with Google we receive your Google account identifier, name, e-mail address and profile image. We use them to set up your Farenda account and session and to show your profile in the family. The legal basis is Article 6(1)(b) GDPR (contract). These data are required for signed-in features; without them we cannot provide those features.

Family service

We store families, memberships and roles, person profiles without an account (display name and colour), invitations (optionally with an e-mail address), calendar mappings and sharing settings, event metadata (Google event id, creator, assignment, audience), comments on events, family tasks, shopping lists, habit trackers with their daily entries, a log of family actions (who changed what), plan status and deletion requests. The purpose is to provide the family features you use (Article 6(1)(b) GDPR).

When you enter information about other people who are not parties to the contract (e.g. children, guests), our basis is Article 6(1)(f) GDPR: our and your legitimate interest in the family coordination you request, with restricted access. Please enter only what is necessary and inform those people about this policy. We give particular weight to children's interests (section 7).

External calendar sharing

A family administrator can share a family calendar with someone outside the family by entering that person's e-mail address. We store the address with the calendar and the time. The administrator's device sends it to Google, which creates the share in Google Calendar and may e-mail the person. The legal basis is Article 6(1)(f) GDPR (the family's legitimate interest in sharing). The address is deleted when the share or the calendar is removed. The person concerned can object; contact us or the administrator.

Connecting external calendars

You can show additional calendars in Farenda:

  • Public Google calendars and calendars in your Google CalendarList (e.g. holidays), by their ID or address. When you subscribe, Farenda adds the calendar to your Google CalendarList through the Google Calendar API; the recipient is Google. Farenda tells you this and offers to undo the subscription at Google when you remove the calendar. Calendars newly discovered at Google are no longer shown automatically; Farenda offers them for you to choose.
  • iCal/webcal feeds (ICS addresses), e.g. school holidays. Your device fetches the address directly from the feed's host, about every six hours (using ETag/Last-Modified so unchanged feeds are not downloaded again). The host receives your device's IP address and the request and processes them as an independent controller in its server logs. Our servers never fetch such addresses. The events are stored only locally and read-only on the device.
  • External family calendars. An administrator can add such a calendar to the family and decide for each member whether they see it. The feed is then fetched by the device of each member who was granted access.

A feed address can contain a secret access token and is treated as confidential: it is stored on our server only when an administrator adds it as a family calendar; only the members the administrator grants access can read it (so their devices can fetch the feed). It is never logged and is deleted as soon as the calendar is removed. Feeds you add for yourself stay only on your device. The administrator is responsible for adding only addresses they may use and share with the family.

The legal basis is providing the feature you request (Article 6(1)(b) GDPR); for passing a feed address to granted family members, the family's legitimate interest in a shared calendar (Article 6(1)(f) GDPR).

Optional device features

  • Contacts (optional). If you link a birthday to a phone contact, the operating system opens a contact picker. Farenda reads only the contact you select: identifier, given and family name and birthday. Name and birthday are written as an event into your chosen Google calendar when you save; the identifier and link stay on your device. Your address book is not uploaded. The basis is your consent, Article 6(1)(a) GDPR, which you can withdraw in device settings at any time.
  • Camera. Farenda uses the camera to scan an invitation QR code; images are processed only on the device.
  • Reminders and widgets. Reminders are scheduled locally on the device; widgets read a local copy of your events. Farenda uses no server push notifications.
  • Export. ICS and CSV exports create files you control.
  • Update notice (Android test builds). Directly installed Android test builds request https://farenda.app/app-releases.json to point out new versions. Only the usual server logs arise.

Optional iOS widget weather

On iOS 16 or later Farenda can show Apple WeatherKit weather in the widget. During setup Farenda asks whether you want to share your approximate location for this; the operating system then asks for permission itself ("While Using the App", no background location). If you decline, you can choose a city instead (the search text goes to Apple's geocoding service) or go without weather. Coordinates are rounded to two decimal places (about 1 km) before any use. The sole purpose is the weather forecast in the widget: the rounded coordinates are sent by the app and by the widget extension only directly to Apple (WeatherKit), automatically at most about every 30 minutes, plus on manual refresh (at most once a minute); our server never receives them, they are not linked to your account or your events and are used for nothing else. Storage: place and forecast stay only on your device and are renewed when they expire; turning weather off, revoking location permission or signing out deletes them. The legal basis is your consent (Article 6(1)(a) GDPR; for access to the device location § 25(1) TDDDG), which you give by allowing access and can withdraw at any time in iOS Settings or in Farenda; the rest of the app works without it. Apple processes the request as an independent controller; according to Apple's Weather & Privacy the location used for forecasts is not associated with your identity. The Android beta has no weather feature.

Personal tester pages (Android test programme)

If you take part in the Android test programme, we send you a personal, non-public link (https://farenda.app/dl/…). The controller is the one named in section 1. Through the tester page we process:

  • Participant record: the name or label you gave us, your e-mail address if you want, an internal note (for example your test device), the code of your link and when it was created and switched off.
  • Acceptance of the tester terms: before every download you confirm that you have read this privacy notice and accept the tester terms. For every download we store the time and the version of this privacy policy and of the tester terms you confirmed, linked to that download. This is not consent to processing; the legal bases are below.
  • Downloads: time, downloaded version, the related acceptance and a coarse device label from your browser's user agent (for example "Android 15 · Chrome"). We do not store your IP address for this; it only appears in the server logs (see "Website, web app and server logs"). The download link itself is valid for 15 minutes.
  • Feedback: what you send through the form – type, subject, description, device and Android version, app version and optionally a screenshot (PNG, JPEG or WebP, at most 5 MB) – together with your participant record, plus time and status. The page prefills device and Android version from your browser; you can change or clear them. Your tester page shows only the type, subject, date and status of your own reports; only we see the text and screenshots. Please cover other people's events or names in screenshots if they don't matter for the problem.
  • Link with your Farenda account: so that the app can tell you about new test builds, we link your participant record to your Farenda account (account identifier, how and when it was linked). This happens automatically when your account's e-mail address confirmed by Google matches the e-mail address you gave us for the test programme; or when you tap "Connect the app" on your tester page; or when we set it up at your request. An account can be linked to exactly one participant record. To stop others from guessing links, we keep your account's failed connection attempts for one hour.
  • The app's update check: while the app is open, the Android test build asks our server function, with your sign-in, automatically at most about once an hour and whenever you check for updates yourself, whether a newer test build is available. The answer only contains whether your account is linked, the version and notes of the current test build and the address of your tester page, which the app opens in your browser when you tap "Update"; acceptance and download work as above there. We do not store the individual checks; Supabase processes technical log data. If your account is not linked, the app shows no download link but asks you to contact us for your personal link.

Purpose: running the test programme – providing the test build, reproducing and fixing problems, staying in touch with you about them and showing you their status, and – through the link with your account – pointing you to new test builds in the app. Legal basis: Art. 6(1)(b) GDPR (your participation in the test programme at your request and the tester terms); also for the account link and the app's update check; for counting downloads, evidencing the accepted tester terms and abuse protection (limits on reports, downloads and connection attempts, a form field invisible to people) Art. 6(1)(f) GDPR – our legitimate interest in a secure, traceable test operation.

Processing and recipients: the tester page is served by our server at IONOS; it forwards the page's requests without your IP address to a server function at Supabase, which stores the data in our database in the EU. Screenshots are kept there in a non-public storage area. Both are our processors (see section 6). Only we can read the data, through the protected admin console or an administration tool.

Retention: the participant record, downloads, feedback with screenshots and acceptances are deleted 12 months after your link is switched off. The link with your account ends immediately when your tester link is switched off, when you request deletion of your Farenda account or the account is deleted, and at the latest with the other test data; we remove it any time on request. When the test programme ends, we switch off all links; the 12 months then start for everyone. A daily automatic deletion run removes the data once the period has passed. On request we switch off and delete earlier – write to info@farenda.app. Your rights under section 9 apply here too.

The tester page sets no cookies and embeds no third-party services. It only keeps your language and light/dark choice in your browser's local storage (§ 25(2) no. 2 TDDDG).

Crash reports (Sentry)

If a build ships with crash reporting, the app sends crash and error reports to Sentry. Before sending, the app removes e-mail addresses, access tokens, event titles, descriptions, comment texts and member identifiers; no user profile is attached and screenshots and performance tracing are off. What remains: error type and cleaned message, stack trace, cleaned breadcrumbs, device model, operating system and version, app version and environment; Sentry technically receives the IP address. The web app sends only a failure code, the app version and, where relevant, a latency. The purpose is fixing errors; the basis is Article 6(1)(f) GDPR (legitimate interest in a working service).

Website, web app and server logs

When you open farenda.app, the web app or the admin console, our server processes technically necessary data (IP address, time, path, browser identifier, errors) for delivery, security and diagnosis under Article 6(1)(f) GDPR. Logs are rotated daily and 14 rotated files are kept (about 14 days plus the current file). Keep invitation and confirmation links private, as their address can appear in logs.

The information pages use no analytics or advertising cookies and embed no tracking services; fonts and images are served from our server. The website stores only your light/dark choice in your browser's local storage. The web app sets one strictly necessary cookie (farenda_google, HttpOnly) for the Google Calendar connection and keeps settings in the browser's local storage (§ 25(2) no. 2 TDDDG). The Android test request form only creates an e-mail draft in your browser; we receive something only when you send the e-mail yourself.

Contact by e-mail

If you write to us, we process your address and message to reply (Article 6(1)(b) or (f) GDPR) and privacy requests to meet legal obligations (Article 6(1)(c) GDPR). The mailbox is provided by IONOS.

We make no automated decisions and do no profiling within the meaning of Article 22 GDPR. We do not sell data and show no advertising.

3. Access to Google user data

Farenda requests Google sign-in data (OpenID, e-mail, profile) and Google Calendar permissions. The apps and the web app request the same four Calendar permissions: access to events (calendar.events), the calendar list (calendar.calendarlist), calendars (calendar.calendars) and sharing (calendar.acls). They let you choose calendars, read, create, change and delete events, create calendars and share a family calendar at your request. We use this access only for those features.

Google stores the actual event contents (title, description, location, time, recurrence, reminders). Farenda adds its own fields to events (extendedProperties.private, keys imc_*), e.g. assignment, audience and birthday details. The apps connect directly to Google and keep a local copy with pending changes for offline use. Our database stores calendar identifiers and family metadata, not event contents.

How we protect Google credentials and calendar data is described in section 4. Google is an independent controller for your Google account (Google Privacy Policy).

Farenda's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not sell Google user data, use it for advertising, use it for creditworthiness decisions or train generalised AI models on it. Humans read Google data only with your affirmative agreement for a specific support case, where needed for security or legal obligations, or as that policy otherwise permits.

You can revoke access under Google Account → Connections.

4. How we protect your data

We protect Google user data and the other data described in this policy, in particular sensitive data such as Google sign-in and Calendar credentials, with the following technical and organisational measures:

  • Encryption in transit. The apps and the web app communicate with Google, with our database provider Supabase and with our servers only over encrypted HTTPS (TLS) connections. The website farenda.app redirects unencrypted requests to HTTPS.
  • Encryption at rest at our hosting provider. Our hosting provider Supabase (processor, see section 6) stores the database in the EU (AWS region eu-north-1, Stockholm, Sweden) and encrypts the database and its backups at rest (AES-256); the keys are separate for each project and protected by FIPS 140-2 compliant hardware security modules. Supabase protects data in transit with TLS and holds SOC 2 Type 2 and ISO 27001 certifications.
  • Calendar requests go directly to Google. The iOS and Android apps call the Google Calendar API directly from your device; event contents are not routed through or stored on our servers.
  • Google credentials in the iOS and Android apps. Google sign-in and the Calendar authorisation are handled by Google's own sign-in components (Google Sign-In on iOS, Google Play services on Android). Farenda does not write Google access or refresh tokens to its database, to files or to preference files on the device. Your Farenda sign-in session is stored in the iOS Keychain (bound to this device, never transferred to another device) or in Android storage encrypted with a key from the Android Keystore.
  • Google credentials in the web app. The web app keeps the Google refresh token and access token only on the server side, encrypted with AES-256-GCM. The key is held on our web server, separate from the database. The encrypted record is bound to your Farenda session and your Google account and is stored in a table that only our web server can read with its server key; signed-in users and the public database interface have no access to it. Your browser receives only a short-lived access token, kept in memory, and an HttpOnly cookie (Secure on HTTPS) with a random identifier; only a hash of that identifier is stored. The record expires after at most 180 days and is deleted when you disconnect Google Calendar, sign out or when your Farenda session ends. Signing out of the web app removes this record from our server but does not revoke Farenda's access at Google, because the same Google authorisation is also used by the Farenda apps on your other devices; it is revoked when you delete your account (section 8), or you can revoke it yourself under Google Account → Connections.
  • Local copy on your device. The apps keep the offline copy of your events in a separate database for each Farenda account inside the app's private storage, which other apps cannot read. On iOS the database is protected by iOS file encryption (Data Protection) and excluded from backups; on Android, backups and device-to-device transfer of app data are disabled. The local database is deleted when you delete your account or reset the app, and when you uninstall the app. The web app keeps events only in the memory of the browser tab, not in browser storage.
  • Access control in our database. Row Level Security is enabled on every table of the database interface the apps use, so each user can read only the data of their own account and family according to their role. Changes to family data go through server functions that check permissions; internal tables (e.g. web Calendar credentials, external share addresses, purchase records) are not reachable through that interface at all.
  • Least-privilege operator access. Server keys that bypass these rules are used only on our servers and are never shipped in the apps. Our admin console is available only to individually authorised operators with two-factor authentication (TOTP), and every operator action is recorded in an audit log. Because we do not store event contents, the admin console cannot show them.
  • Logs and crash reports. Crash reports are cleaned before sending as described in section 2 (no e-mail addresses, access tokens, event titles, descriptions or comment texts). Server logs are kept for about 14 days.
  • Data minimisation, retention and deletion. We request only the Google permissions the features need and store only calendar identifiers and family metadata on our servers. Retention and deletion are described in section 8. You can revoke Farenda's access to your Google account at any time under Google Account → Connections.

5. Purchases through the App Store and Google Play

During the test phase (beta) Farenda offers no paid plans and no in-app purchases (see the Terms of Service); the processing below applies only once paid plans are introduced.

You buy paid plans in the App Store (seller: Apple Distribution International Ltd., Ireland) or on Google Play (seller: Google Commerce Limited, Ireland). Apple and Google process payment and order data as independent controllers under their own privacy policies; we receive no payment details.

We use RevenueCat (RevenueCat, Inc., USA) as a processor to manage purchases. The app identifies itself to RevenueCat with your Farenda account identifier (no advertising ID, name or e-mail); RevenueCat receives receipts and transaction data from the store and reports purchase events to our server. From these we store: store, test or production environment, original transaction identifier, the purchaser's account identifier, family, product and plan, kind, status, renewal, purchase and expiry time, and an event log. We discard price, currency, country and other attributes. The purpose is unlocking the paid plan for the family (Article 6(1)(b) GDPR); keeping the purchase record after an account deletion is based on Article 6(1)(c) and (f) GDPR (proof of purchase, handling renewals and refunds). Transfers to the USA are based on the EU Standard Contractual Clauses.

6. Recipients, processors and international transfers

Family members see family data according to their role. Anyone with access to a calendar through Google also sees it outside Farenda.

RecipientRoleDataLocation / transfer basis
Supabase (contracting party under the DPA: Supabase Pte. Ltd., Singapore; group parent Supabase Inc., USA) – database, sign-in, server functionsprocessoraccount and family data, purchase records, test programme datastored in the EU: AWS region eu-north-1 (Stockholm, Sweden). Access from outside the EU (support, operations, sub-processors incl. in the USA) based on the EU Standard Contractual Clauses (Decision 2021/914) in the DPA
Google Ireland Ltd. / Google LLC (sign-in, Google Calendar)independent controllersign-in, events, shares, entered share addressesadequacy decision (EU-US Data Privacy Framework) where Google LLC is certified
Hosts of iCal/webcal feeds you or your administrator addindependent controllerdevice IP address and fetch request (directly from the device)depends on the host; fetched at your request
RevenueCat, Inc. (purchase management)processoraccount identifier, receipts, transactionsUSA; EU Standard Contractual Clauses
Apple Distribution International Ltd. / Google Commerce Limited (stores)independent controllerspurchase, payment, withdrawal, refundunder their privacy policies
Apple (WeatherKit, geocoding, TestFlight)independent controllerrounded coordinates or search text; beta participationunder Apple's privacy policy
Functional Software, Inc. (Sentry)processorcleaned crash reports, IP addressSentry's EU data region; EU-US Data Privacy Framework, Standard Contractual Clauses as fallback
IONOS SE, Elgendorfer Str. 57, 56410 Montabaur (server for website, web app and admin console)processorserver logs, web sessions, delivery of tester pages and test buildsGermany
IONOS SE (e-mail)processore-mails, account deletion warningsGermany

Ask info@farenda.app for information on the safeguards and a copy of the Standard Contractual Clauses. We also disclose data only where required by law or necessary to protect the service against abuse.

7. Children

Families can enter names, birthdays, events, tasks and trackers of children, including children without an account of their own (person profiles). Parents or guardians manage these profiles in the family. Children under 16 should not use their own account without parental agreement; where processing is based on consent (e.g. contacts access), it must be given or authorised by the holder of parental responsibility for children under 16 (Article 8 GDPR). Google's age rules also apply. Please do not enter unnecessary sensitive information (e.g. about health) in events, tasks or lists; Farenda does not analyse such content.

8. Retention, account deletion and cancellation

We keep account data while you use Farenda. An in-app deletion request starts a 30-day period and signs you out locally. Until it ends you can sign in again and cancel the deletion.

Before automatic deletion the service sends two warning e-mails (about seven days and 24 hours before) in the last saved app language, each with a link to an explicit cancellation confirmation; opening a link alone does not cancel. Deletion proceeds only after both warnings were delivered and at least 24 hours have passed since the last one. Current operational status: the automatic mail workflow remains disabled until outgoing mail is configured and verified. Until then, deletion requests remain pending and can be cancelled; write to info@farenda.app to have deletion completed immediately. This operational delay does not restrict your GDPR rights.

When you request deletion of your account, Farenda also revokes its access to your Google account at Google: the iOS or Android app on which you request deletion revokes its Google authorisation right away, and our web server revokes any Google authorisation of the web app that it holds for your account, at the latest when your account is deleted. If revocation fails (for example without a network connection), deletion still proceeds; you can revoke access yourself at any time under Google Account → Connections.

Permanent deletion removes your Farenda account, sessions, profile, memberships, your comments, deletion records and associated personal metadata. A family with no remaining members is deleted. Shared entries still needed by the remaining family members may remain without reference to you. Your Google account, Google calendars and phone contacts are not deleted.

Other periods:

  • Family log: as long as the family exists; deleted with the family.
  • Purchase records: kept after an account deletion with the (then no longer attributable) account identifier so that renewals, refunds and a family's Lifetime plan are handled correctly; deleted once no longer needed for that and for statutory evidence obligations.
  • Web sessions and the web app's Google connection: until expiry, sign-out or end of the session.
  • Feed addresses of external family calendars: until the calendar is removed; feed events stay only on the device.
  • Test programme (personal tester pages): 12 months after the link is switched off, deleted automatically (see Test programme).
  • Server logs: about 14 days.
  • Crash reports: Sentry's retention period for our project.
  • Backups of the database provider expire under its rotation; they are used only for recovery and security, and a restore reapplies completed deletions.
  • E-mail correspondence: as long as needed to handle and evidence a request.

9. Your rights

Subject to the GDPR you have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18) and data portability (Art. 20). You can object at any time, on grounds relating to your particular situation, to processing based on Article 6(1)(f) GDPR (Art. 21). You can withdraw consent at any time with effect for the future; this does not affect the lawfulness of earlier processing.

Write to info@farenda.app. We respond without undue delay, normally within one month, and may ask for proportionate identity verification.

You can lodge a complaint with a data protection supervisory authority, in particular in the member state of your habitual residence, place of work or place of the alleged infringement (Art. 77 GDPR). The supervisory authority competent for us is the State Commissioner for Data Protection and Freedom of Information Baden-Württemberg.

10. Changes

We update this policy when features or processing change. The date and version above identify the current version. We announce material changes in the app.

Legal Notice (Impressum) · Terms of Service

FarendaPrivacy PolicyTerms of ServiceLegal Notice (Impressum)info@farenda.app
PrivacyImprintTermsContact