Skip to content

Instantly share code, notes, and snippets.

@mmoreram
Last active April 14, 2026 22:19
Show Gist options
  • Select an option

  • Save mmoreram/a7e7e685c96cfa4ad16c0c32903b2a51 to your computer and use it in GitHub Desktop.

Select an option

Save mmoreram/a7e7e685c96cfa4ad16c0c32903b2a51 to your computer and use it in GitHub Desktop.

Privacy Policy for Ding!

Last updated: April 15, 2026

1. Introduction

Ding! ("we", "our", or "us") is committed to protecting your privacy. This Privacy Policy explains how we handle information when you use our mobile application. Our core philosophy is to minimize data collection and ensure that your personal information remains on your device whenever possible.

2. Information Collection and Use

Phone Authentication (SMS)

To ensure secure access and verify your identity, we use Firebase Phone Authentication.

  • Verification: When you sign up, you provide your phone number to receive a one-time verification code (SMS).
  • Processing: This process is handled directly by Google Firebase.
  • Privacy: We do not store your raw phone number in our primary cloud database; we only use it for the initial authentication and to generate your unique user Hash.

Address Book and Contacts (READ_CONTACTS)

Our app requires access to your contact list to identify which of your friends are already using Ding!.

  • Privacy-First Processing: We do not upload your raw contact list (names or plain phone numbers) to our servers.
  • Local Hashing: Phone numbers are processed locally on your device using a one-way cryptographic hash. Only these anonymous hashes are sent to our servers to perform a match with existing users.
  • No Raw Data Storage: Your original phone numbers and contact names never leave your device and are never stored on our cloud servers.

User and Group Data (Firebase Cloud Database)

To enable the app's functionality (sending "Dings" and managing groups), we use Google Firebase as our cloud provider:

  • Anonymous Identifiers: We do not store raw phone numbers in our cloud database. We only store cryptographic Hashes (unique user IDs) and FCM Tokens (required to deliver push notifications).
  • Group Management: Group structures and memberships are managed using these anonymous hashes.
  • Security: All cloud data is encrypted in transit and protected by strict Firebase Security Rules.

Local Storage (SQLite)

We use a local SQLite database on your device to store:

  • Contact names and profile photos.
  • App preferences and message history. This data is 100% local. It stays on your physical device, is not accessible by us or any third party, and is never uploaded to the cloud.

3. Service Providers

We use the following third-party services for the app to function:

  • Google Firebase: For secure authentication, cloud database management (Firestore), and delivery of push notifications (FCM).
  • Google Play Services: For security and app integrity.

4. Data Retention and Deletion

You can delete your account at any time within the app settings. Upon account deletion, your associated Hash and FCM Token will be permanently removed from our Firebase cloud database. Since we do not store your contacts on our servers, there is no contact data to delete from our side.

5. Children's Privacy

Our services do not address anyone under the age of 13. We do not knowingly collect personally identifiable information from children.

6. Changes to This Privacy Policy

We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.

7. Contact Us

If you have any questions or suggestions about our Privacy Policy, do not hesitate to contact us at: yuhu@mmoreram.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment