Reddr

Your data, in plain language

Privacy Policy

Safety needs trust. This policy explains the personal data Reddr uses, why we use it, and the choices you keep.

Last reviewed: 28 July 2026

1. Who this policy is for

This policy explains how Reddr handles personal data when you visit reddr.app, create an account, use the Reddr mobile app, or contact us. Reddr is a personal-safety service.

For privacy questions or requests, email hello@reddr.app. Before public launch, this page will be updated with the legal name, registered address, and—if required—the data-protection contact for the company that operates Reddr.

2. Data we collect

Account and sign-in data: when you create an account with email and password, we collect your name, email address, phone number, password hash, login-session information, and the information needed to verify your email or reset your password. If you choose Google Sign-In, we receive the account identifier and profile information Google provides for that sign-in; because Google Sign-In does not provide a phone number, adding one is optional at that step.

Safety network data: the contacts, connection requests, group memberships, invitations, notification preferences, and plan status you choose to create. Reddr does not access or import your phone address book.

Emergency and location data: when you start an SOS, the app sends a small emergency packet to the Reddr server, including the location available at that moment. Reddr follows three recipient steps: first, it notifies your accepted emergency contacts; second, it notifies the members of your own groups; third, when the nearby-group feature is enabled, it finds groups near the SOS location and notifies their members. The current release provides the first two steps. A person included in more than one step receives one emergency notification only. SMS, automated calls, and the helper network are not active parts of this flow yet.

Device and communication data: device platform and push-notification token, plus delivery and security records needed to send service messages such as verification codes, password resets, contact invitations, and emergency updates.

Witness video: Witness Mode is for recording video evidence during an emergency. Videos are stored in protected cloud storage as part of the Reddr safety service and are not used for advertising. Witness Mode does not provide photo or audio recording.

Website and support data: information you send us by email or through a form, together with the limited technical information needed to operate and secure the website.

3. Why we use it

We use account, contact, group, and device data to provide the service you ask us to provide: create and secure your account, maintain your safety network, deliver service notifications, and operate an emergency you start.

We use information to protect the service and its users, prevent misuse, troubleshoot faults, comply with legal obligations, and respond to requests. Where consent is required—for example, for optional location permissions or a future identity-check feature—we ask for it in the app and you can withdraw it in device or app settings.

We do not sell personal data or use emergency, location, or recording data for advertising.

4. Location, emergencies, and your choices

Location is especially sensitive. The first emergency alert may include your available location because it is necessary to help the people you selected understand where help is needed. After that, the sharing rules you choose for a contact control any further location sharing.

The app presents three sharing choices—Always, Emergency only, and Nearby. At the current stage, only Emergency only is an active, reliable sharing mode. Always and Nearby will not become live-sharing features until the necessary background-location and privacy controls are in place.

You can manage contacts, emergency-circle choices, app permissions, and notification settings. Blocking or removing a contact should stop future sharing with that person; it cannot undo information already received in an emergency alert.

5. Who receives data

Your chosen contacts and relevant group members receive the emergency information needed to respond when you trigger an emergency. They may receive your name, the fact that an emergency was raised, and the location available at that time.

We use service providers to operate Reddr, including hosting and database providers, SendGrid for transactional email, Google for optional Google Sign-In and Firebase notification infrastructure, and map providers when a map feature is enabled. A provider is only used for the feature it supports and under appropriate contractual safeguards.

Potential future providers—such as Twilio for SMS or voice escalation, RevenueCat for purchases, and Didit for identity verification—are not part of the current public product flow. We will update this policy before activating them.

6. Retention and deletion

We keep account and safety-network data while your account is active, unless a shorter period is needed for the service or a longer period is required by law. We keep security and transaction records only as long as reasonably necessary for security, dispute handling, and legal obligations.

Reddr is designed around short-lived emergency data. Our product target is to close an unresolved emergency after six hours and remove associated emergency-sharing data. This retention workflow is still being completed and validated; until it is fully deployed, do not rely on automatic deletion as your only way to remove information.

You can request account deletion. Deleting an account does not require us to delete information that must be retained by law, needed to resolve a dispute, or already received and independently kept by another person.

7. Your privacy rights

If the GDPR applies to you, you can ask for access to, correction of, deletion of, restriction of, or portability of your personal data, and you can object to certain processing. Where we rely on consent, you can withdraw it at any time. You may also complain to your local data-protection authority; in the Netherlands, this is the Autoriteit Persoonsgegevens.

To make a request, email hello@reddr.app from the address linked to your account. We may ask for enough information to verify that the request is yours.

8. Security and changes

We use technical and organisational measures intended to protect personal data, including access controls and secure account authentication. No internet or mobile service can promise absolute security, especially during an emergency or when a device is unavailable.

We may update this policy as Reddr changes. For material changes, we will provide notice in the app or by another appropriate method before the change takes effect where required by law.