Privacy & data handling

Only what you type into Helm, plus basic account and usage information:

• Your account email and password (the password is stored hashed by our authentication provider, never in plain text).
• Your profile and short onboarding survey: your role, your organisation's name and what it does, how comfortable you are with AI, and the tools you already use.
• Your workflow work: steps, descriptions, 5C answers, evaluations, coach conversations, reflections, and experiment plans.
• Product usage events: which page or stage you opened, timings, and counts. These carry IDs, not your free-text answers.

Helm requires an account, so everything you do is saved to your own account in a managed Postgres database hosted on Lovable Cloud (Supabase on AWS). Your browser also keeps a local working copy so pages load instantly and you can pick up where you left off. Traffic is encrypted in transit with TLS, and the database is encrypted at rest. Each account can only read and write its own row; this is enforced by row-level security in the database, so no other Helm user can see your work.

If a browser already holds work that isn't linked to any account — for example from an earlier version of Helm — we ask you once, after you sign in, whether to add it to your account or discard it. Nothing is merged without your choice, and the local copy is only cleared once the work is safely saved to your account or you choose to discard it. Signing out clears the local copy on that browser; your account keeps everything.

To generate coaching, evidence readings, and experiment plans, the text you enter is sent to AI providers. We deliberately do not send your name, email address, or organisation name in those requests — only your role, comfort level, tools, and the workflow text itself. These providers operate on API terms that do not use submitted data to train their models.

Because your free text leaves Helm to be processed, please do not enter client, beneficiary, donor, health, or case-level personal information anywhere in the app.

Your work is kept for as long as your account exists. Deleting your account removes your stored work immediately and unlinks your usage events so they remain only as anonymous counts. Note that the managed database takes automated backups, so deleted data can persist in those backups for the platform's backup retention window before ageing out. AI providers keep their own request logs on their own schedules, and any plan you shared to Slack stays in that Slack workspace under its retention policy.

You can download everything Helm stores about you, or permanently delete your account and its data, at any time from your progress page.

Go to your progress page

If you're evaluating Helm on behalf of an organisation and need more detail — data processing agreements, residency, or subprocessor terms — contact the Helm team before rolling it out to staff.