Skip to content

Solutions / Security & compliance

GDPR and data protection

Minimize and localize the personal data involved in licensing — or keep it entirely inside your own systems.

The challenge

Under GDPR you are accountable for the personal data your processors handle. A licensing service that stores customer identifiers, in a region you do not control, adds a processor to your data map and enlarges your risk and your obligations.

The lower-risk path is to process less personal data, keep what you do process where you choose, and — where possible — avoid adding a third-party processor at all.

1 Self-host no third-party processor
2 Localize keep EU data in the EU
3 Minimize keys, not personal troves
4 Control access, retention, deletion

How Delta1 Labs helps

A layered approach

1

Self-host to avoid a processor

Run licensing inside your own infrastructure so no personal data is shared with a third party at all — the cleanest way to keep your data map small.

2

Localize

Choose the region your data lives in and keep EU data in the EU.

3

Minimize

Licensing operates on keys, machine fingerprints and entitlements — not on large stores of personal data.

Capabilities

What you get

Self-hosted keeps data in-house
No third-party processing of personal data.
Regional / EU residency
Run where your obligations require.
Data minimization by design
Keys and fingerprints, not personal troves.
Audit log of access
See who did what, when.
Encrypted secrets at rest
Signing keys protected under your KEK.
Deletion under your control
You own the database and its lifecycle.

Built with

Outcomes

  • Fewer processors on your data map.
  • EU data stays in the EU.
  • Less personal data at rest overall.
  • Retention and deletion in your hands.

Frequently asked

Questions, answered

Is Keyright a data processor for us?

In a self-hosted deployment, no — the service runs in your infrastructure and we process no personal data on your behalf. On the managed service we act as a processor under our terms.

What personal data does licensing need?

Very little — typically a license key, an optional email for the portal, and a machine fingerprint for node-locking. It is designed around minimization.

Let's talk about your setup

Tell us what you're building — we'll help you protect, license and ship it, managed or self-hosted.