Privacy Policy

The public pages (home, features, docs, about, contact, legal) do not require an account. The site does not include third-party analytics, advertising or tracking scripts, and the public pages do not set cookies for visitors who do not sign in. Like any web server, the hosting stack may keep standard request logs (such as IP address and requested URL) for operations and abuse prevention.

If you use the contact form, the name, email address, subject and message you enter are sent by email to the site operator so they can reply. The form is rate-limited per IP address. The application does not store message contents in its database and does not write them to its logs.

To be confirmed: Retention of contact emails in the operator's mailbox, and the web server or reverse proxy log retention period in production.

Accounts are created by an administrator; there is no public sign-up. For each account we store an email address, a role (viewer or admin), a salted password hash (never the password), and session records. Sessions use an HttpOnly, Secure, SameSite=Lax cookie, expire after inactivity and after an absolute lifetime, and are revoked when the password changes.

Sign-in attempts are recorded (email and IP address) to throttle password guessing. An append-only audit log records sign-in events, state changes and log reads together with the acting account and the caller's IP address.

Sutra monitors servers and websites that its operators connect. An agent on a monitored server reports health data such as resource metrics, service and container status, and check results. Operators can also request logs from monitored servers (for example service journals); those requests are recorded in the audit log. Logs and diagnostics can contain whatever the monitored software writes, so operators are responsible for what they choose to monitor and view.

The software removes data automatically. Defaults, each adjustable by the operator through RETENTION_* settings:

• Raw check results: 3 days; hourly uptime and latency rollups: 400 days
• Resource metrics: 30 days; sign-in attempts: 30 days
• Notifications: 180 days; resolved incidents: 730 days
• Audit log: 400 days (the database refuses earlier purges)
• Sessions: removed one day after expiry

To be confirmed: The retention periods actually configured in production, and the process for handling deletion, access or correction requests for account data.

Access is role-based and enforced on the server for every API route. Stored secrets such as notification credentials are encrypted at rest with AES-256-GCM and are never returned by the API. See the security page for more, including what is not yet implemented.

Sutra does not send data to analytics or advertising providers. Operators may configure notification destinations: Microsoft Teams webhooks, Power Automate flows and an SMTP mail server. When configured, alert content (such as check names, status and summaries) is sent to those services, which have their own privacy terms. The contact form uses the SMTP server the operator configures for it.

To be confirmed: The hosting provider and region for the production deployment, and any processors the operator has added.

Depending on where you live you may have rights to access, correct or delete your personal data. Contact # falls back to SITE_CONTACT_EMAIL about privacy questions.

To be confirmed: Applicable data-protection law and any legal basis statements, which need legal review.

We may update this policy as the software changes. The effective date will be shown here once confirmed.