Trust center

Security is
infrastructure too.

Context infrastructure holds your most sensitive knowledge. We built Docklee with encryption, isolation, and auditability as first-class primitives, not features bolted on later.

  • Industry-standard encryption protecting data at rest and in transit
  • Tenant data kept logically separate throughout the platform
  • Operations are logged to support accountability and review
  • Designed with common compliance frameworks in mind
Security posture
  • EncryptedAt rest and in transit
  • IsolatedSeparated per tenant
  • AuditedKey operations logged
  • Access-controlledScoped credentials

Security pillars

Four properties that never get traded away

These are the non-negotiables. Every line of infrastructure code is held to all four.

  • Encryption

    Data at rest and in transit is protected using encryption. We follow current industry practice and review our approach as part of ongoing security work.

    • Encryption applied to stored data
    • Data in transit is encrypted
    • Key management follows current best practice
    • Encryption approach reviewed regularly
  • Tenant separation

    Each customer's data is handled in its own isolated context. The architecture is designed to prevent one customer's data from being accessible by another.

    • Data contexts isolated per customer
    • Access controls scoped to each account
    • Separation enforced at the design level
    • Reviewed as part of ongoing security work
  • Auditability

    Key platform operations are logged with actor identity and timestamps to support accountability, review, and investigation.

    • Structured logs for key operations
    • Actor identity captured on relevant events
    • Logs retained per our data policy
    • Audit trail available for your security reviews
  • Access control

    Access to the platform and to customer data is controlled through scoped credentials and a principle of least privilege.

    • API credentials scoped per integration
    • Internal access requires explicit authorisation
    • Role-based model for team permissions
    • Access rights reviewed as the team changes

Data architecture

What we store, why, and how it is protected

Docklee processes context data on your behalf. This is what we store, under what controls, and how it stays yours.

We store what retrieval needs: the indexed knowledge chunks and their embeddings, the metadata you provide, and the audit trail. All of it stays scoped to your workspace, and you can delete it at any time.

You own your data. Always.

We do not use your context data to train models, improve our own systems, or share it with third parties. See our Privacy Policy for full details.

  1. Your ApplicationClient layer
    • Encrypted API connections
    • Scoped API credentials
    • Request authentication
  2. Context APIDocklee edge
    • Request auth and rate limiting
    • Tenant routing
    • Input validation
  3. Context EngineProcessing layer
    • Tenant-isolated processing
    • Ephemeral compute
    • Processing scoped to each request
  4. Storage LayerPersistence
    • Encrypted stored data
    • Logically separated tenant storage
    • Access controls on stored content
  5. Audit + ObservabilityCompliance layer
    • Structured event log
    • Trace context on operations
    • Audit trail available for your reviews

Compliance posture

Designed with enterprise compliance frameworks in mind

Aspirational, not a certification or legal guarantee.

  • SOC 2 Type II

    Security, Availability, Confidentiality

    On the roadmap

  • GDPR

    EU General Data Protection Regulation

    Designed around this

  • CCPA

    California Consumer Privacy Act

    Designed around this

  • ISO 27001

    Information Security Management

    On the roadmap

  • Designed around these standards: architecture reviewed against their requirements
  • Planned: on the roadmap for future work

Infrastructure

Hardened at every layer

  • Network Design

    • Network segmentation between components
    • Public and internal surfaces separated by design
    • Traffic handling reviewed in security assessments
    • Access to internal services restricted by default
  • Compute Practices

    • Workloads isolated from one another where feasible
    • Compute environments kept ephemeral where possible
    • Dependencies tracked and monitored for known issues
    • Build hygiene reviewed as part of engineering practice
  • Storage Practices

    • Stored data encrypted using current best practices
    • Access to stored data restricted by design
    • Data removal handled according to our retention policy
    • Storage configuration reviewed in security assessments
  • Resilience and Recovery

    • Infrastructure designed with resilience in mind
    • Recovery processes documented and maintained
    • Incident response procedures in place
    • Architecture reviewed for failure scenarios
  • Secrets Management

    • Credentials stored in dedicated secret stores
    • Access to secrets follows least-privilege principles
    • Credential lifecycle managed according to policy
    • Secret access is logged and reviewable
  • Software Supply Chain

    • Third-party dependencies tracked and reviewed
    • Known vulnerability reports monitored
    • Build pipeline integrity considered in design
    • Dependency hygiene part of engineering practice

Your data

Your data stays yours.

How Docklee treats the knowledge and memory you bring to the platform.

  • Never used for training

    Your context data is used solely to serve your application's requests. It is not used for model training or internal product development.

  • Operated by automation, not by reading your data

    Running Docklee relies on automated systems, metrics, and usage counts. Monitoring, support, and billing work from operational metadata, not from the contents of your knowledge or memory.

  • Yours to export and delete

    You can request an export of your data at any time. When you close your account, your stored data is deleted in line with our retention policy.

  • Reviews on your terms

    Security reviews, architecture walkthroughs, and custom data processing agreements are available for prospective and existing customers.

Responsible Disclosure

Security vulnerability reporting

If you discover a security vulnerability in Docklee, we ask that you report it responsibly. We will work with you to understand and address the issue, and keep you informed throughout the process.

  • We aim to acknowledge all reports promptly
  • No legal action for good-faith security research
  • Public credit offered if you would like it

Report a vulnerability

Response
We aim to respond promptly
Scope
All Docklee-owned systems

Security reviews

Have more questions for our
security team?

Enterprise security reviews, architecture walkthroughs, and custom data processing agreements are all available. Reach out and we will get back to you.