Summary: PermitCore is a B2B SaaS platform. We collect minimal data necessary to provide the service. Eligible public pages use Google Analytics Consent Mode v2 with limited cookieless measurements while storage is denied. Analytics cookies and custom signup/checkout events require acceptance in our cookie preferences. If you use our "Permit AI" chat widget, your question and matching documentation excerpts are sent to Anthropic to generate a reply. You can change optional analytics preferences at any time. We do not sell your data.
1. Who We Are
Project operator name: permitcore. Project location: Zagreb, Croatia. Contact: info@permitcore.dev. This is the project identity, not a claim of a separately incorporated company. Hosting location is described separately in our security information.
PermitCore ("we", "us", "our") is a software-as-a-service platform for license key management. Our service is provided to businesses (tenants) and their administrators.
For GDPR purposes, PermitCore acts as a Data Controller for account and billing data, and as a Data Processor for data tenants upload or generate (e.g. license keys, customer records).
2. Data We Collect
2.1 Account Data
- Name and email address (required to create an account)
- Password (stored as Argon2id hash — never in plaintext)
- Company name and account tier
- IP address and user agent at time of login (for security)
- MFA secret (stored encrypted at rest)
- Billing country and, if you provide one at checkout, a tax identification number (e.g. an EU VAT ID) — collected to calculate applicable tax
2.2 Service Data (Tenant-Uploaded)
- License keys (encrypted with AES-256-GCM; we store only the ciphertext and a keyed HMAC-SHA256 lookup value)
- Customer email addresses (for license assignment)
- Product and order information
- Audit log entries (all administrative actions)
2.3 Usage Data
- API call logs (IP address, endpoint, response code, timestamp)
- Activation and validation events for license keys
- Dashboard analytics (aggregate, not personal)
3. Sub-Processors & Third-Party Services
We use the following sub-processors that may receive personal data:
The Admin Leaflet library is served from our own host, including on the sign-in page. Opening authenticated geographic maps can still request tiles from the configured tile provider; hosting the library locally does not eliminate those map requests.
| Service | Purpose | Data Shared | Location |
|---|---|---|---|
| Stripe | Payment processing; for eligible plans, merchant of record via Stripe Link (see below) | Billing name, email, payment details, billing country, tax ID if provided | US (SCCs) |
| Hetzner / cloud host | Infrastructure & database hosting | All data at rest | EU |
| Google Analytics (GA4) | Eligible public marketing and registration usage — limited cookieless measurements while storage is denied; analytics cookies and custom events require Analytics consent; private Admin areas, internal/test traffic and marked internal browsers are excluded (see our Cookie Policy) | Page/request and consent information in denied mode; after consent, pages viewed, referrer, approximate location, device/browser type, pseudonymous client identifier, signup events and confirmed checkout plan, transaction reference, amount and currency — no card, billing address, license data or private Admin content | US (SCCs) |
| Anthropic (Claude API) | Generates replies for the "Permit AI" chat widget on this website — only when that widget is enabled and you choose to use it | The message you type and excerpts from PermitCore's own public documentation — no account data, no browsing history | US (SCCs) |
Stripe Managed Payments / Link disclosure: For eligible plans, your purchase may be completed through Stripe's Managed Payments service. When it is, Stripe (through its Link service) is the merchant of record for that transaction — it independently determines how it calculates and remits indirect tax (VAT/GST/sales tax), screens for fraud, and handles payment disputes and transaction-level support for that purchase, in addition to processing the payment on our behalf. See Stripe's own Privacy Policy for how it uses your data in that capacity.
License Store checkout providers: New Store checkouts support Stripe, Paddle and Lemon Squeezy. Each vendor chooses one Stripe, Paddle or Lemon Squeezy account for its Store. Checkout sends the order reference and required customer details to that provider; payment details are entered with the provider. Payment events return the transaction and customer information needed to deliver licenses and retain payment history. Paddle and Lemon Squeezy act as merchant of record under their respective terms and privacy policies. See Paddle privacy and Lemon Squeezy privacy for their processing and international transfers.
4. Legal Basis for Processing (GDPR)
- Contract performance — Account data, license data, billing data processed to deliver the service
- Legitimate interest — Security audit logs, fraud prevention, abuse detection
- Consent — Marketing communications (opt-in only)
- Legal obligation — Billing records retained where required by applicable obligations and reviewed legal holds
5. Data Retention
- Account data: Retained while the account is active; erasure requests have a 30-day review due date, with human completion and applicable legal holds. This is not an automatic purge of every copy
- Audit logs: Tenant cleanup follows plan windows — 7 days (Free), 30 days (Starter), 90 days (Professional), unlimited (Enterprise). Daily maintenance records committed batch counts; failures can leave earlier batches completed and other rows pending. System audit cleanup is a separate operator-controlled scope, disabled by default. These are not exact-time deletion or backup-erasure guarantees
- Server logs: Application file logs retain 30 daily rolling files; host, proxy and container logs have separate operational limits
- License activation events: the daily minimization job clears IP address, country/city and end-user email on records older than the configured retention window (365 days by default), including when the IP is already empty. This is not an exact expiry-time deletion guarantee. The activation record, date, device binding and license relationship remain; other device/software metadata and retained backups have separate review and retention boundaries
- Billing records: Reviewed against applicable legal obligations; no universal automatic seven-year deletion rule
New scheduled database backups and deployment snapshots use separate GPG-encrypted generations. Complete new copies become eligible for cleanup after 30 days, after verification; holds, failed checks and retention of the newest deployment recovery point until replaced can extend that period. Existing legacy generations are retained separately under operator-managed review and are outside automatic expiry. Older gzip rollback copies are not encrypted merely by compression. Erasure review must include retained copies and prevent reintroduction after recovery. See the security and recovery boundaries.
6. Your Rights (GDPR)
If you are in the EU/EEA, you have the following rights:
- Right of access — Request a copy of your personal data
- Right to rectification — Correct inaccurate data
- Right to erasure — Request deletion (subject to legal retention requirements)
- Right to portability — Export your data in machine-readable format
- Right to object — Object to processing based on legitimate interest
- Right to restrict processing — Limit how we use your data
To exercise any right, email: privacy@permitcore.dev. We respond within 30 days.
Browsers may send Content Security Policy diagnostics to our own API. The collector stores only grouped surface, directive, source-family and report/enforcement labels, counts and timestamps in server memory for up to 24 hours. Raw report URLs, query parameters, tokens, script samples and user identities are discarded; restarting clears these diagnostic counts. No external reporting service is used. Ordinary server/proxy access logs follow their separate retention limits above.
7. Security
- All data in transit encrypted via TLS 1.2+
- Default Admin-created license ciphertext uses browser/passphrase encryption. Validation/activation receive plaintext keys over HTTPS; Store delivery material uses server-managed protection and opt-in escrow permits audited SuperAdmin passphrase recovery. See the encryption and access boundary.
- Passwords stored as Argon2id hashes with per-user salts
- MFA secrets encrypted at rest
- Security headers (HSTS, X-Frame-Options, CSP) on all responses
- Application encryption protects selected fields; this is not a claim of database-wide transparent data encryption (TDE).
8. Cookies
Admin panel authentication uses JWT tokens stored in browser local storage, not a cookie. See our Cookie Policy for the complete, current list of cookies this site uses and how to control them.
9. Data Transfers Outside the EU
Stripe is US-based. Transfers are covered by Standard Contractual Clauses (SCCs). All other primary infrastructure is EU-based.
10. Changes to This Policy
We will notify account holders by email at least 14 days before any material changes take effect. The current version is always available at this URL.
11. Contact
PermitCore Data Controller
Email: privacy@permitcore.dev
For GDPR requests: privacy@permitcore.dev
© 2026 PermitCore. All rights reserved. · Home · Privacy Policy