Your privacy, protected.

1. Introduction

This Privacy Policy explains how Ring for a ... ("the App", "we", "our") collects, uses, and protects information when you use our mobile application available on Android and iOS. By using the App, you agree to the practices described in this policy.

Your use of the App is also governed by our Terms of Use / End User License Agreement.

We are committed to protecting your privacy. We collect only the minimum data necessary to provide the App's core functionality and improve the user experience.

2. Information We Collect

2.1 Information You Provide

• Display name - an optional name you set so your partner can identify you when you ring them. This name is transmitted to our backend server solely for the purpose of delivering notifications.

2.2 Information Collected Automatically

• Device identifier - a randomly generated UUID created locally on your device and stored in local app storage. It is used to identify your device on our backend and is never linked to your real identity.
• Firebase Cloud Messaging (FCM) token - a push notification token issued by Google Firebase. It is sent to our backend to enable delivery of bell-ring notifications. The token may be refreshed periodically by the system.
• Ring history - a local log of ring events (type and timestamp) stored exclusively on your device. This data is never uploaded to any server.
• App settings and preferences - stored locally on your device (sound, haptics, dark mode, language, selected preset, etc.). Not transmitted to any server.
• Achievements and gamification data - stored locally on your device only.

2.3 Feedback and Optional Diagnostics

When you submit feedback through the App, we collect the feedback category and the message you choose to provide. This information is transmitted to our backend so we can review your request, investigate issues, and improve the App.

• Contact e-mail - optional. If you choose to provide your e-mail address, we use it only to respond to your feedback or support request. Providing an e-mail address is not required to send feedback.
• Basic feedback metadata - when feedback is sent, we may include basic technical information such as App version, build number, environment, platform (Android/iOS), operating system version, device model, manufacturer, whether the device is physical or an emulator/simulator, locale, and time zone. This helps us understand which App version and device environment the feedback relates to.
• Optional diagnostics - if you enable the "Attach diagnostic data" option, the App may also send additional technical diagnostic data, such as current App screen/route, selected theme, notification permission status, connectivity type, premium/subscription status, number of paired connections, selected bell type, recent sanitized API errors, recent Flutter exceptions and stack traces, push notification status, hashed FCM token, RevenueCat status/error information, short in-memory App logs, selected App settings, and basic performance metrics such as App uptime or recent API duration.
• Custom bell text - the full text of a custom bell is not automatically included in diagnostics. Diagnostics may only indicate that a custom bell text exists and its approximate length, unless you explicitly type that text into your feedback message.
• Screenshots - the App does not currently collect or upload screenshots as part of feedback.
• Data we do not include in feedback or diagnostics - we do not intentionally collect or send raw FCM/APNs tokens, authentication tokens, refresh/session tokens, Authorization headers, cookies, passwords, payment card details, purchase tokens, store receipts, advertising identifiers, IMEI, MAC address, device serial number, precise GPS location, contacts, clipboard content, installed app lists, private message content, notification content, names or identifiers of paired users, full API request/response bodies, full local storage, or raw RevenueCat customer information.

2.4 Data Collected by Third-Party Services

The App integrates the following third-party SDKs, each of which may collect data independently according to their own privacy policies:

• Firebase - Google Firebase (Firebase Cloud Messaging, Firebase Core) may collect device and diagnostics data. Privacy policy: https://firebase.google.com/support/privacy
• RevenueCat - RevenueCat processes in-app purchase and subscription data, including purchase receipts and subscription status. RevenueCat does not receive personally identifiable information from the App. Privacy policy: https://www.revenuecat.com/privacy
• Google AdMob - Google Mobile Ads (AdMob) may collect and process data such as device information, app interaction data, advertising identifiers where available, IP address, approximate location derived from network information, diagnostics, and ad performance data. This data may be used to show, measure, limit, and improve advertisements, including personalised or contextual advertisements depending on your consent choices and applicable law. Ads are shown only to users on the free plan. Privacy policy: https://policies.google.com/privacy
• Google User Messaging Platform (UMP) - where required, the App may use Google's User Messaging Platform to request, store, and communicate your advertising consent choices for Google AdMob and its advertising partners. Consent choices may include whether ads can be personalised, whether cookies or similar identifiers may be used, and whether advertising data may be used for measurement. Learn more about Google's privacy practices: https://policies.google.com/privacy

2.5 Download Page Analytics

When you visit our app download page, we may collect basic, cookie-free analytics to understand interest in the App and improve our marketing. This may include the detected platform (Android, iOS, desktop, or unknown), approximate country derived from network information, date and time of the visit, selected store destination, campaign parameters such as UTM source, medium, campaign or content, and the referring domain where available.

We do not use this download page analytics to identify individual visitors, create user profiles, track users across websites, or link website visits to specific App users. We do not store cookies, advertising identifiers, device IDs, full IP addresses, or full user-agent strings for this purpose.

3. How We Use Your Information

We use the collected information for the following purposes:

• To deliver bell-ring notifications to your paired partner's device.
• To identify your device on our backend and maintain the pairing connection.
• To display your chosen name in notifications received by your partner.
• To process and verify in-app subscription purchases through RevenueCat.
• To display advertisements to free-tier users via Google AdMob.
• To request, store, and respect your advertising consent choices where required by law.
• To measure ad performance, prevent fraud and abuse, frequency-cap advertisements, and maintain the safety and reliability of advertising services.
• To maintain and improve the App's functionality and stability.
• To receive and process feedback, bug reports, and support requests submitted by users.
• To diagnose and reproduce technical issues when you choose to attach optional diagnostic data.

We do not sell or rent your personal information. We do not use pairing data, private ring data, feedback messages, optional diagnostic data, or support e-mails for advertising or profiling. Data is shared with third-party SDKs only to the extent required to provide the services described above.

