Privacy

Controller

The controller within the meaning of the General Data Protection Regulation (GDPR) is:
Dr. Stefan Borja Bammesberger (Zen.Here.Now)
Erzbergerstr. 10, 70191 Stuttgart, Germany
Email: [email protected]

This website

Hosting. This website is hosted and delivered by Cloudflare, Inc. (Cloudflare acts as a processor pursuant to Art. 28 GDPR). Cloudflare processes technically necessary connection data (including IP address, date and time of access, page requested) to deliver the website and protect it against abuse. The legal basis is my legitimate interest in secure and functional operation (Art. 6 (1) (f) GDPR).

Cookies and tracking. This website itself does not set any analytics, marketing, or tracking cookies. Fonts, images, and scripts are served exclusively from the site’s own server — there is no connection to Google Fonts or any other external provider.

Beta sign-up. The form behind the "Try it" button runs directly on this site, not with an external provider — you never leave friendlyping.app. On submission, your name, email address and answers are sent to this site’s Cloudflare Worker under this domain, which composes and sends an email to the operator (Cloudflare acting as a processor pursuant to Art. 28 GDPR, as with hosting above). Your details are not stored in a database — the email itself is the only record. The legal basis is Art. 6 (1) (b) GDPR (steps taken at your request to join the beta programme).

Contacting me by email. If you contact me by email, I process your details (email address and message content) solely to handle your request. The legal basis is Art. 6 (1) (f) GDPR (legitimate interest in responding to inquiries), or Art. 6 (1) (b) GDPR where the inquiry relates to entering into a contract.

The Friendly Ping app

Legal basis for optional analytics. Detailed usage analytics and A/B tests are based on your consent (Art. 6 (1) (a) GDPR). You can withdraw it in settings at any time. Withdrawal does not affect the lawfulness of processing before withdrawal.

Optional detailed usage analytics and A/B tests. Before first use, you can allow analytics or continue without analytics. Only after your permission does Supabase Auth create a random installation identifier without a name or email address. I record onboarding steps, visible app areas, actions, active time spent and the test variant actually displayed. This includes which pings from the library were sent, opened, liked or hidden, which sounds, qualities and situations you choose, which settings you change (not the value you set), your stated meditation experience, and steps in the purchase flow. Events include a timestamp, session, onboarding run where applicable, platform, language and app/build version. This data is pseudonymous and links multiple sessions of the same installation; a new installation receives a new identifier. Your own ping texts, free-text acquisition answers, exact reminder times and screen recordings are not sent through this analytics channel. The aggregate daily counters continue separately.

Withdrawal and deletion. You can turn analytics off or request deletion of detailed analytics data in settings at any time. Collection stops immediately and the local event queue is cleared. Offline deletion requests are sent when you reconnect. Detailed events are automatically deleted after 180 days. Completed test reports without installation identifiers may be kept permanently. Technical authentication accounts are removed by the daily cleanup after withdrawal. Reports are restricted to approved administrators and use Supabase.

Private analytics dashboard. The administrator-only area connects directly to Supabase for authentication and reporting. Administrator login uses an email address and password; session tokens are held in the browser session storage until logout or the tab is closed. This area is separate from the public website and does not offer public registration.

Local storage. Your settings (e.g. reminder times, chosen sounds, self-written pings) are stored on your own device. Self-written pings and your reminder times never leave the device. Which sounds and settings you choose is included in the statistics as described in this section.

Anonymous usage statistics. The app counts certain events (e.g. how often a ping was played) in aggregated form to help me improve it. What is counted is THAT and HOW OFTEN something happens. In this aggregate analytics channel, no device, installation, or advertising identifiers are created or transmitted, nor are timestamps, nor the wording of self-written pings. This counting runs through the service provider Supabase. Because no unique identifier of your device is transmitted in this channel, this statistic cannot be traced back to a person.

