iyedy

Data processing agreement

In force from 25 October 2026.

1. Parties and purpose

This data processing agreement (the "Agreement") is made between:

• the business customer that subscribes to a Team or Enterprise plan, or to the Pro or Pro+ plan for the needs of its business (the "Customer"), as controller;
• Youssef ASKRI EI, sole trader, publisher of the iyedy service, 96 rue Jean Jaurès, 95870 Bezons, France, SIREN 105 883 425 ("iyedy"), as processor.

It sets the terms on which iyedy processes personal data on the Customer’s behalf, under article 28 of Regulation (EU) 2016/679 (the "GDPR"). It is part of the terms of use and sale (the "Contract"); the Customer accepts it when subscribing, by ticking the checkbox provided for this. For the Enterprise plan, the signed contract may supplement it. If they conflict on the protection of personal data, the Agreement prevails over the Contract.

2. Definitions

The terms "personal data", "processing", "controller", "processor", "data subject" and "personal data breach" have the meaning given in article 4 of the GDPR. "Customer Data" means the personal data iyedy processes on the Customer’s behalf in providing the service. A "sub-processor" is a provider to which iyedy entrusts all or part of that processing.

3. Description of the processing

Subject matter and duration

Providing the Customer with the iyedy service described in the Contract, for the term of the Contract, then for the time needed to return and delete the data (section 13).

Nature and purpose

Hosting, storage, organisation, consultation, display and sharing according to the Customer’s settings, search, version management, audit log, backup, AI assistance, the landscape map included, according to the Customer’s settings (section 9), support at the Customer’s request and the security of the service. The sole purpose is to provide the service to the Customer and its users.

Data subjects

The users the Customer authorises (members and guests: viewers, commenters, editors), invited persons, and persons whose data the Customer puts in its content (staff, contacts or suppliers named in a diagram, a review or a decision).

Categories of data

• Identification and business contact details: name, e-mail address.
• Roles, seats and membership of spaces.
• Connection data: sessions, single sign-on identifiers.
• Audit log: actions, dates, IP addresses, browser.
• The Customer’s content (diagrams, models, documents, comments, decisions, imported files) and the personal data it puts in it.
• Requests sent to the assistant and the files attached to them, the web search queries it makes to answer them, conversation threads, and the summaries of the landscape map.
• Support exchanges.

Sensitive data

The service is not designed to process special categories of data (GDPR art. 9) or data relating to criminal convictions and offences (art. 10); the Customer refrains from putting any in its content.

Outside the scope of the Agreement

The data iyedy processes on its own account, as controller (management of the customer account and the contract, billing, security of the service and abuse prevention, audience measurement), is covered by the privacy policy.

4. Obligations of the Customer

The Customer:

• has a legal basis for the processing it entrusts to iyedy and informs the data subjects;
• gives iyedy instructions that comply with the GDPR;
• chooses the settings suited to its data: AI and the landscape map on or off, classification ceiling, guests, public links, roles and seats; a conversation thread retention shorter than 30 days is asked of support;
• ensures that its users comply with the Contract and keep their sign-in details confidential;
• puts no sensitive data in its content (section 3).

5. Obligations of iyedy

iyedy:

• processes Customer Data only on the Customer’s documented instructions, including for transfers outside the European Union: the Contract, the Agreement and the settings the Customer makes in the service are its instructions;
• immediately informs the Customer if an instruction appears to infringe the GDPR or other data protection provisions;
• if Union or member state law requires it to process the data otherwise, informs the Customer before processing, unless that law prohibits it;
• does not use Customer Data for its own purposes: no sale, no advertising, no training of AI models;
• keeps a record of the categories of processing carried out on behalf of its customers (GDPR art. 30(2));
• cooperates with the supervisory authority.

iyedy’s data protection contact is contact@iyedy.com.

6. Confidentiality

iyedy ensures that anyone authorised to process Customer Data has committed to confidentiality or is under an appropriate legal obligation of confidentiality. On the date of the Agreement, only the publisher administers the service. iyedy accesses the Customer’s content only when needed to provide the service, at the Customer’s request (support), to handle a security incident or to meet a legal obligation.

7. Security

iyedy implements the technical and organisational measures described in annex 1 to ensure a level of security appropriate to the risk (GDPR art. 32). These measures may change with the service, never lowering the overall level of protection.

8. Sub-processors

The Customer gives iyedy a general written authorisation to engage sub-processors (GDPR art. 28(2)). The current list, with the name, country, service and safeguards of each, forms annex 2 "List of sub-processors". It is not published on this site: it is sent to the Customer when it subscribes, then on request at contact@iyedy.com. Its categories are summarised in annex 2 below.

iyedy informs the Customer of any intended addition or replacement of a sub-processor at least 30 days before it takes effect, by e-mail to the owners and billing administrators of its organisation or, for the Pro and Pro+ plans, to the account holder. The Customer may object within that period, in writing and on reasonable grounds relating to data protection. The parties then look in good faith for a solution, for example turning the feature concerned off for the Customer. Failing one, the Customer may terminate the part of the service concerned without penalty before the change takes effect, and iyedy refunds the part of the price paid in advance for the period still to run.

