Privacy Policy

What personal data Herald collects, why, and what you can do about it.

Last updated: 26 October 2026

This policy explains how 11924109 Canada Inc. ("we", "us") handles personal data when you visit getherald.ai, use the Herald app, or connect an agent to it.

There are two kinds of personal data here, and we play a different role for each.

Account data is the data we hold about you as a user of the Service: who you are, how you sign in, what you do in the app. For this we are the controller, and this policy is the full story.
Content is what your team writes into its workspaces. It may contain personal data about other people (customers, prospects, colleagues). For that data, your organization is the controller and we are its processor, acting on its instructions under our Data Processing Addendum. If you want to know what a company that uses Herald holds about you, ask that company.

Who we are

The controller for account data is 11924109 Canada Inc., a federal corporation based in Quebec, Canada, at 14 rue Iberville, Notre-Dame-de-l'Île-Perrot, Quebec J7W 1N3, Canada. Email us about privacy at support@getherald.ai.

Under Quebec's privacy law, the person in charge of the protection of personal information at the company is its president, reachable at the same address. Personal data is stored and processed in the United States, by the providers listed on our subprocessors page.

Account data we collect

What	Where it comes from	Why
Name and email address	You, when you sign up or accept an invitation; your identity provider if you sign in with Google or single sign-on	To create your account, identify you in the app and to your team, and send service email
Sign-in details	WorkOS, our authentication provider. We never see your password.	To sign you in and keep your session secure
Organization and workspace membership, role and access	You and your organization's admins	To decide what you can see and do
Invitations you send	You	To invite the person. Kept 14 days, then deleted if not accepted
Activity in the app: what you create, edit, publish or delete, and when	Your use of the app	Shown to your team as revision history and Activity, so changes can be reviewed and undone. Revision history is kept for one year.
Agent requests: which tool was called, by which person or key, when, from which IP address, country and client software, what was asked and which pages were returned	Your agents	Shown to your team under Activity, so you can see how your context is used, and checked against what each connection is allowed to read. Kept 90 days.
Refused agent requests: a revoked, unknown or wrong key or sign-in, or an edit a connection wasn't allowed to make, with the IP address and client software it came from	Your agents, and anyone presenting a token	To detect unauthorized access and leaked keys. Kept one year.
Product analytics: pages viewed, features used, counts and timings, browser and device type, approximate location from IP	Your use of the app and the MCP server, via PostHog	To understand which features are used and fix what isn't working. See "Analytics" below for what we deliberately leave out.
Server logs: IP address, request path, timing and errors	Your browser and agents	To keep the Service secure and running. Kept 30 days.
Email you send us	You	To answer you

We don't collect payment data; the Service is free during early access. If that changes, we'll update this policy before we take a payment.

Why we're allowed to use it

Canadian law (PIPEDA and Quebec's private-sector privacy act) asks us to collect only what we need, for purposes a reasonable person would expect, and with your consent, which you give by signing up and which the uses in the table reflect. Under the GDPR and UK GDPR we also need a lawful basis for each use. Ours are:

Performing our contract with you (or your organization): creating your account, signing you in, serving the Service, showing activity to your team, and sending service email such as invitations, security notices and changes to these terms.
Our legitimate interests: keeping the Service secure, preventing abuse, understanding how it's used so we can improve it, and dealing with disputes. We've weighed these against your interests and limited what we collect, as described under Analytics.
Legal obligations: keeping records we're required to keep, and responding to lawful requests.
Consent, where we ask for it, such as non-essential cookies if we ever add them, or marketing email. You can withdraw consent at any time.

We don't make automated decisions about you that have legal or similarly significant effects.

Analytics

We use PostHog to learn how the app and the MCP server are used. Analytics are about the shape of what happened, not its content. We send user and workspace ids, which features were used, counts, durations and outcomes.

We deliberately never send to analytics: the text of tasks or searches, page titles or bodies, tag or pack names, file names, API key names, error messages, or invitees' email addresses. Those stay in our own database.

One exception: when an agent calls our MCP server, the agent may describe, in its own words, what its user is doing. We currently send that description to PostHog, because it's the best signal we have about what agents do with the product. It can name people or companies. If your organization would rather we didn't, email support@getherald.ai and we'll turn it off for everyone; there is a switch for it.

Workspace API keys act for nobody in particular, so their analytics are counted by workspace, not by person.

Cookies

The app sets one essential cookie: an encrypted session cookie from WorkOS that keeps you signed in. It is required for the Service to work and needs no consent.

When analytics are on, PostHog sets cookies or local storage in your browser to tell one visit from the next. We treat these as analytics cookies. On the marketing site we don't show a cookie banner because we don't set non-essential cookies before you sign in; if that changes we'll ask first.

We don't use advertising cookies or cross-site tracking.

We don't sell personal data. We share it with:

Service providers who host and run the Service for us, listed with their roles and locations on our subprocessors page: infrastructure (hosting, storage, authentication, email), AI models, and analytics. Each is bound by contract to use the data only to provide its service to us.
Your organization. Your name, email, role and activity are visible to the admins and members of the organizations you belong to, as the app's permissions allow.
Authorities and others when the law requires, such as to comply with a court order, or to protect our rights, our customers or the public. We'll tell you if we're allowed to.
A successor, if we are acquired or merge, in which case this policy continues to apply to your data until you're told otherwise.

International transfers

We are in Canada and our providers are in the United States, so your data is stored and processed there, where it is subject to US law and may be accessed by US authorities under that law. Canada is recognised by the EU and the UK as providing adequate protection for data handled by commercial organisations, so transfers to us need no further safeguard. Where personal data protected by the GDPR or UK GDPR then goes on to our US providers, we rely on the European Commission's Standard Contractual Clauses (with the UK Addendum where applicable), or on the provider's certification under the EU-US Data Privacy Framework and its UK extension. Ask us if you'd like a copy of the safeguards in place.

How long we keep it

Data	Kept for
Account and membership	While your account exists, then deleted within 30 days of closure
Pending invitations	14 days
Agent request logs (Activity)	90 days
Refused agent requests and access checks	365 days
Page revision history	365 days
Deleted pages and files (Recently deleted)	90 days, then permanently removed
Server logs	30 days
Product analytics	30 days
Backups	Daily backups, each kept 7 days
Email correspondence and legal records	As long as needed for the purpose, or as the law requires

Your rights

Depending on where you live, you may have the right to access the personal data we hold about you, correct it, have it deleted, restrict or object to how we use it, take it with you in a portable format, and withdraw consent you've given. You can see and change your name and email in the app. For anything else, email support@getherald.ai. We'll reply within one month, and we won't treat you differently for asking.

In Canada, you can complain to the Office of the Privacy Commissioner of Canada (priv.gc.ca) or, in Quebec, the Commission d'accès à l'information (cai.gouv.qc.ca). If you're in the EEA or UK and unhappy with our answer, you can complain to your data protection authority. In the UK that's the Information Commissioner's Office (ico.org.uk). In the EEA, your national authority is listed at edpb.europa.eu.

If you're a California resident, the rights above cover the rights to know, delete and correct under the CCPA. We don't sell or share personal data for cross-context advertising, and we don't use sensitive personal information to infer characteristics about you.

If the data in question is Content that a customer of ours controls, we'll pass your request to them, and help them answer it.

Security

We protect personal data with encryption in transit (TLS) and at rest, access scoped to what each person and key is allowed, a least-privilege database role for the app, dependency scanning and protected deployment branches. The Data Processing Addendum describes our measures in more detail. No system is perfectly secure; if we learn of a breach affecting your data we'll tell you and any regulator we're required to, without undue delay.