Legal
Data Processing Addendum
Version: teams-dpa-2026-11-17
Effective: November 17, 2026
This Data Processing Addendum ("DPA") applies whenever iGrow Inc. ("i-Grow.co") processes personal data for a Customer under the Customer Terms. i-Grow.co acts as the Customer's processor and service provider, and follows only the Customer's instructions. Terms defined in the Customer Terms have the same meaning here.
1. Definitions
Data Protection Laws: all laws on personal data that apply to the processing, including the GDPR, the UK GDPR, the Swiss Federal Act on Data Protection, the California Consumer Privacy Act as amended ("CCPA"), and other US state privacy laws.
Customer Personal Data: personal data in Customer Data that i-Grow.co processes on the Customer's behalf.
Security Incident: a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data.
Subprocessor: a third party i-Grow.co engages to process Customer Personal Data.
SCCs: the standard contractual clauses approved by the European Commission in Decision 2021/914.
"Controller", "processor", "data subject" and "processing" have the meanings in the GDPR. "Business" and "service provider" have the meanings in the CCPA.
2. Roles and scope
- The Customer is the controller of Customer Personal Data (or a processor acting for its affiliates). i-Grow.co is its processor.
- i-Grow.co is an independent controller only for account and billing data about the Customer's purchasing contacts, and for Usage Data. Our privacy policy covers that data.
- Annex I describes the processing.
3. Instructions
- i-Grow.co processes Customer Personal Data only on the Customer's documented instructions. These Terms, the Order and the Customer's configuration of the Service are those instructions.
- We will tell the Customer if we believe an instruction breaks Data Protection Laws, and we may pause that processing until it is resolved.
- If the law requires processing beyond the instructions, we will tell the Customer first, unless the law forbids it.
4. Learner privacy
The Customer instructs i-Grow.co to keep each Learner's Learner Content private to that Learner, as Section 3 of the Customer Terms describes. Admins see participation, progress and the scores from formal assessments, not practice transcripts or feedback, unless the Learner chooses to share them. If the law compels disclosure of Learner Content, we notify the Customer, where permitted, and disclose only what is required.
5. Our personnel
Only personnel who need access to provide the Service can access Customer Personal Data. They are bound by written confidentiality obligations.
6. Security
i-Grow.co maintains the measures in Annex II. We may update them, but never in a way that lowers the overall protection of Customer Personal Data.
7. Subprocessors
- The Customer authorizes the Subprocessors on the Subprocessor List.
- We give at least 15 days' notice before a new Subprocessor processes Customer Personal Data, by updating the list and emailing Customers who ask for updates.
- The Customer may object within those 15 days on reasonable data protection grounds. We will work in good faith on an alternative. If none is found within 30 days, the Customer may terminate the affected Service and receive a refund of prepaid fees for the unused term.
- Each Subprocessor is bound by written terms that protect Customer Personal Data at least as well as this DPA. We remain responsible for our Subprocessors.
8. AI processing
- AI Subprocessors process Customer Personal Data only to generate Outputs for the Customer.
- Neither i-Grow.co nor any Subprocessor uses Customer Personal Data to train or improve AI models.
- AI Subprocessors may keep inputs and outputs only for the limited period their terms allow for abuse monitoring: up to 30 days at OpenAI and at Anthropic, unless the law requires longer.
- We do not create voiceprints, face geometry or any other biometric identifier. Learner audio goes directly to OpenAI, which uses it only to transcribe and respond. i-Grow.co does not store it.
- We send AI providers only the data needed for each request. Learner names and email addresses are not sent.
9. Data subject requests
If a Learner or Admin asks us to exercise privacy rights over Customer Personal Data, we refer them to the Customer, unless the law requires otherwise. We help the Customer respond, through the Service's features or on request, within 10 business days.
10. Security Incidents
- We notify the Customer within 72 hours of confirming a Security Incident affecting its Customer Personal Data.
- The notice describes, as far as known: what happened, the categories and approximate number of people and records affected, the likely consequences, the steps taken, and a contact. We send updates as we learn more.
- We take reasonable steps to contain the incident, and cooperate with the Customer's own response and notifications.
- Notifying the Customer is not an admission of fault.
11. Assessments
We give reasonable help with the Customer's data protection impact assessments and any consultation with a regulator, using information about the Service that we hold.
12. Deletion and return
- When a subscription ends, access ends. For 30 days afterwards, we email the Customer a copy of its reports on request.
- Within 30 days after that window, we delete Customer Personal Data from active systems. We do not currently keep separate database backups; if we add them, deleted data leaves them within a further 30 days.
- We confirm deletion in writing on request. We may keep data only where the law requires, and then only for that purpose.
13. Audits
- Once every 12 months, on request, we answer the Customer's written security questionnaire and provide our security documentation. We will share a SOC 2 report once we have one.
- If that is not enough to show compliance, or a regulator requires it, the Customer may audit once every 12 months. The audit requires 30 days' notice, happens during business hours, is limited to Customer Personal Data, is done by the Customer or an independent auditor under confidentiality, and is at the Customer's cost.
- A further audit may follow a Security Incident affecting the Customer.
14. International transfers
- i-Grow.co stores and processes Customer Personal Data in the United States. Our email provider, Brevo, processes Admins' and Learners' names and email addresses in the European Union to send email.
- For personal data from the European Economic Area, the SCCs apply: Module 2 where the Customer is a controller, Module 3 where it is a processor. Annexes I and II of this DPA and the Subprocessor List complete them. Clause 7 does not apply. Under Clause 9, option 2 applies with the notice period in Section 7. The optional wording in Clause 11 does not apply. Clause 13 follows the Customer's establishment. Under Clauses 17 and 18, Irish law and the courts of Ireland apply.
- For personal data from the United Kingdom, the UK International Data Transfer Addendum to the SCCs applies.
- For personal data from Switzerland, the SCCs apply with the changes the Swiss FADP requires, and the Swiss Federal Data Protection and Information Commissioner is the supervisory authority.
15. US state privacy laws
For Customer Personal Data covered by the CCPA or a similar US state law, i-Grow.co acts as a service provider or processor and:
- Does not sell or share it, as those laws define those terms.
- Does not use, keep or disclose it outside the direct business relationship with the Customer, or for any purpose other than providing the Service.
- Does not combine it with personal data from other sources, except as those laws permit.
- Complies with those laws and gives the same level of privacy protection they require.
- Notifies the Customer if it can no longer meet these obligations, and lets the Customer take reasonable steps to stop and fix unauthorized use.
16. Liability and precedence
- Liability under this DPA is subject to Section 10 of the Customer Terms.
- If documents conflict, the SCCs prevail, then this DPA, then the Customer Terms.
- This DPA lasts as long as i-Grow.co processes Customer Personal Data.
Annex I: Details of processing
| Item | Details |
|---|---|
| Exporter | The Customer, as the controller, at the address in its account or Order |
| Importer | iGrow Inc., Chicago, Illinois, USA, as the processor. Contact: info@i-grow.co |
| Subject matter | Providing i-Grow.co Teams: building training programs and running AI conversation rehearsals |
| Duration | The subscription, plus the export and deletion periods in Section 12 |
| Purpose | Creating programs from Customer Content; running rehearsals; giving feedback and scores; showing progress to Admins; support; security |
| Data subjects | The Customer's Admins and Learners (employees and contractors). Individuals mentioned in Customer Content |
| Categories of data | Name, work email, job title and team; login and device data, including IP address; assignments and progress; Learner Content, including rehearsal text, transcripts, audio while it is processed, AI feedback and scores; personal data in documents the Customer uploads |
| Sensitive data | None intended. The Acceptable Use Policy prohibits it. Customer Content uploaded in breach of that policy is the Customer's responsibility |
| Frequency | Continuous, while the subscription is active |
| Retention | Audio: not stored by i-Grow.co; kept by OpenAI for up to 30 days for abuse monitoring. All other data: until 30 days after the export window, then deleted |
| Subprocessors | See the Subprocessor List |
Annex II: Security measures
| Area | Measure |
|---|---|
| Encryption | TLS 1.2 or higher in transit; AES-256 at rest through the database and hosting providers |
| Customer separation | Each Customer's data is separated by organization: every query is scoped to one organization, and row-level security is enabled on the database tables |
| Access control | Least privilege; multi-factor authentication on every production console (hosting, database, code, payments, AI and email providers); access reviewed every quarter and removed within 24 hours of someone leaving |
| Authentication | Admins and Learners sign in with their work email, or with Google if they choose; passwords are stored only as salted hashes |
| Secrets | Credentials are kept in the hosting provider's encrypted environment settings, never in source code |
| Change management | Every change is built in a preview environment, passes automated type checks, tests and lint, and is reviewed before it is promoted to production |
| Vulnerability management | Security fixes are prioritized by severity |
| Logging and monitoring | Application logs are kept by our hosting provider for no more than 30 days and are used to investigate errors and security issues |
| Backups | We do not currently keep separate database backups. If we add them, they are kept for no more than 30 days |
| Data minimization | Audio is not stored by i-Grow.co; AI providers receive no Learner names or email addresses |
| AI providers | Business API accounts only; no training on Customer Personal Data |
| Personnel | Confidentiality agreements for everyone with access; security training each year |
| Incident response | A written response plan; Customers notified within 72 hours of confirming a Security Incident |
| Physical security | Provided by the cloud providers' data centers, which hold SOC 2 and ISO 27001 certifications |