Data Processing Agreement (DPA)
Article 28 GDPR processing terms for SyncSpace | Last substantively revised: 1 November 2026
1. Parties, roles and precedence
For the personal data that a customer organization controls within SyncSpace, the customer acts as Controller and CODINGTAILORS S.R.L. (Str. Opanez nr. 10, Sector 2, Bucharest, Romania; CUI 49984073) acts as Processor. This DPA supplements the applicable SyncSpace service agreement. If a specific signed DPA governs a customer relationship, its express negotiated provisions prevail to the extent valid under applicable law. CODINGTAILORS acts separately as Controller for its own billing, account administration, website security and customer-support relationship.
2. Processing specification (Article 28(3))
| Subject matter | Hosting and operating the customer workspace, file synchronization, indexing/search, collaboration features and user-authorized AI assistance |
|---|---|
| Duration | The contracted service period and subsequent deletion/return period, subject to mandatory legal retention |
| Nature and purpose | Collection, storage, organization, retrieval, authorized transmission, backup/restore, erasure, and (if enabled and instructed) Remi/RAG processing to provide the service |
| Data subjects | Workspace members, customer staff, clients, business contacts and other individuals appearing in customer-selected content |
| Personal data | Names, contact details, communications, documents, uploaded files, scheduling and transaction records, plus any other categories selected by the Controller; special-category data may arise where supplied by the Controller |
Remi: automatic retrieval within authorized scope
As part of customer-authorized AI functions, a user request may cause Remi to search, retrieve and combine relevant documents, extracted content, metadata, calendars, reminders, conversations and tool outputs accessible to that user. Such processing is not confined to records expressly attached to the chat. Relevant context, potentially including personal or confidential data, may be disclosed to OpenAI as an authorized AI subprocessor to complete the requested operation. The Controller's instructions encompass the enabled AI service subject to the service agreement, appropriate lawful bases, user access controls, and data minimization. This does not authorize cross-organization access or relieve either party of its mandatory GDPR duties.
3. Documented instructions
The Processor processes personal data only on documented instructions from the Controller, including instructions expressed through authorized configurations and user actions, unless required by EU or Member State law. Where law requires processing outside instructions, the Processor will notify the Controller beforehand unless prohibited by law. The Processor will promptly inform the Controller if, in its opinion, an instruction infringes GDPR or other relevant EU or Member State data-protection law.
4. Confidentiality, security and access
The Processor ensures that persons authorized to process personal data are bound by confidentiality obligations or an appropriate statutory duty. It applies technical and organizational measures appropriate to the risks as required by GDPR Article 32, including access control, authorization, transport protections, appropriate encryption for supported storage operations, security logging and maintenance practices. These measures must be assessed against the deployed service and do not constitute a warranty of absolute security. Authorized use of Remi may involve transmission of relevant content in a form the AI provider can process; encrypted-at-rest storage does not eliminate that disclosure.
5. Subprocessors and changes
The Controller grants general written authorization for the subprocessors made available in the Subprocessors list, subject to any applicable written agreement and a reasonable advance notification and objection mechanism for intended additions or replacements. The Processor imposes data-protection obligations on subprocessors that are no less protective, in substance, than those required by GDPR Article 28(3), and remains liable to the Controller for their performance as provided by Article 28(4). A payment provider acting as an independent controller is not classified as a subprocessor merely because it provides payment services.
6. International transfers
For transfers of Controller personal data outside the EEA, the parties will comply with GDPR Chapter V using a valid transfer mechanism, such as an applicable adequacy decision or Standard Contractual Clauses, together with any necessary supplementary measures. OpenAI API processing locations and terms depend on the configured provider arrangement. The service must not be assumed to be EU-only without verified contractual and technical commitments.
7. Assistance, rights and incidents
Taking account of the nature of processing and available information, the Processor assists the Controller by appropriate technical and organizational means with data-subject requests, security duties, breach notifications, data protection impact assessments and prior consultations under GDPR Articles 32–36. The Processor notifies the Controller without undue delay after becoming aware of a personal-data breach affecting Controller data and provides available details and reasonable updates to enable the Controller to meet its own legal obligations. The parties will establish practical incident-reporting contacts and channels in their service arrangement.
8. Return, deletion and records
On termination, at the Controller's choice and subject to the service arrangement, the Processor returns or deletes Controller personal data and deletes existing copies unless EU or Member State law requires retention. Technical deletion from backups may follow controlled rotation; any applicable timetable and exceptions should be specified in the operational retention schedule rather than presumed. The Processor makes available information reasonably necessary to demonstrate Article 28 compliance and allows and contributes to audits by the Controller or an authorized auditor under reasonable security, confidentiality and operational safeguards.
9. Controller responsibilities and contact
The Controller determines lawful purposes and bases, issues appropriate documented instructions, provides notices, implements user permissions and assesses whether particular data may be processed by AI services. Instructions involving special-category or confidential personal data must be lawful and proportionate. DPA questions: suport@codingtailors.ro. This publicly displayed DPA should be confirmed as incorporated into the actual customer contract, including its subprocessor-notice procedure, before being treated as an executed bilateral agreement.
AI-assisted processing and external actions
Within the Controller's documented instructions and the applicable permissions, processing can include retrieval of relevant workspace context, generation of files and authorized email, messaging, calendar, reminder or connected-device operations. Information needed for these operations may be sent to configured AI and connected service providers. All processing remains subject to applicable security, confidentiality, processor and transfer obligations.