Studio privacy approach

Scope of this page

This is a studio‑level overview. It is not a legal contract or a final policy for any specific app. When an app is ready for release, it may include its own terms and privacy information directly inside the app and at a separate URL such as /lockbox/privacy/ .

Information collected

The goal is to collect as little information as is practical to operate and improve apps. Where analytics or crash reporting are used, they are intended to focus on technical health and usage patterns rather than personal content.

• Contact information you send directly (for example, via email).
• High‑level usage metrics, where enabled, to understand which features are helpful.
• Technical logs necessary to diagnose crashes or errors, where enabled.

On‑device versus server data

Many Viya App Studio apps are designed to keep sensitive content on the device rather than on remote servers. When a feature requires server communication, it will be described in the relevant app documentation.

Per‑app privacy pages

As apps mature, each one can publish a more detailed page under a dedicated path. For example:

• LockBox: /lockbox/privacy/
• Future apps: /apps/<app-name>/privacy/

These pages can describe exactly what data an app uses, how long it is stored, and what choices you have.

Updates

This page may evolve over time as the studio, apps, and applicable regulations change. Meaningful changes can be summarised in release notes or in a short change log.