LEGAL / PRIVACYWORKING POLICY · REVIEW BEFORE PRODUCTION

Privacy, without the fog machine.

A plain-language view of the information Zurvo needs to create a workspace, move an artifact, and keep access under control.

LAST UPDATEDJuly 10, 2026VERSION 2026-07-10

THE SHORT VERSION

Clear enough to use. Specific enough to trust.

This is the product-facing policy draft that the registration flow references today. Replace it with counsel-approved language before a public launch.

Information that makes the workspace work

Zurvo handles the account details you provide, such as your name and email address. If you use GitHub, we receive the identity information GitHub authorizes for sign-in. We also process the files, metadata, and access settings you choose to publish.

Why we use it

That information lets us authenticate you, create and deliver artifact links, apply expiry and revoke controls, and protect the service from misuse. We do not need a password from GitHub; GitHub handles that authorization directly.

Sharing is an intentional product choice

A public artifact link can be accessed by people you share it with. Choose your access controls carefully and do not place sensitive material behind a link that is meant to be public.

Retention follows the product state

Temporary artifacts are designed around the expiry you select. Account information and operational records may remain while they are needed to run, secure, or support the workspace. Final production retention periods should be reviewed with counsel before launch.

The agreement you are acknowledging

Creating a workspace records the current version of this notice alongside the Terms of Service. Optional product marketing, if offered later, must be a separate choice.