3ngram
How it works
use casesexamples for operators, product leads, eng leads, founders, and legal work.replaceswhere typed memory replaces a manual context scratchpad, and where it does not.
Pricing
aboutwhy 3ngram exists, and why follow-through matters after retrieval.securitywhat 3ngram reads, what it stores, and what it will never train on.switch to 3ngramconnect hosted MCP, self-host the backend, or explicitly save selected context.blognotes on memory, context, and the follow-through thesis.docs ↗the MCP server, REST API, SDK, CLI, and self-hosting.
GitHub ↗Sign in
GitHubSign inGet started

Subprocessors

Last updated July 9, 2026

B3dmar ApS, trading as 3ngram, uses the providers below to operate the hosted service. A provider receives only the categories of data needed for its stated purpose. This list does not apply to a self-hosted deployment controlled by you.

ProviderPurposeData categories
VercelMarketing-site and hosted-dashboard delivery; anonymous web analytics and performance measurementsRequest and device metadata, page paths, anonymous events, performance measurements
RailwayHosted API, MCP server, and background runtimeAccount and memory data in transit, bounded operational metadata
NeonManaged PostgreSQL and pgvector databaseAccount records, memories, embeddings, audit metadata, subscription state
OpenAIVector embeddings for semantic searchMemory or query text submitted for embedding; no card or authentication data
StripeSubscription checkout, invoices, taxes where enabled, and customer billing portalBilling identity, payment details, subscription and invoice state
SentryError and performance monitoringScrubbed diagnostic and request metadata; memory content is prohibited by policy
ResendTransactional account and billing emailEmail address, delivery metadata, and the transactional message being sent

International transfers

Some providers may process data outside the EEA. Where GDPR requires a transfer mechanism, we rely on the provider's applicable data-processing terms and safeguards, such as the EU Standard Contractual Clauses or an adequacy framework.

Data-use limits

Providers may process customer data only to deliver their contracted service. Customer memory content is not used by 3ngram to train a foundation model. OpenAI receives text only for the disclosed embedding request under its API data-use terms.

Changes

We will update this page before a new provider begins materially processing customer personal data. Customers with a signed DPA receive the notice and objection rights stated in that DPA.


Questions or a DPA request: legal@3ngram.ai. See also our Privacy Policy, Data Processing Agreement, and security page.

3ngram

shared memory and follow-through for your AI work. captures from: claude · chatgpt · cursor · codex + more · only what you ask the agent to save, never in the background.

product
use casesreplacessourceshow it workspricing
resources
aboutsecurityblogchangelogswitch to 3ngramdocs ↗use-case guides ↗claude code guide ↗connecting tools ↗single-account company brain ↗recall & supersession ↗benchmarks ↗
company
why 3ngram?contactgithub ↗
contact
hello@3ngram.ai
legal
privacytermscookiesacceptable useDPAsubprocessors
© 2026 3ngram