Privacy Policy

When an account is created, the application stores the account name and email address, together with authentication data needed to protect the account. Passwords are stored as password hashes rather than readable passwords.

The control plane may also store organization and project information associated with an account, along with resources and settings created within those workspaces.

For registered sessions, the application records session identifiers and security metadata including the connecting IP address and user-agent string. This supports session review, security controls, and session revocation.

The application may send account verification and password-reset messages to the email address associated with an account. Production transactional delivery is configured through the Resend email provider when enabled.

This notice does not add claims about advertising identifiers, analytics providers, payment processors, or third-party tracking that are not part of the current application functionality.

Essential cookies and local storage support account and session security, privacy preferences, and privacy-preserving first-party site analytics used to understand site usage and operate or improve the service.

The current implementation uses no advertising tracker and no third-party analytics provider. It may collect bounded session and event data such as normalized page paths, coarse device and browser family, campaign fields, safe referrer category, and trusted country metadata when available. Raw IP addresses and raw user-agent strings are not stored in analytics tables, and fingerprinting is not used.

This notice does not make GDPR, cookie-law, or other legal compliance guarantees.

As the platform moves from control-plane availability to infrastructure service availability, this notice may be expanded to describe service-specific processing. Updated terms will be published before those services launch.