1. In short
- No account, no cookies, no tracking, no analytics, no advertising.
- This service has no database of its own. What it needs to remember is stored in the Chaster extension session of your lock — the secret box credentials only in encrypted form.
- The pages load no resources from third parties.
2. What is processed
2.1 Data received from Chaster
When you open the extension inside a lock, Chaster hands the page a short-lived token. With it, our server asks the Chaster Extensions API for the session it belongs to and receives: your Chaster user ID and role (wearer or keyholder), the usernames of wearer and keyholder, the lock ID, title and status including when it was archived or recovered, the configuration of this extension and the data this extension stored in the session.
2.2 Data stored in the Chaster session
The extension stores the following in the extension session of your lock at Chaster:
- the box credentials (box key, admin credentials, keypad admin code), encrypted with AES-256-GCM before they leave our server — Chaster only holds ciphertext;
- the Bluetooth name of the box, its last reported battery level;
- when the box was paired and by which role, and the last action (type, time, role);
- a random secret used to sign the links to the box controller.
If logging is enabled in the configuration, pairing, opening, locking, resetting, removing and revealing the keypad code are also written to the lock history at Chaster, visible to wearer and keyholder.
2.3 Bluetooth
The browser connects to the box itself; choosing the device happens locally in your browser. To open or lock the box, your browser forwards the encrypted messages of the box to our server and back, together with the Bluetooth name of the box. No location data and no data about other Bluetooth devices around you are transmitted.
2.4 On your device
The box controller remembers your recovery link in your browser's local storage (lock ID, lock title, your role and the link token), so you can find your box again under /box. It stays on your device until you press “Forget” there or clear your browser data. Links to the controller carry their token after the # sign, which browsers do not send to servers.
2.5 Server logs
To run the service and find errors, the application logs which action was performed, by which role, a shortened session identifier and error messages — no IP addresses, no usernames, no keys. The web server in front of the application processes the IP address, time, requested address and browser identification of each request; this is technically necessary to deliver the pages and to defend against attacks. Logs are kept only as long as needed for operation and troubleshooting and are not used for any other purpose.
3. Purposes and legal basis
- Providing the extension you or your keyholder added to the lock (sections 2.1–2.4): Art. 6(1)(b) GDPR.
- Operating the service securely and fixing errors (section 2.5): our legitimate interest, Art. 6(1)(f) GDPR.
4. Recipients
- Chaster, where the lock and the extension session live. Chaster processes your data under its own responsibility; see the privacy policy on chaster.app.
- Hosting: the server this service runs on, operated on our behalf.
We do not sell data and do not pass it on for any other purpose.
5. How long data is kept
- Data in the Chaster session exists as long as the session does. The box credentials are deleted as soon as the box is reset or removed in the extension; the whole session is deleted by Chaster together with the lock or when the extension is removed.
- Local storage on your device: until you forget the box or clear your browser data.
- Server logs: see section 2.5.
6. Your rights
You have the right to access, rectification, erasure, restriction of processing, data portability and to object to processing based on legitimate interest (Art. 15–21 GDPR). You can do it yourself: remove the box in the extension, remove the extension from the lock, or delete the lock at Chaster — this deletes everything stored for it. Your recovery link you delete under /box on your device.
You also have the right to lodge a complaint with a data protection supervisory authority, in particular in the EU member state of your residence.
7. Changes
We update this policy when the service changes. The date at the top shows the current version.