Security Policy
SyncSpace | Last substantively revised: 1 November 2026
1. Purpose and responsibility
CODINGTAILORS S.R.L. applies risk-based technical and organizational security measures to support the confidentiality, integrity and availability of SyncSpace. The precise controls available to an account depend on the deployed modules and configuration. No security system can guarantee zero incidents or uninterrupted operation.
2. Identity, authorization and account protection
Users authenticate to access the application, and permissions govern access to relevant workspaces and operations. Customers are responsible for managing members, assigned roles, access to shared content and the security of their own endpoints and credentials. We recommend strong credentials and timely reporting of suspected account compromise.
3. Transport, storage and backups
SyncSpace uses HTTPS for its publicly accessible application connections and authorization controls for file operations. Supported file content uses the application's encryption and chunked transfer design. Depending on the deployment and storage history, files may be held in existing local storage or self-hosted SeaweedFS object storage behind an HTTPS reverse proxy. Cryptographic protections differ by data flow and do not imply that every item is end-to-end encrypted in all circumstances. Access to infrastructure, backups, logs and administrative functions requires appropriate operational protection.
4. Remi, document retrieval and external services
When a user invokes Remi, authorized prompt context, selected/retrieved document excerpts and tool outputs may be disclosed to the configured OpenAI API service for processing. Such material must be intelligible to the AI service when needed to fulfil the instruction; encryption applied to stored files does not prevent these authorized disclosures. Customers should control who may invoke AI features and which documents may be used, and review AI actions with material business or legal consequences.
5. Monitoring, incident response and maintenance
Security and application logs may be used for investigating unauthorized activity, availability issues and errors. We maintain the service through updates and corrective measures as vulnerabilities are identified. Where a personal-data breach affects customer-controlled information, notifications and assistance are governed by the DPA and GDPR; not every technical incident constitutes a personal-data breach. The Company should maintain internal incident-response, recovery and patch-management procedures suited to the actual production architecture.
6. Limitations, reports and revisions
For security reasons, this public document does not disclose detailed infrastructure secrets, credentials or attack-sensitive operational procedures. It is not a guarantee of an independently certified security standard or a fixed recovery-time objective unless separately agreed. Report security concerns to suport@codingtailors.ro. Material changes to the security approach will be reflected in updates to this policy.
Anonymous and registered access
Visitors may start in an isolated anonymous guest session. Registered users may sign in with email and password or, where configured, Google authentication. Browser or network similarity is not treated as proof of authorization to retrieve another account's private conversations or files.