Privacy notice
What personal data we collect, why we collect it, who sees it, how long we keep it, and what you can ask of us.
1. Who is responsible for your data
1.1Tominko Ltd, a company registered in England and Wales under number 12089741, registered office 5 Canon Court, Institute Street, Bolton, United Kingdom, BL1 1PZ, is the controller of the personal data described in this notice. "We", "us" and "our" mean Tominko Ltd.
1.2We have not appointed a data protection officer, because the law does not require us to. For any question about this notice or your data, use the contact form (say it is a privacy request), email [email protected], or write to our registered office.
2. What this notice covers
2.1This notice covers personal data we handle when you visit processmanager.dev, write to us, run the APM software, use the APM Portal (portal.processmanager.dev) or the APM Network relay (apm.processmanager.dev), or buy a paid plan.
2.2The reports and traffic your daemons send to the Portal and the relay can contain personal data about other people — for example a host named after a person, or a log line containing an address. If you use the Portal for a business, that business is the controller of that data and we are its processor under the data processing addendum. If you use the Portal for your own projects, we handle that data only to provide the service to you, as described in section 7.
3. Visiting the website
3.1Cloudflare. Every request to our sites passes through Cloudflare, which protects them and delivers them quickly. Cloudflare sees your IP address, the page you ask for, your browser's user-agent string and your approximate location, and may set a strictly necessary cookie to tell people from bots (see the cookie policy).
3.2Our web server log. Our server records each request — the time, the page, the response, the referring page and your browser's user-agent string — with the address of the Cloudflare server that passed it on. We use the log to run and secure the site and keep it for 14 days.
3.3Google Analytics — only if you agree. If you choose Accept analytics in the cookie banner, Google Analytics records which pages you visit, how you arrived, your device and browser type and your approximate location, using cookies. If you choose Reject or make no choice, Analytics does not load at all. Our lawful basis is your consent, which you can withdraw at any time with the cookie settings. Google keeps Analytics data for the retention period set in our Analytics account, at most 14 months.
3.4Badges. Our home page shows badge images from launch directories (codetrendy.com, peerpush.net, tinylaunch.com and nxgntools.com). Loading an image sends your IP address and browser details to the site it comes from, as with any image on the web. Those sites' own privacy policies apply.
3.5Your theme and cookie choices are stored in your own browser (see the cookie policy) and are not sent to us.
3.6Our lawful basis for 3.1, 3.2 and 3.4 is our legitimate interest in running a secure, fast and well-presented website.
4. Writing to us
4.1When you use the contact form, we receive your name, email address, subject and message, and the IP address you send it from. The form hands them to a program on our server in the United Kingdom, which keeps a copy for 90 days and emails your message to our support mailbox. If that program is unavailable, the form emails your message to us directly through our own mail server (mail.tominko.com). If you email us directly, we receive your message and its headers.
4.2Automatic screening and answers. To keep spam out and answer common questions quickly, your name, email address, subject and message are sent to Anthropic, whose Claude AI models check whether the message is spam, needs a person, or is a question our documentation answers. For such a question, Claude writes an answer from our documentation and licence, and if the answer is complete we email it to you straight away, marked as an automatic AI answer; replying to it reaches a person. When a person needs to read your message, it is forwarded to us and you get an automatic confirmation that it arrived. Messages judged to be spam are not forwarded, but a person reviews a list of them every week. Anthropic acts as our processor, and under its commercial terms it does not use this data to train its models.
4.3We keep each answer our AI writes, with your question, name and email address, for 12 months, to check the answers are right and to improve our documentation.
4.4To stop floods of messages, the form keeps a one-way hash (MD5) of your IP address with the times of your recent messages. These records are on temporary storage that is cleared within 10 days and whenever the server restarts.
4.5We use your message to answer you and to deal with what you ask, including the automatic screening and answers above. Our lawful basis is our legitimate interest in responding to enquiries quickly and keeping spam out, or taking steps at your request before a contract. We keep correspondence for as long as we need it to deal with your enquiry and any follow-up, and no longer than 24 months after the last message, unless it relates to a contract or a legal claim.
5. APM software telemetry
5.1Unless you switch it off, the APM daemon sends usage telemetry to our statistics server (ping.processmanager.dev): about once a minute while it runs, and when it is installed, starts and shuts down. Each message contains:
- a random installation id, created on first run and stored in
/etc/apm/apm.id, and a random id for the current run; - the APM version, operating system, processor architecture, number of CPUs and amount of memory;
- uptime and the number of workers, child processes, restarts and errors; on shutdown, the reason;
- the time of the event (if the daemon's clock is more than a day out, the server's time is used instead).
5.2Telemetry never contains host names, worker or application names, file paths, configuration, environment variables or application data.
5.3Your IP address. The statistics server receives the address each message comes from, but never stores it. It keeps only a keyed hash: the first 16 hexadecimal characters of a SHA-256 hash of a secret key and the address. The key stays on our server, so the hash cannot be turned back into an address or matched against a list of addresses by anyone without it. We use the hash to recognise installations that report from the same address — for example to help a customer understand their own fleet. Installations that have not been in contact since 19 October 2026 still carry an older, unkeyed hash of their address until the retention periods below remove them.
5.4Why. Telemetry tells us how many installations exist, which versions and platforms are in use, and how stable APM is in practice, so we can decide what to support and fix. Our lawful basis is our legitimate interest in maintaining and improving free software. We do not try to identify the people or organisations behind installations, and we do not use telemetry for marketing.
5.5How to switch it off. Add telemetry false; at the top level of /etc/apm/apm.conf (off, 0, no and disabled also work) and reload. Nothing is sent after that.
5.6Remote logging (optional). If you set remote_logging true;, the daemon also sends worker and child lifecycle events — the worker's name, the child's index and process id, the action (such as a start, an exit or a reload) and its detail, such as an exit code, signal or reason. It is off by default; we use it only to diagnose unexpected restarts, usually because you asked us to. Our lawful basis is our legitimate interest in supporting the software, at your request.
5.7How long. Individual pings are deleted after 13 months; run records and install/boot/shutdown events after 25 months; an installation's record 25 months after its last contact; remote-logging events after 90 days. A daily job enforces these periods.
6. Your Portal account
6.1To give you an account we keep your email address, your name if you give one, and either a password hash (scrypt — we never store the password itself) or no password if you sign in only through a provider. We also keep when you joined, when you last signed in and from which IP address, and your display settings (such as the order of your daemons).
6.2Signing in with another account. If you sign in with or connect Google, GitHub, Microsoft, GitLab, LinkedIn, Bitbucket, Discord, Slack or a single sign-on provider we offer, that provider tells us your account id there, your email address and whether it is verified, and your name or handle. We store the provider, the id, the email address and the display name so we can recognise you next time and show you which accounts are connected. We never receive your password at that provider. The provider's own privacy policy covers what it does when you sign in there.
6.3Security. For each signed-in session we keep a record with your IP address and browser's user-agent string; sessions end 14 days after your last visit. After failed sign-in attempts we keep the IP address and the number of failures to stop password guessing; the record lapses after 15 minutes and is deleted within the following hour. Email verification and password-reset links are single-use and stored only as hashes, for 24 hours and 1 hour respectively. When you start signing in through a provider we keep a short-lived, single-use record that ties the attempt to your browser, for 15 minutes (30 minutes if you still need to choose an email address).
6.4Changes by our staff. If we change your account (for example your plan or limits, or suspend it), we record who changed what and when, with the IP address of the person making the change. We keep these records while your account exists and for up to six years after it is closed.
6.5Why. To provide the Portal under our terms (lawful basis: contract) and to keep accounts secure and prevent abuse (lawful basis: legitimate interests).
7. What your daemons send to the Portal
7.1A daemon reports to the Portal only when you give it a portal key. Its reports contain its installation id, host name and the name you or it chose, APM version, operating system, architecture, CPU count and memory, the IP address the reports come from, uptime, CPU, memory and load; for each worker its name, status, number of instances, CPU and memory use, connections, restarts and errors, and, where your plan includes them, advanced figures such as requests, firewall counters, disk input/output, open files and WebSocket clients; and lifecycle events such as a child exiting, with their details.
7.2You can also add alert rules, email alerts and webhook addresses (we send alert messages to the addresses you enter), and, if you switch on remote control for a daemon, read and write its configuration files and follow its logs from the Portal.
7.3How long. Sample history and events are kept for your plan's retention period — Free: samples 2 days, events 7 days; Pro: 30 days each; Business: 90 days each — and then deleted automatically every hour. Workers that disappear from your reports are removed after 30 days. Resolved alert history is kept for 90 days. The remote-control audit log (who ran which command on which daemon, and the result — never the configuration text) is kept for 90 days. Log lines you follow live are passed straight to your browser and never stored. Daemon records and alert rules stay until you delete them or close your account.
7.4Why. To provide the Portal to you (lawful basis: contract). Where you use the Portal for a business, we process any personal data in this section on that business's instructions under the data processing addendum.
8. APM Network relay
8.1For each APM Network key we keep its token, its name, the account it belongs to, any IP allowlist you set, and a record of each connection: the IP address it came from, the daemon's id, the channel names it announced, and when it connected and disconnected. The relay passes messages between your daemons without storing their contents.
8.2Connection records are kept while the key exists and are deleted with it. The relay's own service log records connections and their IP addresses; it is rotated automatically by size.
8.3Why. To provide the relay (lawful basis: contract) and to enforce keys, limits and allowlists and investigate abuse (lawful basis: legitimate interests).
9. Paid plans and payments
9.1Payments are handled by Stripe. Your card details go straight to Stripe — we never see or store your full card number. Stripe acts as an independent controller for the payment itself (for example to prevent fraud and meet its legal duties); Stripe's privacy policy applies to that.
9.2We keep your Stripe customer and subscription ids, your plan, billing period, subscription status and renewal date, and a record of each order (plan, period, amount, currency, status and dates). We also keep copies of the payment notifications Stripe sends us for 90 days.
9.3Why and how long. To take payment and provide your plan (lawful basis: contract), and to keep accounting records (lawful basis: legal obligation). Order records are kept for six years after the end of the financial year they belong to, as UK company law requires.
10. Emails we send
10.1The Portal sends you email address verification and password reset links, security notices (a changed password, a newly connected sign-in account) and the alert emails you set up. These are sent through SMTP2GO, an email delivery service, which keeps delivery records for its own operation; so are the contact form's automatic answers and confirmations (section 4.2) and the copies of form messages to our support mailbox. Stripe emails receipts for payments. We may also email you about material changes to our terms or services.
10.2We do not send marketing email.
11. Who we share data with
We do not sell personal data. We share it only with:
| Who | What for | Role |
|---|---|---|
| IONOS | The servers that run the website, the Portal, the relay, the statistics server and their databases, in the United Kingdom | Processor |
| Cloudflare | Network protection and delivery for our sites; sees all traffic to them | Processor |
| SMTP2GO | Delivering the Portal's emails and the contact form's messages, answers and confirmations | Processor |
| Anthropic | Screening contact form messages and writing automatic answers (section 4.2) | Processor |
| Website analytics, only if you accept analytics cookies | Processor | |
| Stripe | Payments, receipts, invoices and the billing portal | Independent controller for payments; processor for the rest |
| Sign-in providers | Only the provider you choose to sign in with | Independent controller |
| Badge hosts | The home page's badge images (section 3.4) | Independent controllers |
We may also share data with professional advisers, with the police, courts or regulators where the law requires it or to protect our rights, and with a buyer of our business (who would have to respect this notice).
12. International transfers
Our servers and databases are in the United Kingdom. Cloudflare, Google, Stripe, SMTP2GO and Anthropic operate internationally and may process data outside the UK; contact form messages sent to Anthropic are processed mainly in the United States. Where they do, the transfer is covered by UK adequacy regulations, by the UK Extension to the EU–US Data Privacy Framework where the recipient is certified under it, or by the UK International Data Transfer Agreement or the UK Addendum to the EU standard contractual clauses. You can ask us for details.
13. How long we keep data
| Data | Kept for |
|---|---|
| Web server request log | 14 days |
| Google Analytics (with consent) | Our Analytics retention setting, at most 14 months |
| Contact form flood-control records | Cleared within 10 days |
| Contact form messages on our server | 90 days |
| Automatic AI answers, with the question | 12 months |
| Messages to us | Up to 24 months after the last message, longer only for a contract or a legal claim |
| Telemetry pings | 13 months |
| Telemetry runs and install / boot / shutdown events | 25 months |
| Telemetry installation records | 25 months after the last contact |
| Remote-logging events | 90 days |
| Portal account details | Until the account is deleted (see below) |
| Sessions | 14 days after your last visit |
| Failed sign-in records | 15 minutes, deleted within the following hour |
| Verification / reset links | 24 hours / 1 hour |
| Provider sign-in attempts | 15 minutes (30 while choosing an email address) |
| Daemon samples and events | Your plan's retention: Free 2 / 7 days, Pro 30 days, Business 90 days |
| Resolved alerts, remote-control audit | 90 days |
| APM Network connection records | Until the key is deleted |
| Stripe payment notifications | 90 days |
| Orders | Six years after the end of their financial year |
| Records of changes our staff made to an account | While the account exists and up to six years after it is closed |
Closing your account. When you close your Portal account, we revoke all its keys, end all its sessions, delete its connected sign-in accounts and cancel any subscription immediately. History then expires under the periods above. The account record itself (your address and name) is kept so that nobody else can register with your address; if you ask us, we delete the account and everything linked to it within 30 days, except the order records we must keep.
14. How we protect data
All traffic to our services is encrypted in transit (TLS). Passwords are stored as scrypt hashes; API keys, verification and reset links as SHA-256 hashes; session cookies as keyed hashes. Our services accept requests only through our own network edge, each service uses its own database account with only the permissions it needs, and access to production systems is limited to the people who run them. No system is perfectly secure: if a personal data breach is likely to put your rights at risk, we will tell the Information Commissioner within 72 hours where the law requires, and tell you without undue delay where the risk is high.
15. Your rights
15.1Under the UK GDPR you have the right to ask for a copy of your personal data, to have it corrected, to have it deleted, to restrict how we use it, to object to our use of it where we rely on legitimate interests, and to receive data you gave us in a portable format. Where we rely on your consent, you can withdraw it at any time — for analytics, with the cookie settings.
15.2To object to telemetry, the simplest way is to switch it off (section 5.5). Because telemetry does not tell us who you are, we may need your installation id (from /etc/apm/apm.id) to find its records.
15.3To use any right, contact us as in section 1.2. We may ask you to confirm your identity. We answer within one month, and do not charge unless a request is clearly unfounded or excessive.
15.4We do not make decisions about you based solely on automated processing that have legal or similarly significant effects. The automatic screening of contact form messages (section 4.2) only decides how a message reaches us, and a person reviews what it filters out.
15.5If you are unhappy with how we handle your data, please tell us first. You also have the right to complain to the Information Commissioner's Office (ICO): ico.org.uk/make-a-complaint, telephone 0303 123 1113.
16. Children
The Portal and paid plans are for people aged 18 or over, and we do not knowingly collect personal data about children. If you believe a child has given us personal data, contact us and we will delete it.
17. Changes to this notice
We will update this notice when what we do with personal data changes. Each version shows its number and the date it takes effect; if a change matters to Portal account holders, we will also tell them by email before it takes effect.
Tominko Ltd · Company no. 12089741 · Registered in England and Wales · Registered office: 5 Canon Court, Institute Street, Bolton, United Kingdom, BL1 1PZ · Version 1.1 · Effective 25 October 2026