← Back to heyidentity.dev

Privacy Notice

Last updated: October 2026

This notice explains what data is collected when you visit heyidentity.dev or sign up for and use the hosted service at app.heyidentity.dev, manage.heyidentity.dev and api.heyidentity.dev.

1. The heyidentity.dev marketing website

What we collect

We do not collect any personal data just by you browsing this website. There are no analytics scripts and no tracking pixels.

Cookies

This website does not set any cookies.

Hosting and access logs

heyidentity.dev is hosted as a static website. The hosting provider may collect standard web server access logs (IP address, timestamp, path requested, user-agent string) as part of normal infrastructure operation. We do not have direct access to or control over these logs. Please refer to your hosting provider's privacy policy for details.

2. Signing up for and using the hosted service (app., manage. and api.heyidentity.dev)

app.heyidentity.dev, manage.heyidentity.dev and api.heyidentity.dev are one hosted SaaS product: unlike the marketing website, it does collect and store data, described here accurately.

What we collect

• Signup email address and display name. Self-service signup collects the email address and tenant display name you submit, to send a verification link, to let you recover access to your tenant, and to tell you if your tenant is deleted from its management link.
• Tenant and configuration data. The clients, redirect URIs, test users, and claims you define in your tenant's configuration are stored server-side in our database, not on your own machine.
• Durable management link. A management token that authorizes editing your own tenant's configuration without an admin account. Treat it like a password - anyone with the link can edit your tenant.

Who can access it

• You, the tenant owner, via your durable management link, which reaches only the tenant and configuration it was issued for.
• HeyIdentity operators, via the admin section, for operating the service, providing support, and enforcing acceptable use.

Each change to a tenant's configuration is attributed to whether it was made by the tenant owner, an operator or an AI agent through the Agent API, so there is a record of who changed what.

Tenants created by AI agents

• No contact data. When an AI agent creates a tenant through the Agent API or its MCP server, we collect no email address or other contact data of any person, and send no email. The tenant's content (clients, test users, claims) is provided by the person or organisation operating the agent, who is responsible for using fictional test people only.
• Claiming collects your email, with your consent. Your email address is collected only when you open a tenant's claim page, enter it yourself and accept the Terms of Use and this notice. We store it with the version and time of your consent, use it to send the verification link and your management link, to tell you if the tenant is deleted from its management link, and to let you recover access later.
• Agent tokens. We store only a hash of each agent token, with a label, its creation and last-used times, and when it was revoked.
• Rate limiting by IP address. The Agent API limits requests per source IP address and per agent token to prevent abuse. IP addresses are used for these limits in memory and are not stored with your tenant.

Retention and deletion

Tenant and configuration data is retained for as long as the tenant exists. An operator can permanently delete a tenant and all of its configuration data - this is a hard delete, not a soft flag, and the tenant's route becomes unreachable immediately. As the tenant owner you can delete any of your configurations, with its users, clients and claims, on your management page; its endpoints stop working immediately, and a tenant always keeps at least one configuration. You can also delete the whole tenant yourself at the end of your management page by typing its name; everything it holds is permanently deleted at once, and we email a notice of the deletion to your owner address. You can still contact us at the address in section 3 to have a tenant deleted.

• Unclaimed agent tenants: 7 days. A tenant created by an AI agent that nobody claims is permanently deleted, with its configuration and agent tokens, 7 days after it was created.
• Unverified signups: 30 days. A signup whose email address is never verified is permanently deleted, with its email address, consent record and configuration, 30 days after the most recent verification email was sent.
• Deleted agent tenants leave a 90-day record. For 90 days after an unclaimed agent tenant is deleted, or after you delete a tenant that had active agent tokens, we keep only its tenant route id, the hashes of its agent tokens (for a tenant you deleted, only those that were not revoked), and when it was deleted (and, for an unclaimed tenant, when it expired) - no configuration, email address or name - so its agent can be told what happened and support can explain it. The record is then deleted.
• Change history: 365 days. We keep a record of changes to each tenant - what changed, when, and whether the operator, the tenant owner, an AI agent or the service itself made it - for 365 days, also after the tenant is deleted. It holds the names of the tenant, its configurations, test users, clients and claims as they were entered at the time (keep them synthetic), but never your email address, a secret or a token. For an operator, it holds the name or account identifier they signed in to the admin section with. A tenant that was never claimed or verified is recorded without any names, so nothing it was called remains after it is deleted. You can ask us to erase a tenant's change history once its entries are 30 days old; younger entries can't be deleted.

This is a beta service: your data may also be reset as described in the Terms of Use.

Cookies

The hosted service sets a strictly-necessary anti-forgery cookie on any page with a form (signup, verification, claim, tenant management), used only to prevent cross-site request forgery. Operators additionally get a session cookie when signing in to the admin section. When a tester pins a test user on a configuration's user picker or pinned user page, the service sets a functional cookie that holds only that test user's key, so later sign-ins skip the picker; it lasts 30 days and is removed with "Clear pin" on the pinned user page. None of these cookies is used for advertising or analytics.

Keep it synthetic

Do not put real user data (genuine email addresses, PII, production credentials) into a HeyIdentity tenant configuration. Synthetic test data is strongly recommended, and the hosted service is not intended or hardened for protecting real user data.

3. Your rights and contact

To ask about, correct, or delete data we hold about your tenant, email support@heyidentity.dev.

4. Changes to this notice

If this notice changes, the “last updated” date at the top of the page will be updated.