Version 2026-11-06
Data Processing Agreement
Draft for legal review. Items in [square brackets] must be completed and this text approved by a qualified lawyer before the product is offered to the public.
1. Parties and scope
This Data Processing Agreement (“DPA”) is between the ministry or organization that holds a Grow Impact OS workspace (the “Ministry”, the controller) and Yassine Qoura (autónomo), trading as Ravashift (“we”, the processor). It forms part of the Terms of Use and applies to personal data we process on the Ministry's behalf (“Ministry Data”). It is accepted when the Ministry accepts the Terms. A countersigned copy is available on request from yassine@growimpactos.com.
It is written to meet Article 28 of the EU and UK GDPR and the equivalent requirements of the Swiss FADP, the California CCPA/CPRA and other US state laws, Brazil's LGPD, Canada's PIPEDA, South Africa's POPIA, India's DPDP Act and similar laws. Where a law gives the Ministry more protection, that law prevails.
2. Details of the processing
- Subject matter and purpose: providing Grow Impact OS: storing and organizing applicants, students, staff and supporters, publishing the Ministry's websites and forms, sending its messages and processing its payments.
- Duration: while the Ministry has a workspace, plus the deletion periods in section 10.
- Data subjects: applicants, students, alumni, staff, volunteers, donors, website visitors and other people the Ministry chooses to manage.
- Types of data: contact details, application answers, notes, messages, files, program and payment records, and anything else the Ministry collects with its forms.
- Special categories: only if the Ministry chooses to collect them, for example health information or religious beliefs. The Ministry may not use the service to collect data about people under 18, except applicants aged 16 or 17 to a program it has opened to them, with a parent's or guardian's agreement recorded on the form. The Ministry is responsible for the lawful basis and any consent.
3. Our obligations
- We process Ministry Data only on the Ministry's documented instructions. These Terms, this DPA and the Ministry's use of the product's features are its instructions. We will tell the Ministry if we believe an instruction breaks the law.
- We do not sell or share Ministry Data, use it for our own purposes, combine it with other data, or use it to train artificial intelligence models. (For US state laws, we act as a service provider and certify that we understand these restrictions.)
- Everyone who can access Ministry Data at our company is bound by confidentiality.
- We apply the security measures in section 11.
4. The Ministry's obligations
The Ministry is responsible for the lawfulness of the data it collects and its instructions, for giving people a privacy notice (Grow Impact OS provides a standard notice for its forms), for any consents required (including checking a parent's or guardian's agreement for applicants aged 16 or 17), and for keeping its own sign-in details secure.
5. Subprocessors
The Ministry authorizes the subprocessors on our Subprocessors page. We impose data protection terms on them that are at least as protective as this DPA and remain responsible for them. We give at least 30 days' notice of a new subprocessor; the Ministry may object on reasonable data protection grounds, and if we cannot resolve the objection it may end its subscription with a refund of prepaid fees for the remaining period.
6. International transfers
Where Ministry Data is transferred out of the EEA, the UK or Switzerland to a country without an adequacy decision, the European Commission's Standard Contractual Clauses (Module 2 or 3, as applicable) are incorporated into this DPA by reference, with the UK Addendum and Swiss amendments where relevant, and equivalent clauses under other laws (such as Brazil's standard clauses). Governing law and courts for the clauses: Spain. [Lawyer to complete the annexes of the clauses.]
7. Helping with people's rights
The product lets the Ministry find, correct and delete the data it holds [and export it: confirm]. If we receive a request directly from a person about Ministry Data, we pass it to the Ministry without undue delay and do not answer it ourselves unless the Ministry asks. We help the Ministry respond where it cannot do so with the product.
8. Personal data breaches
We notify the Ministry without undue delay, and in any case within 48 hours, after becoming aware of a breach affecting Ministry Data, with what we know about its nature, likely consequences and the measures taken, and we update it as we learn more. We help the Ministry meet its own notification duties to authorities and people (for example 72 hours under the GDPR).
9. Assessments and audits
We give the Ministry the information it reasonably needs to show compliance and to carry out data protection impact assessments. The Ministry may audit our compliance once a year, or after a breach, with 30 days' notice, during business hours and under confidentiality, at its own cost; we may first answer with documentation, such as our providers' security certifications (for example SOC 2 or ISO 27001 reports).
10. Deleting or returning data
When the subscription ends, the Ministry can ask for an export during the read-only period. We delete Ministry Data 60 days after the subscription ends (or at the end of a paid archive), unless the law requires us to keep it. Copies in encrypted backups are deleted as the backups are overwritten [confirm backup period].
11. Security measures
- Encryption in transit (HTTPS/TLS) and at rest, by our hosting providers.
- Separation of each Ministry's data with database row-level security, so one workspace cannot read another's.
- Roles and permissions inside each workspace; staff access to production data only when needed for support or security.
- Two-step sign-in available to every user, slowing down of repeated failed sign-ins, and email alerts for important account changes.
- A log of security events, kept for one year.
- A strict content security policy and other web protections against injected code; spam and abuse controls on public forms.
- Hosting with providers that hold recognized security certifications; regular backups [confirm frequency].
- Regular updates of software dependencies and review of changes before release.
12. Liability and order of precedence
Liability under this DPA is subject to the limits in the Terms, except where the law does not allow it. If this DPA conflicts with the Terms on data protection, this DPA prevails; if it conflicts with the Standard Contractual Clauses, the clauses prevail.