Privacy Policy

Who we are

Leash provides controls for supported AI-agent actions, including approvals, secret protection, policy enforcement, optional provider usage visibility, and activity records. This policy covers the Leash website, Leash Cloud, the desktop client, and the Android and iOS apps.

Privacy contact: privacy@openleash.com. General support: support@openleash.com.

Data we collect

• Account information, such as name, email address, sign-in provider, and authentication metadata. Email and password sign-in, and Sign in with Apple on iOS, use Google Firebase Authentication. Apple sign-in requests your name and email; Hide My Email lets you use an Apple relay address. Leash does not automatically link a private Apple identity to a separate account. Leash forwards passwords securely for verification and does not store them. Browser sessions use secure cookies; refresh credentials are encrypted at rest.
• Business directory information, such as organization domain, member names and work emails, administrator role, group or team membership, and enrollment state when an authorized administrator connects an identity source.
• Device and client information, such as platform, app version, device name, API endpoint, and notification registration state.
• Security event data, such as agent name, project name, supported requested action, policy match, approval decision, timestamp, and audit context.
• Provider usage metadata, such as request counts, token counts, connected provider names, and cost estimates where enabled.
• Optional provider-administration credentials supplied by a Business administrator to retrieve organization usage and cost data.
• Public organization-profile information, such as a company-domain website, page metadata, name, and logo used to prepare a new Business workspace.
• Subscription and trial information, including package, seat count, trial dates, and evaluation allowance usage.
• Support messages and operational communications you send to us.
• Website analytics from Google Analytics, such as pages viewed, referral source, approximate location, and browser or device information, together with basic telemetry from hosting, security, and server logs.

Personal account connections

You choose which accounts to connect and whether assistants may read data or make changes. Signing in alone does not connect your email, files, or other accounts. Connected-account credentials are encrypted at rest. Personal assistant links grant access within your chosen permissions; keep them private and revoke them if exposed.

When an assistant uses a personal Leash connection, Leash processes the requested account data to fulfill the tool request and returns the result to that assistant. The activity history records the account, action, selected resource identifiers, timestamp, outcome, and the reason and task context supplied by the assistant. Those explanations and identifiers may contain personal information. Leash does not automatically add complete tool inputs, email bodies, file contents, or tool responses to this history. Personal activity history is retained for 90 days, and connected-account credentials are removed when you disconnect the account.

Leash observes and controls requests routed through its connection. It cannot see unrelated activity in an account or independently verify an assistant’s explanation. You can pause connections, revoke assistant links, disconnect accounts, and erase your personal Leash connection data from your personal space. Disconnecting Leash does not revoke every permission held by an assistant or remove a provider’s own records; you can also manage authorized applications at that provider.

For supported reversible actions, Undo temporarily stores encrypted recovery information, such as resource identifiers and the previous values needed to restore the item. This information can contain personal data and expires after seven days. Permanent deletion, sent messages and other irreversible actions cannot always be undone.

Decisions and notifications

When Leash asks for your decision, it stores the exact pending action or withheld result encrypted so that your choice applies to that item only. Pending requests expire after ten minutes. Action content is removed after the decision is handled or expires; encrypted results retained for your AI to retrieve are removed about an hour after expiry. Decision history remains with your activity records. Push delivery uses Firebase Cloud Messaging and, on Apple devices, Apple Push Notification service. Device registration identifiers are encrypted at rest. Notification previews contain a generic message and a decision or activity link, not email bodies, file contents or other account content. You can turn off browser notifications or unregister a phone by signing out.

Google account data and Limited Use

When you connect Google, Leash accesses the services you authorize, including Gmail messages, drafts, labels and settings; Drive files, folders, sharing permissions and installed app information; Calendar events and calendars; and Contacts. Read/write connections request permissions for supported create, read, update and delete operations. You can restrict each AI inside Leash. Your Google consent and the provider’s own access restrictions also apply. Our Google connection guide explains each mode, its permissions, current user-facing tasks and the AI privacy requirements.

Leash uses this data to perform your requested tasks, apply your configured protections, show activity and provide supported Undo operations. Relevant request and response content may be processed by TypeSafe’s JEV security evaluator. Requested results are returned to the AI service you chose to connect. The connected AI service handles returned content under its own terms, privacy policy and account settings. Leash does not control those external settings. TypeSafe states that it does not train its models on customer requests or responses; its own retention terms also apply. See our external services page.

Leash’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including their Limited Use requirements. Google account data is not used for advertising, sold to data brokers or used by Leash to train general-purpose AI models. Human access is limited to the circumstances permitted by these policies, such as your explicit agreement for support, necessary security investigations or legal requirements.

