Need a signed copy for your records? Write to legal@keptstone.com. The list of sub-processors is in Annex III.
1. Definitions
- Agreement means the Terms of Service and any Order between EMAK Solution LLC ("Keptstone", "we" or "us") and the customer that accepted them ("Customer" or "you").
- Customer Personal Data means personal data that Keptstone processes on Customer's behalf in providing the Service, as described in Annex I. It does not include the account, billing and usage data that Keptstone handles as a controller under its Privacy Policy.
- Data Protection Laws means the laws on privacy and personal data that apply to the processing under this DPA, including the GDPR (Regulation (EU) 2016/679), the UK GDPR and the UK Data Protection Act 2018, the Swiss Federal Act on Data Protection, the California Consumer Privacy Act as amended by the California Privacy Rights Act (the "CCPA"), and other US state privacy laws.
- Controller, processor, data subject, personal data, processing, personal data breach and supervisory authority have the meanings given in the GDPR, and the equivalent terms in other Data Protection Laws have matching meanings. Business, service provider, sell, share and business purpose have the meanings given in the CCPA.
- Sub-processor means a third party Keptstone engages that processes Customer Personal Data.
- SCCs means the Standard Contractual Clauses annexed to Commission Implementing Decision (EU) 2021/914 of 4 June 2021. UK Addendum means the International Data Transfer Addendum to those clauses issued by the UK Information Commissioner, version B1.0, in force from 21 March 2022.
- Other capitalized words have the meanings given in the Terms of Service.
2. Roles of the parties
- Customer is the controller of Customer Personal Data, or a processor acting for its Clients, who are the controllers. Keptstone is Customer's processor or, where Customer is a processor, its sub-processor.
- Where Customer acts for a Client, Customer confirms that its instructions to Keptstone, including appointing Keptstone, are authorized by that Client. Customer is the single point of contact for its Clients, and Keptstone has no obligations to them directly unless Data Protection Laws require it.
- Keptstone is an independent controller of the account, billing and usage data described in its Privacy Policy. This DPA does not apply to that data.
3. Scope, nature and purpose
Keptstone processes Customer Personal Data only to provide the Service under the Agreement: monitoring Client Sites, updating them safely, protecting them, trying speed settings, building and sending reports, showing the Site care page, and giving support. The processing consists of collecting data from Client Sites through the connector and Keptstone's own checks, storing, organizing and analysing it, showing it to Customer in the app and in reports, sending reports and alerts, and deleting it. It lasts for the term of the Agreement and the deletion period in Return and deletion. Annex I gives the details.
4. Instructions
- Keptstone processes Customer Personal Data only on Customer's documented instructions, including about transfers, unless the law requires otherwise. In that case Keptstone will tell Customer before processing, unless the law forbids it.
- The Agreement, this DPA and Customer's own configuration and use of the Service (the sites it connects, the features it switches on, the people it sends reports to) are Customer's complete instructions. Other instructions need our written agreement.
- Keptstone will tell Customer if, in its opinion, an instruction breaks Data Protection Laws, and may decline to follow it until Customer confirms or changes it.
5. Customer's responsibilities
- Customer is responsible for having a lawful basis for the processing, for giving data subjects any notices and getting any consents Data Protection Laws require (for example in a Client Site's privacy notice), and for the accuracy of Customer Personal Data.
- Customer will connect only sites it is authorized to manage, as the Terms require, and will make sure its instructions comply with Data Protection Laws.
- Customer will not use the Service to process special categories of personal data, data about criminal convictions, or children's data, except what may appear incidentally on the public pages it chooses for checks. It should not choose pages for checks that show such data.
- Customer is responsible for securing its own accounts and for the security settings it chooses in the Service.
6. Confidentiality of personnel
Keptstone makes sure that everyone it authorizes to process Customer Personal Data is bound by confidentiality, and gives access only to people who need it to provide, support or secure the Service or to meet legal obligations.
7. Security
Keptstone implements technical and organizational measures appropriate to the risk, as Article 32 of the GDPR requires, including those in Annex II. Keptstone may change them over time, provided the overall level of protection does not go down.
8. Use of sub-processors
- Customer gives Keptstone general authorization to engage Sub-processors. The current Sub-processors are listed in Annex III. Some are used only when a feature is switched on, as marked there.
- Keptstone has a written contract with each Sub-processor that imposes data protection obligations no less protective than this DPA, as far as they apply to the service it provides. Keptstone remains responsible to Customer for its Sub-processors.
- At least 30 days before a new Sub-processor starts processing Customer Personal Data, Keptstone will update Annex III and tell Customer's account owner by email or in the app. Where a Sub-processor must be replaced urgently to keep the Service running or secure, Keptstone will tell Customer as soon as it can.
- Customer may object to a new Sub-processor on reasonable data protection grounds by writing to us within the notice period. We will discuss the objection in good faith and look for an alternative, such as not using the feature that relies on that Sub-processor. If we cannot resolve it within 30 days, Customer may end the affected part of the Service by notice, with no refund. This is Customer's only remedy for the objection.
9. Requests from data subjects
- Taking into account the nature of the processing, Keptstone will help Customer, by appropriate technical and organizational measures and as far as possible, to answer requests from data subjects exercising their rights. The Service's own tools help: Customer can change or remove WordPress users, export a site's activity log, change report recipients and disconnect sites.
- If Keptstone receives a request from a data subject about Customer Personal Data, it will not answer it except to tell the person to contact Customer, and it will pass the request to Customer promptly where it can tell which customer it concerns.
10. Assessments and consultations
Taking into account the nature of the processing and the information available to it, Keptstone will give Customer reasonable help with data protection impact assessments and prior consultations with supervisory authorities that Data Protection Laws require, where Customer cannot carry them out with the information it already has. Keptstone may charge reasonable fees for help beyond what the Service and this DPA already provide.
11. Personal data breaches
- Keptstone will notify Customer without undue delay, and in any case within 72 hours, after becoming aware of a personal data breach affecting Customer Personal Data. The notice goes to the email address of Customer's account owner.
- The notice will describe, as far as Keptstone knows at the time, the nature of the breach, the categories and approximate number of data subjects and records concerned, its likely consequences, the measures taken or proposed, and a contact for more information. Information not available at first will follow as it becomes available.
- Keptstone will take reasonable steps to contain and investigate the breach and to reduce its effects.
- Customer is responsible for notifying its Clients, supervisory authorities and data subjects where Data Protection Laws require it. Keptstone will not notify Customer's Clients or data subjects directly unless the law requires it or Customer agrees.
- A notice under this section is not an admission of fault or liability.
12. Return and deletion
- During the Agreement, Customer can export Customer Personal Data with the Service's export features.
- When the Agreement ends, Keptstone deletes Customer Personal Data from the Service within 30 days, unless Customer asked in writing before the end for it to be returned instead, or the law requires Keptstone to keep some. Copies in Keptstone's backups are deleted as the backups expire, within six months; until then they stay protected and are not processed except to restore the Service.
- When a Client Site is released, the connector forgets its keys and Keptstone stops collecting data from it. Data the connector keeps on the site itself, such as the site's own activity log, stays under the site owner's control and is removed when the connector is deleted from WordPress.
- Keptstone will confirm the deletion in writing if Customer asks.
13. Audits and information
- Keptstone will make available the information reasonably needed to show that it meets this DPA: this DPA and its annexes, and written answers to a reasonable security questionnaire once a year, or more often after a personal data breach or when a supervisory authority asks. Customer will give at least 30 days' notice of a questionnaire.
- Where that information is not enough to meet a requirement of Data Protection Laws or of a supervisory authority, Customer, or an independent auditor bound by confidentiality who is not a competitor of Keptstone, may audit Keptstone's processing of Customer Personal Data. Customer will give at least 30 days' notice and agree the scope in advance. An audit takes place during business hours, at most once in any 12 months, at Customer's expense, without access to other customers' data and without putting the security of the Service at risk. Keptstone may charge reasonable fees for its time.
- The results of any audit are Keptstone's Confidential Information.
14. International transfers
Keptstone hosts the Service in the United States, and some Sub-processors process data in other countries. Customer authorizes those transfers, subject to this section.
From the European Economic Area
Where Customer Personal Data is transferred from the European Economic Area to a country without an adequacy decision, the SCCs are incorporated into this DPA by reference, with Customer as the data exporter and Keptstone as the data importer:
- Module 2 (controller to processor) applies where Customer is a controller, and Module 3 (processor to processor) where Customer is a processor;
- the docking clause in Clause 7 applies;
- in Clause 9, Option 2 (general written authorization) applies, with the notice period in Use of sub-processors;
- the optional wording in Clause 11 does not apply;
- in Clause 13, the supervisory authority is the one competent for Customer under that clause;
- in Clause 17, Option 1 applies, and the governing law is the law of Ireland;
- in Clause 18, disputes are resolved by the courts of Ireland; and
- Annex I of the SCCs is completed by Annex I of this DPA, Annex II by Annex II, and the list of sub-processors by Annex III.
From the United Kingdom
Where the transfer is from the United Kingdom, the UK Addendum is incorporated into this DPA by reference. Table 1 is completed with the parties' details in Annex I, Table 2 with the modules and options above, and Table 3 with this DPA's annexes. For Table 4, either party may end the UK Addendum as its Section 19 allows.
From Switzerland
Where the transfer is subject to the Swiss Federal Act on Data Protection, the SCCs apply as set out above with these changes: the Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority for those transfers; references to the GDPR include the Swiss act; and "Member State" includes Switzerland, so that data subjects there can bring claims where they normally live.
If the SCCs or the UK Addendum conflict with this DPA, they prevail. If a transfer mechanism stops being valid, we will work with Customer in good faith on another lawful one.
15. CCPA and other US state laws
Where Customer Personal Data is personal information under the CCPA, Customer is a business (or a service provider to one) and Keptstone is its service provider. Keptstone will not:
- sell or share Customer Personal Data;
- retain, use or disclose it for any purpose, including any commercial purpose, other than the business purposes set out in the Agreement, which are providing, securing and supporting the Service;
- retain, use or disclose it outside the direct business relationship between Customer and Keptstone; or
- combine it with personal information it receives from or for anyone else, or collects from its own dealings with a person, except as the CCPA and its regulations allow.
Keptstone will meet the obligations the CCPA places on service providers and give Customer Personal Data the level of privacy protection the CCPA requires. It will tell Customer if it decides it can no longer do so. Customer may take reasonable and appropriate steps to make sure Keptstone uses Customer Personal Data in line with these obligations, through Audits and information, and to stop and fix any unauthorized use. Keptstone's Sub-processors are bound by the same restrictions. Keptstone certifies that it understands these restrictions and will comply with them.
Under other US state privacy laws, Keptstone acts as Customer's processor, and this DPA's terms on instructions, confidentiality, sub-processors, assistance, deletion and audits are the processing contract those laws require.
16. Liability
Each party's liability under or in connection with this DPA, including under the SCCs and the UK Addendum, is subject to the exclusions and limits in the Terms of Service, and counts towards them, except where Data Protection Laws or the SCCs do not allow that liability to be limited, such as liability to data subjects under Clause 12 of the SCCs.
17. Order of precedence and duration
For the processing of Customer Personal Data, the SCCs and the UK Addendum (where they apply) come first, then this DPA, then the rest of the Agreement. In everything else the Terms of Service apply. This DPA lasts as long as Keptstone processes Customer Personal Data. We may update it as the Terms of Service allow, and will not reduce the protection it gives Customer Personal Data during the Agreement unless Data Protection Laws require a change.
18. Annex I: Details of the processing
A. The parties
- Data exporter: Customer, with the name, address and contact details in its Keptstone account. Its role is controller, or processor for its Clients. It signs by accepting the Terms of Service.
- Data importer: EMAK Solution LLC, 1007 N Orange St, 4th Floor, Suite 530, Wilmington, DE 19801, contact legal@keptstone.com. Its role is processor, or sub-processor. It signs by offering the Service under the Terms of Service.
- Activities: providing the Service as described in the Agreement.
B. Description of the processing
Categories of data subjects
- People whose role on a Client Site lets them change it, such as administrators, editors and shop managers.
- People who sign in, or try to sign in, to those accounts.
- Visitors whose requests to a Client Site the firewall records.
- Customers of shops on Client Sites, only through order status changes and refunds in the activity log.
- Customer's Clients and their people who receive reports.
- People who appear in content on the pages Customer chooses for checks, or in the titles of content.
Categories of personal data
- Identity and account details: names, usernames, email addresses, user IDs, roles, registration and last login dates, whether two-step login is used, and how many posts and pages someone published.
- Online identifiers: IP addresses, the country looked up from them on Keptstone's own server, and user agents.
- Activity on Client Sites: what happened, when, by whom and from where, including failed logins, login codes emailed, changes to users, content, media, menus and settings, and exports.
- Requests the firewall records: the request method, the address requested, and the field and text that matched a rule (never for fields named like a password, card number, CVV or token).
- Order events: order status changes and refunds, with their totals.
- Report data: recipients' names and email addresses, each report's figures, and when the live report was first opened.
- Page content: whatever appears in screenshots of the pages chosen for checks, and the paths of pages where PHP errors happened.
- Files from Client Sites that the malware engine reads, which are deleted as soon as they have been read.
Special categories of data
None are intended. Anything of that kind that appears incidentally in screenshots of public pages or in content titles is protected by the measures in Annex II and deleted with the screenshots after 30 days.
Frequency, nature and purpose
Continuous, for the term of the Agreement. The nature and purpose are described in Scope, nature and purpose.
Retention
| Data | Kept for |
|---|---|
| Activity events from Client Sites | 90 days |
| Firewall events | 30 days; automatic blocks for 30 days after they end |
| Screenshots from updates | 30 days |
| PHP errors | 90 days after last seen, once settled |
| Files read by the malware engine | Deleted as soon as they have been read; only a fingerprint and the verdict are kept |
| Everything else | The term of the Agreement and 30 days after it, as in Return and deletion |
| Copies in Keptstone's backups | Until the backups expire, within six months |
Transfers to Sub-processors
The subject matter, nature and duration of each Sub-processor's processing are in Annex III.
C. Competent supervisory authority
The supervisory authority identified under Clause 13 of the SCCs, as described in International transfers.
19. Annex II: Security measures
A summary of the measures Keptstone takes. It describes the Service as it is built today.
Access to Client Sites
- No WordPress passwords are stored. Each site connects with its own Ed25519 key pair.
- Every request between Keptstone and a site is signed and checked both ways, must arrive within a 5-minute window, and cannot be replayed.
- Keys are made for each site, so a leaked site database exposes that one site's keys only, and Keptstone's own private keys are stored encrypted.
- One-click logins use a random token that works once, for 60 seconds; only its hash is stored, the login goes only to the site's own address, and it appears in the site's own activity log.
Access to the Service
- Sign-in with two-step codes and passkeys. Agency owners and admins must use two-step sign-in before they connect sites.
- Roles limit what each person can do. Only owners and admins can connect sites, run updates or change plugins and themes, and members and technicians can be kept to some sites only.
- Every query is limited to one agency's data and refuses to run without it. Database row-level security is built as a second lock.
- An audit log records updates, connections and disconnections, WordPress logins, maintenance mode, plugin and theme changes, reports sent and role changes, with who and when.
Encryption and secrets
- Data travels over HTTPS.
- Third-party keys, Slack webhook addresses, Cloudways keys and Keptstone's private keys for sites are stored encrypted, and keys cannot be read back in the app once saved. Passwords are stored only as one-way hashes.
- Infrastructure secrets live only on the server, never in source control.
Collecting less
- The activity log keeps no content and no passwords. Customers' logins, orders and emails stay on the site and are not sent to Keptstone.
- The firewall never keeps what matched in fields named like a password, card number, CVV or token.
- PHP errors keep the page's path, never its query string or anything submitted.
- The malware engine never reads files with passwords or keys, and deletes each file as soon as it has read it.
- Measuring real visitors' speed uses no cookies, no IP addresses and no visitor IDs.
- Country lookups for IP addresses use a database on Keptstone's own server, so no address is sent anywhere for them.
- Data is deleted on schedule, as listed in Annex I.
Resilience
- Nightly backups of the database and stored files, kept 14 days with monthly copies for six months, and a backup before every release. Restores are tested.
- The key that decrypts stored secrets is kept apart from the backups.
- Keptstone runs in its own containers, with its own network and storage, and the server is reached only with SSH keys.
Building and releasing
- Changes go through automated tests, and dependencies are checked for known vulnerabilities.
- New connector versions reach sites in stages and stop automatically if sites show problems.
- New firewall rules start by recording, not blocking.
People
- Access to production systems is limited to the people who run the Service, who are bound by confidentiality.
- Security problems can be reported to legal@keptstone.com.
20. Annex III: Sub-processors
Keptstone uses these Sub-processors. Those marked "only when switched on" receive nothing until the feature they serve is in use. We will update this list, and tell customers, as described in Use of sub-processors.
| Sub-processor | What for | Data involved | When |
|---|---|---|---|
| Hostinger | The servers Keptstone runs on, in a data centre in the United States | All Customer Personal Data the Service stores | Always |
| Brevo | Sending email: reports, alerts and account emails; setting up agencies' sender domains | Recipients' names and email addresses, the emails' content including report PDFs, and sender domains | Always. Keptstone can also send through Elastic Email, Postmark or another mail server; we will update this list before switching |
| Search Console API: search figures for reports. PageSpeed Insights API: Google's browser loads a site's public pages to measure their speed | Site and page addresses, and the search figures Google already holds for the site | Search Console only when the agency links a site's property; PageSpeed for speed checks and reports | |
| Globalping | Loading a site from other places to confirm an outage before anyone is alerted | The site's address | When a site seems to be down |
| check-host.net | The same outside check, when Globalping cannot answer | The site's address | When Globalping cannot answer |
| Off-site backup storage (Cloudflare R2, or another S3-compatible provider we name here first) | Keeping copies of Keptstone's nightly backups away from its server | Everything in the backups. Stored secrets stay encrypted, and the key that decrypts them is not copied | Only when switched on |
| Anthropic or OpenAI | Drafting the opening paragraph of a report | The report's figures and the names of the site and its client | Only when switched on, with one provider at a time |
| Cloudflare (CDN and proxy) | Its network in front of Keptstone's addresses: every visit and every call from a Client Site passes through it, which protects the Service from attacks and delivers its pages | What passes between people or Client Sites and Keptstone while it does: IP addresses and the details of each request, and the pages, reports and data sent and returned, which Cloudflare decrypts at its edge to pass on | Only when switched on |
| Cloudflare (Turnstile) | The bot check on the signup form | The IP address and browser details of the person signing up. This is Keptstone's own data, not Customer Personal Data | Only when switched on |
| Stripe | Payments, invoices, tax calculation and the billing portal | Billing contacts' names, email addresses, billing addresses and payment details. This is Keptstone's own data; nothing from Client Sites | For paid plans |
Not sub-processors
- Run on Keptstone's own servers: screenshots and PDFs (a browser in Keptstone's own containers), the malware engine, and IP country lookups (DB-IP's database, downloaded to our server; no address is sent to DB-IP).
- Data Keptstone downloads, sending nothing about sites or people: vulnerability data from Wordfence Intelligence, and official files and checksums from WordPress.org to compare a site's files with.
- Services Customer connects itself: Slack, Cloudways, Patchstack and the Search Console access Customer grants are Customer's own providers, under Customer's own agreements with them.
21. Contact
Questions about this document, notices under it and requests about personal data go to:
EMAK Solution LLC1007 N Orange St, 4th Floor, Suite 530, Wilmington, DE 19801
legal@keptstone.com