Privacy notice

Information handled by the service

• Account information. When you choose Google sign-in, Google and Supabase provide authentication identifiers, email verification information, and the profile information included in your sign-in response. Klisten uses a verified user identifier to associate you with your organization and permissions. This sign-in integration does not request access to your Gmail messages, Drive documents, or payment cards.
• Service and usage information. Depending on the API you use, this includes organization and API key identifiers, permission settings, spending limits, request identifiers, timestamps, tool URLs, schemas and descriptions, policy configuration, observations, verification receipts, and usage records. Do not submit secrets or personal information that the operation does not require.
• Supplied product records. Depending on the service and the input you choose to provide, Klisten also processes supplied documents and text, invoice and order rows, contract or SLA terms, consent and deletion-request records, part or entity identifiers, vector metadata, worker skill or proof records, and insurance-loss or sample planning records. These inputs and their calculated results can contain personal or commercially sensitive information. Some services retain organization-scoped records and reports so later operations can use them. Use fictional data for reviews and provide only records you are authorized to process; do not supply unrelated personal information, medical records or credentials.
• Payment records. When checkout is available and you choose to use it, Klisten handles payment references, amounts, currencies, status, account associations, and refund or dispute notifications. PayPal handles the payment details entered in its checkout. Klisten's checkout does not ask you to enter card or bank account details into a Klisten form.
• Connection and support information. Our hosting and security providers handle network information, such as IP addresses, browser request information, and access or error logs. If you email us, we receive your email address and the contents and attachments you send.

Why information is used

Information is used to authenticate users, enforce organization and API permissions, provide requested checks and evidence, record usage, apply spending limits, reconcile payments, investigate errors or abuse, and respond to support requests. Payment and audit records also support accounting and dispute handling.

The Google sign-in integration is used for account access. Signing in does not authorize an agent to spend without the account permissions and limits required by the service.

Service providers and information sharing

Klisten uses the following providers for the functions described here. These providers receive information needed for their respective functions; their own terms and privacy notices also describe how they handle information.

• Google: Google sign-in for authentication and Google Cloud for application hosting and storage. See Google's privacy policy.
• Supabase: authentication and database services for account and application records. See Supabase's privacy policy.
• Cloudflare: website delivery, DNS, and traffic security. See Cloudflare's privacy policy.
• PayPal: checkout, payment processing, and payment status notifications when you use an enabled payment feature. See PayPal's privacy statement.

A requested tool observation contacts the target service, which can receive connection information and the protocol requests necessary for that observation. Use only targets you are authorized to submit. Organization administrators can access information made available through their permissions.

Providers may process information in countries other than your own. Contact us before submitting information that is subject to a specific residency requirement. Information may also need to be disclosed in response to applicable legal requirements.

Browser storage and security

The account page keeps its authentication tokens in the current tab's memory. It uses session storage for a short-lived sign-in verification value needed to complete the redirect. Reloading the account page requires signing in again. Google and PayPal may use their own cookies or storage on their pages and embedded interfaces.

Keep API keys private and revoke keys you no longer need. Never send passwords, payment card details, or secret keys in a support email. Security controls reduce risk but cannot guarantee that every incident will be prevented.

Assistant and MCP connections

When you connect an assistant to a Klisten MCP service, the assistant provider sends the tool arguments needed for your requested operation and receives its result. For ToolGuard, these arguments can include registered service and policy identifiers, tool names, expected fingerprints, idempotency identifiers, and attestation identifiers. Results can include decisions, reason codes and verification evidence associated with your authorized organization. The connection does not require you to paste account passwords or API secrets into a conversation or tool argument.

Other Klisten product connectors receive the arguments you submit to their declared tools, calculate or normalize supplied information, and return results and reports for the authorized organization. Supplied text, identifiers, documents and derived records may be retained by those services. A client plugin does not need your entire assistant conversation, Google password or API secret to be pasted into a tool call. Requesting an unsupported external action does not enable an external integration.

For OAuth connections, Klisten and its authentication provider process client identifiers, permissions, consent and session bindings, expiry information and revocation status to authenticate the connection and enforce your selected access. Connecting an assistant does not itself grant permissions beyond those you approve. The assistant provider handles information received through its service under its own privacy terms. Review the requested permissions before connecting and avoid sending unrelated personal information.

You can disconnect an assistant using that provider's connection controls. Disconnecting the assistant is separate from deleting Klisten account, usage or receipt records. For assistance with revoking delegated access, access or deletion requests, contact [email protected] without sending credentials.

Retention, expiry and deletion

Access expiry is different from deletion of stored records. ToolGuard checks whether a delegated connection and its permissions remain valid before permitting an operation. Revoking a connection or API key prevents further authorized use but does not automatically delete related consent, security, usage or verification records.

ToolGuard keeps account and key identifiers, delegated-consent and session-binding records, usage and security records, and verification receipts to provide the service, enforce permissions and limits, and investigate errors or misuse. The current application does not automatically delete all of these records when a session expires or a connection is revoked. Evidence objects have a separate expiry and cleanup mechanism; receipt and audit metadata may remain after the associated evidence object expires.

For other supplied-data products, stored organization-scoped inputs, workflow state, calculated results, reports and related audit metadata do not have a universal automatic deletion deadline. Do not assume these records are deleted within 30 days or when an assistant session ends. Connection expiry, a sample document validity date and deletion of stored product records are separate matters. Contact us for access or deletion requests; provider systems and backups may retain separate copies as described below.

For access, correction, account closure, delegated-access revocation or deletion requests, contact [email protected]. Identify the relevant account or organization without sending passwords, tokens or API secrets. We may need to verify your authority and identify records subject to accounting, dispute or legal requirements. Provider systems and recovery backups are separate from active application records, so disconnecting an assistant does not immediately remove every backup or provider record.

Access, correction, and deletion requests

You can sign out and manage API keys through the available account controls. You can also remove the application's Google account connection in your Google account settings. Removing that connection does not itself delete your Klisten account or transaction records.

For questions about stored information, retention, access, correction, account closure, or deletion, contact [email protected]. Identify the account or organization involved without sending credentials. We may need to verify your identity and authority before acting on a request. Applicable accounting, dispute, security, or legal requirements may affect which records can be deleted.

Changes and contact

Updates to this notice will be published on this page with a revised date. Contact Klisten Inc at [email protected] with privacy questions.