WhataJig: Data Processing Addendum
docs/legal/ATTORNEY_REVIEW.md.Version: 1.0 · Effective date: [date]
This Data Processing Addendum ("DPA") forms part of the Terms of Service (or another agreement for WhataJig) between [Collablly legal entity name] ("Collablly") and the Customer. It applies automatically, without a signature, whenever Collablly processes Customer Personal Data for the Customer. A Customer that needs a signed copy can ask at [legal email].
1. Definitions
- Customer Personal Data: Personal Data in Customer Data that Collablly processes on the Customer's behalf in providing the Service.
- Data Protection Laws: all laws on privacy and the processing of personal data that apply to a party's processing of Customer Personal Data under the Terms. They include:
- the California Consumer Privacy Act as amended (the "CCPA") and other US state privacy laws
- where they apply, the EU and UK General Data Protection Regulations ("GDPR")
- Controller, processor, data subject, processing, service provider, business: have the meanings given in the Data Protection Laws. "Processor" includes "service provider", and "controller" includes "business".
- Security Incident: a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data in systems managed by Collablly or its sub-processors.
- Sub-processor: a third party that Collablly engages to process Customer Personal Data.
Other capitalized words have the meanings in the Terms.
2. Roles and scope
- Roles. The Customer is the controller (or a processor acting for its own controller) of Customer Personal Data, and Collablly is its processor or service provider.
- Details. Annex 1 describes the processing.
- Customer's duties. The Customer is responsible for:
- complying with Data Protection Laws as a controller
- having a lawful basis for the processing, and giving the notices and getting the consents needed, including to its workers
- the accuracy and quality of Customer Personal Data
- not putting in the kinds of data that Section 7.3 of the Terms forbids
3. Processing on instructions
- Only on instructions. Collablly processes Customer Personal Data only on the Customer's documented instructions, unless the law requires otherwise. If so, Collablly will tell the Customer first, unless the law forbids that.
- What the instructions are. The Terms, this DPA, the Customer's use and configuration of the Service, and its Admins' requests, are the Customer's complete instructions. Additional instructions need a written agreement, and may carry fees.
- Unlawful instructions. Collablly will tell the Customer if it believes an instruction breaks Data Protection Laws, and may then decline to follow it.
4. US state law (service provider) terms
As a service provider under the CCPA and similar laws, Collablly will not:
- sell or share Customer Personal Data, as those terms are defined in the CCPA
- keep, use or disclose it for any purpose other than the business purposes in the Terms and this DPA, including any commercial purpose other than providing the Service
- keep, use or disclose it outside the direct business relationship between Collablly and the Customer
- combine it with personal information that Collablly receives from or on behalf of others, or collects itself, except as Data Protection Laws allow
Collablly will also:
- comply with the obligations that apply to it under the CCPA, and give the same level of privacy protection the CCPA requires
- tell the Customer if it can no longer meet these obligations
The Customer may take reasonable and appropriate steps to stop and remedy unauthorized use of Customer Personal Data. Collablly certifies that it understands these restrictions and will comply with them. De-identified data under Section 7.5 of the Terms is not Customer Personal Data.
5. Confidentiality of personnel
Collablly ensures that everyone it authorizes to process Customer Personal Data is bound by a duty of confidentiality, and has access only as needed for their role. Collablly staff access a Customer's account only to provide support the Customer asks for, keep the Service secure and running, or meet legal obligations.
6. Security
- Measures. Collablly implements and maintains the technical and organizational measures in Annex 2. They are designed to protect Customer Personal Data against Security Incidents, and are appropriate to the risk.
- Updates. Collablly may update the measures, as long as it does not materially lower the overall level of protection.
7. Sub-processors
- General authorization. The Customer authorizes Collablly to use Sub-processors. The current list is at /Legal/Subprocessors and in Annex 3.
- Sub-processor terms. Collablly has a written agreement with each Sub-processor that protects Customer Personal Data at least as well as this DPA, as appropriate to its service. Collablly remains responsible for its Sub-processors.
- New Sub-processors. Collablly will tell the Admins by email at least 30 days before a new Sub-processor starts processing Customer Personal Data, and will update the list.
- Objections. The Customer may object in writing, on reasonable data protection grounds, within that period.
- The parties will discuss the objection in good faith.
- If Collablly cannot reasonably accommodate it, the Customer may end the affected subscription by written notice before the change takes effect, and will get a refund of prepaid fees for the unused period. This is the Customer's only remedy.
- Customer's own services. Services the Customer chooses to connect, such as its identity provider (Microsoft Entra ID or Google Workspace) or its ERP system, are not Collablly's Sub-processors. The Customer's own agreements with those providers govern them.
8. Help with data subject requests
- Requests to Collablly. If Collablly receives a request from a data subject about Customer Personal Data, it will pass it to the Customer without undue delay, and will not answer it except as the Customer instructs or the law requires.
- Tools. The Service lets the Customer access, correct, export and delete Customer Personal Data itself. Where it can't, Collablly will provide reasonable help, taking into account the nature of the processing.
9. Security Incidents
- Notice. Collablly will notify the Customer of a Security Incident without undue delay, and in any case within 72 hours after confirming it. Notice goes to the Admins' email addresses.
- What the notice says. It will include the information Collablly then has, including, as far as known:
- the nature of the incident
- the categories and approximate number of data subjects and records affected
- its likely consequences
- the measures taken or proposed
Collablly will update the Customer as it learns more.
- Response. Collablly will take reasonable steps to contain, investigate and mitigate the incident, and will give the Customer reasonable help to meet its own obligations to notify authorities and data subjects.
- Not an admission. Notice of a Security Incident is not an admission of fault or liability.
- Not Security Incidents. Unsuccessful attempts that do not compromise the security of Customer Personal Data, such as blocked log-in attempts, pings or port scans, are not Security Incidents.
10. Deletion and return
- During the subscription. The Customer can export Customer Personal Data at any time while the account is active or read-only.
- After it ends. After the subscription ends, Collablly deletes Customer Personal Data as described in Section 10 of the Terms: 90 days read-only, warnings, then deletion, and backups overwritten within [35] days.
- Exceptions. Collablly may keep data it is required by law to keep, under continued confidentiality and protection, and only for as long as required.
11. Audits and information
- Information. On written request, no more than once a year, Collablly will give the Customer the information reasonably needed to show compliance with this DPA. This may include answers to a reasonable security questionnaire, a summary of its security measures, and any third-party audit reports it has, such as its hosting provider's SOC 2 or ISO 27001 reports.
- Audits. If the information is not enough to show compliance, or a regulator requires it, the Customer may audit Collablly's compliance, on these conditions:
- at least 30 days' written notice
- no more than once a year, unless a Security Incident or a regulator requires it
- during business hours, without unreasonably disrupting Collablly's business
- by the Customer or an independent auditor bound by confidentiality, who is not a competitor of Collablly
- at the Customer's cost
- remotely where possible
Audits do not extend to Collablly's Sub-processors' facilities, whose own audit reports are provided instead.
12. Data protection impact assessments
Collablly will give reasonable help, where the Customer has no other access to the information, with impact assessments and prior consultations with authorities that Data Protection Laws require for the Customer's use of the Service.
13. International transfers
- Where data is processed. Collablly processes and stores Customer Personal Data in the United States.
- EU, UK and Swiss transfers. Where the GDPR or UK or Swiss law applies to a transfer of Customer Personal Data to Collablly, the parties agree to the Standard Contractual Clauses adopted by the European Commission in Decision 2021/914. They are incorporated by reference, as follows:
- Module 2 (controller to processor) or Module 3 (processor to processor), as applicable
- Clause 7 (docking clause) applies
- in Clause 9, Option 2 (general authorization), with the notice period in Section 7.3
- in Clause 11, the optional language does not apply
- in Clause 17, the law of [Ireland]
- in Clause 18, the courts of [Ireland]
- Annexes 1 to 3 of this DPA complete the Annexes of the Clauses
For UK transfers, the UK International Data Transfer Addendum applies as well. For Swiss transfers, references to the GDPR are read as references to Swiss law.
- Which document wins. If the Standard Contractual Clauses conflict with this DPA, the Clauses win.
14. Liability and order of precedence
- Liability. Each party's liability under this DPA is subject to the limits and exclusions in the Terms, to the extent Data Protection Laws allow.
- Order of precedence. If this DPA conflicts with the Terms on the processing of Customer Personal Data, this DPA wins. Otherwise the Terms apply.
- Duration. This DPA lasts as long as Collablly processes Customer Personal Data.
Annex 1: Details of processing
| Subject matter and purpose | Providing the Service to the Customer under the Terms: tracking tools, calibrated tools, machines and the people who use them, with related support, security and integrations the Customer turns on |
| Duration | The subscription, plus the read-only and deletion periods in Section 10 of the Terms |
| Nature of processing | Collection, storage, organization, retrieval, display, transmission (including to integrations the Customer enables), export and deletion |
| Data subjects | The Customer's Login Users; Shop Staff (workers, contractors and others tools are checked out to); people the Customer adds as email recipients; contacts at the Customer's suppliers and service providers recorded in the Service; and people who raise support tickets |
| Categories of personal data | Names, work email addresses, phone numbers, badge numbers, operator codes (stored only as a one-way hash), roles, staff levels and certifications (including dates, trainer, and images of certification cards), profile photos, records of check-outs, returns, bypass approvals, machine entries and maintenance, notes, support tickets and their attachments, sign-in and audit records, IP addresses and browser details, and anything else the Customer chooses to enter |
| Special categories | None. The Customer must not put them in (Terms Section 7.3) |
| Frequency | Continuous, for the duration |
Annex 2: Technical and organizational security measures
[Collablly to confirm each item against production before publishing.]
- Encryption:
- all traffic to the Service uses HTTPS (TLS 1.2 or higher)
- passwords are stored only as one-way, salted hashes (PBKDF2-HMAC-SHA512, 210,000 iterations); password reset links are random, work once and expire after 2 hours
- connection secrets, such as email and payment keys, are stored encrypted
- data at rest is encrypted by the hosting provider's storage encryption [confirm for the production database and file storage]
- Separation: the Service is designed so that every record belongs to one company, and each screen, report and API call is limited to that company's data. The API uses a key bound to one company, not a signed-in session.
- Access control:
- role-based access within each company (Store Room Clerk, Standard User, Machine Operator, Admin)
- optional single sign-on
- accounts lock after repeated failed sign-ins
- Collablly staff access to production is limited to the people who need it, with individual accounts [and multi-factor authentication: confirm]
- Floor tablet codes: operator codes are stored only as a one-way hash, and easy-to-guess codes are refused.
- API security:
- API keys are stored only as a cryptographic hash
- keys can be revoked at once
- calls are rate-limited
- Logging: changes to settings, users and records are kept in audit logs, for up to 7 years. Error and diagnostic logs are kept for 90 days.
- Backups and recovery: regular backups, kept for [35] days [confirm the backup frequency and location].
- Development: changes are tested on a separate staging environment before release. Production data is not used for testing [confirm].
- Sub-processors: chosen for their security practices, and bound by data protection terms.
- Incident response: a documented process to investigate and notify, as in Section 9.
Annex 3: Sub-processors
See Sub-processors.
