Data Processing Agreement
Article 28 GDPR terms governing YPrtnrs's processing of personal data on behalf of paid customers.
Last updated: 2 November 20261. Parties and Scope
This Data Processing Agreement ("DPA") forms part of the YPrtnrs Terms of Service between SASU YPrtnrs (RCS Paris 106 818 321, registered office 1 rue de Stockholm, 75008 Paris) ("Processor") and the customer entity that orders a one-time paid analysis (360° AI Diagnostic, 360° AI Diagnostics Pack, Complete AI Blueprint) or subscribes to a paid YPrtnrs plan ("Controller"). It governs the processing of personal data carried out by YPrtnrs on behalf of the Controller in connection with the Services, in accordance with Article 28 GDPR.
For shared workspaces, the Controller is the account holder; YPrtnrs acts as Processor for personal data of invited team members and content placed inside the workspace.
2. Subject Matter and Duration
Subject matter: provision of the YPrtnrs platform (AI Pulse, AI Blueprint, project execution service, RAG knowledge base and supporting tools).
Duration: for a one-time analysis, for the time needed to perform and review the ordered service; for a subscription, for the term of the active subscription. In both cases, subsequent retention follows the per-data-type periods described in the Privacy Policy, plus any period strictly required by law or expressly agreed in writing.
3. Nature and Purpose of Processing
Hosting, structuring and serving Controller content; running diagnostics; generating Blueprints and recommendations; running the Y Chief of Staff agent; managing accounts, billing and support; producing aggregated, non-personal usage analytics.
4. Categories of Data Subjects and Personal Data
Data subjects: the Controller's employees, contractors, invited team members and authorised end-users.
Personal data categories:
- Identification: name, email, job title, organisation
- Account / authentication: password hashes, session tokens, IP address (truncated)
- Content provided by the Controller: diagnostic responses, uploaded documents, knowledge-base content, agent conversations
- Usage: pages, actions, timestamps, device / browser metadata
No special-category data (Art. 9 GDPR) is intentionally processed; the Controller undertakes not to upload such data without prior anonymisation.
5. Processor Obligations
YPrtnrs shall:
- process personal data only on documented instructions from the Controller (the Services configuration and these terms constitute such instructions)
- ensure persons authorised to process personal data are bound by confidentiality
- implement the technical and organisational measures described in §8
- assist the Controller in fulfilling data-subject requests and DPIAs
- notify the Controller without undue delay (and within 72 hours where feasible) of a personal data breach
- at the Controller's choice, delete or return all personal data after end of provision of services
- make available all information necessary to demonstrate compliance and allow audits as set out in §9.
6. Sub-Processors
The Controller provides general written authorisation for YPrtnrs to engage sub-processors. The current list is published at https://yprtnrs.com/legal/sub-processors and is incorporated into this DPA by reference.
YPrtnrs will inform the Controller of any intended addition or replacement of sub-processors with at least 30 days' notice via email or in-product notice, giving the Controller the opportunity to object on reasonable, documented data-protection grounds.
YPrtnrs imposes data-protection obligations on each sub-processor that are no less protective than those in this DPA, and remains fully liable for the performance of each sub-processor.
7. International Transfers
Persistent customer data (databases, files) is hosted in the EU (AWS Frankfurt primary, Dublin failover; Supabase EU). RAG retrieval today is keyword/SQL only, run in-EU on Supabase Postgres — no vector database and no vector transfer occur. If vector embeddings are introduced in the future they will stay in-EU (in-region pgvector or an EU-hosted equivalent), and this DPA will be updated before that change ships.
The model provider, model and region applicable to each function are those identified in the contractual processing schedule for the service concerned and in the sub-processor list; there is no single fixed mapping between a function and a provider. Whatever the provider, your data is not sold, is processed only for the purpose of the service, remains confidential and is not used to train AI models. Each provider’s retention periods are those set by its applicable terms and by the processing schedule. For information, the analysis engine’s code documents an integration with Mistral AI. This describes a technical capability: it does not add a sub-processor and is not a commitment on region or retention.
Persistent storage remains in the European Union. Where AI processing takes place outside the EU/EEA, it happens only within the existing contractual safeguards, including the EU Standard Contractual Clauses (Decision 2021/914), with encryption in transit and data minimisation.
8. Security Measures (Annex II)
Encryption: TLS 1.3 in transit; AES-256 at rest; signed URLs with short expiry; secrets stored in vault. Access control: per-user authentication, role-based access, least-privilege principle, has_role() security-definer functions, scoped/expiring API keys, two-factor verification for sensitive actions. Data isolation: per-tenant Row-Level Security across 60+ tables; service-role tables restricted from client access. Application security: input validation and DOMPurify sanitisation, rate limiting, CORS controls. Infrastructure: EU residency, multi-AZ redundancy, monitored incident response, AWS / Supabase SOC 2 (sub-processors: AWS, Supabase — see /legal/sub-processors). Governance: documented retention, deletion and incident-response procedures; annual review.
9. Audits
On reasonable prior written notice (at least 30 days, except for incidents) and not more than once per 12 months, the Controller may request a written audit response covering YPrtnrs's compliance with this DPA. YPrtnrs may satisfy this through up-to-date third-party certifications (e.g. SOC 2 reports of underlying providers), security questionnaires, and the published security documentation. On-site audits, if strictly necessary, are subject to a separate confidentiality and cost-allocation agreement.
10. Data Subject Rights and Assistance
Taking into account the nature of processing, YPrtnrs assists the Controller with appropriate technical and organisational measures, insofar as possible, in fulfilling its obligations to respond to requests from data subjects (access, rectification, erasure, restriction, portability, objection). Most actions can be performed by the Controller directly via the dashboard; manual assistance can be requested at privacy@yprtnrs.com.
11. Return or Deletion
On termination of the Services, YPrtnrs will, at the Controller's choice, return or delete all personal data processed on behalf of the Controller within 30 days, unless retention is required by Union or Member-State law. Standard backups are purged within their normal rotation window (maximum 35 days).
12. Liability and Governing Law
Liability under this DPA is governed by the limitations set out in the YPrtnrs Terms of Service. This DPA is governed by the laws of France; competent courts of Paris have jurisdiction, without prejudice to any mandatory data-protection rules of the data subjects' jurisdictions.
Need a counter-signed copy or have questions about this DPA?
Contact privacy@yprtnrs.com →
