This repository has been archived on 2026-11-17. You can view files and clone it, but cannot push or open issues or pull requests.
caelum0x 49b183818c Unify gitgram + aitimemachine into the monorepo (de-submodule) and merge vendored engines
Convert gitgram/ and aitimemachine/ from embedded git repos (which showed as
opaque submodule gitlinks on GitHub) into fully-tracked first-party content.

AITM now merges its 7 vendored repos as first-party engines:
- memory: beads (Go task DAG) + context7 (docs SDK), unified into saved_contexts
- git: vendored C git (bundled binary) + gitnexus (in-process code intelligence)
- agentic: a2a (@a2a-js/sdk) + pal (AITM-managed Python subprocess)

Includes the full session's product build: Gitgram web/mobile/backend features,
AITM website/CLI/MCP, the unified memory layer, engine build tooling
(scripts/build-engines.sh, Dockerfile, CI), docs (README, ENGINES.md, ARCHITECTURE.md),
and extensive test suites.

Build artifacts, node_modules, external/, and gemini-cli are gitignored.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-23 14:14:09 +03:00

59 lines
2.8 KiB
Plaintext

---
title: Security
sidebarTitle: Overview
---
Context7 takes security and privacy seriously. This page outlines our security practices, data handling, and compliance measures.
## Highlights
- Your original prompts stay with your AI assistant; Context7 only receives search queries formulated by the MCP client, which is instructed to strip sensitive data before sending them
- Documentation is indexed inside SOC 2 compliant infrastructure operated by Upstash
- API keys are encrypted, rate limited, and easy to rotate from your dashboard
- Enterprise customers can enable SSO (SAML, OAuth, OIDC) and receive dedicated audit trails
- The [Context7 Addendum](https://upstash.com/trust/context7addendum.pdf), [Upstash Terms and Privacy Policy](https://upstash.com/docs/common/help/legal) applies to all users; see [trust.upstash.com](https://trust.upstash.com/) for full infrastructure compliance details, certifications
## Security Areas
Explore the main security topics in Context7:
<CardGroup cols={2}>
<Card title="Data Privacy" icon="shield" href="/security/data-privacy">
Learn how Context7 handles privacy, retrieval scope, and data.
</Card>
<Card title="Infrastructure" icon="server" href="/security/infrastructure">
Review platform protections, operational controls, abuse prevention, and secure development practices.
</Card>
<Card title="Authentication and Access Control" icon="key" href="/security/auth-and-access-control">
See how API keys, SSO, and enterprise access controls are handled.
</Card>
<Card title="Data Safety" icon="magnifying-glass" href="/security/data-safety">
Understand how Context7 detects malicious content and prevents it from reaching AI assistants.
</Card>
<Card title="Compliance and Reporting" icon="badge-check" href="/security/compliance-and-reporting">
Find reporting guidance, transparency commitments, and compliance details.
</Card>
<Card title="Best Practices" icon="book-open" href="/security/best-practices">
Follow practical recommendations for using Context7 securely.
</Card>
</CardGroup>
Context7 also uses verification badges to help signal trusted libraries. For full verification details, see [Library Verification](/howto/verification).
For more details on how Context7 handles quality and safety, see the [Quality and Safety in Context7](https://upstash.com/blog/context7-quality-and-safety) blog post.
## Questions and Support
For security-related questions:
- Contact us through [GitHub Issues](https://github.com/upstash/context7/issues)
- Join our [Discord Community](https://upstash.com/discord)
- Enterprise customers: Contact your dedicated support team
For privacy policy details, visit: [context7.com/privacy](https://context7.com/privacy)
---
**Last Updated**: March 2026
We continuously improve our security practices. Check this page regularly for updates.