The question about where you heard of Friendly Ping. On first launch the app asks once how you found Friendly Ping. The question is optional and can be skipped. If you pick one of the offered answers, only that answer is counted. If you type something under “Somewhere else”, that text is counted too — but it is first reduced on your device to lowercase letters and spaces and shortened to 40 characters: email addresses and links are discarded entirely, digits and all other characters removed. Here too, nothing is transmitted that could tie the text to a person. Your answer about how much meditation experience you have (one of three levels) is likewise counted once.

Notifications. Reminders are scheduled and triggered locally on your device, not via a push service with an external, person-identifying component.

Technical connection data. Connections to Supabase and RevenueCat involve technically necessary data such as IP address, request time, platform, and app and operating system version. This data supports service delivery, security and troubleshooting. Transmission is encrypted using HTTPS. I do not use advertising identifiers or location-based analytics.

Error counts. The app counts caught app errors together with the app version. It does not transmit error messages, stack traces or self-written ping texts. With your analytics consent, this count may also be linked to the pseudonymous installation.

Purchases and Premium access

RevenueCat and Supabase. I use RevenueCat, Inc. (USA) and my Supabase backend to verify and manage purchases and Premium entitlements. A random technical purchase identifier is created automatically when the app starts; you do not need to provide a name, email address or password. RevenueCat uses this identifier to associate purchases and existing access rights with the same installation. This check may also take place during a free access period.

Supabase server location. My Supabase backend runs in the Stockholm region (AWS eu-north-1) within the EU. My contract partner is Supabase Pte. Ltd., based in Singapore; for transfers outside the EU, the data processing agreement with Supabase provides EU Standard Contractual Clauses.

Purchase data processed. Purchases and restoration involve product and transaction identifiers, purchase time, price and currency, store, renewal and expiry status, and purchase receipts or technical purchase tokens. My backend receives the store notifications needed for Premium access and, where applicable, manages the start and end of a free trial or gifted access. Credit card and bank details are processed by the relevant app store and are not transmitted to me or RevenueCat.

Purpose and legal basis. This processing is necessary to provide, restore and protect your access, based on Art. 6 (1) (b) GDPR, or on Art. 6 (1) (f) GDPR for secure technical operation. Purchase and entitlement data is also used for business analysis of purchases. The purchase identifier is separate from the optional analytics identifier. Only with your analytics consent may purchase and trial events additionally be associated with your pseudonymous usage history; withdrawing analytics consent does not end your Premium access.

Processing in the USA. RevenueCat processes data as a service provider on my behalf. This may involve processing in the USA. RevenueCat’s data processing addendum provides EU Standard Contractual Clauses for transfers without an adequacy decision. Further information is available in RevenueCat’s privacy notice.

Request data deletion

You can request deletion of detailed analytics data directly in the app settings. For purchase, trial and entitlement data, email me at [email protected] with the subject “Friendly Ping – Data deletion”. To identify the correct records securely, I may ask for the technical purchase identifier or a purchase receipt. Do not send passwords, bank details or full credit card details.

I review and handle requests for data held by me and my service providers. Statutory retention obligations and data needed to settle existing claims may prevent complete deletion. Uninstalling the app alone does not delete server-side data. Deleting data does not cancel a store subscription; subscriptions remain managed in the relevant app store.

Retention period

Hosting connection data is automatically deleted after a short period unless it is needed to investigate a fault. I delete email inquiries once they have been fully handled and no statutory retention obligations apply.

Purchase, trial and entitlement data is retained while needed to verify or restore your access, prevent repeated trials or settle existing claims. When receiving a deletion request, I review which data can be deleted or anonymised and which data must still be retained to comply with legal obligations.

Your rights

You have the right to access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20), and objection (Art. 21) regarding your personal data. Simply contact me at the email address above.

You also have the right to lodge a complaint with a data protection supervisory authority. The competent authority is:
Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg
Königstraße 10a, 70173 Stuttgart, Germany

Changes to this notice

I update this privacy notice whenever the website, the app, or legal requirements change. The most recently published version applies.

Last updated: October 2026