Your work. Your choices.

Privacy.

Hay saves your workspace on your device. When a feature uses an online service, the information needed for that feature leaves your device. This page explains what that includes.

Last updated

About this notice

This notice covers the Hay desktop app, hay.so and the Hay account and plugin services. For questions or requests about personal information, contact privacy@hay.so.

Your workspace stays on your device

Workspaces, chats, local documents, app data and settings are saved on your device. Hay does not automatically upload your workspace to a Hay cloud service. Exports and backups you create contain the data you choose to include; you control where you store or share them.

Account sessions, model keys and connector credentials are kept by the native app using operating-system credential encryption. This protection is separate from your workspace files, which are not all encrypted by Hay. Device encryption, backups and access to your Mac remain under your control.

Websites opened in Hay’s browser receive normal browser requests and may save cookies and sign-ins in that workspace’s browser storage. Their own privacy policies apply. An app or plugin receives only the capabilities you grant; review its source, permissions and publisher before using it with personal information.

Google Docs access

Availability depends on your installed build. Google connections are disabled in the current friend-release configuration; the details below describe Google-enabled builds. See connection availability.

Connecting Google lets Hay verify your account identity and work with Google Docs you select. Hay requests your email and account identity, plus drive.file access to individual files used with Hay. It does not request access to your entire Drive or Gmail.

Google’s file selection and Hay’s permissions are separate steps. Choosing a file in Google makes it available to the connection. You then review which chat may read or edit that exact document. Connecting an account alone does not grant every chat access.

Hay reads the selected document’s identifier, title, returned text, tabs and revision information to display it beside chat, prepare context you choose to attach, and check edits. Each supported replacement shows the exact text and destination for review before it is sent to Google. Hay reads the result back to check what was saved.

Google access and refresh tokens remain encrypted on your device and are sent to Google when needed to authorize requests. Hay’s account service does not receive them. The document view holds returned text in memory. Saved navigation and operation receipts contain identifiers, revisions, hashes, timestamps and outcomes, rather than a stored copy of the document body.

Text you explicitly attach to a model request is sent to your selected AI provider. If you grant a chat or plugin both document access and model access, its assistant or declared AI features can also read the permitted document and send returned content to that provider. The access review explains this. Prompts and replies remain in local chat history, and a reply may quote or summarize the source.

Hay does not sell Google user data or use it for advertising. Hay’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We use this information to provide the document features you choose, not to train general-purpose AI models.

Disconnect a Google account in Connections to remove its saved credential and related permissions from Hay. You can also choose Google-side revocation, or remove Hay in your Google account connections. Disconnecting does not delete your original Google files, undo completed edits, or erase existing chat replies, exports or backups.

What goes to an AI provider

When you use AI, your prompt, relevant conversation and permitted tool or document context go to the provider configured for that workspace. You can inspect or remove manual document attachments before sending. Separately, a chat or plugin with both model and document access can retrieve its granted content for the model. Granting model access also lets a plugin’s declared AI features send their permitted context.

Depending on your choice, the recipient may be OpenAI, Anthropic, another API endpoint or a local model. The provider’s account settings, retention and data policies apply. Hay does not promise zero data retention for a hosted connection. Use a provider and account configuration that does not use Google-derived content for general model training before sending that content.

Hay does not operate a model-training service. Generating a response is separate from training a model. If you contact support, include only the information you want us to see; we do not need your connector tokens or model keys.

Accounts, publication and support

The Hay account service stores your email, account identifier, verification status, sessions and related security information, including IP address and user agent. If you create a profile or publish a plugin or skill, it also stores your display name, handle, ownership records and the release content and metadata you submit. A public release makes its published content and publisher profile available to others. Private publications are restricted to the owning account.

Cloudflare hosts the public website and account and registry services, including the account database. Resend delivers sign-in emails. Google Workspace receives and stores support and privacy correspondence. See the subprocessors page for the provider list and policy links. These providers process the request, delivery and security information needed to provide their services. Your model and connected-service requests go to those services directly from the app.

Hosting providers receive ordinary request details, such as IP address, requested URL, browser information and time, to deliver and protect the service. Hay’s static website does not load advertising or analytics scripts. Account pages use essential session and sign-in cookies; websites and services you visit separately may use other cookies.

If you email us, we receive your address and message, together with any files you choose to send. We use them to answer your request and maintain the service. We do not sell personal information.

How long information is kept

Local work remains until you remove it, its workspace or the app’s saved data. Removing the application alone may leave its saved data behind. Copies in exports, device backups or third-party services must be managed separately.

Sign-in codes expire after five minutes. Hay sessions normally expire after 30 days unless renewed, and can be revoked by signing out. Expiry limits access; it does not mean every related database or provider log entry is immediately erased.

Account and profile records are kept while needed to provide your account and resolve security, ownership or support issues. There is no automatic inactivity deletion schedule. Contact us to request deletion. Published releases are versioned and intended to remain available to people who installed them, so public copies and release history may remain after an account request. We will explain any information we need to retain for security, legal obligations or publication integrity when handling your request.

Your choices and rights

You can remove pending context, revoke a chat’s document permissions, disconnect an external account, sign out, and delete local chats or workspaces. Removing a connection does not retract data already sent to a model provider. Manage that data through the provider’s account controls or privacy contact.

For personal information held by Hay’s hosted services, email privacy@hay.so to request access, correction, deletion or a copy. We may need to verify your identity. Depending on where you live and the applicable law, you may also have rights to restrict or object to processing, withdraw consent and complain to a supervisory authority. UK users can contact the Information Commissioner’s Office.

We use account information to provide the services you request, security information to prevent abuse and keep those services reliable, and support messages to respond to you. Where UK or EU data protection law applies, these purposes rely on performing our agreement with you or taking steps at your request, our legitimate interests in operating and protecting Hay and answering support requests, and legal obligations where applicable. Optional connections and disclosures remain under your control.

Online providers may process information outside your country. Their locations, contractual safeguards and privacy controls depend on the provider and account you choose. Contact us for information about the safeguards applicable to Hay’s hosted-service providers.

Changes to this notice

We will update this page when Hay’s data handling changes and revise the date above. Material changes that affect existing permissions will need appropriate notice before they apply.