If a sub-processor must be replaced urgently (failure, end of business, security risk), iyedy informs the Customer as soon as possible, and the Customer has the same right to object.

iyedy imposes on each sub-processor, by contract, the same data protection obligations as those set out in this Agreement, in particular sufficient guarantees to implement appropriate technical and organisational measures (GDPR art. 28(4)), and remains fully liable to the Customer for the performance of their obligations.

9. Transfers outside the European Union

Customer Data is hosted in the European Union. While the AI assistant is on, what it sends to the AI model provider is processed by that provider with no guarantee of processing inside the European Union, and deleted by it within 30 days, except content flagged by its safety checks, which it keeps under its own terms. This is what each request of the Customer’s users needs (the useful part of its content, or the photo or PDF attached, sent whole), the web search queries the assistant makes and, while the landscape map is on, the elements of the diagrams the assistant summarises in the background (name, kind, technology, short description and links). The Customer can turn AI off, or only the landscape map, or set a classification ceiling above which a diagram is never sent.

For the Pro and Pro+ plans, the AI assistant and the landscape map are on by default: accepting this Agreement when subscribing is a documented instruction of the Customer (section 5) for this processing, which the Customer stops at any time in the AI settings. For the Team and Enterprise plans, the AI assistant stays off until an owner of the organisation has accepted the AI addendum (version 2026-09) in the application, by which the Customer accepts the processing by the AI model provider that this section describes in its version in force; that acceptance is a documented instruction of the Customer (section 5). The text of this section accepted with the addendum before 25 October 2026 is in annex 3. The landscape map stays off there until an owner or a security admin turns it on, which is also a documented instruction.

The other sub-processors, all OVH SAS (France), for hosting, e-mail and backups, host the Customer Data in the European Union; any access by them from outside the Union, for support or maintenance, falls under the next paragraph.

Any transfer outside the European Economic Area is covered by the standard contractual clauses adopted by the European Commission (Implementing Decision (EU) 2021/914, module 3: processor to processor) made with the sub-processor concerned, or by an adequacy decision where it applies. The Customer can obtain a copy at contact@iyedy.com.

10. Data subjects’ rights

iyedy assists the Customer, by appropriate technical and organisational measures, in answering requests to exercise data subjects’ rights (GDPR art. 12 to 22). For this, the service provides the management of members, their roles and their access; the export of each view of the diagrams and, at an owner’s request to support, an archive of the space; viewing and erasure by each user of their conversation threads with the assistant; the deletion of diagrams and comments.

If iyedy receives a request from a data subject about Customer Data directly, it passes it on to the Customer without undue delay and does not answer it itself, except to tell the person to contact the Customer.

11. Assistance to the Customer

iyedy assists the Customer in meeting the obligations of articles 32 to 36 of the GDPR (security, breach notification, impact assessment, prior consultation), taking into account the nature of the processing and the information available to it: in particular, it provides the Agreement, its annexes and its answers to security questionnaires.

12. Personal data breaches

iyedy notifies the Customer of any personal data breach affecting Customer Data without undue delay, and no later than 72 hours after becoming aware of it, by e-mail to the owners of its organisation or, for the Pro and Pro+ plans, to the account holder. The notification describes, as far as possible, the nature of the breach, the categories and approximate number of data subjects and records concerned, its likely consequences, the measures taken or proposed to address it and mitigate its effects, and the contact from whom more information can be obtained. Where not all the information is available at once, it is provided in phases without undue delay.

iyedy documents every breach and assists the Customer in notifying it to the supervisory authority and, where needed, to the data subjects.

13. Return and deletion of data

Throughout the Contract, the Customer can export its data: each view as SVG, PNG, draw.io, Mermaid, PlantUML or C4-PlantUML, and the review file as PDF; an archive of the workspace is provided at an owner’s request to support@iyedy.com. When a subscription ends, members keep read and export access while the organisation exists.

On the written request of an owner of the organisation to support@iyedy.com, iyedy deletes the organisation and Customer Data within 30 days and confirms it in writing: at the latest 30 days after that request, the encryption keys specific to the Customer are destroyed, which makes its encrypted content unreadable in the live database; the backups that still hold those keys expire at the latest about 65 days later. The other Customer Data is erased within the same 30 days in the live database, then disappears from the backups no later than about 65 days after that. iyedy keeps only what the law requires it to keep as a controller, such as invoices.

14. Audits

iyedy makes available to the Customer the information needed to demonstrate compliance with article 28 of the GDPR: the Agreement, its annexes and its answers to security questionnaires. The Customer may also have an audit carried out, by itself or by an independent auditor bound by confidentiality who is not a competitor of iyedy, at most once a year, and in addition after a data breach affecting it or at the request of a supervisory authority, with 30 days’ written notice. The audit is first carried out on documents; an on-site check takes place only if the documents are not enough. It takes place during business hours, without disrupting the service, giving access to other customers’ data or compromising their security. Its costs are borne by the Customer.

