Legal
How the website and DiamaneOS network services handle data, and how to contact the controller.
Impressum
Abhinav Jhanwar
c/o RA Matutis
Berliner Straße 57
14467 Potsdam
Email: abhinav.jhanwar@proton.me
Privacy policy
The controller for this website and the DiamaneOS services described here is the person named in the Impressum. Use the postal address or email published there for privacy requests.
Purposes and legal bases
Connection data is processed to deliver the requested website or service and limit abuse. The legal basis is Article 6(1)(f) GDPR: legitimate interests in secure, reliable services, with request logging disabled and temporary processing limited to those purposes.
Native service messages are processed to return requested provisioning and positioning responses. This includes device identifiers or location-bearing protocol contents. Article 6(1)(f) GDPR applies to providing those device functions, with fixed destinations, bounded messages and no request-body retention.
Contact details and messages are processed to answer enquiries and handle follow-up. This also relies on Article 6(1)(f) GDPR: legitimate interests in responding to people who contact the project. Providing a reply address is necessary to receive an answer.
Website
These pages set no cookies and run no scripts. Fonts, images and styles come from this site. The contact form submits to this site’s own handler. There is no analytics, advertising or embedded third-party content.
A connection exposes your IP address, request time, requested page and browser headers to OVHcloud, the website host in Germany. The logging and retention policy below applies to the website and OS backend services.
Links to other websites are ordinary navigation links. Following one connects your browser to that website, whose own privacy policy applies.
Hosting
| Services | Hosting provider | Server location |
|---|---|---|
| Website, primary downloads, connectivity checks, time and service relays | OVHcloud | Germany |
| Optional OS and app download mirror | ServaRICA | Canada |
| Attestation | OVHcloud | France |
The Canadian mirror handles OS and app downloads. Other services use their own endpoints. A download from Canada exposes connection metadata to the Canadian host; content signatures protect authenticity, not the confidentiality of that connection metadata.
Processing outside the EEA
The Canadian mirror is provided by Rica Web Services Inc. (ServaRICA). Canada’s adequacy decision covers commercial organisations subject to PIPEDA, including cross-border commercial processing. The mirror’s location does not make connection metadata anonymous.
Contact-form delivery uses mailbox.org, Germany. The receiving contact mailbox uses Proton AG, Switzerland. Proton Mail stores mail in Switzerland, Germany and Norway. These providers process messages and delivery metadata.
Switzerland has an EU adequacy decision; Germany and Norway are within the EEA.
Native provisioning, SUPL and network-location requests can reach Google’s or Apple’s services outside the EEA. Their transfer arrangements are described in Google’s data-transfer framework and Apple’s privacy policy. These links do not establish a DiamaneOS-specific processing agreement.
Contact us for information and copies of safeguards applying to transfers of your data.
Connection data and retention
For each request, backend services handle your IP address, request time, requested path and relevant protocol headers to return the requested response and limit abuse. These requests are not used for advertising or user profiling.
The web servers have request access logs and request-associated error logs disabled. Temporary rate-limit state is held in memory. Public assistance data, certificate-transparency data and signed download files can be cached without storing a history of individual requests.
Operational logs use volatile storage with a configured one-day retention limit and are cleared on reboot. They describe service operation, rather than providing a request history. Monitoring notices use service names and failure or recovery categories, without including user request bodies or device identifiers.
Hosting and network providers can observe connections and maintain their own security, account or billing records. Disabling DiamaneOS request logs does not guarantee that those providers retain no data.
What each service receives
| Service | Data processed for the request |
|---|---|
| Connectivity and online checks | Connection metadata and HTTP headers; no account is required |
| Network time | Connection metadata needed to return the time |
| OS and app downloads | Connection metadata and the requested catalogue, package or release path |
| Satellite assistance data | Connection metadata and a fixed assistance-data object |
| System certificate-transparency data | Connection metadata and public transparency-data objects; no browsing history is submitted to this cache |
| SUPL positioning assistance | Native positioning messages, which can contain device identifiers and location information |
| Remote attestation-key and Widevine provisioning | Native provisioning messages and permitted query fields, which can contain device identifiers |
| Optional network location | Nearby Wi-Fi and cellular identifiers, which can reveal approximate location |
Relays and external services
Provisioning relays forward permitted requests to Google’s provisioning services. Satellite assistance uses Qualcomm’s public assistance-data service. The SUPL relay forwards native positioning messages to Google’s SUPL service.
The optional network-location relay forwards native Wi-Fi and cellular queries to Apple. It does not keep a query cache or location history. Apple sees the relay’s IP address and the information contained in the query.
HTTP relays remove IP-forwarding headers, including the original client IP address. They terminate encryption and can process the protocol contents in memory. A relay does not remove identifiers carried inside the native message or make that message anonymous.
DNS checks use the recursive resolver selected on the device and INWX’s authoritative DNS service. Those providers can receive DNS queries. DiamaneOS does not operate the authoritative nameservers for this domain.
An OpenStreetMap geocoding service, when selected, is contacted directly. The provider receives the client’s IP address and lookup text or coordinates; there is no DiamaneOS geocoding relay.
Mirrored GrapheneOS-signed Vanadium packages retain the publisher’s built-in service endpoints. Apps, mobile carriers, eSIM providers and separately selected DNS or location providers have their own data handling; this notice does not describe their policies.
Attestation
When you use remote attestation, the service processes account, device and security-state information to verify device integrity and send selected alerts. Its separate privacy policy explains that data, hosting, cookies and retention.
Contact and rights
If you contact DiamaneOS, your email address, message and any attachments are processed to handle your request. Do not include passwords, private keys or unnecessary device identifiers. Proton Mail receives contact mail; mailbox.org delivers form messages and service notifications.
The contact form accepts an email address and a plain-text message, without attachments. Its handler processes the message in memory and forwards it by encrypted mail transport. It keeps no message queue or request log. Request limits use temporary state.
Correspondence is kept while the enquiry and necessary follow-up are active. Resolved conversations are reviewed quarterly and deleted from active mailboxes within six months of resolution. A specific legal obligation or legal claim can require longer retention.
Mail-provider backup expiry is separate from inbox deletion. Proton states that its encrypted backups are retained for up to 30 days. Postal correspondence at the c/o address is handled through RA Matutis, Germany.
Mail transport encryption does not make the contact form end-to-end encrypted. The sending and receiving mail services can process delivery metadata and the message during delivery. The form sends no copy to the submitted address.
Under the GDPR, you can request access, correction, erasure or restriction of your personal data where the applicable conditions are met. You can also object to processing and request portability where those rights apply.
You can complain to a data-protection supervisory authority, including one where you live or work. Send privacy requests using the contact details in the Impressum.
Privacy requests receive a response within one month. Where complexity or the number of requests requires an extension, up to two additional months are allowed; you will be informed of the reason within the first month.