SimpleOS Growth Data Processing Addendum

Last updated 13 November 2026

This text is in effect as published. Our attorney is completing a review of it. If the review changes anything, we will post the new text here and email workspace administrators before the change takes effect.

This Addendum is part of the agreement between Simple Intelligence Group, Inc. ("SIG") and the organization that uses SimpleOS Growth ("Customer"). It applies wherever SIG handles Personal Data for Customer in providing the Service. It needs no signature: it applies when Customer accepts the Terms of Service. A Customer that needs a signed copy can ask for one at legal@simpleintelligencegroup.com.

1. Words with a set meaning

"Agreement", "Service", "Workspace", "Administrator" and "Customer Data" have the meanings given in the Terms of Service.

"Data Protection Law" means the privacy and data protection laws that apply to a party's handling of Personal Data under the Agreement.

"Personal Data" means information about an identified or identifiable person.

"Customer Personal Data" means the Personal Data within Customer Data.

"Security Incident" means a breach of security that leads to the accidental or unlawful destruction, loss or alteration of Customer Personal Data, or to unauthorized disclosure of it or access to it, while SIG or a Subprocessor holds it.

"Subprocessor" means another company that SIG engages and that handles Customer Personal Data in providing the Service.

"Controller" and "processor" have the meanings Data Protection Law gives them. Where that law uses "business" and "service provider" instead, those words apply in the same way.

2. Roles

2.1 Customer is the controller of Customer Personal Data, and SIG is its processor. Where Customer is itself a processor for someone else, SIG is Customer's subprocessor, and Customer confirms that its instructions to SIG are ones it is allowed to give.

2.2 This Addendum does not cover the data for which SIG is a controller: the account details of people who sign in, billing contact details, support messages and the operational logs of the Service. The Privacy Policy describes how SIG handles that data.

2.3 Annex 1 describes the processing.

3. SIG's obligations

3.1 Instructions. SIG handles Customer Personal Data only on Customer's documented instructions. Those instructions are the Agreement, this Addendum, and what Customer's Administrators and users do in the Service. If SIG believes an instruction breaks Data Protection Law, it will tell Customer. If the law requires SIG to handle the data in another way, SIG will tell Customer first unless the law forbids that.

3.2 Limits on use. SIG will not sell Customer Personal Data or share it for advertising. SIG will not keep or use it for any purpose other than providing the Service to Customer, and will not combine it with Personal Data from another source except as the Service requires to do what Customer asks. SIG will not use Customer Personal Data to train, retrain or fine-tune any AI model.

3.3 People. SIG makes sure that the people it authorizes to handle Customer Personal Data are bound to keep it confidential and reach it only where they need to in order to run or support the Service.

3.4 Security. SIG maintains the measures in Annex 2. SIG may change them over time but will not make the protection of Customer Personal Data materially weaker.

3.5 Help with requests from individuals. The Service lets Customer's Administrators find, correct, export and delete the data in the Workspace. Where a request cannot be met that way, SIG gives Customer reasonable help on written request. If a person sends a request directly to SIG, SIG passes it to Customer and does not answer it in Customer's place.

3.6 Help with assessments. On written request, SIG gives Customer the information it reasonably needs about the Service to carry out a data protection impact assessment or to consult a regulator.

3.7 Compliance. SIG will tell Customer if it can no longer meet its obligations under this Addendum or under Data Protection Law.

4. Customer's obligations

4.1 Customer is responsible for having a lawful basis for the Personal Data it puts into the Service, for giving any notice and obtaining any consent the law requires, and for the accuracy of that data.

4.2 Customer will not put into the Service any category of Personal Data that the Terms of Service say the Service is not designed to hold, unless a signed order says it may.

4.3 Customer is responsible for who it admits to its Workspace, for the roles it gives them, and for the outside services its Administrators connect.

5. Subprocessors

5.1 Customer authorizes SIG to use the Subprocessors listed in Annex 3.

5.2 Each Subprocessor is engaged under written terms that require it to protect Customer Personal Data and to handle it only to provide its service. SIG is responsible to Customer for what its Subprocessors do with Customer Personal Data.

5.3 Before a new Subprocessor starts to handle Customer Personal Data, SIG will update Annex 3 on the published page and tell Customer's Administrators by email at least 30 days in advance.

5.4 Customer may object in writing, on reasonable data protection grounds, within those 30 days. The parties will then discuss the objection in good faith. If SIG cannot offer a way to use the Service without the new Subprocessor, Customer may end the affected subscription before the new Subprocessor starts, and SIG will refund the fees Customer prepaid for the period after the end date.

5.5 SIG may use its affiliates and contractors to operate and support the Service. They act on SIG's instructions under a duty of confidentiality, and SIG is responsible for them as for itself.

