Claude Code GDPR

Make Claude Code controllable inside the company.

Claude Code is attractive for developers, but a local CLI alone is not an enterprise operating model. 2342.ai sits in front as a controlled gateway: team policy, budget, logging, model routing and one invoice.

Create access View API gateway

Platform, not individual access

The CLI workflow stays. Control moves into the platform.

2342.ai does not sell direct provider accounts or third-party API keys. Customers receive access to the 2342.ai platform. Third-party models may be used as technical infrastructure components and subprocessors for selected platform functions.

POST /v1/messages POST /v1/responses policy.check() route.model() meter.usage()

Team policy

Not every developer decides alone

Workspace rules define which model configurations, data classes and budgets are allowed for coding workflows.

  • Approved models per workspace
  • Budget limits per team
  • API key management
  • Visible usage and cost

GDPR

Sensitive data needs an approved mode

For personal data, not every available model should be allowed. 2342.ai can restrict providers and models per workspace and approve only documented configurations.

  • DPA available
  • Subprocessor list
  • Deletion and retention per feature
  • Customer data is not used for training by 2342.ai

Billing

One invoice for platform and routed usage

Usage credits cover routed model execution, gateway processing, policy enforcement, metering and provider costs. Usage stays part of the governed 2342.ai platform service.

Rollout

Governance first. Then scale usage.

01

Set workspace policy

Define which teams, data classes, budgets and models are approved.

02

Connect API or tool

Connect existing integrations to 2342.ai with minimal changes.

03

Measure and refine usage

Keep cost, model routing and data paths visible over time.

Is 2342.ai a Claude Code reseller?

No. Customers receive access to the 2342.ai platform. Third-party models may be used as technical infrastructure components and subprocessors for selected platform functions.

Are all models automatically GDPR-compliant?

No. The right approach is an approved GDPR mode: admins decide which provider and model configurations are allowed for sensitive data.

What happens to existing tools?

OpenAI-style or Anthropic-style integrations can connect with minimal changes. The endpoints remain 2342.ai platform endpoints with policies, routing, billing, rate limits and logs.