Privacy Policy

Draft for POC review. Professional legal review and a complete business-identity configuration are required before commercial publication.

Effective date: 2026-01-01

What we collect

Account data (email, password hash, MFA configuration metadata, recovery-code hashes), session and device information, IP addresses, security-event records, organization membership data, server metadata, public IP addresses, SSH public keys and fingerprints, firewall configuration, orders, support tickets and internal support notes, abuse reports, transactional-email metadata and delivery status, monitoring metrics and agent heartbeat data where monitoring is enabled, legal-policy acceptance records, and contact-form submissions are processed to operate the platform.

Why we collect it

Each category above is collected to provide the account/portal/server functionality you use, to secure accounts and infrastructure, to investigate abuse and fraud, to provide support, to meet legal and accounting obligations, and to operate the public status and abuse-reporting systems described elsewhere on this site. Billing data will be processed only once real payments are enabled, and will be described in an updated version of this policy before that happens.

Retention

Data is retained for as long as your account is active, plus a limited period afterward where retention is needed for security, fraud-prevention, legal, or accounting purposes. There is no automated deletion pipeline in place today; do not rely on data being erased automatically on a fixed schedule.

Security measures

Passwords are stored only as modern one-way hashes (Argon2id), never in plaintext. Provider and monitoring credentials are encrypted at rest. Sessions use HttpOnly, Secure cookies with idle and absolute expiry. Traffic to the production service is served over HTTPS. Access to customer data is restricted by role-based authorization and organization-scoped queries. See the Security page for the current list of implemented controls.

Sharing and subprocessors

We do not sell your personal data. Infrastructure, database, monitoring, and email subprocessors necessarily process data needed to provide the service — RYVARA does not claim that data is never shared with a subprocessor, or that server contents are never accessed; access is limited to operating the service, security, abuse handling, or legal requirements. The current list of subprocessors, their purpose, and the data categories each one processes is published at Subprocessor Disclosure. Data may be processed in the region where each subprocessor operates; RYVARA does not currently claim a specific data-localization guarantee beyond what is described there.

Your rights

You may request access to, correction of, or deletion of your account data by contacting legal-placeholder@example.invalid. Some records must be retained despite a deletion request where security, fraud-prevention, legal, or accounting obligations require it — we will tell you if that applies to your request. Formal legal-basis language (for example under a specific data-protection law) will be added only once a jurisdiction is configured and the language has been reviewed; none is claimed today.

Changes to this policy

We may update this policy. Material changes will be published as a new version with a clear effective date.

Contact

Privacy questions or requests: legal-placeholder@example.invalid.