Privacy & Data Sovereignty

Private by default. Clear about what can be erased.

Kvisl separates the locked core record from user-controlled timeline material so provenance can remain trustworthy without turning every upload into an irreversible public artifact. Last updated 3 September 2026.

Information Kvisl processes

Kvisl may process maker account and studio information, client details entered by the maker, Piece specifications, production updates, uploaded media, handoff events, certificates, Physical Link records and related security data needed to provide the service.

Locked core record

When a Piece reaches its record-lock point, the core production facts used for its permanent identity and SHA-256 integrity check are sealed. Those fields are retained as part of the provenance record and are not treated like ordinary editable timeline content.

Sovereign timeline media

Non-core progress notes, images and other timeline material remain under the maker's data-sovereignty controls. Makers can hide eligible material from presentation, make it visible again, or permanently delete eligible records and media. A deletion event may remain in the audit history without retaining the deleted content itself.

Maker's final message

A final maker message can be added as text, audio or both before the Piece is sealed. Once it is intentionally sealed with the final record, it becomes part of that completed archival context rather than ordinary editable timeline media.

Client information

Client contact information is not intended to be public by default. Makers should enter only information necessary for the work and should share private Piece links only with the intended recipient.

Service providers and storage

Kvisl relies on infrastructure and software providers to host the application, authenticate users, store data and media, and deliver related functionality. Those providers process information as needed to operate the service.

Security

Kvisl uses authenticated account access, row-level access controls, private storage where appropriate, server-side credentials for protected operations and integrity checks for locked production records. No online system can promise absolute security, so users should also protect account credentials and private links.

Access, correction and deletion requests

Product controls should be used where self-service hiding or deletion is available. For other privacy requests associated with Kvisl, contact distributary@kvisl.com.