ContextDB
Menu

Home / Legal

Terms and privacy

Terms and Privacy Policy

These terms govern use of ContextDB Cloud and this website. They explain the service boundary, acceptable use, data handling, and how to contact us.

Marks and attribution

Trademark

ContextDB and the ContextDB logo are trademarks of Atoms AI. The Apache-2.0 license covers the SDK's copyright and patents, not the marks. You may say you use ContextDB and state compatibility when true. You may not use the name for a competing product or imply endorsement. Full terms: COMMERCIAL.md and NOTICE.

Open SDK

The SDK license

pycontextdb is Apache-2.0. There is no license key and no local paid boolean. Code published through commit 2554dae is Apache-2.0 forever, including forks already taken. Substantial new contributions require a CLA so future dual-licensing of new work remains possible. That never revokes Apache-2.0 on what is already released.

Current data handling

Privacy Policy

  • This site sets no cookies, runs no analytics, and loads no third-party trackers.
  • The hosted service stores agent memories with PII encrypted before any embedding call. Memory content and queries are never written to logs.
  • OAuth MCP connectors store the authorizing account, selected project, client identifier, scopes, and grant timestamps. Access and refresh tokens are stored only as hashes, rotate on refresh, expire, and can be revoked from Console settings. Marketplace tools use a server-derived private partition rather than a caller-supplied customer identifier.
  • In the open SDK, deletion can be checked with verify_forgotten. Hosted Alpha supports request-driven deletion of one scoped memory or stable slot, plus verified user-partition erasure with typed confirmation and immediate residue checks. Scheduled retention and large asynchronous erasure remain planned, so customers must enforce schedules externally.
  • An API-key MCP confirmation records authenticated project-credential context against one scoped memory. An OAuth MCP confirmation records the authorizing ContextDB account and bound connector partition. The customer host authenticates any separate application end user and retains any end-user attestation. A Console confirmation records operator context. No confirmation proves objective truth. Confirmation records are audit data. Customers choose retention policy and must run scheduled deletion externally during alpha.

Service boundary

Acceptable use (summary)

Do not use the service to violate law or others' rights. Do not probe or disrupt other tenants. Do not misrepresent attestation as objective truth in regulated decisions without human review. The full terms ship with the first customer contracts.

Support

Get help with a blocked request.

Email gaurav@saaslabs.co. Include your organization ID, project ID, request ID, UTC timestamp, endpoint, and HTTP status. Never email an API key, memory content, or end-user personal data.

  • Check the service status before reporting an outage.
  • For 409 idempotency_ambiguous, do not retry with a new key. Inspect current business state and include the original request ID.
  • Support coverage and current service availability are described on the Status page.

Contact

Product and cloud: gaurav@saaslabs.co. Trademark misuse: same address, subject ContextDB trademark.