Skip to content

Security

Where your data lives, and who can see it

This page matches the Privacy Notice (teams-privacy-2026-11-17) and the Data Processing Addendum (teams-dpa-2026-11-17).

Where data lives

We store and process data in the United States. Brevo processes names and email addresses in the European Union to send email. Where data protection law requires it, transfers are covered by the European Commission’s Standard Contractual Clauses, the UK International Data Transfer Addendum and, for Switzerland, those Clauses with the changes Swiss law requires, as the Data Processing Addendum describes.

Teams data is stored separately from an individual i-Grow.co plan, even when both use the same email address. It is not shown in or shared with that individual account. Signing in to Teams uses its own session. Signing out of one does not sign you out of the other.

Who can see what

Your organization is the controller of the data it and its people put into Teams. We process that data as its processor. Admins and leaders can see:

  • that someone was invited and joined
  • the programs assigned to them
  • whether they have started or completed those programs
  • how many of a program’s lessons they have marked as read
  • for a formal assessment: a rating level for each TEND dimension, whether it was backed by the learner’s own words, the date, and the rubric version

They see an assessment reply or feedback only if the learner chooses to share it, for example with a re-check request.

Practice stays with the learner

Practice is private to the learner. Admins and leaders never see practice transcripts. The organization’s contract gives it no right to see, export, or receive practice, and we will not act on a request from it to reveal practice.

We look at or disclose practice only to provide the service to the learner, to investigate a security incident or abuse (through authorized staff bound by confidentiality), at the learner’s request, or when the law requires it. In the last case, we tell the learner where the law allows.

In voice practice, audio goes to OpenAI to be transcribed and answered. i-Grow.co does not store that audio. OpenAI may keep inputs and outputs for up to 30 days for abuse monitoring. Neither we nor our AI providers use practice to train or improve AI models. AI providers receive only what each request needs, never a learner’s name or email address.

How long we keep it

  • While the subscription is active, we keep the organization’s data, including practice.
  • When a subscription ends, access ends. For 30 days, the organization can ask for a copy of its reports. Those reports never include practice. Within 30 days after that window, we delete the 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.
  • If the organization removes someone, access ends at once. Their records stay until the organization asks us to delete them, or until the organization’s data is deleted as above.
  • Free-trial data is deleted 30 days after a trial ends, unless the organization subscribes.
  • Hosting logs are kept for no more than 30 days.
  • Billing and terms-acceptance records are kept as long as tax, accounting, and legal rules require.

The notice and the addendum set these periods. We confirm deletion in writing on request. Automatic deletion after the window is not part of the product running today.

How it is protected

  • TLS 1.2 or higher in transit, and AES-256 at rest through the database and hosting providers.
  • Each organization’s data is separated. Row-level security is on, and the browser does not query the database directly.
  • Passwords are stored only as salted hashes. Multi-factor authentication is on for production consoles.
  • Two independent switches can pause the whole product.

We do not currently hold a SOC 2, ISO 27001, or HIPAA certification. Physical security is the cloud providers’ data centers, which hold SOC 2 and ISO 27001 certifications. That is their certification, not ours.

Who else handles data

The providers that help us run Teams are listed on the subprocessor list: Vercel, Supabase, OpenAI, Anthropic, Stripe, Brevo, and Google (only if someone chooses Sign in with Google). Firecrawl reads public website pages for the website analysis and receives no personal data from Teams.