Velyra
EspanolOpen app

Privacy

Your content stays private by default.

Velyra is built around personal data, so the public beta explains what is stored, what is not logged, and how export works.

Private content

Velyra treats personal system data as user-owned content.

  • Registry entries default to private.
  • Tasks, notes, goals, projects, focus sessions, habits, and internal calendar events are scoped by user and workspace.
  • Analytics must not include task text, note content, Registry content, calendar details, or project names.

Integrations and exports

External connections and exported files carry clear privacy boundaries.

  • Google Calendar data is used for calendar sync and visible calendar context.
  • Export files can contain private data; do not share them casually.
  • Exports exclude OAuth tokens, refresh tokens, secrets, and integration credentials.

Account control

The public docs prepare the account and data controls for beta use.

  • Users can disconnect Google without deleting internal Velyra data.
  • Read and export remain available when active creation is blocked.
  • Closure and retention rules must be finalized before paid launch.