01Who we are
Grove is a developer tool operated by Bramble Labs Inc. This policy covers usegrove.cloud, our hosted Grove service, and related support. Contact grove@mawa.dev for privacy questions or requests.
If you run Grove yourself, you control that deployment and its providers, retention, and users. This policy describes our hosted service; a separate operator is responsible for their own deployment. Your connected agents and model providers have their own privacy practices.
02Information Grove handles
- Account information: your authentication identifier, email and available profile details, sign-in/session information, and account lifecycle state.
- Memory content: text you or your agents save, preferences, decisions, facts, solutions, task handoffs, project identities, tags, revisions, timestamps, and archive/deletion state.
- Search information: recall queries and the memory content processed to produce search results, full-text indexes, and numerical embeddings.
- Connections: agent/client names, approved scopes, access grants, API-key records and protected credential material, revocations, and connection activity needed to operate and secure access.
- Operational information: request and error metadata, network addresses processed by infrastructure, security and recovery records, and correspondence you send us.
Do not save passwords, API secrets, or information you are not permitted to share. A memory can include personal information about you or others if you put it in the text.
03How we use information
We use information to authenticate accounts, store and revise memories, retrieve relevant context, manage project scopes and connections, provide exports and deletion, respond to support, maintain reliability, and investigate misuse. Where a legal basis is required, this can include providing the service you request, legitimate operational and security interests where permitted, consent for optional processing, and legal obligations.
Grove’s tools save selected context rather than a continuous transcript of every conversation. Optional client hooks can retrieve a bounded profile or handoff. What is sent depends on the agent, tools, and configuration you choose.
04Your agents and your controls
Hosted memories belong to your account. Connections require authentication and the scope you approve. You can inspect memories, correct them, view revisions, archive or restore them, permanently delete them, and revoke connections in Your Grove.
When an agent recalls a memory, the selected content is sent to that agent. Its AI provider may then process the content under its own terms. Revoking access or deleting a memory cannot retract copies already delivered to an agent, conversation history, export, or another service.
Access controls protect account boundaries. Grove is not end-to-end encrypted against its operator: the service must process readable memory text to store and retrieve it.
05Providers and other recipients
We use Clerk for sign-in, sessions, and account identity; Neon for hosted PostgreSQL and recovery history; DigitalOcean for API and worker hosting; Vercel for the website and website analytics; and Porkbun for domain/DNS services. These providers process information needed to perform their roles. Hosted embeddings are currently computed by the Grove worker using a local model, rather than by sending memory text to an external embedding API.
Authorized support and operations personnel may access information where needed to provide support, investigate an incident, or comply with law. We may disclose information for lawful requests, protection of rights, professional advice, or a business transfer subject to applicable protections. We do not sell memory content or use it for advertising.
Providers may process information outside your country. Applicable transfer protections and local legal rights continue to apply; contact us for information relevant to your situation.
06Website analytics and local storage
The public marketing pages use Vercel Web Analytics for aggregate visits, referrals, and broad device/region information. It does not use tracking cookies. Website analytics are not mounted in Grove’s private dashboard, and memory content is not sent as marketing analytics.
Authentication uses cookies or similar session storage needed to keep you signed in. The CLI keeps protected credentials on your machine, partitioned by API origin, agent, and account. Installation-copy controls write the displayed command to your clipboard only when selected. Public demos use example content, not customer memories.
07Retention and deletion
Durable memories and revisions remain until you change or delete them or delete your account. Archiving is reversible and keeps the record; it is not permanent deletion. Task handoffs have an expiry and are subject to retention cleanup.
Permanent deletion removes live memory content, revisions, vectors, and pending associated jobs. Account cleanup is asynchronous and can require provider follow-up. Minimal deletion, revocation, and recovery records are retained to prevent deleted information from reappearing after recovery. Infrastructure logs and provider records have separate operational lifecycles.
The hosted database currently has a one-day point-in-time recovery window. Deletion does not instantly rewrite that history or independent exports. Restores must reconcile newer deletion and revocation decisions before reopening access. Contact us about a deletion request or any information retained for legal or security reasons.
08Your choices and rights
Use the memory library and connection settings to manage saved context and access. You can export your data or request account deletion in Settings. You can also email us for access, correction, deletion, portability, or questions about processing. We may need to verify that you control the account and explain any lawful exceptions.
Depending on your location, you may have rights to restrict or object to processing, withdraw consent, or complain to a privacy authority. Nothing in this policy limits mandatory rights. If you believe a child has provided personal information without required authorization, contact us.
09Security and policy updates
We use authenticated access, scoped permissions, account-level database controls, protected credentials, and encrypted network transport for the hosted service. No system can promise perfect security. Contact us privately about suspected exposure; do not post secrets or memory content in a public issue.
We update this policy when our practices change, show the effective date, and provide notice or obtain additional consent where required.