How we process your personal data, in plain language.
This Privacy Policy describes how SINAURA S.R.L. processes the personal data of users of the website ariaplt.com and of the platform app.ariaplt.com, pursuant to Regulation (EU) 2016/679 (the “GDPR”) and Italian data protection law.
Version 1.4 · Last updated: 6 October 2026 · Reference: GDPR · Italian D.Lgs. 196/2003 · EU AI Act (Reg. 2024/1689) · NIS2 (Dir. 2022/2555) · EU Data Act (Reg. 2023/2854)
DOCUMENT MAP
- Controller, joint roles and Data Protection Contact
- Scope, intended audience and roles
- SINAURA acting as Controller — processing of prospects, visitors, candidates, business contacts
- SINAURA acting as Processor — processing of Customer data on the Platform
- Categories of data
- Purposes, legal bases and retention — Controller-side
- Purposes, legal bases and retention — Processor-side
- Legitimate interest — synthetic balancing test (LIA summary)
- Automated processing, Artificial Intelligence and transparency under the AI Act
- Industrial data, telemetry, and interaction with the EU Data Act
- Recipients and sub-processors
- Extra-EU transfers
- Security measures (Art. 32 GDPR), NIS2 and DORA
- Personal data breach — dual-track procedure (Controller / Processor)
- Data subject rights
- Cookies, trackers and tracking pixels
- Privacy by design and by default (Art. 25 GDPR)
- DPIA and accountability
- Children
- Special categories (Art. 9) and criminal-conviction data (Art. 10)
- Complaints to the Supervisory Authority
- Document hierarchy and language
- Amendments
- Applicable addenda and exhibits
- Contacting SINAURA
1 · CONTROLLER, JOINT ROLES AND DATA PROTECTION CONTACT
Controller
SINAURA S.R.L. ("SINAURA", "we", "us", "our") — Viale Luigi Majno n. 7, 20122 Milan, Italy. VAT no. IT14280020968. Certified email (PEC): sinaurasrl@legalmail.it. General email: info@sinauragroup.com.
Data Protection Contact
Sinaura™ Legal Department — info@sinauragroup.com. SINAURA has not designated a Data Protection Officer under Art. 37 GDPR, as it does not, at the date of this version, meet the mandatory designation criteria of Art. 37(1) GDPR. The Legal Department acts as the internal contact point for data protection matters and responds to all data protection requests.
For industrial and workspace data uploaded by the Customer onto the platform, SINAURA acts as Processor (Art. 28 GDPR) on behalf of the Customer, according to the terms of the DPA signed by the Parties.
Joint controllers
SINAURA does not act as joint controller (Art. 26 GDPR) for the operation of the AriaPLT™ Platform. Any future joint controllership arrangement will be governed by a separate written agreement and disclosed in this Privacy Policy.
2 · SCOPE, INTENDED AUDIENCE AND ROLES
This Privacy Policy describes how SINAURA processes the personal data of:
- visitors of the websites ariaplt.com and sinauragroup.com;
- prospects who submit demo requests, contact forms, attend webinars or events organised by SINAURA;
- candidates who apply for open positions;
- suppliers, partners and business contacts of SINAURA;
- Authorised Users (natural persons designated by Customers) of the SaaS platform reachable at app.ariaplt.com;
- Customer-side data subjects whose personal data is uploaded onto or generated within the Platform by the Customer.
AriaPLT™ is a professional B2B Agentic AI platform addressed to legal entities operating in safety/mission-critical industrial environments (DCS, SCADA, MES, SIS). The Platform is not directed to consumers and not directed to minors (see §19).
Roles under GDPR
SINAURA processes personal data under two distinct GDPR roles, with separate disciplines:
| Scope | Role | Reference |
|---|---|---|
| ariaplt.com / sinauragroup.com websites, marketing, prospects, candidates, suppliers, billing, business contacts | Controller under Art. 4(7) GDPR | §3 of this Privacy Policy |
| Personal data uploaded by the Customer onto AriaPLT™ or generated by the Authorised Users within the Customer's tenant workspace | Processor under Art. 4(8) and Art. 28 GDPR, acting on behalf of the Customer (who is the Controller) | §4 of this Privacy Policy and DPA executed between SINAURA and the Customer |
The distinction is binding. Where SINAURA acts as Processor, the instructions of the Customer prevail, subject to the limits of Art. 28(3)(a) GDPR (unlawful instructions).
3 · SINAURA AS CONTROLLER — WEBSITES, MARKETING, PROSPECTS, CANDIDATES, BUSINESS CONTACTS
This section discharges the information obligations of Art. 13 GDPR (and, where applicable, Art. 14 for data not collected from the data subject) for processing activities carried out by SINAURA as Controller.
3.1 Visitors of ariaplt.com and sinauragroup.com
- Data: IP address, browser, operating system, pages visited, referrer, technical event data, technical cookies and aggregated analytics (see §16).
- Purpose: operation, security and statistical analysis of the websites.
- Legal basis: Art. 6(1)(f) GDPR — legitimate interest of SINAURA in operating and securing its websites (see §8 for balancing test).
- Retention: technical server logs 12 months; aggregated analytics up to 24 months in anonymised form.
3.2 Prospects (demo requests, contact forms, webinars, events)
- Data: name, business email, company, role, country, message content.
- Purpose: respond to the request, evaluate pre-contractual interest, send the requested commercial information.
- Legal basis: Art. 6(1)(b) GDPR — pre-contractual measures taken at the request of the data subject; Art. 6(1)(a) GDPR for subsequent direct marketing.
- Retention: 24 months from last interaction in the absence of a contract; afterwards anonymisation or deletion. Marketing consent: until withdrawal.
3.3 Candidates (recruiting)
- Data: CV, contact details, professional history, technical skills, optional information voluntarily provided by the candidate.
- Purpose: evaluation of the application for a current or future open position.
- Legal basis: Art. 6(1)(b) GDPR — pre-contractual measures; for retention beyond the specific position, Art. 6(1)(a) consent.
- Retention: 12 months from receipt of the application; longer retention only with explicit consent to be kept in the talent pool, maximum 36 months.
- Note: candidates are invited not to upload special categories of data under Art. 9 GDPR (e.g. health information, photographs revealing sensitive information) unless strictly relevant.
3.4 Direct marketing communications
- Existing Customers — communications on similar products/services: legal basis Art. 6(1)(f) GDPR combined with Art. 130(4) D.Lgs. 196/2003 ("soft opt-in"). Right to object at any time at no cost, including via the one-click withdrawal link in every email.
- Prospects and contacts not yet Customers: legal basis Art. 6(1)(a) GDPR — explicit, freely given, specific, informed, unambiguous and documented consent obtained at registration. Withdrawal at any time without consequences (Art. 7(3) GDPR).
- Retention: until withdrawal of consent or exercise of the right to object; logs of consent collection retained for 10 years to demonstrate accountability under Art. 5(2) GDPR.
3.5 Newsletter and event registrations
- Data: business email, name, organisation, topics of interest.
- Legal basis: Art. 6(1)(a) GDPR.
- Retention: until withdrawal.
3.6 Suppliers and business contacts
- Data: name, role, business email, business phone, organisation.
- Legal basis: Art. 6(1)(b) GDPR (contract); Art. 6(1)(f) GDPR for ongoing relationship management and B2B prospecting on professional roles.
- Retention: term of the contractual relationship + 10 years for accounting/fiscal purposes under Art. 2220 Italian Civil Code and tax laws including Art. 22 DPR 600/1973 within statutory limits.
3.7 Billing and tax compliance
- Legal basis: Art. 6(1)(c) GDPR — legal obligation (accounting, VAT, electronic invoicing via SdI).
- Retention: 10 years (Art. 2220 c.c.) in encrypted read-only archives.
3.8 Whistleblowing (where applicable)
SINAURA does not currently meet the applicability thresholds of D.Lgs. 24/2023 transposing the Whistleblowing Directive (EU) 2019/1937 and has not activated an internal reporting channel. This section will be updated, together with a dedicated privacy notice, if and when the thresholds are met.
4 · SINAURA AS PROCESSOR — PROCESSING OF CUSTOMER DATA ON THE PLATFORM
When SINAURA processes personal data uploaded by, or generated within, the Customer's tenant workspace of AriaPLT™ (including Authorised User accounts, telemetry, work orders, agent conversations and outputs), SINAURA acts as Processor under Art. 4(8) and Art. 28 GDPR on behalf of the Customer, who is the Controller.
The terms of this processing are governed by the Data Processing Agreement (DPA) executed between SINAURA and the Customer in compliance with Art. 28(3) GDPR, available at Data Processing Agreement (DPA). The DPA prevails over this Privacy Policy on Processor-side processing.
In particular, the DPA covers:
- subject-matter, nature, duration and purpose of the processing;
- categories of personal data and data subjects;
- detailed obligations of the Processor (assistance, audit rights, sub-processor management, return/deletion, breach notification within 48 hours, technical and organisational measures);
- sub-processor list and management;
- international transfer regime.
5 · CATEGORIES OF DATA
We process only data strictly necessary to provide the Platform and related services. We do not sell data to third parties. We do not use Customer data to train generalist AI models intended for or shared with other customers.
A. Account and identity data (Authorised Users)
- Name, surname, business email, role/title, organisation.
- Hashed credentials, MFA factors.
- Access logs and device information.
B. Usage and telemetry data
- Product events, sessions.
- Application logs (IP, user-agent).
- Performance metrics.
- Audit trail of actions.
C. Industrial content data (uploaded or generated by the Customer)
- Technical documents (P&IDs, manuals, SOPs).
- Work orders, CMMS/ERP integration data.
- SCADA/PLC/DCS telemetry (may or may not be personal — see §10).
- AgenticAI inputs, outputs and agent conversations.
D. Website browsing data
- Technical cookies, anonymised analytics, technical session data.
E. Prospect, candidate and supplier data (Controller-side)
- See §3 for detail.
Special categories (Art. 9 GDPR) and criminal-conviction data (Art. 10)
See §20.
6 · PURPOSES, LEGAL BASES AND RETENTION — CONTROLLER-SIDE
| Purpose | Categories | Legal basis | Retention |
|---|---|---|---|
| Website operation and security | D | Art. 6(1)(f) — legitimate interest | 12 months (logs); 24 months (anonymised analytics) |
| Demo/contact responses, pre-contractual evaluation | E (prospect) | Art. 6(1)(b) — pre-contractual measures | 24 months from last interaction |
| Direct marketing — existing Customers (similar products) | E | Art. 6(1)(f) + Art. 130(4) D.Lgs. 196/2003 — soft opt-in | Until objection |
| Direct marketing — non-customer prospects | E | Art. 6(1)(a) — consent | Until withdrawal |
| Newsletter, events | E | Art. 6(1)(a) — consent | Until withdrawal |
| Candidate evaluation | E (candidate) | Art. 6(1)(b) — pre-contractual; Art. 6(1)(a) for talent pool | 12 months (36 with consent) |
| Supplier and business contact management | E (supplier) | Art. 6(1)(b); Art. 6(1)(f) for relationship management | Duration of relationship + 10 years (Art. 2220 c.c.) |
| Billing and tax compliance | E | Art. 6(1)(c) — legal obligation | 10 years |
| Defence in legal proceedings | All | Art. 6(1)(f) — legitimate interest | Until conclusion of proceedings + statute of limitations |
7 · PURPOSES, LEGAL BASES AND RETENTION — PROCESSOR-SIDE (CUSTOMER DATA)
| Purpose | Categories | Legal basis (of the Customer as Controller) | Retention |
|---|---|---|---|
| Service provision (Platform operation) | A · B · C | Art. 6(1)(b) — contract between Customer and data subject, or applicable basis under Customer's documented instructions | Term of agreement + T0–T15–T30 procedure |
| Security and anti-fraud (Platform-wide) | A · B | Art. 6(1)(f) — legitimate interest of SINAURA and the Customer (see §8) | 12 months (security logs) |
| Per-Customer agent specialization (see §9) | C · feedback | Art. 6(1)(b) — contract between SINAURA and Customer; underlying basis as instructed by the Customer | Term of agreement + T0–T15–T30 |
| Service improvement (anonymised data only) | B and C reduced to anonymised, aggregated data outside the scope of GDPR | Outside GDPR for anonymised data; Art. 6(1)(f) where any personal data residually remains | 24 months |
| Product communications to Authorised Users (operational) | A | Art. 6(1)(b) — contract | Term of agreement |
| Compliance with legal obligations on SINAURA (e.g. requests from public authorities) | Variable | Art. 6(1)(c) | As required by law |
End of retention: irreversible deletion or anonymisation. See the T0–T15–T30 deletion procedure below.
T0–T15–T30 deletion procedure (Customer offboarding)
- T0 — workspace closure, suspension of access, security snapshot.
- T1–T15 — final export window (CSV/JSON/PDF/API) at Customer's request.
- T16–T30 — deletion of accounts, embeddings, RAG vault, specialized agent configurations and crypto-shredding of backups.
Statutory exceptions
- Billing and tax records: 10 years (Art. 2220 c.c.).
- Security and access logs: 12 months for accountability and security.
- GDPR audit trail: term of agreement + 12 months.
- Litigation hold: data subject to ongoing proceedings or authority requests retained until conclusion.
8 · LEGITIMATE INTEREST — SYNTHETIC BALANCING TEST (LIA SUMMARY)
Pursuant to Art. 6(1)(f) GDPR, Recital 47, EDPB Guidelines 1/2024 on legitimate interest and CJEU C-621/22 KNLTB (4 October 2024), SINAURA carries out, prior to the start of processing, a documented three-step test (purpose / necessity / balancing). The complete Legitimate Interest Assessment (LIA) is available upon request from the Data Protection Contact.
Summary
| Processing | Purpose | Necessity | Balancing — safeguards | Right to object |
|---|---|---|---|---|
| Security and anti-fraud (Platform logs) | Detection and prevention of fraud, intrusions, abuse | No less intrusive alternative; logging is essential for security | Strict access control, 12-month retention, no profiling of individuals beyond security purposes, encryption | Art. 21(1) GDPR — qualified objection on grounds relating to particular situation |
| Service improvement (anonymised B/C) | Improve quality, reliability and accuracy of the Platform | Necessary to maintain industry-grade reliability for safety-critical operations | Strict anonymisation following WP29 Opinion 05/2014 standard; no individual-level profiling; aggregate only | Right to object remains, although anonymised data fall outside GDPR scope |
| Defence in legal proceedings | Ability to enforce and defend SINAURA's rights | Necessary to exercise legal rights | Strictly limited to data relevant to the proceeding, access restricted to legal team | Art. 21(1), balanced against compelling legitimate grounds |
| Website operation and security | Operate and protect the websites | Logs and basic analytics are necessary | Anonymisation of analytics, 12-month retention of logs | Art. 21(1) |
| B2B business contact processing for relationship management | Maintain ordinary B2B contact relationships | Necessary and proportionate in B2B context with professional contacts | Limited to professional contact data, no profiling, easy unsubscribe | Art. 21(1) and (2) for direct marketing |
Right to object: at any time, by writing to info@sinauragroup.com, with no formal requirements and without prejudice to any other right.
9 · AUTOMATED PROCESSING, ARTIFICIAL INTELLIGENCE AND TRANSPARENCY UNDER THE AI ACT
AriaPLT™ is an Agentic AI platform: it uses AI models to assist industrial processes. This section satisfies the transparency obligations under Art. 13(2)(f) GDPR (existence of automated decision-making) and Art. 50 AI Act (transparency obligations for certain AI systems).
9.1 Four binding commitments
- No training of generalist models — Customer data and content is never used to train AI models intended for or shared with other customers. The only content that reaches other customers is what a Customer itself decides to publish as a Marketplace Item (see §9.2), which SINAURA does not use to train any model.
- Zero data retention with external LLM providers — calls to LLM providers are made with "no training" and "zero retention" flags active, under dedicated DPAs with the providers.
- Isolated vertical RAG — embeddings derived from Customer documents are stored within the Customer's tenant workspace, segregated, encrypted at-rest (AES-256) and deleted on closure.
- Human-in-the-loop by design — agent outputs are decision-support and require human review; they do not represent fully automated decisions under Art. 22 GDPR, see §9.4 below.
9.2 Per-Customer agent specialization
The Platform's AgenticAI agents may be specialized to the Customer's own context through fine-tuning, instruction-tuning, retrieval-augmented configuration and reinforcement on the Customer's data and feedback. This is the only form of training that SINAURA performs on Customer data. It is exclusively:
- per-tenant, within the isolated Customer workspace, never cross-tenant;
- on the Customer's own Input, Output, Customer Data and feedback as training signal;
- for the sole benefit of the Customer's own agents, with no carry-over of trained weights, prompts or specialization artefacts to agents serving other customers, save for the Marketplace Items that the Customer itself decides to publish (see Marketplace below);
- under the same encryption, segregation and access-control safeguards as Customer Data (AES-256 at-rest, tenant isolation, RBAC, immutable audit trail);
- only where the Customer has expressly opted in through the administration console or through the Order Form (in the absence of opt-in, the agents operate in pre-trained baseline mode);
- documented in the Customer's records of processing activities;
- subject to a DPIA where Art. 35 GDPR is triggered;
- with complete deletion of the specialized agent configurations and any derived training artefacts upon termination of the Subscription, under the T0–T15–T30 procedure.
Marketplace. The AriaPLT™ marketplace is the channel through which a Customer may, at its sole discretion, make knowledge developed in its own tenant available to other customers. The Customer may package knowledge content, presets and configurations derived from its own tenant, including from its training environment, into Marketplace Items (for example, per equipment category); only content that the Customer has expressly classified as publishable is published. A purchaser acquires a Marketplace Item and SINAURA copies it into the purchaser's own tenant, where the purchaser obtains agents already specialized and ready to use and then trains them further on its own operations. Distribution therefore takes place by the publishing Customer's own publication, under its own terms, and not by any use of that content by SINAURA.
SINAURA acts solely as technical provider of the marketplace: it copies a Marketplace Item into a purchaser's tenant only upon the publishing Customer's publication or written instruction, acquires no right in its content, and does not use it to train, fine-tune or improve any model, nor to pool or abstract it across tenants. Content that a purchaser adds or generates in its own tenant remains in that tenant, and the publishing Customer has no access to it unless the purchaser consents.
9.3 Data distillation
By "data distillation" we mean the extraction of vector representations (embeddings) and semantic summaries from technical documents, enabling search, retrieval and answering by AgenticAI agents over Customer data. Distillation is carried out within the tenant workspace, never cross-tenant, with AES-256 at-rest encryption, logical segregation, no feeding of generalist models, and complete deletion on workspace closure.
9.4 Art. 22 GDPR — automated individual decision-making
SINAURA does not, in the design and default operation of the Platform, carry out solely automated decisions producing legal effects or similarly significantly affecting natural persons within the meaning of Art. 22(1) GDPR, as interpreted by CJEU judgment C-634/21 SCHUFA of 7 December 2023. The Platform's agents produce decision-support outputs that require human review by Authorised Users (Human-in-the-Loop by design). The natural person responsible for the final action remains the Authorised User and/or the Customer.
Where the Customer chooses to integrate AriaPLT™ outputs into its own decision workflows in such a way that the result is a solely automated decision producing legal or similarly significant effects on natural persons (e.g. employees, contractors, third parties), the Customer is the Controller responsible for compliance with Art. 22 GDPR and must:
- ensure that one of the exceptions of Art. 22(2) applies (necessary for contract, authorised by Union or Member State law with safeguards, or explicit consent);
- implement suitable measures to safeguard the rights and freedoms of the data subject, including at minimum the right to obtain human intervention, to express his or her point of view and to contest the decision (Art. 22(3) GDPR);
- inform data subjects pursuant to Art. 13(2)(f) and Art. 14(2)(g) GDPR with meaningful information about the logic involved and the significance and envisaged consequences.
SINAURA makes available technical documentation and FRIA/DPIA support materials to assist the Customer.
9.5 AI Act — Art. 50 transparency
Where the Customer integrates AriaPLT™ output into systems, products or services made available to natural persons, the Customer is responsible for the transparency duties of Art. 50 AI Act:
- disclosure of interaction with an AI system to natural persons interacting with it;
- labelling of AI-generated or AI-manipulated content as such (text, audio, image, video), with machine-readable markings where required.
SINAURA supports compliance through digital signatures and metadata on agent outputs.
9.6 AI Act — High-risk AI systems (Art. 6 and Annex III)
Where the Customer integrates Outputs into AI systems classified as high-risk under Art. 6 and Annex III AI Act (e.g. critical infrastructure, employment management, access to essential services, law enforcement, education), the Customer assumes the obligations of deployer (or, where applicable, provider) including risk management, conformity assessment, human oversight, post-market monitoring and reporting.
The Customer acknowledges that, as deployer:
- under Art. 26(9) AI Act, it shall use the information provided by the provider to comply with its DPIA obligation under Art. 35 GDPR;
- under Art. 27 AI Act, where it is a body governed by public law or a private operator providing public services, it shall conduct a Fundamental Rights Impact Assessment (FRIA) before deployment;
- under the Digital Omnibus on AI (political agreement of 7 May 2026), the applicability of certain high-risk AI obligations has been postponed from August 2026 to December 2027 (with further extensions for products covered by EU product safety legislation). This postponement does not exempt the deployer from preparatory work, which should begin now.
SINAURA's role is limited to providing the underlying Platform and does not, on its own, constitute deployment of a high-risk AI system.
9.7 Prohibited AI practices (Art. 5 AI Act)
The Customer undertakes not to use AriaPLT™ to implement AI practices prohibited under Art. 5 AI Act (e.g. social scoring, biometric categorisation for sensitive inference, real-time biometric identification in publicly accessible spaces outside the legal exceptions, manipulative or exploitative techniques, untargeted scraping of facial images). Violation may result in immediate suspension of the Service and notification to the competent authorities.
9.8 Specific rights related to AI
In compliance with Art. 22 GDPR and the AI Act, every data subject has the right to:
- request meaningful information on the logic of the agents that concern them;
- obtain human review of any decision producing significant effects on them;
- express their point of view and contest the decision.
Requests are addressed to info@sinauragroup.com.
10 · INDUSTRIAL DATA, TELEMETRY AND INTERACTION WITH THE EU DATA ACT
AriaPLT™ processes large volumes of industrial data (SCADA/PLC/DCS telemetry, MES events, CMMS records, work orders, technical documents, agent conversations). The qualification of such data under GDPR requires case-by-case assessment.
10.1 Personal vs non-personal industrial data
Industrial data is qualified as personal data under Art. 4(1) GDPR and Recital 26, as interpreted by CJEU C-582/14 Breyer of 19 October 2016, when it relates to an identified or identifiable natural person, including by means of combination with other available information. Examples relevant to industrial environments:
- HMI/SCADA actions associated with operator login or shift schedule;
- manual overrides, safety acknowledgements, near-miss reports identifying operators;
- biometric badge access logs;
- video/image data from plant cameras;
- agent conversations including operators' names or signatures.
Such data is treated by SINAURA as personal data under the discipline of §4 and the DPA.
Industrial data that is purely machine-to-machine, without any link (direct or indirect) to identifiable natural persons, falls outside the scope of the GDPR. It remains subject, where applicable, to the EU Data Act and to contractual confidentiality.
10.2 EU Data Act (Reg. 2023/2854)
The EU Data Act applies in full from 11 September 2025. By 12 September 2026, connected products newly placed on the EU market must be designed and manufactured in compliance with the access-by-design principle of Art. 3 Data Act, allowing the user to access generated data in a structured, machine-readable, free, continuous and real-time format.
AriaPLT™, as a B2B platform for connected industrial environments, supports the Customer (as data holder vis-à-vis the Customer's own users) in fulfilling its access-by-design and data sharing obligations under the EU Data Act, by providing export functionalities (CSV/JSON/PDF/API) and documented data interfaces.
10.3 EU Data Governance Act (Reg. 2022/868)
SINAURA does not provide data intermediation services within the meaning of Art. 10 of the Data Governance Act. Any future deployment of such services will be notified to the competent authority and disclosed in this Privacy Policy.
11 · RECIPIENTS AND SUB-PROCESSORS
All sub-processors operate under DPAs compliant with Art. 28(2)–(4) GDPR. The up-to-date list and revision history is published at Annex 3 – List of Authorised Sub-processors (DPA) and is incorporated by reference into the DPA.
| Sub-processor | Role / purpose | Data location | Provider certifications |
|---|---|---|---|
| Amazon Web Services EMEA SARL | Hosting infrastructure, storage, compute, database, backup | EU — Frankfurt (eu-central-1, 3 AZ) | ISO 27001 · ISO 27017 · ISO 27018 · SOC 1/2/3 · C5 (BSI) · PCI DSS |
| Vercel Inc. | Hosting of the public front-end ariaplt.com (landing, marketing). No Customer product data. | EU — Frankfurt region pinning | SOC 2 Type II · ISO 27001 · GDPR |
| Postmark / AWS SES | Sending transactional emails (account verification, password reset, notifications) | EU | SOC 2 · GDPR |
| Stripe Payments Europe Ltd | Processing of subscription payments | EU — Ireland | PCI DSS Level 1 · SOC 1/2 · GDPR |
| Anthropic PBC | LLM inference via EU-resident endpoints with no-training, zero retention | EU / Customer opt-in | SOC 2 Type II · Dedicated DPA · No Training |
| OpenAI Ireland Ltd | LLM inference via EU-resident endpoints with no-training, zero retention | EU / Customer opt-in | SOC 2 Type II · Dedicated DPA · No Training |
| Mistral AI SAS | EU-native LLM inference for specific modules | EU — France | GDPR · No Training |
Changes to the sub-processor list are notified to the Customer at least 30 days in advance via email to the administrative address and via update of Annex 3 – List of Authorised Sub-processors (DPA), with a right of reasoned objection under §5(1) of the DPA. The list of AWS sub-sub-processors is published and kept up to date at aws.amazon.com/compliance/sub-processors.
12 · EXTRA-EU TRANSFERS
AriaPLT™ is designed as an EU-resident platform by design. The entire production infrastructure for Customer data is hosted on AWS Frankfurt (eu-central-1), distributed across three physically separated Availability Zones.
- Storage, compute, backup never outside the EU for Customer production data by default.
- AES-256 at-rest, TLS 1.3 in-transit.
- No extra-EU transfer of Customer Data by default.
- No SINAURA personnel, contractor or group entity accesses Customer Data from outside the EEA.
Any extra-EU transfer (e.g. activation of an extra-EU LLM module upon explicit Customer opt-in, or global support access by sub-processors of the cloud provider) takes place under:
(i) an adequacy decision pursuant to Art. 45 GDPR, including the EU-US Data Privacy Framework (Commission Implementing Decision 2023/1795 of 10 July 2023), where the recipient is DPF-certified and the data falls within the recipient's certification scope; or
(ii) Standard Contractual Clauses (Commission Implementing Decision 2021/914 of 4 June 2021), accompanied by a documented Transfer Impact Assessment following EDPB Recommendations 01/2020 and 02/2020, with supplementary technical, contractual and organisational measures where the TIA so requires.
Although the validity of the DPF was confirmed by the General Court of the EU on 3 September 2025 (Case T-553/23 Latombe v Commission), SINAURA monitors the evolving case-law and reserves the right to apply SCC + TIA as a precautionary primary mechanism, without prejudice to DPF coverage.
The Customer is informed that activation of extra-EU LLM modules may trigger the Customer's obligation to perform a DPIA under Art. 35 GDPR; SINAURA makes available an up-to-date DPIA template aligned with the EDPB DPIA Template 2026.
13 · SECURITY MEASURES (ART. 32 GDPR), NIS2 AND DORA
13.1 Technical and organisational measures (Art. 32 GDPR)
SINAURA adopts a security-by-design approach, aligned with the NIST CSF framework and with the requirements of Directive (EU) 2022/2555 (NIS2) as transposed in Italy by D.Lgs. 138/2024.
- SSO SAML/OIDC, mandatory MFA for admins, granular RBAC.
- AES-256 at-rest and TLS 1.3 in-transit encryption, strict tenant segregation.
- Immutable audit trail, cryptographic hashes, digital signatures on outputs.
- Multi-AZ backups, RPO < 24h, RTO < 4h, 99.9% SLA.
- Annual penetration tests, continuous vulnerability scanning (SAST/DAST/SCA).
- DLP and content scanning at upload time to detect and flag potential special-category data and minors' data.
- GDPR / EU AI Act / NIS2 training programmes for personnel.
- AI Governance Committee.
- Designated Authorised Personnel under Art. 29 GDPR with documented instructions.
Technical details are set out in Annex 1 of the DPA (Technical and Organisational Measures).
13.2 NIS2 — SINAURA as ICT service provider
Based on its size and sector, SINAURA has assessed that it currently falls outside the direct scope of D.Lgs. 138/2024 (NIS2). It nevertheless aligns its security measures with Art. 21 NIS2 (see §13.1) to support Customers that are subject to supply-chain security obligations.
13.3 DORA — Customers in the financial sector
For Customers that are financial entities under Regulation (EU) 2022/2554 (DORA), applicable since 17 January 2025, SINAURA supports the Customer's obligations under Art. 28-30 DORA, including:
- inclusion in the Customer's Register of Information (ROI) with the reference date applicable to each annual cycle (the 2026 cycle reference date is 31 December 2025);
- inclusion of contractual provisions required by Art. 30 DORA in the DPA and MSA;
- cooperation with the Customer in resilience testing where applicable;
- monitoring of designations of Critical ICT Third-Party Providers (CTPPs) by ESAs, including the 19 designated on 18 November 2025 (AWS, Microsoft Azure, Google Cloud, others), where they are part of SINAURA's supply chain.
13.4 Vulnerability disclosure
Security vulnerability reports may be sent to info@sinauragroup.com under the responsible disclosure policy published at ariaplt.com/.well-known/security.txt (RFC 9116).
14 · PERSONAL DATA BREACH — DUAL-TRACK PROCEDURE
SINAURA distinguishes its obligations depending on the role.
14.1 Breach affecting Customer data — SINAURA as Processor (Art. 33(2) GDPR)
SINAURA notifies the Customer without undue delay and in any case within 48 hours of becoming aware of a personal data breach affecting Customer data, under §3.5 of the DPA, providing the information required by Art. 33(3) GDPR (nature of the breach, categories and approximate number of data subjects and records concerned, likely consequences, measures taken or proposed). Upon Customer request and at reasonable cost, SINAURA assists the Customer in any subsequent notification to the supervisory authority (Art. 33(1) GDPR) and communication to data subjects (Art. 34 GDPR).
14.2 Breach affecting Controller-side data — SINAURA as Controller (Art. 33(1) and Art. 34 GDPR)
For breaches affecting personal data processed by SINAURA as Controller (e.g. website users, marketing contacts, candidates, suppliers), SINAURA:
- assesses the breach following EDPB Guidelines 9/2022 and the internal data breach procedure;
- notifies the Garante per la Protezione dei Dati Personali via the portal servizi.gpdp.it within 72 hours of becoming aware where the breach is likely to result in a risk to the rights and freedoms of natural persons (Art. 33(1) GDPR);
- communicates the breach to the affected data subjects without undue delay where the breach is likely to result in a high risk (Art. 34 GDPR), unless one of the exceptions of Art. 34(3) applies;
- documents every breach in the internal Breach Register pursuant to Art. 33(5) GDPR.
14.3 NIS2 cyber incident reporting
Where the breach also qualifies as a significant cyber incident under Art. 23 NIS2 / Art. 25 D.Lgs. 138/2024 and SINAURA is subject to the related reporting obligations, SINAURA performs the early warning to CSIRT Italia within 24 hours, the incident notification within 72 hours and the final report within one month, in coordination with the privacy notification timeline.
15 · DATA SUBJECT RIGHTS
Under Chapter III GDPR, every data subject may exercise the following rights by writing to info@sinauragroup.com. SINAURA responds within one month of receipt of the request (extendable by two further months in case of complexity, with notice within the first month) pursuant to Art. 12(3) GDPR.
- Art. 15 — Right of access to personal data and to information.
- Art. 16 — Right to rectification of inaccurate or incomplete data.
- Art. 17 — Right to erasure (right to be forgotten).
- Art. 18 — Right to restriction of processing.
- Art. 19 — Notification obligation regarding rectification, erasure or restriction.
- Art. 20 — Right to data portability in a structured, commonly used and machine-readable format.
- Art. 21 — Right to object to processing based on legitimate interest or direct marketing (the latter is absolute and cost-free).
- Art. 22 — Right not to be subject to solely automated decisions producing legal or similarly significant effects.
- Art. 7(3) — Right to withdraw consent at any time, without affecting the lawfulness of previous processing.
Where the data subject exercises a right relating to Customer data processed by SINAURA as Processor, SINAURA forwards the request to the Customer (Controller) within reasonable time and assists the Customer under Art. 28(3)(e) GDPR.
For security reasons, SINAURA may, only in case of reasonable doubts about the identity of the requester (Art. 12(6) GDPR), request additional information necessary to confirm the identity. Such verification is proportionate, minimised and the documents are deleted upon completion of the case.
16 · COOKIES, TRACKERS AND TRACKING PIXELS
The websites ariaplt.com and sinauragroup.com use:
- Strictly necessary technical cookies (no consent required under Art. 122(1) D.Lgs. 196/2003);
- Analytics cookies anonymised in compliance with the criteria of the Italian Garante's Provv. n. 231 of 10 June 2021 (Cookie Guidelines), or, in absence of such anonymisation, subject to consent.
No third-party profiling cookies or marketing trackers are activated without prior, free, specific, informed, granular and unambiguous consent collected through a cookie banner compliant with EDPB Guidelines 03/2022 (deceptive design patterns) and with the Italian Garante's Cookie Guidelines.
The cookie banner offers, on equal-level placement, the options "Accept all", "Reject all" and granular preferences, with no pre-ticked boxes and with the ability to withdraw consent at any time at the same ease with which it was given (Art. 7(3) GDPR).
The extended cookie notice with full list of cookies, durations, providers and purposes is available at Cookies (Website Privacy Policy).
Tracking pixels in email communications
In compliance with the Italian Garante's Provv. of 17 April 2026 on tracking pixels in email communications, SINAURA:
- in transactional emails (e.g. password reset, billing, service notifications), uses only technical pixels strictly necessary to deliverability and security, on the legal basis of Art. 6(1)(b) and (f) GDPR;
- in marketing emails, where tracking pixels for open-rate analytics are used, collects prior explicit consent at the same level of granularity as the marketing consent, with a separate option, and provides at any time the ability to opt out;
- documents pixel usage in the cookie/tracker policy referenced above.
EDPB Guidelines 2/2023 on the technical scope of Art. 5(3) ePrivacy
SINAURA acknowledges that the application of Art. 5(3) ePrivacy extends beyond cookies to a broad range of tracking technologies (tracking pixels, URL parameters, IP-based tracking, fingerprinting, IoT-side identifiers) and ensures that the same consent regime applies to all such technologies when used for non-strictly-necessary purposes.
17 · PRIVACY BY DESIGN AND BY DEFAULT (ART. 25 GDPR)
SINAURA implements privacy-by-design and privacy-by-default measures in compliance with Art. 25 GDPR and EDPB Guidelines 4/2019, including:
- data minimisation in collection forms and platform inputs;
- default tenant isolation and least-privilege RBAC for Authorised Users;
- default encryption at-rest and in-transit;
- default deletion at expiration of retention periods;
- prior privacy/security review of every new feature (DPbDD Gate within the SDLC);
- maintenance of records of design decisions to demonstrate accountability (Art. 5(2) GDPR).
18 · DPIA AND ACCOUNTABILITY
SINAURA has carried out a Data Protection Impact Assessment (DPIA) under Art. 35 GDPR on the Platform's high-risk processing activities, in line with the EDPB DPIA Template 2026 (adopted in consultation in April 2026, expected to become the harmonised standard). The DPIA is reviewed at every material change, and a DPIA is carried out for every new feature impacting personal data and for per-Customer agent specialization where Art. 35 GDPR is triggered.
The DPIA expressly covers the AriaPLT™ marketplace described in §9.2: the packaging of Marketplace Items by a Customer, their publication and their copying into a purchaser's tenant, as well as the per-Customer specialization of agents (§9.2) from which they are derived. In particular, the assessment takes into account that:
- publication is decided solely by the publishing Customer, and only content that the Customer has expressly classified as publishable is published;
- SINAURA acts solely as technical provider: it copies a Marketplace Item into a purchaser's tenant only upon the publishing Customer's publication or written instruction, and acquires no right in its content;
- no Customer Data is exported for training purposes, and SINAURA does not train, fine-tune or improve any model on Marketplace Items, nor pool or abstract them across tenants;
- Marketplace Items are not resold or otherwise distributed by SINAURA in general: they reach other customers only through the publishing Customer's own publication;
- content that a purchaser adds or generates after the copy remains in the purchaser's tenant and is not accessible to the publishing Customer without the purchaser's consent;
- a Marketplace Item is a starting configuration: the behaviour of the Platform in the purchaser's tenant also depends on the facts, cases, data and training that the purchaser adds.
A summary of the DPIA, including the residual risk assessment and the technical and organisational measures, is available to the Customer upon request and under confidentiality, to assist the Customer in its own DPIA obligations as Controller and, where applicable, as deployer of high-risk AI systems under Art. 26(9) AI Act.
SINAURA has not submitted the DPIA for prior consultation under Art. 36 GDPR, as the residual risk is assessed as not high.
The Italian Garante's national list of processing operations subject to mandatory DPIA (Provv. n. 467 of 11 October 2018) is taken into account.
19 · CHILDREN
AriaPLT™ is a professional B2B platform addressed to legal entities. The Platform is not directed to minors. Authorised Users designated by the Customer must be of legal age and act within the scope of duties assigned by the Customer.
SINAURA does not knowingly process personal data of minors. Technical detection measures (DLP, content scanning at upload) are in place to identify potential upload of minors' data. Where such data is detected, SINAURA notifies the Customer within 5 working days requesting prompt removal and, where the Customer fails to act, may suspend the affected processing pursuant to Art. 28(3)(a) GDPR and the DPA.
The age of consent under Art. 8 GDPR for information society services in Italy is 14 (Art. 2-quinquies D.Lgs. 196/2003); this does not apply to AriaPLT™, which is not an information society service offered to minors.
20 · SPECIAL CATEGORIES (ART. 9) AND CRIMINAL-CONVICTION DATA (ART. 10)
20.1 Special categories under Art. 9 GDPR
Personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, trade-union membership, genetic data, biometric data for identification purposes, health data, data concerning sex life or sexual orientation, are not processed by the Platform unless under a specific written agreement between SINAURA and the Customer, supported by a documented Art. 9(2) condition (e.g. Art. 9(2)(a) explicit consent, Art. 9(2)(b) employment law context, Art. 9(2)(h) occupational medicine) and a prior DPIA.
In industrial environments such data may be incidentally relevant — e.g. occupational health certificates, biometric access control, near-miss reports containing health data. SINAURA implements technical safeguards (DLP, content classifiers, redaction tooling, segregation of buckets with elevated controls) to detect and prevent unintended upload, and notifies the Customer in case of detection within 5 working days.
20.2 Criminal-conviction data under Art. 10 GDPR
Personal data relating to criminal convictions and offences are not processed by the Platform, save in compliance with Art. 10 GDPR and Art. 2-octies D.Lgs. 196/2003 and only under a specific written agreement with a documented legal basis. The same technical safeguards as 20.1 apply.
20.3 Prohibited AI practices
The Customer further undertakes not to upload onto the Platform any data used for AI practices prohibited under Art. 5 EU AI Act, including biometric categorisation for sensitive inference and untargeted scraping of facial images.
21 · COMPLAINTS TO THE SUPERVISORY AUTHORITY
Without prejudice to any other administrative or judicial remedy, every data subject has the right to lodge a complaint with the Italian Data Protection Authority — Garante per la Protezione dei Dati Personali (Piazza Venezia 11, 00187 Rome — garanteprivacy.it) or with the supervisory authority of the EU Member State of his or her residence, workplace or place of the alleged infringement (Art. 77 GDPR).
22 · DOCUMENT HIERARCHY AND LANGUAGE
This Privacy Policy is an integral part of the contractual document set (ToS, Order Form, DPA, SLA, Privacy Policy). In case of conflict on matters of personal data processing, the DPA prevails; for other matters, the order of precedence set out in Art. 19 of the ToS (Order of precedence) applies.
This Privacy Policy is published in English and in Italian on Platform Privacy Policy. For data subjects resident in Italy, the Italian version is fully effective. Between SINAURA and the Customer, on the purely contractual portion of this document, in case of interpretative conflict the English version prevails; this priority is not enforceable against individual data subjects in their relationship with SINAURA in respect of their understanding of the processing.
23 · AMENDMENTS
SINAURA may update this Privacy Policy to reflect regulatory or product evolution. Material changes are notified via email to registered users and to the Customer administrative address, and via notice on ariaplt.com. The current version is always available at Platform Privacy Policy with indication of version, date and changelog. Prior versions are archived and available upon request.
24 · APPLICABLE ADDENDA AND EXHIBITS
The following documents are incorporated by reference into this Agreement and form an integral part of it:
- Terms of Service
- Acceptable Use Policy
- Service Level Agreement
- Data Processing Agreement
- Master Services Agreement
- SINAURA Website Privacy Policy
25 · CONTACTING SINAURA
- Registered office: SINAURA S.R.L., Viale Luigi Majno n. 7, 20122 Milan, Italy
- General contact: info@sinauragroup.com
- Customer support: info@sinauragroup.com
- Legal (with copy labelled "Attention: Legal"): certified mail (PEC): sinaurasrl@legalmail.it
- Data Protection Contact: info@sinauragroup.com
- Security: info@sinauragroup.com
© 2026 SINAURA S.R.L. · AriaPLT™ and Sinaura™ are registered trademarks of SINAURA S.R.L · Version 1.4 · Last updated: 6 October 2026