Privacy notice
What this deployment stores and why
Account information
Google handles sign-in. Agentropy requests basic identity information to verify your account, then stores the identity-provider issuer and subject identifier. It does not store your Google password or provider refresh token. The email-verification claim is checked during login.
Projects and agent data
The deployment stores project memberships, agent identities, agent state, submitted message payloads, results and operational audit records. These records support durable execution, recovery and access control. Project viewers can inspect stored receipt results; project owners control viewer access.
Cookies and credentials
The console uses a signed, encrypted essential session cookie. Session tokens and backend API keys are stored as digests. Console sessions expire after eight hours and can be revoked. Agentropy does not include advertising trackers or third-party analytics in this pilot. Fonts and visual assets are served by this deployment.
Retention and deletion
Agent state remains stored until the deployment operator removes it. Default receipt and audit retention settings are 30 and 90 days respectively; deletion requires the operator to run retention maintenance. Backup copies follow the operator’s backup schedule. Contact the operator for access or deletion requests.
Service providers and operational access
Google processes sign-in requests. The operator’s hosting provider stores the runtime and database. Authorized operators maintain the service, backups and security controls. Basic request metadata can be used for rate limiting, diagnostics and security. Customer handlers deployed by an operator may have additional external integrations; the included MemoryAgent does not call a model provider.
Contact
Contact your deployment operator at gibranrodriguezluna@gmail.com.