Privacy Policy

Last updated 12 August 2026

Glaard ("we", "us") is operated from Belgium. This page explains what we collect when your studio uses Glaard, why, and who else ever sees it.

What we collect

  • Account information: the email address and name you sign up with, and your studio workspace name.
  • Team members: names and, optionally, email addresses of the people you add to your studio workspace so tasks can be assigned to them.
  • Forwarded messages: the full content (subject, body, sender address, and attachment metadata) of anything sent to your studio's Glaard address. This is the core input the product runs on.
  • Extracted tasks: the titles, dates, categories, and status of to-dos generated from your forwarded messages.

We never access any inbox other than the unique address you forward things to.

Who else processes it

We use a small number of service providers to run Glaard. Each only sees what it needs to do its job:

  • Anthropic (Claude API): processes the text of forwarded messages to extract tasks. Message content is sent to Anthropic for this purpose only.
  • Brevo: receives inbound email sent to your forwarding address and sends the daily digest email.
  • Supabase: hosts our database and handles account authentication. Each studio's data is isolated at the database level so only members of that studio can ever query it.
  • Vercel: hosts the application itself.
  • Stripe: processes payment information (card details, billing address) to handle your subscription. We never see or store your full card number ourselves.

We do not sell your data, and we do not use it to train our own models.

How long we keep it

We keep your data for as long as your account is active. If you delete your account, we delete your studio's data within 30 days, except where we're required to retain records for legal reasons.

Your rights

You can ask us to access, correct, export, or delete your data at any time by emailing hello@glaard.com. If you're in the EU/EEA, this includes the rights guaranteed under the GDPR.

Security

Data is encrypted in transit (HTTPS) and access to your studio's data is restricted at the database level so that only that studio's members can read it, even from our own infrastructure's perspective.

Changes

If this policy changes materially, we'll update the date at the top of this page and, where appropriate, notify you directly.

Contact

Questions about this policy: hello@glaard.com