Who can read?
The trusted server process and trusted server admins can read files and metadata.
Security & trust
Private means you control the server.
SyncVisor uses a server-readable trust model by design: you choose where the server runs, who administers it, where storage lives, and where backups go.
Know what the server can do
The trusted server can read files and metadata so WebUI, WebDAV, sharing, versions, deduplication, compression, previews, and restore workflows can work. Plan that trust deliberately with TLS, strong admin credentials, protected backup credentials, and optional server-side at-rest encryption.
Plan server trust deliberately: use TLS, choose trusted admins, protect backup credentials, and verify restore procedures before relying on important data.
Access controlYou define users, groups, roles, shares, and device access.
Transport securityUse TLS and fix certificate warnings before relying on an address for daily access.
Server-readable by designThe trusted server process can read, process, and store files and metadata.
At-rest encryptionUse optional server-side at-rest encryption when your deployment needs storage-layer protection.
Backup and recoveryYou control backup targets, credentials, retention, and restore procedures.
Server trust boundary
Trusted devicesNative apps, WebUI, WebDAV, and rclone
Server trust boundary
SyncVisor serverAccess, sync, files, metadata, and restore
TLS for transport
Optional at-rest encryption
StorePrimary files
BackupOptional copy
AdminUsers and shares
Trusted server-readable capability
Security controls
Deployment choices you own
What protects it?
TLS, access control, admin security, protected credentials, and optional server-side at-rest encryption.
Who owns recovery?
You choose backup targets, retention, recovery credentials, and restore checks.
Report a security issue
Email a short description, affected version, setup details, and reproduction steps. Avoid sharing exploit details publicly before we respond.
Email security report