4. Download Page Analytics

Our website may provide a download page or smart link that helps visitors open the correct store page for their device, such as Google Play for Android devices or the App Store for iOS devices.

For this purpose, we may process basic technical information from the web request to detect the visitor's platform and approximate country. We store only simplified, non-identifying analytics such as platform category, country code, date and time, selected store destination, campaign parameters, and referring domain where available.

We use this information only to understand which channels bring visitors to the download page, estimate interest by platform and country, and improve our app promotion. We do not use this data for advertising profiling, remarketing, cross-site tracking, or identifying individual visitors.

Any IP address or browser information used to determine country or platform is processed only transiently for that request and is not stored in full as part of the download analytics record.

5. Advertising and Consent

The free version of the App may display advertisements provided by Google AdMob. Premium users do not see ads and the App does not load AdMob ad placements for users while Premium is active.

Depending on your location and applicable law, we may ask for your consent before showing personalised ads or before using certain advertising identifiers, cookies, local storage, or similar technologies. In the European Economic Area, the United Kingdom, and Switzerland, the App may use Google's User Messaging Platform (UMP), a consent management solution for Google advertising, to present privacy choices and to communicate your choices to Google and its advertising partners.

If you give consent, AdMob may use data such as advertising identifiers, device information, app usage, approximate location, and ad interaction data to show personalised ads and measure their performance. If you do not give consent, the App may show non-personalised or limited ads where available, or it may not show ads at all. Your choice does not affect access to the App's core free features.

You may be able to manage or change your advertising privacy choices later from the App's settings through the "Privacy options" entry, where available. You can also manage advertising preferences through your device settings and your Google account settings.

Advertising data is processed by Google and its advertising partners according to their own privacy policies and consent frameworks. We do not receive raw advertising identifiers from AdMob for our own use, and we do not combine advertising data with pairing data, feedback messages, optional diagnostic data, or support e-mails.

6. Device Pairing and Backend Data

The App allows you to pair your device with a partner's device. To enable this feature, your device identifier, FCM token, display name, and pairing status are stored on our backend server. This data is used exclusively to route ring notifications between paired devices.

Pairing data is deleted from our servers when you disconnect the pairing within the App. Backend data is stored on servers operated by our hosting provider and is protected by industry-standard security measures.

Custom bell text or preset label - when you ring a paired device, the selected bell label may be transmitted through our backend and Firebase Cloud Messaging to deliver the notification. This data is used only to deliver the notification and is not used for advertising.

7. Data Retention

• Device identifier and FCM token are retained on our servers for as long as your device is actively paired or registered. They are removed when you delete the pairing or uninstall the App and your device is deregistered.
• Display name is retained on our servers alongside the device record and is deleted together with it.
• Local data (ring history, settings, achievements) is retained on your device until you uninstall the App or clear its data.
• Subscription and purchase data is retained by RevenueCat in accordance with their data retention policy.
• Advertising and consent-related data is processed and retained by Google AdMob, Google User Messaging Platform, and their advertising partners according to their own privacy and retention policies. The App may store your consent status locally or through Google UMP so that your advertising choices can be respected.
• Feedback messages are retained for as long as reasonably necessary to review and resolve the request, improve the App, and maintain support records.
• Optional contact e-mail addresses provided with feedback are retained only for the purpose of responding to the feedback or support request and are not used for marketing.
• Optional diagnostic data attached to feedback is retained only as long as reasonably necessary for troubleshooting and App improvement. Diagnostic data is stored separately from advertising data and is not used for advertising or profiling.
• Download page analytics are retained only as long as reasonably necessary to understand app interest, evaluate marketing channels, and improve the download experience. These records do not include full IP addresses, full user-agent strings, cookies, advertising identifiers, or device IDs.

8. Data Security

All communication between the App and our backend is transmitted over HTTPS/TLS. Each device is authenticated using a randomly generated secret key stored locally. We implement reasonable technical and organisational measures to protect the data we hold against unauthorised access, loss, or disclosure. However, no method of transmission over the internet or electronic storage is 100% secure.

Before diagnostic data is sent, the App is designed to sanitize the payload and remove or mask sensitive values such as tokens, authorization headers, cookies, e-mail addresses, phone numbers, pairing codes, and other accidental identifiers where technically feasible.

9. Your Rights

Depending on your location, you may have the following rights regarding your personal data:

• Right of access - you may request a copy of the personal data we hold about your device.
• Right to rectification - you may correct your display name at any time within the App settings.
• Right to erasure - you may request deletion of your device record and associated data by contacting us (see Section 12). Disconnecting all pairings within the App and uninstalling it will remove most data automatically.
• You may also request deletion of feedback records, optional contact e-mail addresses, and diagnostic data associated with your device or support request, where we can identify the relevant record.
• Right to restriction - you may request that we restrict processing of your data.
• Right to data portability - you may request your data in a machine-readable format.
• Right to object - you may object to data processing based on our legitimate interests.
• Advertising choices - where available, you may manage advertising consent choices in the App through "Privacy options" or through your device and Google account advertising settings.

To exercise any of these rights, please contact us using the details in Section 12. We will respond within 30 days.

10. Children's Privacy

The App is not directed to children under the age of 16. We do not knowingly collect personal information from children under 16. If you believe a child under 16 has provided us with personal information, please contact us and we will take steps to delete such data promptly.

11. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. When we do, we will revise the "Last updated" date at the top of this page. If the changes are significant, we will provide a more prominent notice (for example, a notification within the App). We encourage you to review this policy periodically.

Your continued use of the App after changes are posted constitutes your acceptance of the updated Privacy Policy.

12. Contact Us

If you have any questions, requests, or concerns about this Privacy Policy or the handling of your data, please contact us at: