Trust & transparency
Security & data.
Know where your work goes, what a task can access, and which controls are yours.
Last reviewed
Know what stays on your Mac
Chats, local documents, app records and workspace settings are saved on your device. Signing in to Hay does not automatically upload that workspace to Hay’s servers.
Account sessions, model keys and connection credentials use operating-system credential encryption. Workspace files are separate and are not all encrypted by Hay. Use your Mac’s device encryption and keep backups of work you need.
Know what leaves it
| Destination | What is sent | When |
|---|---|---|
| Hay’s account service | Email, account and session information, and security request details | Signing in and using account features |
| Hay’s registry | Release code, metadata and publisher details you submit | After you review and approve a public or private publication |
| Your model provider | Prompts, relevant conversation and context made available to the request | When you use an assistant or an app’s AI features |
| A connected service | Requests and content needed for the action you permit | When you read or make a reviewed edit to connected material |
| A website | Normal web requests and any information you enter there | When you visit it in Hay’s browser |
Scroll the table horizontally to see all columns.
The privacy notice explains retention and your choices. Subprocessors lists the providers used for Hay’s hosting, sign-in email and support inbox.
Review access at the task
Installing an app does not grant its capabilities. Review the requested access, then enable what the task needs. A chat’s document permissions and a connected account’s own permissions are separate controls.
If a task can read a document and use a model, permitted document content can become model context. Check both permissions before using confidential material. Read the provider’s policies and your organization’s rules before sending work to a hosted model.
Connected-document edits use a review step showing the proposed change and destination. An uncertain write needs its outcome checked before another attempt. Local records and generated drafts still need your review; an assistant’s answer is not proof that an external action succeeded.
Connections and build availability
The current friend-release configuration disables Google connections. A Google-enabled preview needs its own configured build and consent. Notion page connections are separate and use the supported native page view; they do not provide the full Notion website editor inside Hay.
Google-enabled builds use per-file access and separate user-interactive and assistant connection roles. An existing account connection does not grant every task access to its documents. Help explains how to check what your build offers.
Protect an account and a workspace
Enter sign-in codes in Hay or on app.hay.so. Browser and desktop sessions are separate. Signing out on one surface does not sign out every other device or delete local files.
Keep workspace exports, shared files and public releases under review. A public release makes its submitted code and metadata available to others. Check for secrets before publishing. Removing a connection cannot retract information already sent to another service.
Hay is in private beta. It currently provides a personal desktop workspace, with no shared live workspace or organization-wide administration interface. This page describes implemented controls, rather than a certification or enterprise service commitment.
Report a security issue
Email privacy@hay.so with the affected feature, app version and steps to reproduce. Use a small synthetic example where possible. Leave out sign-in codes, tokens, model keys and private documents. We can arrange an appropriate way to receive more detail if needed.