Privacy-first app design in practice

Privacy is not a slogan. It is a set of product decisions users can verify.

2026-10-05

Say what the app does with data

Users should not have to guess. We publish privacy policies, terms, and deletion instructions on voysapps.io, and we link them from product pages. If a feature needs an account, we explain why. If a notebook stays on-device, we say that too.

NoteLab is an example of local-first design: handwriting and PDFs can live on the device, with optional AI only when the user asks. That framing sets expectations before anyone pastes sensitive notes into a chat box.

Minimize what you collect

Collecting less data reduces risk and support burden. We prefer store billing so we do not handle raw card numbers. Diagnostics stay limited to what helps reliability. Ads, when present, follow Google publisher and consent rules for European users.

Account deletion is a first-class path. People can start in-app or at https://voysapps.io/account-deletion. We keep only what law or fraud prevention requires after a verified request.

Design for consent and clarity

Consent banners and policy links are not decoration. They are part of using advertising and analytics responsibly. We configure messaging for users in the EEA, UK, and Switzerland and keep ads.txt and app-ads.txt available at the apex domain for sellers authorization.

Privacy-first design is continuous work: review new SDKs, update policies when features change, and answer deletion requests promptly. That is how a small studio stays trustworthy at global scale.