EYMINT
DocumentationAPI Reference
BlogDashboard
EYMINT
SectionsDocumentationAPI Reference

Getting Started

  • Keymint Documentation
  • Introduction
  • Getting Started
  • License Keys
  • Changelog

SDK References

  • Software Development Kits (SDKs)
  • Node.js SDK
  • Go SDK
  • Python SDK
  • C# SDK

Integration Guides

  • Integration Guides
  • Customer Portal for Vendors
  • Roles & Permissions
  • Radar Alert Destinations
  • Payment Provider Integrations
  • Stripe Subscription Licensing
  • Email Delivery
  • API Key Management
  • Webhook Deliveries
  • Analytics and Retention
  • Dashboard Workflows
  • Electron Licensing
  • PyQt Licensing
  • Tauri Licensing
  • Next.js SaaS Licensing

Licensing Guides

  • Licensing Concepts
  • Node-Locking & Machine Identifiers
  • Floating Licenses
  • Offline Verification
  • License Radar
  • Public Key Management and Rotation
  • Feature Flags
  • Webhooks & Events

Templates

  • Starter Templates
  • Electron License Starter
  • PyQt License Starter
  • Tauri License Starter
  • Next.js SaaS License Starter

Security & Trust

  • Security & Trust

Support

  • Frequently Asked Questions
  • Customer Portal
  • Using the Customer Portal
  • Workspace Settings and Roles

Legal

  • Privacy Policy
  • Subprocessors
  • Data Processing Agreement
  • Security Overview
  • Terms of Service
  • Service Level Agreement (SLA)
  • GDPR Compliance
Go to Dashboard

Getting Started

  • Keymint Documentation
  • Introduction
  • Getting Started
  • License Keys
  • Changelog

SDK References

  • Software Development Kits (SDKs)
  • Node.js SDK
  • Go SDK
  • Python SDK
  • C# SDK

Integration Guides

  • Integration Guides
  • Customer Portal for Vendors
  • Roles & Permissions
  • Radar Alert Destinations
  • Payment Provider Integrations
  • Stripe Subscription Licensing
  • Email Delivery
  • API Key Management
  • Webhook Deliveries
  • Analytics and Retention
  • Dashboard Workflows
  • Electron Licensing
  • PyQt Licensing
  • Tauri Licensing
  • Next.js SaaS Licensing

Licensing Guides

  • Licensing Concepts
  • Node-Locking & Machine Identifiers
  • Floating Licenses
  • Offline Verification
  • License Radar
  • Public Key Management and Rotation
  • Feature Flags
  • Webhooks & Events

Templates

  • Starter Templates
  • Electron License Starter
  • PyQt License Starter
  • Tauri License Starter
  • Next.js SaaS License Starter

Security & Trust

  • Security & Trust

Support

  • Frequently Asked Questions
  • Customer Portal
  • Using the Customer Portal
  • Workspace Settings and Roles

Legal

  • Privacy Policy
  • Subprocessors
  • Data Processing Agreement
  • Security Overview
  • Terms of Service
  • Service Level Agreement (SLA)
  • GDPR Compliance

GDPR Compliance

How Keymint approaches GDPR, data subject rights, international transfers, subprocessors, and safeguards for software licensing data.

Keymint is built to help software teams run licensing workflows while respecting privacy rights, limiting access, and keeping data handling visible.

Data Subject Rights

We support the following data subject rights under the General Data Protection Regulation (GDPR):

  • Right to be informed — Knowing what data we collect and how it is used.
  • Right of access — Requesting a copy of your personal data.
  • Right to rectification — Correcting inaccurate or incomplete data.
  • Right to erasure — Requesting deletion of your personal data.
  • Right to restrict processing — Limiting how we use your data.
  • Right to data portability — Exporting your data in a structured, machine-readable format.
  • Right to object — Objecting to data processing under specific conditions.
  • Rights related to automated decision-making — Guarding against fully automated processes with legal effects.

To exercise any of these rights, please email us at support@keymint.dev.

Primitives and Data Scope

Keymint processes the data needed to create accounts, verify license keys, manage customer records, process payments, respond to support requests, and protect the service from abuse.

We do not sell personal data. Analytics and marketing cookies are consent-based, and users can manage cookie preferences from the site footer at any time.

Safeguards

We implement appropriate technical and organizational measures to secure personal and licensing data:

  • Transport and Storage Protections: We use HTTPS/TLS for all traffic, end to end, encrypt our databases, servers and backups at rest, and apply industry-standard security controls around stored account, license, and operational data.
  • Scoped Access: Role-based access and scoped API keys reduce unnecessary access to licensing operations and customer records.
  • Provider Review: We rely on trusted service providers for payments, hosting, storage, and analytics, and strictly review the data each provider needs.

Subprocessors

Keymint relies on trusted subprocessors for hosting, database, payments, email delivery, security, monitoring, analytics, and AI features. The current list, with each provider's purpose and location, is on our Subprocessors page. Our Data Processing Agreement sets out how we process personal data on behalf of vendors.

Exercising Privacy Rights

If you need to exercise a privacy right, please send a request from the email address tied to your Keymint account so we can verify ownership:

  • Email: support@keymint.dev
  • Required Details: Please specify whether you are requesting access, correction, deletion, export, restriction, or objection.

On this page

  • Data Subject Rights
  • Primitives and Data Scope
  • Safeguards
  • Subprocessors
  • Exercising Privacy Rights