Effective date: November 2026 · Version 1.0
This privacy notice explains how Tunndu handles personal data when you use our mobile application, visit our website, or contact us about the service. It sets out what personal data we process, why we process it, who receives it, how long we keep it, and the rights you have in relation to your information.
Tunndu is a legacy-planning app. It helps you record references to your accounts, assets, insurance policies and other arrangements, and make that recorded profile available to the trusted contacts you choose. We do not store bank passwords, PINs, security codes, or full financial account numbers.
Please read this notice alongside our Terms and Conditions. If anything in this notice is unclear, or if you have questions about your personal data, contact us at support@tunndu.com.
Tunndu is a mobile application for recording and organising personal information and making your recorded legacy profile available to designated trusted contacts.
The controller responsible for the personal data processing described in this notice is:
This notice covers:
This notice explains what personal data we process, why we process it, who receives it, how long we keep it and your rights.
You can contact us about privacy matters at support@tunndu.com.
The information we process depends on the features you use and the information you choose to provide. Some technical information is processed automatically to operate, protect and diagnose the service.
We process information needed to create and manage your account, including:
You sign in using your email address and password. Authentication is provided through Supabase Auth. Your password is stored as a hash rather than in readable form.
We process the profile and contact information you provide, including:
Your email address is also used for account authentication and account-related communications, as described elsewhere in this notice.
You may record references to your accounts, assets and arrangements, including:
Our structured account-reference fields accept only the last four digits of an account, policy or reference number.
We do not ask you to provide bank login passwords, PINs or security codes. Please do not enter these in other free-text fields.
Tunndu does not provide a general notes feature or allow users to upload files through the App.
Please provide information about other people only where you are entitled to do so, and limit it to what is necessary for the feature you use.
If you designate a trusted or legacy contact, we process the information you provide about them, including:
We also process the records needed to administer the sharing feature, including your confirmation that the contact has consented and the timestamp of that confirmation.
The confirmation is provided by you. It is not a record of consent obtained directly from the contact by Tunndu.
Tunndu does not provide per-category or per-contact content selection. Each authorised contact who receives access can view the information included in your recorded legacy profile, subject to the sharing arrangements described in Section 4.
Purchases are processed through the Apple App Store or Google Play, depending on your device and the store through which you purchase your subscription. Tunndu does not receive or store your full payment-card details.
We use RevenueCat to validate purchases, manage subscriptions and determine access to paid features.
We provide RevenueCat with the unique internal user ID assigned to your Tunndu account. This allows RevenueCat to associate purchases and subscription entitlements with your account. We also receive subscription information from RevenueCat and associate it with the same user ID in our database.
In Tunndu's own subscription records, we currently store your internal user ID and subscription status. RevenueCat processes additional purchase and technical information as described below; not all of that information is copied into Tunndu's database.
In connection with these services, RevenueCat processes information including:
Tunndu uses the relevant subscription information to recognise purchases, restore paid access and maintain your subscription entitlements.
We process technical information to operate, protect and diagnose Tunndu.
Error reporting and performance monitoring
Diagnostic information includes:
We use Sentry for error reporting and performance monitoring. Sentry receives the relevant diagnostic and technical information described above, including reports of errors encountered during email verification and password reset.
We do not add your name, email address or Tunndu account ID as user-identification fields in Sentry reports. Instead, the SDK uses a separate installation identifier that is not your Tunndu account ID. Error messages and request URLs included in diagnostic reports may nevertheless contain personal information.
Performance tracing is configured with a 20% transaction sampling rate. This is not a statement that only 20% of error reports are collected.
We do not enable screenshot capture, view-hierarchy capture or session replay, and we do not configure Sentry to send file attachments.
We use this information to identify and fix technical problems and maintain the reliability and performance of the service. We do not use it for advertising or marketing.
Security and inactivity information
We process information to protect sharing-code redemption and operate the inactivity check-in feature.
Sharing-code security
We record sharing-code redemption attempts to prevent repeated guessing of codes and investigate misuse. These records include an associated user identifier, the code entered, whether the attempt succeeded and the time of the attempt.
We use these records to enforce a limit of five attempts within ten minutes. Records are retained for 90 days, after which they are deleted through a scheduled daily deletion process.
Inactivity reminders and contact alerts
We record the account holder's last activity time, the current reminder stage, and when the inactivity record was created and updated. Activity information is updated when the account holder opens the App or interacts with a reminder.
We send check-in reminders to the account holder after 30 and 37 days of inactivity. After 44 days of inactivity, we send an alert to designated trusted contacts so they can check on the account holder.
Inactivity alert records include identifiers associated with the account holder and recipient, the account holder's display name, the alert message, when the alert was created, and whether it has been read or dismissed. These alert records are retained for 90 days, after which they are deleted through a scheduled daily deletion process.
The inactivity feature does not delete information, suspend accounts or grant access to legacy content. An inactivity alert does not, by itself, give a recipient permission to view the account holder's legacy profile.
Authentication and platform logs
Supabase separately maintains authentication and technical platform logs. These are subject to the retention arrangements described in Section 9.
Notifications
Where push notifications are enabled, we process device notification tokens and notification content to deliver notifications to your device.
We store notification tokens together with the associated Tunndu user identifier and device platform. We use the Expo Push Service and the relevant platform delivery service (Apple Push Notification service for iOS or Firebase Cloud Messaging for Android) to deliver push notifications.
We also store your notification preferences, as described in Section 2.10.
Biometric sign-in
If you enable biometric sign-in, your device performs the biometric check. Tunndu receives the result of that check, not your fingerprint or facial template. We do not collect or store a copy of your biometric information.
To support this feature, we store the following information in your device's secure storage:
The stored token is kept up to date during normal sign-in and session refresh. When you use biometric sign-in, the App retrieves the token only after the biometric check succeeds and uses it to restore your session.
Your biometric information remains on your device. Session authentication information is used to communicate with our authentication provider, Supabase, as needed to authenticate you and maintain your session.
If you disable biometric sign-in, we remove the locally stored information used specifically for that feature.
When you join our waitlist, submit a website contact form or contact support, we process the information you provide, including:
For waitlist signups, we also store the signup source and timestamp.
If you report a problem through the App, we also process:
Contact-form processing
We use Web3Forms to deliver submissions made through our website contact form. Web3Forms may also process submission metadata, such as your IP address, the submission timestamp and the page from which you submitted the form.
Our website forms do not accept file attachments. If you email us directly, we process any attachments you choose to include as part of your message.
Website hosting
Our website is hosted on Cloudflare. When you visit our website, Cloudflare processes your IP address and other technical request information, such as the pages requested and request timestamps, to deliver and operate the website.
Website fonts
Our website loads fonts from Google's servers. When your browser requests these fonts, Google receives your IP address, the requested resource URL and HTTP request headers, which may include browser and operating-system information and the referring page.
We keep records of your acceptance of our Terms and Conditions, including the version and the date accepted. Where we request your consent to process personal data, we also keep a record of that consent.
We store some preferences you set in the App on our servers, specifically your notification preferences, including whether you want push notifications, security alerts and account updates.
Your biometric sign-in preference is stored locally on your device and is not sent to Tunndu's servers. Other device-level settings, such as your theme, also stay on your device.
When you contact us to exercise a data-protection right (for example, to request access to, correction of or deletion of your personal data), we process the information you provide to handle your request through our support process and respond as required by applicable law.
We process personal data for the purposes below.
| Purpose | Personal data involved | Legal basis |
|---|---|---|
| Creating accounts and providing requested app features | Account information, profile information and relevant user-provided content | Performance of our contract with you, where processing is necessary to provide the requested service. |
| Managing subscriptions and paid access | Account identifiers and subscription information | Performance of our contract with you. |
| Protecting accounts, investigating abuse and maintaining security | Authentication information and relevant activity and security records, including sharing-code attempt logs | Our legitimate interests under Article 6(1)(f) GDPR in protecting accounts and our services, preventing unauthorised access and investigating abuse. |
| Diagnosing errors and maintaining reliability | Diagnostic, performance and device information, including an installation identifier. We do not add names, email addresses or Tunndu account IDs as user-identification fields, but error messages and request URLs may contain personal information. | Our legitimate interests under Article 6(1)(f) GDPR in identifying and fixing technical problems and maintaining the reliability and performance of the service. You may object on grounds relating to your particular situation. |
| Managing trusted-contact designations and access | Contact information, permissions, sharing-code and access records, and the account holder's confirmation that the contact has consented, including the confirmation timestamp | For account holders: performance of our contract where necessary to provide the requested sharing feature. For contacts: our legitimate interests under Article 6(1)(f) GDPR in enabling account holders to designate trusted recipients of their legacy profile. Account holders must obtain the contact's consent before adding them; the App records the account holder's confirmation, not consent obtained directly from the contact. |
| Providing service notifications, inactivity check-in reminders and alerts to designated trusted contacts | Notification tokens, device platform, notification preferences, account-holder and recipient identifiers, relevant activity information, account-holder display name, notification and alert content, timestamps, and read/dismissed status | Performance of a contract (Article 6(1)(b) GDPR): processing the account holder's information where necessary to deliver service notifications and the inactivity check-in and contact-alert features they request. Legitimate interests (Article 6(1)(f) GDPR): processing designated contacts' information where necessary to deliver those alerts, in the interests of enabling account holders to notify their chosen contacts and enabling those contacts to check on them. |
| Responding to support enquiries | Contact information, message contents and any attachments provided; for in-app problem reports, the selected problem type, account email and relevant app and device information | Performance of our contract with you where necessary to provide the requested service; otherwise, our legitimate interests under Article 6(1)(f) GDPR in responding to enquiries and resolving problems. |
| Administering a waitlist and sending launch notifications | Email address, signup source and signup timestamp | Your consent, given when you submit your email address to join the waitlist and receive the launch notifications described at signup. You may withdraw your consent at any time. |
| Delivering, operating and securing the website | Technical request information, including IP addresses, requested pages and request timestamps | Legitimate interests (Article 6(1)(f) GDPR): our interests in making the website available to visitors, maintaining its reliable operation, identifying technical faults and protecting it against misuse and security threats. |
| Meeting applicable legal obligations | Relevant account, purchase or request records | Compliance with the specific legal obligations that apply to us. |
| Establishing, exercising or defending legal claims | Relevant account, purchase, support and other records necessary for the claim | Our legitimate interests under Article 6(1)(f) GDPR in establishing, exercising or defending legal claims and protecting our legal rights. |
Where we rely on legitimate interests, these include:
We assess whether the processing is necessary and balance these interests against your rights and freedoms.
You may object to processing based on legitimate interests on grounds relating to your particular situation by contacting us at support@tunndu.com.
Where we rely on consent, we explain what you are consenting to and obtain your consent separately from acceptance of our Terms and Conditions.
You may withdraw your consent at any time using the withdrawal method provided for that purpose or by contacting us at support@tunndu.com. For example, you may contact us to withdraw your consent to receive waitlist launch notifications.
Withdrawal does not affect the lawfulness of processing carried out before withdrawal.
You can manage your notification preferences and biometric sign-in setting in the App, and you can remove trusted contacts. These controls are distinct from withdrawing consent where consent is our legal basis.
You may withdraw your consent to receive waitlist and launch communications at any time by emailing support@tunndu.com. We will act on your request without undue delay and stop sending these communications. Withdrawing consent does not affect the lawfulness of processing carried out before withdrawal.
If you no longer wish to use the service, you can delete your account from the App's Profile screen.
We delete personal data associated with your account in accordance with the retention and deletion practices described in this notice, except where retention is necessary to comply with legal obligations or to establish, exercise or defend legal claims.
Certain information is necessary to create an account and provide the features you request. If you do not provide it, we cannot create your account or provide the relevant feature.
To create an account, we require:
You must also verify your email address using the link we send you before you can sign in.
You choose whether to provide the following information:
Not providing optional information does not prevent you from using the core service, but it may limit the information available or the features that depend on it.
You do not need a subscription to use the core app to record and manage your references.
Sharing your legacy profile with trusted contacts is a Pro feature and requires a subscription, subject to the grace-period arrangements described in Section 4.
Tunndu allows you to authorise designated contacts to access your recorded legacy profile.
Sharing is not configurable by category. An authorised contact can view the records you have saved in your shared legacy profile, including accounts, insurance policies, assets and your contact details. Information you have not recorded is not included. Access is authorised separately for each contact. Before creating a sharing code, you must confirm that the contact has agreed to be designated as a recipient of your shared legacy profile.
To give a contact access, you generate a six-digit sharing code after confirming their consent. The contact enters the code in the App to access your profile.
Nothing is released automatically. Death, inactivity or another event does not trigger access.
Our inactivity reminders encourage your contacts to reach out to you; they do not grant access.
Code redemption is rate-limited, and you cannot redeem your own sharing code.
Sharing is a Pro feature. Recipient access remains available while your subscription is active and for a 30-day grace period after it ends.
After the grace period, recipient access is paused until you renew your subscription. Your recorded information is not deleted merely because this grace period ends, and access resumes when you renew.
You can change or revoke future access at any time from the App's Share section by removing a contact or switching off their consent setting.
This invalidates their sharing code and stops them from viewing your profile in the App.
Once an authorised recipient has viewed your information, deleting it from Tunndu or revoking access does not remove copies they have independently retained, such as screenshots.
We disclose personal data where necessary to provide our services, carry out your sharing instructions, comply with applicable legal obligations or protect the security of the service.
Depending on the feature you use and the circumstances, recipients include:
The personal data disclosed depends on the service or purpose. Not every recipient receives all of your information.
Your authorised contacts can access the information included in your recorded legacy profile, subject to the access, subscription and revocation arrangements described in Section 4.
Tunndu does not provide per-category or per-contact content selection.
| Provider or platform | Purpose and relevant information |
|---|---|
| Supabase | Database hosting, authentication and waitlist storage. Processes relevant account information and app content, including account records, server-stored preferences, consent and confirmation records, trusted-contact information, and waitlist email addresses with signup source and timestamp. Supabase Auth handles email-verification and password-reset workflows. |
| RevenueCat | Subscription and entitlement management. Processes app-user identifiers and relevant purchase, subscription and technical information, as described in Section 2.6. |
| Apple | App distribution and in-app purchase processing on iOS through the App Store and StoreKit. Apple processes information associated with your Apple Account and relevant purchase and subscription transactions. |
| Sentry | Error diagnostics and performance monitoring. Processes the diagnostic and technical information described in Section 2.7, including device information, error reports, stack traces, timestamps, diagnostic breadcrumbs, sampled performance information and an SDK-generated installation identifier. |
| Expo Push Service, Apple Push Notification service (APNs) and Firebase Cloud Messaging (FCM) | Push notification delivery, where enabled. Process push tokens and notification payloads, including inactivity reminders. When the Expo Push Service is used, it forwards notifications to APNs for iOS or FCM for Android. |
| Web3Forms | Website contact-form delivery. Processes submitted form information, including name, email address, subject and message, together with technical metadata such as IP address, timestamp and referring-page information. Our website forms do not accept file attachments. |
| Cloudflare Pages | Website hosting. Processes technical request information, such as your IP address, the pages requested and request timestamps, to deliver and operate the website. |
| Google Fonts | Website font delivery. Our website loads fonts from Google's servers. When your browser requests these fonts, Google receives your IP address, the requested resource URL and HTTP request headers, which may include browser and operating-system information and the referring page. Google states that it uses this information to deliver fonts and for security purposes, and does not use information collected through Google Fonts to create end-user profiles or for targeted advertising. |
| Google Play | Android app distribution and in-app purchase processing. Google processes information associated with your Google Account and relevant purchase and subscription transactions for purchases made through Google Play. |
The App does not use cookies or third-party tracking technologies for advertising purposes.
We use Sentry for the diagnostic purposes described in Section 2.7, not for advertising or marketing.
This statement concerns the App. Website request processing and Google-hosted font delivery are described separately in Sections 2.9 and 5.2.
We may disclose relevant personal data where necessary to comply with applicable legal obligations or legally binding requests, establish, exercise or defend legal claims, or investigate and prevent misuse of our service.
We do not sell your personal data.
If a Tunndu user designates you as a trusted or legacy contact, we receive your information from that user rather than directly from you.
This may include your name, your relationship to the user, and the contact details they choose to record, such as your phone number, country and address.
We use this information to:
We do not automatically send you an invitation or notification when a user adds you. The user shares the access code with you themselves, using their device's sharing features.
We rely on our legitimate interests under Article 6(1)(f) GDPR in enabling users to designate trusted recipients of their legacy profiles and administering those access arrangements.
Our Terms require users to obtain a contact's consent before adding their information. The App records the user's confirmation that they have done so; it does not record consent obtained directly from you.
Further information about the categories of personal data and legal bases is provided in Sections 2 and 3. Retention periods and deletion practices are described in Section 9.
This notice is available during account creation and sharing-code redemption.
You can contact us at support@tunndu.com to ask about your information or exercise applicable data-protection rights, including if you do not have a Tunndu account.
You may object to processing based on legitimate interests on grounds relating to your particular situation.
We and our providers process personal data in the locations described below. A primary hosting location does not necessarily identify every location from which personal data may be accessed or otherwise processed.
| Provider or platform | Where personal data is processed |
|---|---|
| Supabase | Frankfurt, Germany, in the AWS eu-central-1 region, for our primary project database and authentication service. This project location does not necessarily cover all supporting services, including email delivery. |
| Sentry | Frankfurt, Germany, for event data in Sentry's EU region, with event-data backups remaining in the EU. Some account and integration metadata may be processed in the United States. |
| RevenueCat | United States, using AWS infrastructure, according to the provider information identified in our review. |
| Web3Forms | United States, using AWS infrastructure. |
| Expo Push Service | United States, using AWS infrastructure. Notifications are forwarded to Apple APNs or Google FCM for delivery. |
| Apple App Store, StoreKit and APNs | Processing may take place in multiple countries, depending on the service. Apple provides iOS app distribution, purchase processing and push notification delivery. |
| Google Play and Firebase Cloud Messaging (FCM) | Processing may take place in multiple countries, depending on the service. Google provides Android app distribution, purchase processing and push notification delivery. |
| Cloudflare Pages | Website content is delivered through Cloudflare's global network. Technical request information is processed as necessary to deliver and operate the website. |
| Google Fonts | While our website loads fonts from Google, associated request information is processed through Google's font-delivery infrastructure. This connection is separate from Google Play and FCM. |
Hosting data in the EU does not necessarily mean that all supporting processing, technical support or access takes place exclusively within the EU. Information about international-transfer safeguards is provided in Section 7.2.
Some of our providers process personal data outside the European Economic Area (EEA), including in the United States.
Depending on the provider and the transfer, we rely on the following safeguards:
Where UK data-protection law applies, we use the additional or alternative safeguards required under that law, such as the UK International Data Transfer Agreement (IDTA) or the UK Addendum to the EU SCCs.
Where Swiss data-protection law applies, we use the safeguards required under that law, such as the EU SCCs with the necessary Swiss adaptations.
Hosting data in the EU does not necessarily mean that all supporting processing or access takes place exclusively within the EU.
You can request further information about these arrangements, including a copy of relevant safeguards where applicable, by contacting support@tunndu.com.
We maintain technical and organisational measures appropriate to the risks associated with the personal data we process.
These measures include:
Tunndu does not provide end-to-end encryption. Infrastructure-level encryption does not prevent authorised processing of information by Tunndu and its service providers.
No method of electronic transmission or storage is completely secure. We review our safeguards and respond to security incidents as appropriate.
We retain personal data for as long as necessary for the purposes described in this notice, taking account of applicable legal requirements.
Retention periods differ according to the category of information and whether it is held in our live application database, backups or a provider's systems. Where deletion is performed by a scheduled daily cleanup process, records are deleted on the next scheduled run after the applicable retention period has elapsed.
| Category | Retention period or criteria |
|---|---|
| Account and profile information | Retained while your account remains open. We do not automatically delete accounts solely because of inactivity. Our inactivity feature sends check-in reminders; it does not delete information or grant access. |
| User-provided content and account references | Retained while your account remains open unless removed earlier. When you remove an item, it is hidden from the App and excluded from recipients' profile retrieval, but remains in our live database as a soft-deleted record. After 30 days, it is permanently deleted from the live database by the scheduled daily cleanup process. Deleted information may remain in existing backups until those backups expire. |
| Information after subscription expiry | Subscription expiry does not itself delete your account or recorded content. Recipient access continues during the 30-day grace period described in Section 4, then pauses until renewal. Your information remains subject to the other retention and deletion rules in this section. |
| Trusted- and legacy-contact information | Retained while the contact remains designated. When you remove a contact, their record is soft-deleted and their access is revoked immediately. After 30 days, the scheduled daily cleanup process permanently deletes the soft-deleted contact record and removes associated orphaned received-profile records and inactivity alerts. Other associated records follow their applicable retention periods. |
| Account data following account deletion | When you delete your account, the App immediately removes your authentication account and associated records covered by its database-deletion process. These include account and profile records, recorded content, contacts, sharing records, inactivity records, push tokens, consent records, in-app problem reports, account-linked sharing-code attempt logs and subscription-status records. This does not immediately remove information held separately in backups, diagnostic systems, purchase platforms or our support mailbox. |
| Database backups | Information deleted from live systems may remain recoverable through our Supabase backups for up to seven days. Individual records cannot be selectively removed from these backups. We do not retain separate database exports outside the Supabase backup system. |
| Sentry diagnostic and performance information | Error events and sampled performance data are retained according to the periods applicable to our Sentry plan and the relevant data categories. Diagnostic event data is stored in Sentry's EU region in Frankfurt, Germany. Performance tracing is configured with a 20% transaction sampling rate. Screenshots, view-hierarchy capture, session replay and file attachments are not enabled. Diagnostic events are not automatically removed by Tunndu's account-deletion process. |
| Sharing-code attempt logs | Retained for 90 days from the attempt timestamp, then permanently deleted by the scheduled daily cleanup process. Account-linked logs are also deleted when the associated account is deleted. |
| Authentication and platform logs | Supabase's authentication and service logs are separate from the application records removed by our account-deletion process. Auth Audit Logs have a one-hour retention window, and API and database logs have a one-day retention window. |
| Subscription and purchase records | Tunndu's account-linked subscription-status records are deleted with your account. Records held separately by RevenueCat, Apple or Google are not removed by Tunndu's database-deletion process and follow the retention arrangements applicable to those services. |
| Waitlist information | We retain your email address, signup source and signup timestamp to administer the waitlist and send the launch notifications described at signup. Submissions are permanently deleted by the scheduled daily cleanup process after 180 days from signup. You can request earlier removal at support@tunndu.com. |
| Website contact-form submissions | Support correspondence, including website contact-form messages delivered to our support mailbox, is retained for two years after the enquiry is closed, unless longer retention is necessary to comply with a legal obligation or establish, exercise or defend legal claims. |
| Support messages and in-app problem reports | In-app problem reports stored in Tunndu's database are deleted when you delete your account. Support emails, including contact-form messages delivered to our support mailbox and any separately retained copies of problem reports, are retained for two years after the enquiry is closed, unless longer retention is necessary to comply with a specific legal obligation or establish, exercise or defend legal claims. |
| Terms-acceptance and consent records | Account-linked records, including the type, version and acceptance timestamp, are retained while your account remains open and deleted with it. We do not retain a separate archive of these records after account deletion. |
| Data-protection request records | Requests and responses are handled through our support mailbox. Request correspondence, responses and outcomes are retained for two years after the request is closed, unless longer retention is necessary to comply with a specific legal obligation or establish, exercise or defend legal claims. Any additional identity-verification material is retained only for as long as necessary to verify identity and handle the request, rather than automatically for the full two-year correspondence period. |
Where particular information must be retained to comply with a legal obligation, or where retention is necessary to establish, exercise or defend legal claims, we retain only the information needed for that purpose.
Deleting your account or revoking sharing access does not remove copies that authorised recipients have independently retained, such as screenshots.
Depending on the applicable law and the circumstances, you may have the right to:
These rights are subject to applicable conditions and exceptions.
To exercise your data-protection rights or ask a question about this privacy notice, contact us at:
Email: support@tunndu.com
Please indicate whether your message concerns a data-protection request or a general support enquiry so that we can handle it appropriately.
You can also delete your account from the App's Profile screen and manage the available preferences and sharing controls in the App. Account deletion is subject to the retention and deletion arrangements described in Section 9.
You do not need a Tunndu account to contact us about your personal data. This includes requests from people designated as trusted or legacy contacts.
Where we have reasonable doubts about your identity, we may request additional information necessary to verify it before providing personal data or acting on a request.
For requests governed by the GDPR, we respond without undue delay and within one month of receiving the request. Where necessary because of the complexity or number of requests, we may extend that period by up to two further months. We will notify you of an extension and explain the reasons within the initial month.
If we do not act on your request, we will explain why and inform you of your options to complain to a supervisory authority and seek a judicial remedy.
You may lodge a complaint with a competent data-protection supervisory authority, including in the EU Member State of your habitual residence, place of work or the alleged infringement.
For our establishment in Baden-Württemberg, the relevant supervisory authority is:
Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg (LfDI BW)
State Commissioner for Data Protection and Freedom of Information Baden-Württemberg
Postal address: Postfach 10 29 32, 70025 Stuttgart, Germany
Email: poststelle@lfdi.bwl.de
Telephone: +49 711 615541-0
Official complaint information and online complaint form: www.baden-wuerttemberg.datenschutz.de/beschwerde
You may contact us first so that we can try to address your concerns, but you are not required to do so before lodging a complaint.
Access to legacy content is directed by the account holder, who authorises sharing, designates trusted contacts and manually shares an access code. Our inactivity feature sends check-in reminders only; it does not automatically delete information, suspend accounts or grant access to legacy content.
We use automated controls to protect sharing-code redemption against repeated unsuccessful attempts and to check subscription status. Recipient access continues during a 30-day grace period after subscription expiry and is then paused if the subscription has not been renewed.
We do not use automated profiling, scoring or risk assessments.
The App stores certain information on your device to support sign-in and your preferences:
Tunndu does not collect or store your fingerprint, facial scan or other biometric templates. Biometric verification is handled by your device's operating system.
We use Sentry to identify errors and monitor the App's technical performance. Screenshots, view-hierarchy capture, session replay and file attachments are not enabled.
We do not use product analytics SDKs, advertising SDKs or advertising identifiers such as Apple's IDFA or Android's advertising ID.
Our website uses Cloudflare Pages for hosting, Supabase for waitlist registration and email verification, and Web3Forms to process contact-form submissions. The Supabase browser client is loaded from jsDelivr on the relevant pages. These services receive the information needed to handle the relevant requests, including technical connection information and any details you submit.
During email verification, Supabase may store authentication information in your browser's local storage.
Our website currently loads fonts from Google Fonts. This sends Google technical request information, including your IP address and browser information. The Google Fonts API does not set or log cookies.
We do not use advertising scripts, product analytics or session replay on the website.
Tunndu is intended for account holders aged 18 or over. Our Terms require account holders to be at least 18, and we do not direct account registration to children.
Adult account holders may designate trusted or legacy contacts who are under 18. When designating a contact, an account holder may provide the contact's name, relationship, country, address and phone number. We do not collect dates of birth for designated contacts.
Designated contacts do not create accounts. They can retrieve shared information only after the account holder authorises sharing and manually provides them with an access code. Designating someone as a contact does not, by itself, grant access.
If you believe someone under 18 has created a Tunndu account, or you have concerns about personal information relating to a child, contact support@tunndu.com so we can investigate and take appropriate action.
We may update this notice to reflect changes in our services, processing practices or legal requirements. We will update the effective date and version shown above.
Where appropriate, we will provide additional notice of material changes through the App or by email to the address associated with your account.
If a change requires your consent, we will request it separately before carrying out the processing that requires it. Updating this notice or your continued use of the App does not, by itself, constitute consent where consent is required.
For questions about this notice, our handling of personal data, or to exercise your data-protection rights, contact:
Emmanuel Echa
Memelstrasse 12
88400 Biberach
Germany
Email: support@tunndu.com
You do not need an active Tunndu account to contact us about your privacy rights.