APM
Home Manual Downloads Modules Portal Deployment Story License Contact
v2.13.0
Legal documents
Legal overview Terms of service Privacy notice Cookie policy Acceptable use policy Data processing addendum Software licence
On this page
1. When this addendum applies 2. Processing on your instructions 3. Confidentiality and security 4. Subprocessors 5. Helping you meet your obligations 6. Personal data breaches 7. Deletion at the end 8. Information and audits 9. International transfers Annex 1 — Details of the processing Annex 2 — Security measures Annex 3 — Subprocessors
Legal

Data processing addendum

The terms under which we process personal data on your behalf when your daemons report to the APM Portal or talk through the APM Network relay.

Version 1.0 · effective 19 October 2026

1. When this addendum applies

1.1This addendum forms part of our terms of service between Tominko Ltd ("we", the processor) and a business customer ("you", the controller). It applies whenever we process personal data contained in Customer Data — what your daemons send to the APM Portal or through the APM Network relay, and what you put into your Portal account (the "Personal Data"). It meets the requirements of Article 28 of the UK GDPR.

1.2It does not cover personal data for which we are the controller — your account details, billing records and APM telemetry — which our privacy notice describes.

1.3"UK GDPR", "personal data", "processing", "data subject", "personal data breach" and "supervisory authority" have the meanings given in the UK GDPR and the Data Protection Act 2018. If this addendum and the terms conflict on data protection, this addendum wins.

2. Processing on your instructions

2.1We process Personal Data only on your documented instructions. Your instructions are these terms, this addendum, and what you do in the Portal and with your daemons' configuration — for example choosing a plan's retention, deleting a daemon, following a log, or running a remote-control command. Annex 1 describes the processing.

2.2We may process Personal Data otherwise only where UK law requires it; we will tell you first unless that law forbids it. We will tell you if we think an instruction breaks data protection law.

2.3You are responsible for having a lawful basis for the Personal Data your daemons send, for telling the people concerned where needed, and for not sending special category data or payment card data.

3. Confidentiality and security

3.1Everyone we allow to process Personal Data is bound by confidentiality.

3.2We take the technical and organisational measures in Annex 2, appropriate to the risk, and may improve them over time without lowering the overall level of protection.

4. Subprocessors

4.1You authorise us to use the subprocessors in Annex 3. We have written contracts with them that give the Personal Data protection equivalent to this addendum, and we remain responsible for their performance.

4.2We will tell you at least 30 days before we add or replace a subprocessor, by email to your account address and by updating Annex 3. If you object on reasonable data protection grounds, we will discuss it with you in good faith; if we cannot resolve it, you may close your account before the change takes effect and receive a refund of the unused part of any period you have paid for.

5. Helping you meet your obligations

5.1Taking into account the nature of the processing, we help you respond to requests from data subjects. Most can be met directly in the Portal — you can see and delete daemons, workers, alert rules and keys yourself. If we receive a request about Personal Data directly, we pass it to you and do not answer it ourselves unless you ask us to.

5.2We give you reasonable information and help with security, breach notification, data protection impact assessments and prior consultation with the Information Commissioner, as far as they concern our processing.

6. Personal data breaches

We will tell you without undue delay after becoming aware of a personal data breach affecting Personal Data, with the information you need to meet your own obligations — what happened, the data and people likely to be affected, the likely consequences and what we are doing about it — and keep you updated as we learn more.

7. Deletion at the end

7.1During the contract, history is deleted under your plan's retention period and everything else when you delete it. You can see what the Portal holds about your daemons at any time, and delete it yourself.

7.2When you close your account, keys stop working at once and history expires under the retention periods. On your request we delete all Personal Data linked to your account within 30 days, unless UK law requires us to keep it.

8. Information and audits

We make available the information reasonably needed to show that we meet this addendum — normally by answering your written questions about our measures and subprocessors. Where that is not enough, or a supervisory authority requires it, we allow an audit by you or an independent auditor you appoint, on reasonable notice, at your cost, during business hours, no more than once a year, under confidentiality, and without access to other customers' data.

9. International transfers

Our servers are in the United Kingdom. Some subprocessors in Annex 3 may process Personal Data outside the UK. We transfer it only where the transfer is covered by UK adequacy regulations, by the UK Extension to the EU–US Data Privacy Framework for certified recipients, or by the UK International Data Transfer Agreement or the UK Addendum to the EU standard contractual clauses.

Annex 1 — Details of the processing

Subject matter and purposeProviding the APM Portal (collecting, storing and showing daemon reports, alerts, remote control and live logs) and the APM Network relay (routing messages between your daemons).
DurationThe term of the contract, then until deletion under section 7.
Nature of processingReceiving, storing, aggregating, displaying, relaying, transmitting (alert emails and webhooks you configure) and deleting.
Types of personal dataWhatever personal data appears in Customer Data, which may include: host names, daemon and worker names, IP addresses of your servers, lifecycle event details, configuration file contents read or written through remote control, log lines followed live (relayed, not stored), webhook addresses and alert recipients, and the contents of messages between your daemons (relayed, not stored).
Data subjectsYour staff and contractors, and any other individuals whose data your systems place in the above — for example your own customers or users.
Special category dataNone is intended; you agree not to send it.

Annex 2 — Security measures

  • Encryption in transit: all connections to the Portal and the relay use TLS. Cloudflare terminates TLS at its edge and re-encrypts traffic to our servers.
  • Credentials: passwords are stored as scrypt hashes; portal API keys, verification and reset tokens as SHA-256 hashes; session ids as keyed (HMAC-SHA-256) hashes, so a copy of the database cannot be replayed as keys or sessions.
  • Access control: every request needs a valid session or key; keys can be revoked or regenerated at any time; APM Network keys can be limited to IP allowlists; remote control is off unless you enable it per daemon, and every command is recorded in an audit log.
  • Network edge: the services answer only requests that arrive through our own web server (a secret edge header), and the Portal origin accepts traffic only from Cloudflare.
  • Least privilege: each service uses its own database account with only the permissions it needs.
  • Abuse protection: rate limits, sign-in lockout after repeated failures, and checks against cross-site requests.
  • Data minimisation: live logs and relay messages are passed through without being stored; configuration text is never written to the audit log; history is deleted automatically after the plan's retention period.
  • Software integrity: APM releases are signed, and the installer and upgrade verify the signature.
  • People: administrative access to production systems is limited to Tominko staff who need it.

Annex 3 — Subprocessors

SubprocessorPurposeLocation
IONOSHosting: the servers and databases that run the Portal and the relayUnited Kingdom
Cloudflare, Inc.Network protection, TLS and delivery for all traffic to the Portal and the relayGlobal network, including outside the UK
SMTP2GODelivering the Portal's emails, including alert emails that name your daemons and workersMay be outside the UK
StripeBilling only — receives no Customer DataMay be outside the UK

Tominko Ltd · Company no. 12089741 · Registered in England and Wales · Registered office: 5 Canon Court, Institute Street, Bolton, United Kingdom, BL1 1PZ · Version 1.0 · Effective 19 October 2026

APM v2.13.0 — Tom's Advanced Process Manager
Docs Downloads Portal Discord GitHub LinkedIn Contact ☕ buy me a coffee
Terms Privacy Cookies Acceptable use License Legal Cookie settings © Tominko Ltd · Company no. 12089741 · England and Wales