Draft: this text has not yet been reviewed by a lawyer and is not binding. Highlighted parts are still to be filled in.
DRAFT for legal review. Placeholders in
[[ ]]. Reviewer: decide whether to base this on the European Commission's standard contractual clauses for controllers and processors (Implementing Decision (EU) 2021/915) instead of a custom text.
Between the Customer (the organization using PulseIQ Cloud, "Controller") and JiraSoft Group sp. z o.o., ul. Księcia Witolda 49/15, 50-202 Wrocław, KRS 0001109139, NIP 8982308518 ("Processor"). This agreement forms part of the Terms of service and applies automatically when the Customer uses the Service; Enterprise customers may sign it separately.
1. Subject and duration
1.1 The Processor processes personal data on behalf of the Controller to provide PulseIQ Cloud as described in Annex I.
1.2 This agreement lasts as long as the Processor processes personal data for the Controller under the Terms.
2. Instructions
2.1 The Processor processes the data only on the Controller's documented instructions. The Terms, this agreement and the Controller's settings in PulseIQ (projects, retention, masking, erasure requests, integrations) are the instructions. Further instructions must be in writing (e-mail is enough).
2.2 The Processor tells the Controller without delay if it believes an instruction breaks the law, and may suspend that instruction until the Controller confirms or changes it.
2.3 If EU or Member State law requires the Processor to process the data otherwise, it informs the Controller beforehand, unless that law forbids it.
3. Confidentiality
The Processor ensures that everyone authorised to process the data is bound to confidentiality and has access only as far as their work needs.
4. Security
4.1 The Processor implements the technical and organisational measures in Annex II and keeps them up to date with the state of the art. It may replace measures with equivalent or better ones.
4.2 Personal data breaches: the Processor notifies the Controller without undue delay and at the latest within 48 hours after becoming aware of a breach affecting the Controller's data, with the information it has (nature, categories and approximate numbers concerned, likely consequences, measures taken), and supplements it as it learns more.
5. Subprocessors
5.1 The Controller gives general authorisation for the subprocessors in Annex III.
5.2 The Processor informs the Controller at least 30 days before adding or replacing a subprocessor (by e-mail to the organization owners and on pulseiq.com/legal/subprocessors). The Controller may object on reasonable data protection grounds within that period; if no solution is found, the Controller may end the contract before the change takes effect and receives a refund of prepaid fees for the remaining period.
5.3 The Processor imposes the same data protection obligations on each subprocessor by contract and remains liable for them.
6. Transfers outside the EEA
Customer telemetry (Annex I) is stored and processed only in the EU region the Controller chose. The Processor does not transfer it outside the EEA. Any future transfer requires a valid mechanism under Chapter V GDPR and the procedure in section 5.
7. Assistance
7.1 Data subject requests: the Service lets the Controller find, export and erase a person's data itself (GDPR erasure covers every data table and stored session recordings). If a request reaches the Processor, it forwards it to the Controller and does not answer it itself.
7.2 The Processor helps the Controller with security, breach notifications, data protection impact assessments and prior consultations, as far as the Processor's information allows. Reviewer: reasonable costs for assistance beyond the Service's features?
8. Deletion and return
8.1 During the contract, data is deleted according to the retention set per project and on erasure requests.
8.2 When the contract ends, the Controller can export its data until the end date. The Processor then deletes all personal data within 30 days and from backups within a further 30 days, unless EU or Member State law requires it to be kept, and confirms the deletion on request.
9. Audits
9.1 The Processor makes available the information needed to show compliance: this agreement, Annex II, the security overview, and the summary of the latest independent penetration test once available.
9.2 The Controller may audit the Processor, itself or through an independent auditor bound to confidentiality, once a year with 30 days' notice, during business hours and without disrupting operations, or at any time after a personal data breach. Reviewer: costs; remote audits first.
10. Liability
Liability is governed by the Terms, subject to Art. 82 GDPR. Reviewer: separate cap for data protection?
Annex I: Description of processing
| Nature and purpose | Collecting, storing, analysing and displaying telemetry from the Controller's applications: product analytics, error tracking, session replay, performance monitoring, tracing, customer-account health, alerts. |
| Data subjects | Users of the Controller's websites and applications; the Controller's own staff where they use those applications. |
| Categories of data | Pseudonymous identifiers (anonymous browser id, session id) and, if the Controller sends them, user ids and account ids; traits the Controller sends with identify and group (for example plan, company name); events and their properties; page URLs and referrers (sensitive query parameters removed by the SDK); browser, operating system and device type; approximate location (country, region, city; coordinates rounded to about 10 km), derived from the IP address, which itself is never stored; error messages, stack traces and breadcrumbs (recent clicks and navigations); session recordings of the page structure and interactions, with all text and inputs masked by default; performance measurements and traces. |
| Special categories | None. The Controller must not send them (Terms 4.2). |
| Masking by default | Property names that look sensitive (password, token, secret, card, IBAN, PESEL, NIP, …), values that look like e-mail addresses or card numbers, and sensitive URL parameters are replaced by [Filtered] before data leaves the SDK. |
| Retention | Per project, set by the Controller. Defaults: events 395 days, errors 90 days, session recordings 30 days, traces 30 days. |
| Location | The EU region chosen at sign-up: Germany (Falkenstein) or Finland (Helsinki). Dedicated instances: the Hetzner location agreed in the contract (Falkenstein, Nuremberg or Helsinki). |
| Duration | The term of the contract, plus the deletion periods in section 8. |
Annex II: Technical and organisational measures
Encryption
- TLS for all traffic between browsers, SDKs and the Service; HSTS.
- Secrets in the application database (SSO client secrets, integration tokens) are encrypted with the application key. Passwords are hashed with bcrypt; API keys, SCIM tokens and personal tokens are stored only as SHA-256 hashes.
- Cloud: encryption at rest of the ClickHouse, Postgres and object storage volumes; describe the actual setup of the production servers.
Separation of customers (tenant isolation)
- Every query for customer data is forced through a layer that refuses queries without the organization and project filter.
- The SQL editor runs as a separate database user per project, read-only, with a row policy limited to that project.
Access control
- Customers: roles per organization and project, single sign-on (SAML, OIDC) with verified domains, SCIM provisioning, append-only audit log of access changes, key changes, integrations and data exports.
- JiraSoft staff: access to production only for the people who operate the Service, with personal accounts, SSH keys and multi-factor authentication; access logging.
Data minimisation and privacy by default
- Masking in the SDKs and in session recordings as in Annex I; IP addresses are used only for the approximate location and are not stored.
- Retention per project with automatic deletion; erasure of a person in every table and in stored recordings; events that arrive late for an erased person are dropped.
Application security
- Content Security Policy that allows only the application's own scripts; secure, HttpOnly session cookies; CSRF protection; rate limits on sign-in and APIs; outgoing webhooks limited to public HTTPS addresses.
- Automated dependency audits and static analysis in continuous integration; OWASP ZAP baseline scans; an independent penetration test before general availability and yearly after that once done.
Availability and resilience
- Data is accepted into durable queues before processing; tested so that worker, database and queue failures lose no data.
- Monitoring every minute with a public status page; encrypted database backups before every update and on a schedule: describe frequency, location and restore tests for the cloud.
Organisation
- Confidentiality obligations for all staff; security training; incident response procedure with notification as in section 4.2.
Annex III: Subprocessors
| Subprocessor | Service | Data | Location |
|---|---|---|---|
| Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany | Servers and storage (infrastructure) | All data of the region | Germany or Finland, as chosen |
| E-mail provider | Sending service e-mails and alert notifications | E-mail addresses of the Customer's members; alert texts | EU |
| Stripe Payments Europe, Ltd., Ireland | Payments, invoices, tax | Billing contact and payment data only, no telemetry | EU / USA Reviewer: controller or processor, see README question 7 |
Integrations that the Customer turns on itself (Slack, Microsoft Teams, Jira, GitHub, GitLab, webhooks, its identity provider) are not subprocessors of JiraSoft: data is sent there on the Customer's instruction.