15. Liability

iyedy’s liability under the Agreement is governed by the conditions and limits the Contract sets towards businesses (section 15 of the terms); the Customer’s, by the general law. These provisions do not limit the rights data subjects hold under article 82 of the GDPR.

16. Term and changes

The Agreement takes effect on subscription and lasts as long as iyedy processes Customer Data. The clauses on confidentiality, deletion of data and liability survive its end for as long as needed.

iyedy may change the Agreement to follow changes in the law or the service, informing the Customer at least 30 days in advance; a change that would reduce the protection of Customer Data gives the Customer the right to terminate without penalty before it takes effect. This version applies to Agreements made from 25 October 2026; for an Agreement made before that date, it applies from 25 November 2026, after that notice.

17. Governing law

The Agreement is governed by French law. Disputes fall under the courts designated in the Contract for businesses. The French version prevails.

Annex 1: technical and organisational measures

• Encryption in transit. Connections between browsers and the service are encrypted (HTTPS), as are the service’s exchanges with the payment provider and the AI model provider, and the sending of e-mail.
• Encryption of content. The Customer’s content (models, descriptions, reviews, layouts, versions, change log, stored objects, the assistant’s conversation threads, the summaries of the landscape map) is encrypted with AES-256-GCM under a key specific to the Customer, itself encrypted by a master key of the environment. Titles, names, tags and search text stay in clear so that lists and search work.
• Cryptographic erasure. The key specific to the Customer is destroyed in the live database at the latest 30 days after the request to delete its organisation (section 13); earlier backups, which still hold it, expire afterwards (see Backups).
• Customer isolation. The database itself only lets each request read or write the data of the customer of its context, a signed context that an SQL injection cannot change. A refused access does not reveal whether the resource exists.
• Access control. Roles per organisation, space and diagram; guests limited to the read, comment or edit rights granted; public links created at the Customer’s initiative; the organisation’s single sign-on, depending on the plan.
• Authentication. Passwords kept as hashes by the identity service; e-mail address confirmed with a code; sessions identified by tokens of which only a hash is stored.
• Audit log. Actions in spaces are written to an append-only log, chained by hashes and sealed regularly: any change, deletion or insertion after the fact can be detected, and the Customer can check its integrity. Its retention depends on the plan.
• AI under the Customer’s control. AI is turned off per account or organisation, and the landscape map on its own; a classification ceiling stops diagrams classified above it from being sent, the landscape map included; requests are built by the server from the stored model; for a simple request, the preview of what will be sent is exactly what is sent, and a longer request (a change, a review, research) then lists what it read, under "How I got this"; neither requests nor content appear in the technical logs.
• Infrastructure. A dedicated server at OVH SAS (a rented physical server), in the European Union, which also runs other services, each in its own space; a segmented internal network where each component can only reach those it needs; containers run without privileges on a read-only file system; administration consoles not exposed to the internet; a test environment separate from production (distinct space, database, keys and secrets) and holding no real data.
• Backups. A backup every night, encrypted (AES-256) before it leaves the server, to separate storage that is versioned and locked against deletion; kept 30 days, deleted data disappearing from it at the latest about 65 days later; restore tested.
• Monitoring. Logs and metrics collected on iyedy’s own infrastructure, with no third-party monitoring service; they hold user identifiers and IP addresses, never secrets, requests to the assistant or diagram content.
• Organisation. A single administrator, the publisher; secrets specific to each environment, never stored in the source code; a security self-assessment against OWASP ASVS level 2. No certification and no external audit to date.

Annex 2: sub-processors

The list of sub-processors by name (name, address, country, service, data concerned, safeguards) is not published on this site. It is sent to the Customer when it subscribes and on request at contact@iyedy.com, and kept up to date under section 8. It covers the following categories:

• Hosting of the service and its data: OVH SAS (France), in a data centre in the European Union.
• Sending the service’s e-mail: OVH SAS (France), in the European Union.
• Storage of the encrypted backups: OVH SAS (France), Object Storage, Paris region.
• AI model provider: while the assistant is on (section 9), for what each request needs, attached files included, the assistant’s web search queries and, while the landscape map is on, the elements of the diagrams it summarises; processing with no guarantee of location inside the European Union, deletion within 30 days, except content flagged by its safety checks.

Stripe, iyedy’s payment provider, processes the billing data of the business relationship between iyedy and the Customer, for which iyedy is the controller: it is not a sub-processor within the meaning of the Agreement.

Annex 3: earlier text of section 9

The first two paragraphs of section 9, in the version organisation owners accepted with the AI addendum (version 2026-09) before 25 October 2026. They are reproduced for reference: section 9 above describes the processing as it is, and applies to those organisations under section 16.

Back to the home page