Data Processing Addendum
This Data Processing Addendum ("DPA") forms part of the Terms of Service or other agreement (the "Agreement") between [COMPANY LEGAL NAME] ("Provider", "Processor") and the customer that accepted the Agreement ("Customer", "Controller") for the Certorum service (the "Service"). Effective: [DATE]. In case of conflict on data protection matters, this DPA prevails over the Agreement.
1. Definitions
"Data Protection Laws" means all laws applicable to the processing of Personal Data under the Agreement, including Regulation (EU) 2016/679 ("GDPR"), the UK GDPR and Data Protection Act 2018, the Swiss FADP, the California Consumer Privacy Act as amended ("CCPA") and other U.S. state privacy laws, and Canada's PIPEDA, each as applicable. "Personal Data", "Controller", "Processor", "Data Subject", "Processing" and "Supervisory Authority" have the meanings given in the GDPR; "Customer Personal Data" means Personal Data in Customer Data processed by Provider on Customer's behalf; "Personal Data Breach" means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Customer Personal Data; "Subprocessor" means a third party engaged by Provider to process Customer Personal Data.
2. Roles and scope
2.1 Customer is the Controller (or a Processor acting for its own customers) and Provider is the Processor of Customer Personal Data. For the CCPA, Provider is a "service provider" (or "contractor").
2.2 The subject matter, nature, purpose, duration, types of Personal Data and categories of Data Subjects are set out in Annex 1.
2.3 Provider processes account and billing data of Customer's users as an independent Controller as described in its Privacy Policy; this DPA does not apply to that processing.
3. Customer obligations
3.1 Customer is responsible for the lawfulness of the Customer Personal Data and its instructions, including providing notices and obtaining any consents needed for Provider to process the data and to send emails and text messages to End Customers on Customer's behalf.
3.2 No special-category or health data. Customer will not submit special categories of Personal Data (GDPR Art. 9), data relating to criminal convictions, protected health information under HIPAA, patient or research-subject data, government identification numbers or payment card data. The Service is designed for equipment and facility records and business contact details. Provider does not act as a HIPAA business associate.
4. Provider obligations
4.1 Instructions. Provider processes Customer Personal Data only on Customer's documented instructions - the Agreement, this DPA, and Customer's use and configuration of the Service - unless required otherwise by law, in which case Provider will inform Customer before processing unless the law prohibits it. Provider will inform Customer if it believes an instruction infringes Data Protection Laws.
4.2 CCPA. Provider will not sell or share Customer Personal Data; retain, use or disclose it for any purpose other than the business purposes specified in the Agreement or outside the direct business relationship with Customer; or combine it with personal information from other sources except as permitted by the CCPA. Provider will notify Customer if it can no longer meet its CCPA obligations.
4.3 Confidentiality. Persons authorised by Provider to process Customer Personal Data are bound by confidentiality obligations and access it only as needed to provide, support and secure the Service.
4.4 Security. Provider implements the technical and organisational measures in Annex 2, appropriate to the risk. Provider may update them provided the overall level of protection is not reduced.
4.5 Data Subject requests. Taking into account the nature of the processing, Provider will assist Customer, by appropriate technical and organisational measures, in responding to Data Subject requests. Customer can view, correct, export (on plans including CSV export) and delete most data directly in the Service; on request Provider will provide a complete export of Customer's data or perform deletions Customer cannot perform itself. If Provider receives a request directly from a Data Subject identifying Customer, it will forward it to Customer without undue delay and not respond except to direct the Data Subject to Customer.
4.6 Assistance. Provider will provide reasonable assistance with Customer's data protection impact assessments and prior consultations with Supervisory Authorities, to the extent relating to the Service and information reasonably available to Provider.
5. Subprocessors
5.1 Customer gives general authorisation for Provider to engage Subprocessors. The current list is at https://certorum.com/subprocessors (see Subprocessors).
5.2 Provider will notify Customer of new Subprocessors at least 30 days in advance by [email to the account owner / an update to the list with an email subscription]. Customer may object on reasonable data protection grounds within that period; the parties will discuss in good faith, and if no resolution is found Customer may terminate the affected Service and receive a refund of prepaid fees for the remaining term.
5.3 Provider imposes data protection obligations on each Subprocessor that are no less protective than this DPA and remains responsible for its Subprocessors' performance.
6. Personal Data Breaches
Provider will notify Customer without undue delay, and in any event within 48 hours, after becoming aware of a Personal Data Breach, providing the information Customer reasonably needs to meet its obligations (nature of the breach, categories and approximate numbers of Data Subjects and records, likely consequences, measures taken or proposed), supplemented as it becomes available. Notification is not an admission of fault.
7. International transfers
Provider processes Customer Personal Data in [the United States / REGIONS]. To the extent Customer Personal Data originating in the EEA, UK or Switzerland is transferred to a country without an adequacy decision, the parties agree to the Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914), Module Two (controller to processor) and, where Customer is a processor, Module Three, which are incorporated by reference with: Clause 7 (docking) included; Clause 9 option 2 (general authorisation, notice period per section 5.2); Clause 11 optional language omitted; Clause 17 governed by the law of [EU MEMBER STATE]; Clause 18 courts of [EU MEMBER STATE]; Annexes I and II completed by Annexes 1 and 2 of this DPA. For UK transfers, the UK International Data Transfer Addendum applies; for Swiss transfers, the SCCs as adapted for the FADP. [Alternatively or additionally: the EU-U.S. Data Privacy Framework, if Provider is certified.]
8. Return and deletion
On termination of the Agreement, Provider will, at Customer's choice made within 30 days, return Customer Personal Data in a machine-readable format (CSV) and then delete it from production systems within 30 days. Backups containing Customer Personal Data are deleted on Provider's normal rotation, currently within 35 days, and are protected under this DPA until then. Provider may retain data required by law, protected as set out here.
9. Audits
Provider will make available information reasonably necessary to demonstrate compliance with this DPA, including by answering a reasonable security questionnaire once per year [and providing third-party audit reports, if any]. Where required by Data Protection Laws and such information is insufficient, Customer may conduct an audit at its own cost, on 30 days' notice, during business hours, no more than once a year, by an auditor bound by confidentiality, in a manner that does not compromise other customers' data or Provider's security.
10. Liability and term
Each party's liability under this DPA is subject to the limitations in the Agreement, to the extent permitted by Data Protection Laws. This DPA lasts as long as Provider processes Customer Personal Data.
Annex 1 - Description of processing
| Item | Description |
|---|---|
| Subject matter | Provision of the Certorum service: operations software for equipment certification businesses. |
| Duration | The term of the Agreement plus the deletion periods in section 8. |
| Nature of processing | Hosting, storage, backup, retrieval, display, structuring, transmission (email/SMS delivery), PDF generation, export and deletion. |
| Purpose | Managing End Customers, sites, equipment and instruments; scheduling and routing site visits; recording and evaluating test readings; issuing certificates, labels, failure reports and repair quotes; sending notices, confirmations, certificates and invoices; invoicing and recording invoice payments; reporting; keeping an audit trail; providing a customer portal to End Customer contacts. |
| Categories of Data Subjects | (a) Customer's personnel using the Service (owners, technicians, office staff); (b) contact persons at Customer's End Customers (e.g. laboratory managers, facility, EHS and biosafety officers, pharmacy managers, accounts-payable contacts), including those who use the customer portal; (c) other individuals named in records by Customer (e.g. site escorts). |
| Categories of Personal Data | Names; business email addresses and phone numbers; job roles; site and billing addresses and map coordinates; site access notes (badging, escort and gowning requirements); technician names on certificates and test records; content of messages sent through the Service; quote decisions; invoice payment status; portal sign-in records; audit trail entries (user, action, time); IP addresses and request logs. |
| Special categories / sensitive data | None. Prohibited by the Agreement (see section 3.2). |
| Frequency of transfer | Continuous, as Customer uses the Service. |
| Retention | Per Customer's use of the Service, then section 8. Server logs 30 days. |
| Subprocessors | As listed at https://certorum.com/subprocessors. |
Annex 2 - Technical and organisational security measures
Access control and authentication
- Passwords stored only as salted scrypt hashes; minimum length enforced.
- Sessions use random 256-bit tokens; only SHA-256 hashes of tokens are stored;
session cookies are
httpOnly,SecureandSameSite=Lax, expire after 30 days without use, and are revoked on sign-out and on password change (other devices). - Optional two-factor sign-in (TOTP authenticator apps, one-time recovery codes); authenticator secrets encrypted at rest with AES-256-GCM, recovery codes stored only as hashes.
- Password reset, email verification and customer-portal sign-in by single-use, short-lived emailed links; only hashes of the link tokens are stored.
- Role-based permissions within each account (owner, technician, office); customer-portal access limited to the invited End Customer's own records.
- Rate limiting of sign-in and sign-up attempts and of API requests per client IP.
- Staff access to production systems and databases limited to named personnel who need it, with multi-factor authentication on hosting, database, email, payment and source-code accounts. [Confirm.]
Tenant isolation
- Every data-access operation in the application is scoped to the customer account; automated tests verify that one account cannot read another's records.
Application security
- Protection against cross-site request forgery (custom header required on every state-changing request, plus SameSite cookies).
- Strict Content-Security-Policy, HSTS, frame-ancestors
noneand other security headers. - Input validation of every API request against a typed schema.
- Payment webhooks verified by signature and processed idempotently.
- Dependency updates monitored (automated update pull requests) and every change type-checked, tested and built in continuous integration before deployment.
- A published vulnerability disclosure policy.
Encryption
- All traffic encrypted in transit with TLS (HTTPS enforced; HSTS).
- Database connections over TLS where they leave the provider's private network.
- Data at rest encrypted by Netlify (hosting) and Supabase (database) [describe]. Off-site backups stored in private, encrypted object storage.
Availability and resilience
- Managed PostgreSQL with provider backups [and point-in-time recovery]; daily off-site logical backups retained 35 days; restore procedure documented and tested.
- Health and readiness monitoring with alerting; graceful shutdown on deploys.
- Database schema changes applied transactionally at deploy.
Integrity
- Tamper-evident, hash-chained audit trail of changes per account; the application provides no way to edit or delete individual entries.
- Signed test records snapshot the specification and instrument calibration used.
Logging and monitoring
- Structured request logs (no request bodies; cookies and authorisation headers redacted), retained 30 days.
- Incident response procedure including breach assessment and notification.
Data minimisation and deletion
- The Service collects business contact and equipment data only; health and special-category data is prohibited.
- Customers can edit, archive and export data; complete account deletion removes all of the account's records from the production database.
Subprocessor management
- Subprocessors selected for their security practices and bound by data protection terms.