Privacy
Privacy, stated plainly.
This public site keeps data collection narrow. When something needs more care, it should be explicit about what is stored and why.
Public pages on ronova.dev can be read without creating an account. Standard delivery, rate-limiting, and hosting logs may still exist at the infrastructure level.
The support portal encrypts the message body and optional contact field in the browser before submission. Topic, project context, submission time, and a small amount of delivery metadata can still remain visible for routing and abuse control.
Community forum reading is public, while publishing and reactions require an active Ronova ID session. Every Ronova ID also has a deterministic internal virtual address in the form `[email protected]`; it is not an SMTP mailbox and is not enabled to send or receive mail by default.
Private message rooms store ciphertext plus limited operational metadata such as room membership, timestamps, and ciphertext size; they do not store readable message bodies.
Direct end-to-end encrypted message requests use a Ronova ID or that virtual address. Email-address lookup never confirms whether a Ronova account exists, and a recipient must approve before a room, device registration, or ciphertext becomes available.
Access codes create short-lived server-validated sessions for private pages. Those sessions can expire, be revoked, and are not intended to turn public browsing into a tracked profile.