1Status of the Parties and GDPR Roles
The business entity holding the subscription account that inputs repair clients' data (client name, phone number, device diagnostics, IMEI code). The subscriber determines the purposes and lawful means of data collection.
The SaaS provider hosting, storing, and technically executing data processing exclusively on documented instructions from the Controller to operate the management software.
2Subject Matter, Data Categories and Data Subjects
2.1. Data Subjects: end-clients of the subscriber repair shop/store (individuals whose devices undergo repairs or who purchase second-hand electronics/accessories) and authorized employees of the subscriber company.
2.2. Categories of Processed Data:
- End-client identity records: full name, mobile phone number (for automated SMS/WhatsApp repair progress updates).
- Device technical data: unique IMEI serial, brand/model, device unlock pattern/PIN (provided voluntarily for diagnostic testing), aesthetic intake photos.
- Digital holographic signature: client touch-screen signature upon device intake and completion receipt.
- Staff operational data: name, business email, role, assigned branch, and system modification audit logs.
2.3. Duration of Processing: data processing continues for the active term of the SaaS subscription and ceases 30 days post-termination, allowing complete subscriber data exports.
3Processor Obligations (Art. 28(3) GDPR)
As Data Processor, Gardenix SRL undertakes the following strict contractual obligations:
- Processing on documented instructions: processes personal data only on documented instructions from the Controller, including regarding international data transfers.
- Confidentiality commitment: ensures that personnel authorized to maintain technical infrastructure and databases are bound by strict contractual non-disclosure obligations.
- Technical security measures under Art. 32 GDPR: adopts all necessary technical and organizational measures to ensure security (AES-256 encryption at rest, TLS 1.3 in transit, multi-tenant Row Level Security, redundant automated backups).
- Sub-processor management: does not engage another sub-processor without prior written authorization, imposing identical data protection obligations on all downstream infrastructure partners.
- Assistance with data subject requests: assists the Controller through technical mechanisms in fulfilling its legal duty to respond to data subject requests under Chapter III of the GDPR (access, rectification, erasure, portability).
- Breach notification (Art. 33 GDPR): notifies the Controller without undue delay (and in any event within 48 hours) upon discovering any personal data breach affecting subscriber records.
- Data return or deletion at contract end: at the Controller's choice, deletes or returns all operational data upon termination and purges residual copies, unless statutory legal retention mandates apply.
- Audits and compliance verification: makes available to the Controller all evidence necessary to demonstrate compliance with Art. 28 GDPR obligations and allows for compliance audits.
4Authorized Sub-processors Roster
The Controller explicitly authorizes the engagement of the following technical infrastructure sub-processors, all ensuring EU data residency or adequacy compliance:
| Sub-processor | Service Provided | Hosting Location | GDPR Safeguard |
|---|---|---|---|
| Oracle Cloud (OCI) | PostgreSQL 17 Database & SaaS Backend | Frankfurt, Germania (UE) | Strict EU Data Residency |
| Cloudflare Inc. | Edge CDN, WAF, DDoS Mitigation, TLS 1.3 | EU / Global Edge Points | EU-US Data Privacy Framework / SCC |
| Paddle.com Market Ltd. | Merchant of Record, Payments & B2B Invoicing | Londra (UK) / Dublin (Irlanda) | UK Adequacy Decision / Ireland EU Entity |
| Resend Inc. | Transactional Email (OTP codes & alerts) | Secure Cloud Infrastructure | Standard Contractual Clauses (SCC) |
5Technical Annex: Security Measures Implemented (Art. 32 GDPR)
PostgreSQL Row Level Security (RLS) guarantees at database engine level the physical impossibility of cross-company data leakage.
All in-transit network traffic is encrypted via TLS 1.3, while resting storage volumes in OCI Frankfurt utilize AES-256-GCM hardware encryption.
Differentiated permissions for administrators, technicians, and cashiers, store-specific scoping, and immediate revocation of active device tokens.
Audit logs record critical operational modifications and undergo automatic data minimization and scheduled rotation cycles.
