Privacy policy

Last updated: DATE · Controller: COMPANY / OWNER, address · Contact: support@remoteguard.app

Note: template – please have it reviewed legally before publishing and fill in the placeholders.

1. Overview

RemoteGuard only processes the data needed to run and operate the app: managing electronic key safes and granting access rights. The app shows no ads, and no data is sold for advertising.

2. What data we process

Account data: email address, display name, role.
Lock data: name/alias, technical identifier (e.g. MAC), protocol type.
Lock credentials: stored encrypted; accessible only to authorized owners.
Shares & actions: invitations, active shares and a log of executed lock actions.
Messages: contents of the in-app chat between the parties of a share (end-to-end encrypted).

3. Purpose and legal basis

Processing serves to provide the app’s functions (performance of a contract, Art. 6(1)(b) GDPR) as well as the security and traceability of access.

4. Processors / hosting

The backend and database run on Supabase. A data processing agreement exists or will be concluded with the provider. Add hosting region/details.

5. Retention

Data is stored as long as your account exists or as long as it is needed for the stated purposes. On account deletion it is removed – see Delete account.

6. Your rights

You have the right to access, rectification, erasure, restriction, data portability and objection. For this, contact support@remoteguard.app.

7. App permissions

Bluetooth is needed to find and operate supported locks nearby. Camera and photos are only used if you take or send a photo in the chat yourself. No location or advertising data is collected through them.

8. Security

Connections are encrypted via TLS/HTTPS. Security-critical lock credentials are stored encrypted, the in-app chat is end-to-end encrypted, and data access is limited by row-level isolation. A detailed, plain-language explanation is at Security & privacy.