These restrictions apply to raw Google data and information derived from it, including summaries, classifications, activity metadata and aggregated or anonymized information. Leash uses derived information only for the same requested features and protections; it is not a separate advertising, profiling, credit or model-training dataset. Google account content is not sent to public website analytics. Leash does not use connected Gmail accounts for unsolicited bulk messaging or email warming, or Drive as a public content delivery network.

Google data uses the personal-connection retention periods above: credentials until disconnection, activity and decision metadata for 90 days, supported encrypted Undo recovery information for seven days, and temporary encrypted pending approval content. Requested content and derived security evaluations are processed for the request; they are not automatically retained as complete activity payloads. Deleting your Leash account removes its active connection credentials and associated personal records. Copies already delivered to your chosen AI are governed by that service’s deletion controls.

You can disconnect a Google account in Leash and revoke access through your Google Account connections. You can erase personal connection data in your Leash personal space or request deletion through our account deletion page.

How we use data

• To authenticate users and connect them to a personal account or Business workspace.
• To deliver approval notifications and let users approve or deny agent actions.
• To enforce security policy, protect secrets, maintain audit logs, and show usage information.
• To populate a Business workspace from a company domain and sync authorized directory or provider-usage sources.
• To provide support, debug reliability issues, prevent abuse, and secure the service.
• To understand website use and improve our content, navigation, and product.
• To comply with legal obligations and enforce our terms.

Individual, organization, and service roles

For direct Personal accounts and for account administration, billing, security, abuse prevention, and product operations, Leash determines why and how the relevant information is processed. For a Business workspace, the customer generally determines which employees, devices, agents, protections, and optional provider-usage sources are enrolled; Leash processes that workspace data to deliver the configured service. The exact controller or processor role can depend on the customer, jurisdiction, and written terms.

Business customers are responsible for giving users legally required notice, establishing a lawful basis for workplace monitoring, and limiting administrator access. Employees should direct requests about employer-controlled workspace records to their organization administrator first; they may also contact privacy@openleash.com for help identifying the appropriate route.

Android and iOS apps

The mobile apps provide account connections, AI and provider permissions, protections, activity and approval decisions. App sessions and pending connection bindings use the device’s secure storage. Google and Microsoft sign-in, and data-provider connections, open a browser authorization flow and return to the app. Sign in with Apple uses Apple’s native sign-in sheet. When you delete an Apple-linked Leash account in the app, you authenticate with Apple again so its authorization can be revoked before deletion. Notification permission is optional; device identifiers and delivery are described above. The apps do not need access to your phone’s contacts, photo library or microphone to connect your cloud accounts.

Sharing and processors

We do not sell personal data. We share data only with service providers needed to run Leash, such as infrastructure, sign-in, email, analytics, monitoring, and support providers, or when required by law.

The current categories include hosted infrastructure, managed AI evaluation, authentication, subscription billing, public website analytics, operational communications, and release distribution. Current named services and the change-contact process are listed on our external services page. Leash does not currently publish a pre-signed DPA template; Business customers that require one should contact privacy@openleash.com before sending production organization data and confirm applicable terms in writing.

For Business workspaces, authorized organization administrators may access enrolled-user, device, agent, policy, security-event, approval, and optional usage information for their workspace. Your employer or organization may separately control that information under its own policies.

Security

We use encryption in transit, access controls, least-privilege operational practices, and audit logging appropriate to the sensitivity of security event data. These measures reduce risk but cannot guarantee that every system, integration, or transmission will be error-free or immune from attack.

Retention and deletion

For personal Leash connections, including our AI plugins and remote MCP integration, activity history is retained for 90 days and encrypted Undo recovery information expires after seven days, as described above. The workspace and desktop-client retention terms in the next paragraph apply to the separate business service, not personal connection activity or Undo recovery information.

For the business service, cloud account, workspace, device, event, approval, and usage records are currently retained while needed to operate an active account or workspace; the product does not currently expose a universal customer-configurable retention period or promise automatic deletion after a fixed number of days. A 30-day dashboard view is a reporting window, not a storage-retention promise. You can request account and associated personal data deletion at openleash.com/account/delete.

After identity and authority are verified, we remove account-associated personal data from active product systems that is not required for another lawful purpose. Residual copies may remain in provider backups until those backups rotate. Billing, security, abuse-prevention, dispute, or legal records may be retained where required or permitted by law. Because the current implementation does not enforce one published maximum deletion period across every system, contact privacy@openleash.com if your procurement or legal requirements need a written retention schedule before purchase.

Your choices

• You can sign out of Leash Cloud and remove enrolled desktop clients.
• You can request access, correction, export, or deletion by contacting privacy@openleash.com.

Children

Leash is not directed to children and should not be used by children under 13.

Changes

We may update this policy as the product changes. If changes are material, we will provide reasonable notice through the website, product, or account email where appropriate.