Back to PermitCore

Data Processing Agreement

Last updated: October 27, 2026  ·  Incorporates GDPR Article 28 requirements

This DPA forms part of the Terms of Service and is automatically applicable to all PermitCore customers who are subject to GDPR or similar data protection regulations. No signature is required — accepting the Terms of Service constitutes acceptance of this DPA.

1. Definitions

Project identity: permitcore · Zagreb, Croatia. Contact: info@permitcore.dev. Hosting residency is described separately in Security.

"Controller" means the Customer (Tenant) who determines the purposes and means of processing personal data through PermitCore. "Processor" means PermitCore, processing personal data on behalf of the Controller. "Data Subject" means any natural person whose personal data is processed. "GDPR" means Regulation (EU) 2016/679.

2. Roles and Subject Matter

PermitCore processes personal data as a Processor acting on behalf of the Controller (Customer). The subject matter is the provision of software license management services as described in the Terms of Service. Processing continues for the duration of the service agreement.

3. Categories of Personal Data Processed

PermitCore may process the following personal data as instructed by the Controller:

  • End-customer records: name, email address (if provided by Controller)
  • Activation records: IP address, country, city, user agent string at the time of license activation
  • License store orders: name, email, delivery address if physical delivery is configured
  • Support interactions: content of messages sent through the License Store portal

Controller account data (admin users' names and email addresses) is processed by PermitCore as a Controller for its own purposes, governed by the Privacy Policy.

4. Processing Instructions

PermitCore shall process personal data only on documented instructions from the Controller (via the PermitCore platform), unless required to do so by applicable law. If required by law, PermitCore shall inform the Controller before processing, unless legally prohibited from doing so.

5. Security Measures

PermitCore implements the following technical and organizational measures (TOMs):

  • AES-256-GCM passphrase encryption for default Admin creation; validation receives plaintext over HTTPS, while Store delivery and opt-in escrow use server-managed protection. Privileged platform access is described in the encryption/access reference.
  • Argon2id hashing for all passwords
  • TLS 1.2+ for all data in transit
  • Database encryption at rest
  • JWT authentication with short-lived tokens
  • TOTP multi-factor authentication support
  • Append-only audit logging of all data access and modifications
  • Role-based access control within each tenant

6. Sub-Processors

PermitCore uses the following sub-processors. The Controller authorizes these sub-processors as part of accepting these Terms. PermitCore will provide 30 days notice before adding new sub-processors:

Sub-Processor Purpose Location
Stripe, Inc. Payment processing and billing USA (SCC)
Cloud hosting provider Infrastructure and data storage EU
Google LLC (Google Workspace) Transactional email delivery USA (SCC)

7. Data Subject Rights

PermitCore will assist the Controller in fulfilling obligations regarding Data Subject rights (access, rectification, erasure, portability, restriction, objection) to the extent technically feasible. Controllers can export available account data and request erasure through the admin settings. Erasure is reviewed and completed by an operator; the request action is not an immediate deletion of every record. Requests that cannot be fulfilled through the platform should be sent to privacy@permitcore.dev.

8. Data Breach Notification

PermitCore will notify the Controller without undue delay upon becoming aware of a personal data breach affecting Controller data. The operator will use the registered account contact, provide available information about the nature, scope, likely consequences and mitigation, and supplement it as the investigation progresses. This processor obligation is separate from the Controller’s assessment of supervisory-authority notification under GDPR Article 33, where feasible within 72 hours. The incident procedure is human-operated, not a guarantee of automated notification or inbox delivery.

9. Data Deletion

Controllers should export their data before terminating service and request erasure at the contact below. Erasure requests are tracked with a 30-day due date and require human review and completion, subject to applicable legal retention and holds; termination alone does not trigger a verified automatic purge. New encrypted scheduled backups and deployment bundles use separate generations. Complete new copies become eligible for cleanup after 30 days after verification; holds, failed checks and retaining the newest deployment recovery point until replaced can extend that period. Legacy generations remain retained under operator-managed review and are outside automatic expiry. No automatic 90-day expiry of every backup is asserted. Recovery must account for previously approved erasure. Controllers may request deletion at privacy@permitcore.dev.

10. Audit Rights

PermitCore will provide reasonable information to demonstrate compliance with this DPA upon written request. On-site audits may be conducted with 30 days written notice, at the Controller's expense, and are limited to security and data processing practices relevant to this DPA.

11. Contact for DPA Matters

DPA inquiries: privacy@permitcore.dev