Data Processing Addendum
This addendum is part of the Terms of Service between Smart Spatial, Inc. and the Customer. It applies whenever SmartSpatial processes personal data in Customer Content on the Customer's behalf, and it takes effect with the Terms, without a signature. For a countersigned copy, email legal@smartspatial.com.
1. Definitions
- Data Protection Laws: the laws on personal data that apply to the processing under this addendum, including the EU General Data Protection Regulation (“GDPR”), the GDPR as it applies in the United Kingdom (“UK GDPR”) with the UK Data Protection Act 2018, the Swiss Federal Act on Data Protection (“FADP”), and US state privacy laws such as the California Consumer Privacy Act (“CCPA”).
- Customer Personal Data: personal data in Customer Content that SmartSpatial processes on the Customer’s behalf in providing the Service.
- Subprocessor: a third party SmartSpatial engages to process Customer Personal Data.
- Security Incident: a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data.
- SCCs: the standard contractual clauses approved by the European Commission in Decision 2021/914. UK Addendum: the International Data Transfer Addendum to the SCCs issued by the UK Information Commissioner.
- “Controller”, “processor”, “data subject”, “personal data”, “processing”, “service provider” and “contractor” have the meanings given in Data Protection Laws. Other terms have the meanings given in the Terms of Service.
2. Roles and scope
The Customer is the controller of Customer Personal Data, or a processor acting for its own customers, and SmartSpatial is its processor (or subprocessor) and service provider. Annex 1 describes the processing. Each party will comply with the Data Protection Laws that apply to it. The Customer is responsible for having a lawful basis for the processing and for the accuracy of the instructions it gives.
3. Instructions
SmartSpatial processes Customer Personal Data only on the Customer’s documented instructions: the Terms and this addendum, the Customer’s use and configuration of the Service (including the requests its members and connected AI apps make), and other written instructions the parties agree. SmartSpatial will tell the Customer if it believes an instruction breaks Data Protection Laws, and is not required to follow it. If the law requires other processing, SmartSpatial will tell the Customer first unless the law prohibits it.
4. Personnel
SmartSpatial gives access to Customer Personal Data only to personnel who need it to provide, secure or support the Service and who are bound by confidentiality obligations.
5. Security
SmartSpatial implements and maintains the technical and organizational measures in Annex 2. It may update them over time, but not in a way that reduces the overall protection of Customer Personal Data.
6. Subprocessors
The Customer authorizes SmartSpatial to engage the Subprocessors listed on the Trust page. SmartSpatial will give at least 30 days’ notice before a new Subprocessor processes Customer Personal Data, by updating that list and by email to Customers who have asked for notices at legal@smartspatial.com. The Customer may object on reasonable data protection grounds within that period; the parties will then work in good faith to resolve the objection, and if they cannot, the Customer may stop using the affected part of the Service and receive a refund of any prepaid fees for it. SmartSpatial imposes data protection obligations on each Subprocessor that are no less protective than this addendum, and remains responsible for its Subprocessors’ performance.
7. Assistance
Taking into account the nature of the processing, SmartSpatial will help the Customer respond to requests from data subjects, through the Console where possible and otherwise on request, and will pass on any such request it receives directly. It will give reasonable help with data protection impact assessments and consultations with supervisory authorities about the Service.
8. Security Incidents
SmartSpatial will notify the Customer without undue delay, and in any case within 72 hours, after becoming aware of a Security Incident. The notice will describe, as far as known, the nature of the incident, the data and data subjects affected, the likely consequences and the measures taken or proposed, with updates as more becomes known. SmartSpatial will take reasonable steps to contain and remedy the incident. A notice is not an admission of fault.
9. Return and deletion
The Customer can export or delete Customer Content through the Service while it uses it, and can request an export for 30 days after the Terms end. SmartSpatial then deletes Customer Personal Data within a further 30 days, except where the law requires it to keep it, and except for copies in backups, which are deleted as the backups are overwritten and protected under this addendum until then.
10. Audits
SmartSpatial will make available the information reasonably needed to show compliance with this addendum, including answers to security questionnaires and its Subprocessors’ audit reports and certifications where they allow it. If that is not enough to meet a requirement of Data Protection Laws or a supervisory authority, the Customer may audit SmartSpatial’s compliance, at its own cost, no more than once a year, with 30 days’ notice, during business hours, in a way that does not disrupt the Service, and under confidentiality.
11. International transfers
SmartSpatial processes Customer Personal Data in the United States. To the extent Customer Personal Data subject to the GDPR is transferred to SmartSpatial in a country without an adequacy decision, the SCCs are incorporated into this addendum as follows: Module Two (controller to processor) applies where the Customer is a controller, and Module Three (processor to processor) where it is a processor; the Customer is the data exporter and SmartSpatial the data importer; the optional docking clause in Clause 7 applies; under Clause 9, option 2 (general written authorization) applies with the notice period in section 6; the optional language in Clause 11 does not apply; under Clauses 17 and 18, the law and courts of Ireland apply; and Annexes I and II of the SCCs are completed by Annexes 1 and 2 of this addendum, with the competent supervisory authority determined under Clause 13.
For transfers subject to the UK GDPR, the UK Addendum is incorporated, with its tables completed by the information in this addendum and either party able to end it as allowed by its Section 19. For transfers subject to the FADP, the SCCs apply with references to the GDPR read as the FADP, the Swiss Federal Data Protection and Information Commissioner as the competent authority, and Switzerland included as a place where data subjects may bring claims. If the SCCs conflict with this addendum or the Terms, the SCCs prevail.
12. US state privacy laws
Where US state privacy laws apply, SmartSpatial acts as the Customer’s service provider or contractor and will not: sell or share Customer Personal Data; keep, use or disclose it for any purpose other than providing the Service, including any commercial purpose, or outside the direct business relationship with the Customer; or combine it with personal data it receives from others, except as those laws allow. SmartSpatial will comply with the obligations that apply to it, provide the same level of privacy protection the laws require, tell the Customer if it can no longer meet them, and allow the Customer to take reasonable steps to stop and remedy unauthorized use. SmartSpatial certifies that it understands these restrictions.
13. General
Each party’s liability under this addendum is subject to the limits in the Terms, except where Data Protection Laws or the SCCs do not allow it. This addendum lasts as long as SmartSpatial processes Customer Personal Data. If it conflicts with the Terms, this addendum prevails for the processing of Customer Personal Data.
Annex 1: Details of the processing
- Parties. Data exporter: the Customer, as identified in its account, contact through its owner accounts. Data importer: Smart Spatial, Inc., a Delaware corporation, contact legal@smartspatial.com.
- Data subjects. The Customer’s members and users, and any people whose personal data the Customer puts into Customer Content.
- Personal data. Account details of members (name, email, role) and any personal data in files, commands, command output, screenshots, chats and other Customer Content, as the Customer determines.
- Sensitive data. None is intended. The Customer will not include special categories of data unless the parties have agreed in writing on additional safeguards.
- Frequency. Continuous, for as long as the Customer uses the Service.
- Nature and purpose. Hosting, storing, transmitting and processing Customer Content on the computers the Customer chooses, running the commands the Customer, its members and its AI apps request, and processing chats with the MachineDock Assistant through the AI models the Customer chooses, to provide, secure and support the Service.
- Duration and retention. For the term of the Terms and the deletion period in section 9, with the retention periods on the Trust page.
- Subprocessors. As listed on the Trust page, for the purposes stated there.
Annex 2: Technical and organizational measures
- Encrypted in transit. Every connection uses TLS: your AI app to MachineDock, MachineDock to each computer, and every file upload and download.
- Encrypted at rest. Files in storage are encrypted with AES-256. Secrets such as API keys are encrypted and sealed to the one computer that uses them. The AI only sees their names.
- Keys that stay on the computer. Each computer makes its own key when it joins, and its credentials are sealed to that key. Updates to MachineDock are signed with an offline key and checked before they install.
- Your work stays yours. The activity log records what ran, not what was in it: no command text, file contents or output. Full logs, with secrets removed, stay off until an owner or admin turns them on.
- Spending limits. Anything paid needs approval in the chat. Owners set monthly budgets, a cap on running machines and the largest size anyone can start.
- Signed commands and approvals. Every command is signed and verified on the computer. Require a person's approval for commands or changes, per project.
- Audit history. A record of every action across the organization. Turn on full tool logs, with secrets redacted, when you need an audit trail.
- No credentials on cloud computers. Cloud computers hold no cloud keys, accept no inbound connections, run behind deny-all firewalls and use encrypted storage.
- Roles and access. Owners, admins and members, with project access you grant. A member's own computer stays private unless an owner or admin shares it with the organization.
- Files stay with the project. Results are kept with the project, on its computer and in storage, ready for the next person and the next run.
- Least privilege. Production systems, keys and secrets are reachable only by the people and services that need them; production and development use separate accounts, keys and databases.
- Data minimization in logs. Service logs record identifiers, digests and sizes, not command text, file contents, output or secrets.
- Retention limits. Data is deleted on the schedule on the Trust page.
- Vendor management. Subprocessors are chosen for their security practices and bound by written data protection terms.
Annex 3: Subprocessors
The current list is on the Trust page.