Legal
Privacy Policy
1. Who we are
Liminal Keys is operated by Liminal Keys, SL (LIMINAL KEYS, SOCIEDAD LIMITADA), NIF B05897715, Calle Arzobispo Morcillo 52, Madrid, Spain. Registered with the Commercial Registry of Madrid, sheet 902316, entry 10/2026/25368, 1st inscription, dated 11 November 2026. ("Liminal Keys", "we"). Privacy and legal contact: legal@liminalkeys.com. Product questions: contact@liminalkeys.com.
2. What this policy covers
This policy covers the website liminalkeys.com and the Liminal Keys service:
- Liminal Console (console.liminalkeys.com), where administrators manage organizations, signing identities, devices, CI trusts, AI agents, policy rules and audit;
- the Liminal Keys API (api.liminalkeys.com);
- Liminal Keys for Mac and the liminal-keys CLI (including the setup-liminal-keys GitHub Action and Linux and Windows runners);
- AI agents and the MCP connector (mcp.liminalkeys.com) and the liminalkeys-sign skill;
- LK Approvals, the approval inbox web app (installable as a PWA), with optional push notifications;
- the optional App Store Connect upload and token broker.
LK Attach has its own privacy policy.
3. What Liminal Keys is, in one paragraph
Liminal Keys lets your organization sign with its own certificates while the private keys stay in cloud custody. Private signing keys are held non-exportable and software-protected in Azure Key Vault (Microsoft Azure, West Europe region). Hardware security module (HSM) custody is on the roadmap and is not available today. Every signature is checked against the policy rules your organization applies and is recorded in an audit log. Liminal Keys is not a qualified trust service provider: it does not provide qualified electronic signatures, seals or timestamps.
4. Our role: controller or processor
| Data | Our role | Document |
|---|---|---|
| Console accounts and sign-in, billing, contact messages, website logs, security logs of our own systems | Controller | This policy |
| Your organization's data in the service: its users, groups, devices, signing identities and certificate metadata, CI trusts, AI agents, policy rules, approval requests, preview images, document labels, digests and sign audit | Processor on behalf of your organization (the controller) | Data Processing Addendum (available on request at legal@liminalkeys.com) |
If you are a user of an organization's workspace, your organization decides how the service is used; contact it first for requests about its data. We will help it answer.
5. What data we process
Account and sign-in. Name, email address and identifiers from the sign-in provider you use (Microsoft work or school account, Google or Apple, handled through Microsoft Entra ID / Entra External ID), organization (tenant) membership and role, and linked sign-in methods.
Organization and signing data. Signing identities and their public certificates and metadata (subject, issuer, serial, validity, fingerprint), enrolled devices and signer nodes, CI trusts (for example GitHub owner, repository and repository ID used for OIDC), policy rules and their versions. We never store private key bytes outside Key Vault. When you generate a key in Console, it is created inside Key Vault. When you import a PKCS#12 file or an App Store Connect .p8 key, the key passes once through our API, in memory, on its way into Key Vault, and cannot be exported afterwards.
Signing requests and audit. For each signature request: outcome, time, signing identity, the device, CI run or AI agent that asked, and the rule applied. We also keep the digest that was signed, as its SHA-256 fingerprint and the full digest hash, and for AI-agent requests the document label the agent sends. Console shows a 16-character snippet of the hash and lets you copy the full value. The audit never stores the raw document, the signature or any key. We do not receive or store the documents or files you sign: the service signs a hash, not the content.
AI agents. Agent names, optional signing caps, and API keys (lkag_…). Each key is shown in plain text only once, when it is issued; we store only a SHA-256 hash of the full key, so we cannot show it again or recover it. Every MCP response is wrapped in a signed response envelope that contains a nonce, the agent ID and a timestamp.
Approvals. When a rule requires approval, we create an approval request with the agent, document label, digest, the approvers named in the rule, its status, who decided and when, and the time it expires (default 10 minutes). The agent may attach up to three preview images (PNG, JPEG or WebP, up to 1 MiB each) so approvers can see what they are approving. Preview images are produced by your agent; we do not check that they match the digest. We delete preview images as soon as the request is approved, rejected or expires, and keep only their number and a hash.
Push notifications. If an approver turns on notifications in LK Approvals, we store that browser's push subscription (endpoint and keys). Each notification contains the title "Signing request", the agent name and the document label. It is sent encrypted through the push service of the approver's browser or device maker (for example Apple, Google, Mozilla or Microsoft). You can turn notifications off in the browser at any time.
Timestamps. Timestamps are optional and off unless configured. When used, we send only the digest (or a timestamp request built from it) to a third-party time-stamping authority, by default FreeTSA (freetsa.org). FreeTSA is not a qualified service, and its timestamps carry no legal presumption that the time is accurate. No names, document labels or files are sent.
App Store Connect broker. If you use it, we hold your App Store Connect API key in Key Vault and use it, on your instructions, to issue short-lived tokens and upload builds to Apple. Apple processes that data under its own terms.
Billing. Plan, subscription status, invoices, billing contact and address, VAT number, and Stripe customer and subscription IDs. Card details are collected by Stripe; we never see full card numbers.
Email. Transactional emails (welcome, end-of-beta and conversion notices, payment issues) and messages you send to our @liminalkeys.com addresses.
Technical logs. IP address, user agent, requested path, time and error codes from our API, Console, MCP server and website, for security and troubleshooting. Logs do not contain private keys, signatures or document content.
6. Why we process it and on what legal basis
| Purpose | Legal basis (GDPR) |
|---|---|
| Providing the service, sign-in, support, transactional email | Contract, art. 6(1)(b) |
| Processing your organization's data | On your organization's instructions under the DPA (art. 28) |
| Billing, invoicing, tax and accounting | Legal obligation, art. 6(1)(c) |
| Security, abuse prevention, audit integrity, logs | Legitimate interest in a secure signing service, art. 6(1)(f) |
| Push notifications | Your choice to turn them on in the browser; you can turn them off at any time |
| Product news by email (if we ever send it) | Consent, art. 6(1)(a), asked for separately |
The policy engine automatically allows or refuses a signature according to the rules your organization sets. This is not a decision about you with legal or similarly significant effects in the sense of GDPR art. 22.
7. Who receives data (subprocessors and other recipients)
| Recipient | What for | Role | Location |
|---|---|---|---|
| Microsoft Ireland Operations Ltd. (Azure: App Service, SQL Database, Key Vault, Static Web Apps, Azure DNS, Communication Services Email; Entra ID / External ID; Microsoft 365 for our mailboxes) | Hosting, key custody, database, email, sign-in | Subprocessor | EU (Azure West Europe region, Netherlands; Communication Services Email: Europe) |
| Stripe Payments Europe, Ltd. | Payments and invoices | Subprocessor; independent controller for payment and fraud data | EU and US |
| FreeTSA (freetsa.org) | Timestamps, only when enabled | Recipient of digests | Outside our control; only the document hash is sent |
| Google, Apple, Microsoft as sign-in providers | Authenticating you | Independent controllers | Under their own terms |
| Browser push services (Apple, Google, Mozilla, Microsoft) | Delivering encrypted push notifications | Recipients | May be outside the EEA |
| GitHub | Verifying OIDC tokens from your CI workflows | Independent controller | US |
| Apple (App Store Connect) | Uploads and tokens you request | Independent controller, on your instructions | US |
The website, Console, API and MCP connector are hosted entirely on Microsoft Azure; we do not use a third-party CDN or proxy. Our domain registrar only points our domain names to Azure DNS and receives no personal data about you.
The AI assistant you connect to the MCP connector (for example Claude) is your own provider under its own terms, not our subprocessor. We announce changes to our subprocessors by email at least 30 days in advance for business customers under the DPA.
8. International transfers
Production runs in Microsoft Azure's West Europe region. Where a provider processes data outside the EEA (for example Stripe, sign-in providers or push services in the US), the transfer relies on the EU-U.S. Data Privacy Framework where the provider is certified, or on the European Commission's Standard Contractual Clauses.
9. How long we keep data
| Data | Retention |
|---|---|
| Account and organization data | While the subscription or beta account is active, then 90 days, then deleted |
| Private keys in Key Vault | Until you remove the identity or the account ends. The keys are then soft-deleted: they can no longer be used to sign but stay recoverable for 90 days, then they are permanently purged. Purge protection is on, so nobody, including us, can purge them earlier |
| Sign audit and approval records (including digest hashes) | 24 months or as set in the DPA, so your organization can prove what was signed |
| Preview images | Deleted when the request is decided or expires (default 10 minutes) |
| Push subscriptions | Until notifications are turned off, the approver is removed, or the subscription stops working |
| Billing records and invoices | As long as tax and commercial law requires (generally 6 years, Spanish Commercial Code art. 30) |
| Technical logs | 90 days |
| Contact messages | 24 months after the last exchange |
10. Security
Private keys are non-exportable and software-protected in Azure Key Vault and never reach Console, the Mac app, the CLI or AI agents. Signing is deny by default. Access is protected with encryption in transit and role-based access. No system is perfectly secure. If a personal-data breach affects you, we will notify the AEPD within 72 hours where required and tell affected customers without undue delay.
11. Your rights
You can ask for access, rectification, erasure, restriction, portability, or object to processing, and withdraw any consent, by writing to legal@liminalkeys.com. We reply within one month. If your request concerns your organization's data, we will pass it to your organization. You can complain to the Agencia Española de Protección de Datos (www.aepd.es) or to the supervisory authority where you live.
12. Cookies and local storage
The website does not use analytics or advertising cookies. Console and LK Approvals store sign-in session data in your browser, which is strictly necessary to keep you signed in. Console and LK Approvals use browser local and session storage only: Microsoft sign-in library (MSAL) session keys (msal.*), liminal.keys.authAuthorityKind (which sign-in path you used), liminal.keys.signupAfterAuthReset (a one-time sign-up marker) and lk.gettingStarted.dismissed (remembers that you closed the getting-started panel). If you allow web push in LK Approvals, your browser stores a push subscription. These are strictly necessary or remember a choice you made, so they need no consent (LSSI art. 22.2). We do not set analytics or advertising cookies.
13. Changes
We will post changes here and, for material changes, notify account administrators by email before they apply.