Encrypted user data
- supported content in applications with active sync
- supported snippets, notes, and attachments
- content fields and file names inside the encrypted envelope where provided by the product
Priviot Sync
Synchronization between your devices.
Priviot Sync requires a paid Pro or Suite subscription. Local core features remain available without an account.
Core principle
Planned: sync requires explicit activation.
Signing in alone does not upload local documents. Under the planned subscription model, PDF and Write documents would be selected individually; Paste and Notes would sync only after their product area is enabled.
Local use and sync are separate.
Without enabled sync, documents, text, snippets, and notes remain on the device. Account data, organizations, and roles belong to the account service and are not presented as document sync.
Process
How Priviot Sync is planned to work.
Planned synchronization requires a paid Pro or Suite subscription. Device approval, recovery, and encrypted transfer are part of the intended flow.
01 · AccountSign in to Priviot
A paid Pro or Suite subscription is required for sync in supported applications.
02 · ApprovalAuthorize the device
New devices are approved through an already authorized device or the designated recovery path.
03 · SyncSynchronize in encrypted form
After approval, supported content is synchronized between your devices in encrypted form.
04 · ControlStay in control
You can manage connected devices and disable sync when you no longer want to use it.
Product scope
Planned application scope.
The following scope describes the planned model and may change. Not every local file is intended to become sync content automatically.
| Application | Planned scope | Important limit |
|---|---|---|
| Priviot PDF | Individually selected PDF documents and their encrypted versions. | Only selected documents; concurrent changes remain as conflict copies. |
| Priviot Write | Individually selected documents in supported formats, including embedded content. | Only selected documents; changes are not merged field by field. |
| Priviot Paste | Text snippets and supported attachments. | Device- or operating-system-specific triggers can remain local and do not overwrite other devices. |
| Priviot Notes | Supported notes, tasks, reminders, projects, tags, areas, filters, and version states. | A reminder's local trigger state remains a device event and is not transferred as a completed alert. |
| Priviot Tasks | Tasks and lists with supported planning fields. | Planned synchronization scope; local reminder events remain device-specific. |
Encryption
Content is protected. Operational metadata remains visible.
Client-side encryption protects content, but it does not make operating a sync service metadata-free.
Technically visible data
- account, device, product, and object identifiers
- object type, schema, revision, and deletion status
- timestamps, ciphertext size, hashes, and encrypted blob references
- For the planned synchronization: public device and identity keys, signatures, key generations, and authorization history
Important: Disabling a product area stops future synchronization. It is not automatically the same as deleting sync data already stored. Local files remain unaffected.
Control
Devices, conflicts, and recovery.
devices used for encrypted synchronization are cryptographically approved and revoked in the app. Signing out an account session on the website is a separate action. Conflicts are not silently overwritten; applications preserve competing states or present them for a decision.
Keys and devices
The exact key provisioning depends on the product and device state. Approved devices receive only the key material required for their encrypted use. Recovery options are explained in the application.
Account and organization
Sign-in, memberships, roles, and invitations are account features. They may be required for sharing or collaboration, but they do not automatically upload local documents.
FAQ
Frequently asked questions about Priviot Sync.
Short answers about sync and the paid subscription requirement.
Do I need sync to use Priviot?
No. The local core features of PDF, Write, Paste, and Notes work without enabled sync and without a mandatory account.
Does signing in upload all files?
No. Signing in alone does not upload local files. Sync requires a paid subscription; PDF and Write documents would also be selected individually.
Can Priviot read my synchronized content?
Supported private content is encrypted client-side before transfer. Technical metadata remains visible for operation; its scope is listed above.
Is sync a backup?
No. Sync aligns working states between devices and does not replace an independent backup of important files.
Synchronization
The next generation of synchronization
The new synchronization is being prepared for Priviot Paste, Notes, and Tasks. PDF and Write are outside this planned scope. Use requires an approved app version and an available service; this description does not announce general activation.
The next generation of synchronization
The new synchronization encrypts content on the device with XChaCha20-Poly1305. Ed25519 signatures verify its origin; X25519 protects key delivery to authorized devices. This describes the new sync architecture, not every local file or the web account area.
Sign-in and content access are separate. A new device needs device approval or recovery. Compare identity and device fingerprints through an independent channel as explained in the app before confirming a connection.
Recovery
Keep your Recovery Secret offline and separate from the device. Resetting the account password does not replace cryptographic recovery. Without an authorized device, valid recovery information, or an independent backup, encrypted content may remain inaccessible.
Shared organization and team snippets in Paste use a separate encrypted scope. Suite Business, membership, and role do not replace cryptographic authorization. Only the current organization owner may recover a library using its separate recovery backup. This organization path has not been publicly released.
Older sync clients are not automatically compatible with the new synchronization. Existing local content is imported into the new sync only after deliberate selection in the app. Keep an independent backup before changing versions.
Device revocation blocks further authorized access but cannot retrieve copies already decrypted. Sync is not a backup. Disabling sync, signing out, and deleting data are separate actions.