Skip to the document
Gomind
MemoryBring together what your team already knows.PermissionsChoose who can read and contribute.ContinuityCarry context into the next conversation.
OverviewShared context in practice.↗
Planning & priorities↗Client service & relationships↗Sales & commercial teams↗Marketing & communications↗Engineering & development↗Context handoffs↗Research & learning↗Creative work & deliverables↗Partners & external teams↗Execution & operations↗
OverviewShared memory for your industry.↗
Software development firms↗Startups and SaaS↗Marketing agencies↗Consultancies↗Design, UX and research↗Product teams↗Data, AI and agents↗Support and Customer Success↗BPO and outsourcing↗Fintech and healthtech↗
LEARNDocumentationGomind guides, SDKs and API.Use casesShared context in practice.BlogIdeas for working with context.
EXPLOREConnectionsSecurityContact
Pricing
ProductMemoryPermissionsContinuity
Use cases
View all use cases↗Planning & prioritiesClient service & relationshipsSales & commercial teamsMarketing & communicationsEngineering & developmentContext handoffsResearch & learningCreative work & deliverablesPartners & external teamsExecution & operations
Industries
Explore industries↗Software development firmsStartups and SaaSMarketing agenciesConsultanciesDesign, UX and researchProduct teamsData, AI and agentsSupport and Customer SuccessBPO and outsourcingFintech and healthtech
ResourcesDocumentationUse casesBlogConnectionsSecurityPricingContactLog in
Try the night experience
Log inGet started
← Back to Gomind
PrivacyTerms

Privacy policy

How Gomind collects, stores, and shares data when you use the memory API, dashboard, and MCP server.

Effective 19 September 2026

On this page

  1. What we store
  2. What MCP and API responses contain
  3. Processors
  4. What we do not do
  5. Retention
  6. Access control
  7. Children
  8. Requests
On this page +
  1. What we store
  2. What MCP and API responses contain
  3. Processors
  4. What we do not do
  5. Retention
  6. Access control
  7. Children
  8. Requests

This policy describes how Gomind (“we”) handles information when you use gominddb.ai, the API at api.gominddb.com, the MCP server at mcp.gominddb.com, and the Gomind dashboard.

What we store

Gomind is a memory service. Most of what we hold is content you or your agents send on purpose.

  • Account. Email, Firebase user id, and optional display name, photo URL, and phone number supplied by Firebase Authentication when you sign in.
  • Organization. Organization name, membership, and roles (admin or user).
  • Memory. Facts (subject, relationship, object, optional source), entities, collections, and 768-dimension embedding vectors used for semantic recall.
  • Credentials. API keys and OAuth access/refresh tokens, stored hashed. We cannot read a key or token back after it is created.
  • Billing. Plan, credit balance, usage events, and Stripe identifiers (customer, subscription, payment intent, invoice). Card numbers are handled by Stripe, not Gomind.
  • Operations. Request traces (trace id, organization id, collection id, operation name) used to run and debug the service.

What MCP and API responses contain

Tools and REST endpoints return the memory records needed for the request: facts, entities, collection codes, and search scores. They do not return API keys, OAuth secrets, or Stripe payment details. Do not put secrets into facts if you do not want them recalled later.

Processors

We use other services to operate Gomind:

When you connect Gomind as an MCP connector in Claude, ChatGPT, Grok, or another host, that host receives the tool results you authorized. Their products are governed by their own policies.

  • Firebase Authentication (Google) — sign-in.
  • Stripe — subscriptions and credit purchases.
  • Embedding providers (Google Gemini and/or OpenAI) — fact text is sent to create vectors. Those providers process that text under their API terms.
  • Google Cloud — API and database hosting.
  • Cloudflare — DNS, TLS, and reverse proxy.

What we do not do

  • We do not scrape Claude, ChatGPT, or Grok conversation history. We only store what a client sends to remember, feed, or similar endpoints.
  • We do not sell your memory graph.
  • We do not use stored facts to train Gomind foundation models. We do not operate a foundation model.

Retention

Facts remain until you delete them with forget / forget_entity, delete a collection, or delete the organization. Collection deletes go active → deleting → purged. Account and billing records are kept as long as the organization exists and as required for tax and fraud prevention.

Access control

Every query is scoped to your organization and collection. Ownership failures return not-found, not a listing of other tenants’ data.

Children

Gomind is for organizations and developers. It is not directed at children under 16.

Requests

To access, correct, or delete personal data, use the Gomind dashboard (forget tools, collection delete, organization settings) or write via the contact path in your account. We will need enough information to verify you control the organization.

Related:Terms of use↗
Gomind

The context stays.
The possibilities grow.

Product

MemoryPermissionsContinuityPricingConnectionsSecurity

Use cases

OverviewPlanning & prioritiesClient service & relationshipsSales & commercial teamsMarketing & communicationsEngineering & developmentContext handoffsResearch & learningCreative work & deliverablesPartners & external teamsExecution & operations

Industries

OverviewSoftware development firmsStartups and SaaSMarketing agenciesConsultanciesDesign, UX and researchProduct teamsData, AI and agentsSupport and Customer SuccessBPO and outsourcingFintech and healthtech

Resources

DocumentationConnect your AIBlog

Gomind

ContactPrivacyTerms of useLog in
Gomind · Shared memory for people and their AIs.Back to top ↑