Data Retention and Deletion Policy
SyncSpace | Last substantively revised: 16 November 2026
1. Governing principles
CODINGTAILORS S.R.L. retains personal data only as long as needed for the relevant service purpose, documented customer instructions, security needs and mandatory legal obligations. Retention decisions depend on whether we act as controller or processor. This policy does not create a right to immediate destruction of financial records or data subject to lawful preservation requirements.
2. Categories and retention criteria
| Category | Retention approach |
|---|---|
| Accounts and subscription entitlements | While the account/service relationship exists, then as needed to complete closure, respond to claims and satisfy applicable law |
| Guest session and introductory-allowance observations | The guest cookie expires after 30 days by default; expired session records are removed by periodic cleanup after a further seven days. Guest device observations, including keyed Android app-install hashes, are removed by periodic cleanup after 90 days. Cookie loss or session expiry does not automatically delete the account or its content. |
| Customer files and workspace records | During the contracted service and in accordance with authorized deletion or return instructions, subject to backups and legal obligations |
| Remi conversations, tool results, RAG context and AI usage records | According to verified operational settings, customer instructions where applicable, billing accuracy and security needs |
| Invoices, payment transactions and fiscal records | For the statutory tax/accounting periods required by Romanian and other applicable law |
| Technical access logs and security/audit trails | For a documented risk-based period needed to secure and maintain the service |
| Support correspondence | For the time needed to resolve the matter and handle reasonably foreseeable legal claims |
| Backups | Until controlled backup rotation or expiry, with restricted access and restoration controls |
3. Deletion, export and backups
Authorized users may delete or export information using supported features or seek assistance where their contractual rights require it. Customer-controlled personal data is deleted or returned in accordance with the DPA and the customer's instructions. Deletion from a live application does not necessarily remove all historical backup copies immediately. Any restored backup must be managed so that previously approved deletions are not inadvertently reversed without lawful reason.
4. Operational schedule and accuracy
Exact durations for SeaweedFS/PostgreSQL backups, Tomcat/NGINX logs, stored chat histories, AI usage records and account termination workflows depend on the deployed configuration. The Company must maintain an internal schedule stating the retention duration, starting event, systems affected and responsible owner for each category. No fixed period is represented here unless verified in production. Customer-specific deletion timelines should be specified in the service agreement or DPA where appropriate.
5. Exceptions, rights and updates
Data may be preserved where required by tax law, litigation holds, fraud prevention or other lawful obligations. Rights requests are assessed in light of those exceptions and the applicable controller/processor role. For enquiries: suport@codingtailors.ro. See the Privacy Policy and DPA.
Standard retention schedule
The following are proposed standard operational targets, subject to implementation, applicable data-controller instructions, mandatory law and justified legal holds. GDPR does not permit a single blanket maximum retention period for all personal data.
| Category | Standard retention / deletion rule |
|---|---|
| Account, profile and service configuration | While the account remains active; target deletion or anonymisation from active systems within 90 days after final closure, subject to lawful exceptions. |
| Files, documents, business records, Remi chats and RAG results | Until deletion by an authorised user or service termination under the organisation's instructions; target deletion from active systems within 90 days after a valid deletion request or contractual end. |
| Backups and technical replicas | Deleted data may remain until rotation; target overwrite or expiry within 180 days of deletion from active systems. Backups are not customer archives and restoration is not guaranteed. |
| Operational and access logs | Ordinarily 90 days; security, abuse prevention and incident logs may be retained for up to 12 months where justified, and longer only on a documented lawful basis. |
| AI usage and credit deductions | Ordinarily 24 months for verification, support and disputes; qualifying accounting records follow statutory accounting retention. |
| Invoices and accounting records | Five years calculated from 1 July of the year after the relevant financial year, subject to Romanian accounting law and any special statutory requirement. |
| Litigation, fraud, regulatory orders or other mandatory preservation | Only while necessary for the documented lawful purpose, with restricted access; delete or anonymise once the basis ends. |
These periods are not mandatory minimum storage times. Data should be erased sooner where the purpose and lawful grounds cease. Customer-content deletion requests are handled in accordance with controller/processor roles and contractual instructions.
European hosting and processing through Remi
SyncSpace's principal application and file-storage infrastructure is hosted in Europe. When a user instructs Remi to perform an AI-assisted operation, the information needed to fulfil it may be transmitted to OpenAI, including prompts, document excerpts, conversation context and tool results. Depending on the provider service and configuration, AI processing may occur outside the European Economic Area. We do not represent that content sent to AI providers is stored or processed exclusively within the EEA. Applicable international-transfer terms and safeguards are addressed separately.
Third-party retention, including OpenAI retention, depends on the applicable service terms and configurations. Our internal schedule does not guarantee deletion from third-party systems on the same timetable.