--- title: "Gazebo Privacy Policy" description: "How Gazebo collects, uses, and protects your information." url: "https://gazebohq.com/privacy" --- # Privacy Policy Last updated: October 24, 2026 ## 1. Who we are Gazebo is operated by Unlimited Ventures Pty Ltd, an Australian company ("we", "our", "us"). Gazebo manages credential access for AI agents. This Privacy Policy explains how we collect, use, and protect information when you use Gazebo at gazebohq.com and any related services (collectively, the "Service"). ## 2. Information we collect Account data We collect your email address and account information. If you use a password, we store a password hash, not your plaintext password. If you use a magic link, we process your email address and a time-limited sign-in token. Google and GitHub sign-in If you choose Google or GitHub sign-in, we receive the provider identifier, verified email information and available name information needed to create, link or authenticate your account. We do not receive your Google or GitHub password. These providers also process information under their own privacy policies. Signing in with GitHub is separate from connecting a GitHub service credential to your vault. Credentials vault When you connect external services, we store the API keys and tokens you provide encrypted at rest using AES-256-GCM. Dashboard connection views do not display stored values. Authorized agent API and MCP retrieval returns the actual credential over HTTPS to the calling runtime; a third-party host running that agent receives it too. Agent tokens We generate a bearer token when you create an agent and store its verification hash and metadata, including the agent name, permitted services, expiry and activity timestamps. Access policies govern credential retrieval, not subsequent provider API calls. Revoking access prevents future retrieval; it does not invalidate credentials already received by an agent. Approval data The Agent Consent Flow stores registered application details, redirect addresses, requested and approved service/key selections, account-linked grants, connection identifiers, approval decisions and token security records. Access and renewal credentials support authorised connections; retained hashes help detect reuse. Temporary encrypted renewal retry responses are cleared after their retry window expires. Audit log data Credential request logs include the agent, requested service and key name, declared HTTP method, outcome and timestamp. They record credential retrieval activity, not the content of subsequent requests to providers. Logs are normally retained for 90 days and removed by routine cleanup. Session data We use server-side sessions to keep you logged in. Session identifiers are stored in an HTTP-only cookie. We may also process request metadata, such as IP addresses, browser information and error details, through hosting, delivery and security systems to operate and protect the Service. Email address for transactional messages We use Resend for account verification, magic links, security and service notifications, onboarding assistance and support communications. We also maintain contact and delivery records. You can unsubscribe from optional messages using the link provided or contact us. Essential authentication and security messages may still be sent. Where consent is required for marketing, we obtain it before sending marketing messages. Website analytics We use Plausible for aggregate website analytics, such as page visits, referral sources and interactions. Its standard website analytics script does not use analytics cookies. We do not intentionally send vault credentials or agent tokens as analytics event data. ## 3. How we use your information - To provide, operate, and improve the Service - To authenticate your identity and keep your account secure - To provide AI agents with scoped credential access to services you have permitted - To maintain an audit log of credential accesses and approval decisions - To send transactional emails (verification, sign-in links, billing notices) - To detect and prevent abuse, fraud, or security incidents ## 4. Third-party services We share data with the following sub-processors to provide the Service: - Resend — Email delivery. Your email address is shared with Resend to send transactional emails. - Replit — Cloud infrastructure and hosting. Our servers, database, and storage run on Replit's platform. - Cloudflare — Website delivery, DNS and security services, which may process network and request information. - Plausible — Aggregate website analytics. When you authorise a connection, selected credentials are disclosed to the agent runtime and, where applicable, its third-party host. Those recipients are not necessarily our service providers; review their privacy and security practices before approving access. Our primary application and database hosting is in the United States. Our service providers may also process information in other countries, so this is not a promise of US-only storage or processing. Information may be transferred outside Australia to operate the Service. Contact us for information about applicable hosting and processing arrangements. We do not sell your data to any third party. ## 5. Data retention - Account data is retained while your account is active. To request account deletion, email hello@gazebohq.com. We verify the request, revoke access and aim to complete deletion from the primary database within 30 days of verification. - Removing a stored credential deletes it from the active vault. This does not delete copies already released to agent runtimes or revoke the underlying key at its provider. - Revoked agent and consent credentials stop granting access. Limited metadata and token hashes may remain for access history, security and replay detection; revocation is not the same as immediate deletion of every record. - Credential request audit logs are normally retained for 90 days and removed by routine cleanup. Consent and connection security records have separate lifecycles; eligible expired token history is cleaned up after a 30-day safety period once the associated connection has ended. - Email verification tokens expire after 24 hours and magic link tokens after 1 hour. - Some information may be retained where reasonably necessary for legal obligations, disputes or security. Expiration of a token does not necessarily mean its record is immediately deleted. - Deleting data from active systems does not instantly erase historical backups or recovery history. Our production database currently uses a rolling 7-day point-in-time recovery window and daily scheduled database backups kept for 7 days. Deleted data may remain in recovery history or backups until it ages out. These settings do not mean every copy held by every provider is erased within seven days. If a backup is restored, deletion requests must be reapplied before the restored account is returned to use. ## 6. Your rights Depending on applicable law, you may have rights to access, correct or delete your personal information. Account deletion is support-assisted, not a self-service setting. For deletion, access, correction, export or a privacy complaint, contact [hello@gazebohq.com](mailto:hello@gazebohq.com). We may verify your identity before acting. We will acknowledge privacy complaints, investigate and respond within a reasonable period. This does not limit any right to complain to an applicable privacy regulator, including the Office of the Australian Information Commissioner where relevant. ## 7. Security We take security seriously. Credentials are encrypted with AES-256-GCM, agent tokens are scoped to specific permitted services, sessions use HTTP-only cookies, and the Agent Consent Flow records explicit approval for selected credential access. No service can guarantee absolute security. For more about our security practices, see our [Security page](https://gazebohq.com/security). ## 8. Cookies We use essential session and routing cookies to keep you signed in and route you to the appropriate application. Our standard Plausible website analytics does not use analytics cookies. We do not use advertising cookies. ## 9. Changes to this policy We may update this policy from time to time. When we do, we'll update the "Last updated" date at the top. For significant changes, we'll notify you by email. ## 10. Contact Questions about this policy? Email us at [hello@gazebohq.com](mailto:hello@gazebohq.com).