Privacy Statement
Controller: Secure Dimensions GmbH, Waxensteinstr. 28, 81377 Munich, Germany. Email privacy@secure-dimensions.de. Telephone +49 89 38151813.
Data protection officer: Andreas Matheus, same postal address, privacy@secure-dimensions.de.
1. What this statement covers
This statement describes personal data processed by the geoNFT Operator Console, the authorization server for Trusted Connected Systems. The Cookie Statement describes the session cookie.
2. Data we process
| Data | Examples | Why |
|---|---|---|
| Account | Name, license number, operator identifier | Create the account and show it in the console |
| Passkey | Credential identifier, public key, signature counter, and transports reported by the browser | Check that a later sign-in or approval comes from the same passkey |
| Session | The tcs_session cookie |
Keep you signed in for up to 12 hours |
| Drone | Alias, system identifier, DID, public key | Enroll the drone and bind it to your account |
| Flight | Flight name, deployment identifier, pairing code, access token, observation addresses, expiry | Open and close a flight and hand the token to the ground station |
We do not collect a password. The private key, and any fingerprint or face check, stay on your device. We do not use analytics or advertising, and we do not sell personal data.
3. Why we may process it
We process this data to provide the account, enrollment, and flights you ask for (Art. 6 (1) (b) GDPR). Checking the passkey and keeping the session cookie are also required to keep that account from being used by someone else (Art. 6 (1) (f) GDPR).
4. Ledger
When you approve enrollment, the drone’s public key is written to a Hyperledger Indy ledger as a DID. That record does not include your name or license number. Anyone who can read the ledger can read the DID and the public key, and a record the ledger has accepted cannot be deleted from it.
5. Connected Systems
Enrollment and an open flight send the drone system and the deployment to the Connected Systems API run for this Service. Those records are what allow observations while the flight is open. They stay on infrastructure operated for Secure Dimensions.
6. How long we keep it
- The session cookie lasts 12 hours, or until you sign out.
- The pairing code and access token are removed when the flight is closed. The token expires eight hours after the flight opens.
- The operator account, the passkey registration, and enrolled drones are kept while the account is in use. We delete them when you ask, except for a public key already written to the ledger.
7. Who receives it
Your name, license number, and session are not passed to advertisers or data brokers. The drone public key is published on the ledger as described above. The systems that host this Service process the data for us.
8. Your rights
You can ask for access, correction, erasure, restriction, or a copy of your personal data, and you can object to processing that is based on legitimate interest. You can also complain to a supervisory authority. For this controller that authority is the Bayerisches Landesamt für Datenschutzaufsicht (BayLDA), Promenade 18, 91522 Ansbach, Germany.
Write to privacy@secure-dimensions.de. The console has no separate delete control.
9. Changes
The date at the top of this page is the date of the current version.
