Collect what the service needs. Keep project data private.

This early-access notice describes the intended privacy boundary. Contract versions and processing details will remain visible as the service matures.

Data we process

Account identifiers, security/session records, authorized project content, service settings, contact messages, and limited operational logs support the requested workflows.

How data is protected

Projects are private by default; permissions, encryption boundaries, redaction, short-lived access grants, and audit controls limit exposure.

Your choices

Users can manage profile and offline data, request export or deletion, and review explicit sharing and QR publication decisions.