5.6 A service that an Administrator chooses to connect to the Workspace is not a Subprocessor. Its provider handles data under its own terms with Customer.

6. Where data is processed and transfers

6.1 The Service is hosted on Microsoft Azure in the East US 2 region, in the United States. SIG does not offer hosting in another country today.

6.2 Customer accepts that Customer Personal Data is transferred to and processed in the United States.

6.3 Where Data Protection Law requires a transfer contract for Customer to send Personal Data to SIG in the United States, the parties will enter into the standard contractual clauses approved for that purpose, and the United Kingdom addendum where it applies, before that data is put into the Service. Customer starts this by writing to legal@simpleintelligencegroup.com. SIG states no other transfer mechanism and holds no certification under a cross-border transfer framework.

7. Security Incidents

7.1 SIG will tell Customer's Administrators by email without undue delay after it confirms a Security Incident.

7.2 The notice will say what SIG knows at that time about what happened, which data is affected and what SIG is doing about it. SIG will add to the notice as it learns more.

7.3 SIG will take reasonable steps to contain the Security Incident and to reduce its effects, and will give Customer the information it reasonably needs to meet its own duties to notify regulators or individuals.

7.4 A notice under this section is not an admission of fault or liability.

8. Return and deletion of data

8.1 While the Agreement is in force, Customer can export Customer Data using the export features of the Service.

8.2 For 30 days after the Agreement ends, an Administrator can still sign in to export Customer Data, or can ask SIG in writing for a copy in a commonly used, machine-readable format.

8.3 After those 30 days SIG deletes Customer Personal Data from the systems that run the Service, and completes that deletion within 90 days after the Agreement ends.

8.4 Copies in backups are not restored for use and expire on the backup schedule of the database service. Until a backup expires, this Addendum continues to protect the data in it.

8.5 SIG may keep Customer Personal Data after that only where the law requires it, and only for as long as the law requires. Where the Service is built to keep a specific record as evidence after other data is deleted, Annex 1 names that record, why it is kept and in what form.

8.6 On written request, SIG will confirm in writing that deletion is complete.

9. Information and audits

9.1 SIG does not hold an independent security attestation or certification today. It therefore cannot offer an audit report in place of an audit.

9.2 Once in any 12 months, and also after a Security Incident that affected Customer, SIG will answer in writing Customer's reasonable written questions about how SIG meets this Addendum. SIG will answer within a reasonable time.

9.3 Where Data Protection Law gives Customer a right to an audit that written answers cannot satisfy, the parties will agree its scope, timing and length in advance. The audit will take place during business hours on at least 30 days' written notice, will be limited to the systems that handle Customer Personal Data, will not expose another customer's data, and will be carried out at Customer's cost by people bound to confidentiality.

10. Liability and precedence

10.1 The limits on liability in the Terms of Service apply to this Addendum.

10.2 If this Addendum and the Terms of Service conflict about Personal Data, this Addendum comes first. If standard contractual clauses are entered into under section 6.3 and they conflict with this Addendum, the clauses come first.

10.3 This Addendum ends when SIG no longer holds Customer Personal Data.


Annex 1. Description of the processing

Annex 2. Security measures

These measures are in place on the date at the top of this page.

1. Hosting. The Service runs on Microsoft Azure platform services in the East US 2 region. SIG does not operate its own data center.

2. Encryption. Data is encrypted in transit with TLS. Data at rest is encrypted by the Azure platform.

3. Sign-in. Users sign in with Microsoft Entra ID work or school accounts. Personal Microsoft accounts are not accepted. Customer's own Microsoft Entra policies, including multi-factor authentication, apply to those sign-ins.

4. Separation of customers. Every record carries the identifier of the Workspace it belongs to. The server takes that identifier from the signed-in session and applies it to every request. It is never taken from what a browser sends, and it does not depend on a screen hiding rows.

5. Access within a Workspace. Roles are administrator, member and viewer. A person who is not an administrator sees only the records assigned to them. The server enforces this.

6. Secrets. Application secrets and keys are held in Azure Key Vault and are not stored in source code.

7. Logging. Actions that change Customer Data are written to an audit log within the Workspace. Where an AI agent reads or changes Workspace data, the call is recorded with the Workspace, the caller and the function used.

8. Change control. Changes are built on separate branches, pass automated tests, and are reviewed before release. Each release is approved and recorded.

9. Staff access. Access to production systems is limited to the people who need it to run and support the Service.

10. Use of AI models. AI models are reached through Azure AI Foundry, a Microsoft Azure service. Records written by an AI feature are marked as AI-generated with a confidence level and a reason, and a person reviews them before they take effect outside the Workspace.

The Trust page lists what SIG does not claim, including certifications, audit reports and recovery objectives.

Annex 3. Subprocessors