Privacy and retention
Which personal data Asterion processes, for how long, and what the operator has to do.
Asterion is designed for the GDPR: data minimisation, defined retention, export and deletion, no unnecessary third parties.
Personal data
| Data | Purpose | Kept |
|---|---|---|
| User accounts (name, e-mail, password hash, TOTP secret, language) | sign-in, roles | until the account is deleted |
| Sessions (IP address, browser) | sign-in | session lifetime, then privacy:prune |
| Password reset links | password reset | 60 minutes |
| Web server logs | operation, security | nginx writes shortened client addresses; the host must delete container logs after PRIVACY_LOG_DAYS (14) |
| Monitoring data (addresses, names, services, certificates of the monitored systems) | the service | see retention |
Monitoring data is usually not personal data of users, but can be (e.g. a hostname containing a name). For customers’ data the operator acts as processor (Art. 28 GDPR) and needs a data processing agreement with the customer.
Rights of users
- Access and portability: My account → Download my data (JSON).
- Deletion: by an administrator.
Cookies
Only the session cookie, the XSRF cookie and the optional keep me signed in cookie. No consent banner is needed.
External services
Satellites contact no third party except your targets: Polaris locates them itself.
See Data sources. No service receives data about users. The address lookup only receives the address a user typed, when they click Look up address.
Privacy policy and imprint
/datenschutz (German, binding, with English translation) and /impressum are public, also on the API-only host. They are filled from COMPANY_*, PRIVACY_* and POLARIS_RETENTION_*. Who changes Polaris so that it processes new personal data must update User::personalData(), the retention jobs, both policy files and privacy.updated.