Privacy, in plain language.

Draft for legal review. This is an implementation description, not an approved privacy policy. Linaw must not open to public production users until the controller details, lawful basis, retention periods and rights contact are completed.

What this version stores

Linaw stores your account details, preferences and information you enter. If you connect Google or Microsoft, it stores selected message excerpts, structured suggestions and calendar event details. OAuth credentials are encrypted on the server. Full email bodies are not retained by the application. Linked UK bank accounts contribute transaction details and, where the configured provider API supports them, balances and regular-payment records. To start a current TrueLayer connection, your full name and Linaw sign-in email are shared with TrueLayer. Account numbers, sort codes and bank login details are not stored. Sandbox test data is labelled and excluded from real Money totals.

Your choices

Connections are optional and read-only. Calendar suggestions require review. You can disconnect a provider, delete its imported data, export your account data or request immediate account deletion in Settings. You can stop individual email/calendar services or disconnect the entire provider. Removing the final service deletes Linaw’s credentials. Google and legacy TrueLayer revocation is attempted where supported. For Microsoft and current TrueLayer connections, also remove consent in the provider or bank settings. Deleting imported data stops that service before removing its records.

Demo and estimates

The demo contains synthetic examples stored only in this browser. It is separate from account data and can be reset in demo Settings. Money values and income estimates depend on the information available and may omit commitments.

Processing and providers

This version uses deterministic parsing and does not call a model provider. Account data is stored in the project owner’s configured Supabase project. Google, Microsoft and TrueLayer Data APIs are contacted only for enabled connections. No payment initiation or external email or calendar editing is implemented. Hosting, backup retention, regional processing, cookies and subprocessor disclosures must be completed before launch.

What still needs legal review

Controller identity and contact, lawful basis, retention schedules, international transfers, UK GDPR rights, complaint procedures, age eligibility, cookie disclosures and Google API Limited Use obligations require owner and legal review. No compliance certification is claimed.