> For the complete documentation index, see [llms.txt](https://docs.askyazi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.askyazi.com/security-and-privacy/compliance.md).

# Compliance

Yazi's position under POPIA and GDPR, what the data processing agreement covers, the current status of ISO and SOC certifications, and how to request the security pack.

This page states Yazi's legal and certification position as plainly as possible: the roles under data protection law, what the data processing agreement (DPA) commits to, and which certifications Yazi holds and does not hold. Certification status changes, so check the date below.

{% hint style="info" %}
**In short:**

* You are the data controller. Yazi is the data processor. A DPA is signed before processing starts.
* POPIA: Yazi's Information Officer is registered with the South African Information Regulator. GDPR and UK GDPR: Yazi processes under an Article 28 DPA.
* Yazi does **not** currently hold ISO 27001, SOC 2, ISO 20252 or Cyber Essentials.

**Last checked: 23 October 2026.**
{% endhint %}

## Who is responsible for what

* **You (the client) are the controller.** You decide why and how participant data is collected, and you own the data collected through Yazi.
* **Yazi is the processor.** Yazi processes data only on your instructions and keeps it secure.
* **When a third party sits in between**, for example a research partner passing on an end client's participants, Yazi is still the processor. The paperwork changes: a DPA with Yazi plus a data sharing agreement between the other two parties. This applies whether participant data arrives by upload or through the API.
* **Ethics clearance** for commercial research sits with the controller. Yazi does not hold ethics clearance on your behalf. You can carry your own approved consent and privacy wording into the participant-facing messages.

## POPIA (South Africa)

* Yazi's Information Officer is registered with the Information Regulator and can be named in your DPA.
* Data is hosted in the UK. Transfers rely on POPIA section 72, because UK law gives protection at least equivalent to POPIA. See [Data residency and hosting](https://docs.askyazi.com/security-and-privacy/data-residency-and-hosting.md).
* A POPIA version of the DPA is available. It can include immediate breach notification, a prohibition on training AI or machine-learning models on survey responses and media unless the data is first de-identified, and a clause covering special personal information (such as health, religious or political beliefs and biometric data).
* Research is market research, not direct marketing. Your participants must have agreed to be contacted for research; marketing consent on a customer list may not cover it.

## GDPR and UK GDPR

* Yazi acts as processor under an Article 28 DPA, signed before processing starts.
* Standard Contractual Clauses can be added where needed. Transfers to Meta for WhatsApp delivery rely on the EU-U.S. Data Privacy Framework. See [Data residency and hosting](https://docs.askyazi.com/security-and-privacy/data-residency-and-hosting.md#whatsapp-and-meta).
* A Transfer Impact Assessment covering EEA, UK, US and South African data flows is available on request.
* Yazi is not registered with the UK Information Commissioner's Office because it is a South African company with no UK establishment. Its South African Information Regulator registration and named Information Officer are given instead.

## What the DPA covers

| Area                | Position                                                                                                                                                                          |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Breach notification | Yazi notifies you after becoming aware of a confirmed personal data breach, with updates as the investigation continues. Negotiated DPAs have committed to immediate notification |
| Containment         | Yazi takes reasonable steps to contain and limit a breach and cooperates with your investigation and any regulator notification                                                   |
| Sub-processors      | Named in the DPA (AWS and Meta as the core two). Notice before a new sub-processor is added, with a right to object                                                               |
| AI training         | Personal data is not used to train AI or machine-learning models, and the same applies to sub-processors by written contract                                                      |
| Backups             | Regular backups with tested restoration                                                                                                                                           |
| Retention           | Set by you in the DPA or statement of work                                                                                                                                        |
| Deletion            | Full deletion on your instruction, including backups and anonymised responses if you ask, with a certificate of deletion                                                          |
| End of contract     | A window to export your data before deletion. The DPA's security obligations continue after termination                                                                           |

Before countersigning, Yazi needs your company name, country and registered address, the governing law and jurisdiction, the effective date and the signatory's details. Sending these up front saves a round trip.

## Certification status

**Last checked: 23 October 2026.** Ask Yazi for the current position before relying on this table in a submission.

| Standard                             | Status                              | Notes                                                                                                                                       |
| ------------------------------------ | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| ISO/IEC 27001 (information security) | **Not certified**                   | Yazi's information security management system is being aligned with ISO/IEC 27001:2022, and certification work is under way                 |
| SOC 2 Type II                        | **Not held**                        |                                                                                                                                             |
| ISO 20252 (market research quality)  | **Not certified**                   | Certification work is under way with an accredited certification body                                                                       |
| Cyber Essentials (UK)                | **Not held**                        |                                                                                                                                             |
| AWS infrastructure                   | Covered by AWS's own certifications | AWS holds ISO 27001 and SOC 2 Type II, among others, available from AWS Artifact. These cover AWS's infrastructure, not Yazi's own controls |

## Security controls in place today

While certification is in progress, these are the controls Yazi can evidence:

* AES-256 encryption at rest, TLS 1.2 or higher in transit
* hosting on AWS in London inside a private network, with least-privilege access
* multi-factor authentication for team sign-in
* separation of each organisation's data, checked on every request
* audit records of changes to study data and of any Yazi staff access to your organisation
* participant phone numbers kept out of system logs, surnames kept out of AI prompts, and participant codes in exports that cannot be reversed
* full deletion at project end with a certificate of deletion

See the [Security overview](https://docs.askyazi.com/security-and-privacy/security-overview.md) for detail.

## Request the security pack

The security pack includes the DPA template, sub-processor register, Information Security Policy, Data Retention Policy, Vendor Management Policy, Data Residency Declaration Policy, Transfer Impact Assessment, and completed SIG Lite and audit documentation questionnaires.

Email <hello@askyazi.com>, or ask your Yazi contact. Use the same address to send a participant's erasure request. Yazi can also meet your security team to go through a questionnaire.

## Limits and things to know

* **No certificate yet.** If your procurement rules require ISO 27001, SOC 2, ISO 20252 or Cyber Essentials before onboarding, raise it early so you can check whether evidence of controls will be accepted instead.
* **Dates move.** Treat any certification date as a target until a certificate is issued.
* **No built-in age gate.** If minors could take part, consent arrangements are part of your study design. See [Participant privacy](https://docs.askyazi.com/security-and-privacy/participant-privacy.md).
* **Other national laws.** If your participants are covered by another country's data protection law, raise it before contracting so the DPA can address it.

## Related

* [Security overview](https://docs.askyazi.com/security-and-privacy/security-overview.md)
* [Data residency and hosting](https://docs.askyazi.com/security-and-privacy/data-residency-and-hosting.md)
* [Participant privacy](https://docs.askyazi.com/security-and-privacy/participant-privacy.md)
* [AI and your data](https://docs.askyazi.com/security-and-privacy/ai-and-your-data.md)
* [Get help](https://docs.askyazi.com/help/get-help.md)
