PermitPlane Data Processing Agreement
Last updated: 2026-11-11.
This Data Processing Agreement ("DPA") sets the GDPR Article 28 terms for personal data that PermitPlane processes for software vendors about their end users. It forms part of the PermitPlane Terms of Service and applies automatically when the Vendor accepts them. No separate signature is needed; a countersigned copy is available on request.
Parties
- Controller: the business that accepted the Terms (the "Vendor").
- Processor: Bitbat Oy, business ID 2602789-3, Latoniitty 3, 04500 Kellokoski, Finland ("PermitPlane").
Words such as personal data, processing, controller, processor, data subject and personal data breach have the meanings in the GDPR (Regulation (EU) 2016/679). If this DPA and the Terms conflict on data protection, this DPA wins.
1. Details of the processing (Art. 28(3))
| Item | Description |
|---|---|
| Subject matter | Hosting and operating the PermitPlane licensing service for the Vendor's software. |
| Duration | For as long as the Vendor uses the Service, plus the deletion period in section 5. |
| Nature of processing | Storing, organising, retrieving, transmitting and deleting data through the Service: issuing and checking licences, activating devices, sending portal sign-in links, delivering webhooks, producing metrics and audit logs, and syncing purchases through connectors the Vendor turns on. |
| Purpose | To provide the Service to the Vendor under the Terms, including security, support and abuse prevention. |
| Data subjects | The Vendor's end users (its customers and their staff who use the Vendor's software), and people named in licence or portal contact fields. |
| Personal data | Customer identifiers chosen by the Vendor; optional licence contact email (used for portal sign-in links); device and installation identifiers, device public keys and platform information (OS, app version); activation and validation records with timestamps; licence and entitlement records; IP addresses in request logs; purchase references from connected payment providers (order and customer IDs, not card data). |
| Special categories | None. The Vendor must not send special-category data or payment card data. |
| Location | Servers in Helsinki, Finland (Hetzner); sub-processors as listed in section 4. |
The Vendor controls which identifiers it sends. We recommend pseudonymous customer IDs rather than names.
2. Obligations of each party
PermitPlane will:
- process personal data only on the Vendor's documented instructions. The Terms, this DPA and the Vendor's use and configuration of the Service (console, API, MCP server, Agents acting with the Vendor's keys) are the instructions. We will tell the Vendor if we think an instruction breaks data protection law, unless the law forbids it;
- process data for other purposes only where EU or Finnish law requires it, and tell the Vendor first unless that law forbids it;
- make sure everyone authorised to process the data is bound by confidentiality;
- take the security measures in section 3 (Art. 32);
- use sub-processors only as set out in section 4;
- help the Vendor answer data subject requests and meet its duties under Articles 32 to 36, as in section 5;
- delete or return the data at the end of the Service, as in section 5;
- make available the information needed to show compliance with Article 28, and allow audits, as in section 5.
The Vendor will:
- have a lawful basis for the data it sends, and give its end users the information required by Articles 13 and 14, including that PermitPlane processes data for it;
- send only the data needed for licensing, and no special-category or card data;
- handle requests from its end users, using the tools in the Service;
- keep its own credentials, API keys and Agent keys secure, and review what its Agents do;
- tell PermitPlane promptly if it learns of a breach involving the Service.
3. Security measures (Annex 1)
PermitPlane keeps at least these measures in place and may improve them.
| Area | Measure |
|---|---|
| Hosting | Servers at Hetzner in Helsinki, Finland, behind a provider firewall. |
| Encryption in transit | TLS for all public endpoints; secure-only, HttpOnly session cookies. |
| Encryption at rest | Stored licence keys and purchase connector credentials are encrypted at application level (Fernet). |
| Licence integrity | Licence grants are signed by the Service; signing keys never leave it. Each device has its own key held in OS-protected storage. |
| Access control | Workspace users must verify their email and use multi-factor authentication. Roles limit access to assigned products and environments. API and Agent keys are scoped, expire, and can be revoked; production changes by Agents can require human approval. |
| Administrator access | Server administration only through a private network (Tailscale) with SSH keys; no public SSH. |
| Logging and monitoring | Audit log of console and API actions. Application logs and error reports are scrubbed of API keys, tokens, licence keys and other secrets before they leave the server; error reports are sent without default PII and without request bodies. |
| Backups | Daily local PostgreSQL backups on the same server, kept for 7 days. There is no off-site copy. |
| Abuse protection | Rate limits on sign-in links, key reveals and API calls; protection against server-side request forgery for webhooks. |
| Data minimisation | When enabled, sandbox data is pruned after a retention window, and idle free workspaces are closed and their personal contact data cleared. |
| People | Access only for staff who need it, under confidentiality. |
4. Sub-processors
The Vendor gives general authorisation for PermitPlane to use sub-processors. The current list is kept on the sub-processors page and is also set out here:
| Sub-processor | What it does with end-user data | Location |
|---|---|---|
| Hetzner Online GmbH | Hosts the servers, database and local backups | Finland (Helsinki) |
| Brevo (Sendinblue SAS) | Sends portal sign-in emails to end users (not yet enabled) | EU (France) |
| Functional Software, Inc. (Sentry) | Receives error reports, scrubbed of secrets and default PII; may include identifiers or IP addresses | EU data region (Germany) |
| Grafana Labs | Stores operational logs and metrics, which may include IP addresses and identifiers | EU region |
Not sub-processors for end-user data: Tailscale (private admin network; it carries no end-user records), Stripe (bills PermitPlane's own subscriptions; a Vendor's own Stripe or Paddle account connected through a purchase connector is the Vendor's own provider) and Google (vendor staff sign-in only).
Changes. We will announce a new or replacement sub-processor at least 30 days before it starts processing, by email to workspace owners and on the sub-processors page. The Vendor may object on reasonable data protection grounds within that period. We will then try to find a solution; if we cannot, the Vendor may end the affected Service and get a refund of prepaid Fees for the unused period.
We impose data protection duties on each sub-processor that are at least as protective as this DPA, and remain responsible to the Vendor for their work.
5. Assistance, breaches, deletion and audits
Data subject requests. The Service lets the Vendor find, export, correct and delete end-user records (console, management API, audit log export). If an end user contacts PermitPlane directly, we pass the request to the Vendor without undue delay and do not answer it ourselves unless the Vendor asks. Further help beyond the self-service tools may be charged at reasonable cost.
Other assistance. We give reasonable help with the Vendor's data protection impact assessments and prior consultations (Art. 35 and 36), using the information available to us.
Personal data breaches. We notify the Vendor without undue delay after becoming aware of a breach affecting its data, with the aim of doing so within 48 hours. The notice goes to workspace owners' email and includes what we know of the nature of the breach, the data and people affected, likely consequences, and the measures taken or proposed. We add details as they become available. The Vendor decides whether to notify the supervisory authority and data subjects; we help as needed.
Deletion and return. Before the Service ends, the Vendor can export its data. After the end, we delete end-user data within 90 days, unless EU or Finnish law requires us to keep it. Backups are kept for 7 days and then overwritten, and are not restored except for disaster recovery. On request, we confirm deletion in writing.
Audits. We make available the information needed to show compliance, such as this DPA, the security summary and sub-processor list, and answers to reasonable security questionnaires once a year. If that is not enough, or an authority requires it, the Vendor (or an independent auditor bound by confidentiality) may audit on 30 days' notice, during business hours, at the Vendor's cost, and in a way that does not expose other customers' data. Not more than once a year unless there was a breach.
6. Transfers, liability and final terms
International transfers. PermitPlane stores end-user data in the EU. A sub-processor may transfer data, or allow access, outside the EU/EEA only with a valid safeguard under GDPR Chapter V: an adequacy decision (including the EU-US Data Privacy Framework for certified US companies) or the European Commission's Standard Contractual Clauses (Decision 2021/914), Module 3 (processor to processor), with supplementary measures where needed. If a Vendor established outside the EU/EEA uses the Service, the parties agree that the SCCs Module 4 (processor to controller) apply where required. The General Court upheld the Data Privacy Framework on 3 September 2025; an appeal is pending, and we will rely on SCCs if it falls.
Liability. Each party's liability under this DPA is subject to the limits in the Terms (the Fees paid for the Service in the 12 months before the event giving rise to the claim; for free use, only liability required by mandatory law), except where the GDPR or other law does not allow a limit. Article 82 GDPR continues to apply towards data subjects.
Duration. This DPA lasts as long as PermitPlane processes personal data for the Vendor.
Changes. We may update this DPA to reflect changes in law, sub-processors or the Service, with notice as in the Terms. Changes will not lower the overall level of protection.
Law and venue. As in the Terms: Finnish law; disputes in the court named in the Terms (the District Court of Itä-Uusimaa).
Contact. Privacy contact: Rami Koivunen, privacy@permitplane.com (data protection); legal@permitplane.com (contract), support@permitplane.com (support).
See also: Terms of Service, Privacy Notice, Sub-processors.