Privacy policy

Last updated 30 October 2026

This policy explains how Kautuka handles information when you install and use the Kautuka agent platform, sign in with Google or Microsoft, connect Google or Microsoft mail, or use the online services needed for sign-in, release information and the in-app catalogue. Kautuka runs on the computer you operate. Devkrity does not host your agents, conversations, files or run history.

Who operates Kautuka

Kautuka is developed by Devkrity, an independent software company in Australia. For privacy questions, contact hello@devkrity.com.

Information stored on your appliance

Kautuka stores application data on the appliance you or your organisation operate. Depending on how you use it, that data can include local user accounts, agent and workflow settings, instructions you submit, files you choose to use, messages and outputs from agent sessions, approval decisions, and run activity.

Users on a shared appliance have separate account-scoped interactions and files. An agent can be shared where its owner chooses; sharing an agent does not by itself merge each user’s conversations or files. The appliance administrator manages access to the installation and its services.

Connector credentials are held separately from agent instructions and are stored by Kautuka’s credentials service on the appliance. Google and Microsoft mail refresh credentials are stored locally in encrypted form. Devkrity cannot remotely browse the local application database or run history.

Google and Microsoft account sign-in

Optional Google and Microsoft sign-in is separate from connecting a mailbox. It uses the openid, email and profile scopes to authenticate your identity. These sign-in scopes do not grant Kautuka access to your mail. Kautuka uses identity details such as your provider account ID, verified email address and display name to authenticate you and link you to your Kautuka account. For released builds, auth.kautuka.io exchanges the sign-in authorization code and returns a signed identity assertion for the appliance to validate. The broker may process authentication and security metadata, but does not receive your Kautuka conversations, files, run history or mailbox content through social sign-in.

Google and Microsoft mail data

If you connect Gmail or Google Workspace, Google asks you to authorise Kautuka’s Gmail API access. The connector requests https://www.googleapis.com/auth/gmail.modify. If you connect Microsoft 365 mail, Microsoft asks you to authorise delegated access to the signed-in user’s mailbox using offline_access, Mail.ReadWrite, Mail.Send and User.Read. Both connectors can list and search mail, read message content and supported file attachments, create or update drafts, and send mail. Kautuka’s built-in mail connectors do not provide a tool for deleting messages.

Kautuka uses Google and Microsoft mail data to carry out the mail and agent features you request. Message details, content or attachments used in a task may appear in that task’s conversation, outputs or run record stored on your appliance.

If you ask an agent to use a cloud model, relevant message content, attachment content and your instructions may be included in the model request sent from your appliance to the model provider you configured. That provider processes the request under its own terms and privacy practices. If you use a model running locally, the model request stays within the local environment you selected. Devkrity does not use mail data for advertising, sell it, or use it to train general-purpose AI models.

For released builds, Google and Microsoft mail connections use Devkrity’s hosted broker at auth.kautuka.io to exchange authorization codes and connector tokens. The broker processes authentication tokens to provide this exchange; the mail connectors send message content and attachments directly from your appliance to the mail provider, not through the broker. Kautuka stores the refresh credential on your appliance. The broker may process connection and security metadata needed to operate and protect the service.

Kautuka’s use of Google user data is intended to follow the Google API Services User Data Policy and its Limited Use requirements. The gmail.modify scope is classified by Google as restricted. Google may require additional verification and a security assessment; publishing a privacy policy alone does not complete those requirements. Microsoft’s permissions and terms also apply when you connect a Microsoft 365 mailbox.

Models and other connected services

You choose the model provider and other services connected to Kautuka. A model provider receives the prompt and context Kautuka sends for each request. A mail, chat or other connector receives the information needed to perform the action you ask it to perform. Each provider’s own privacy policy and terms apply. Review those terms and configure only the connections you intend to use.

Information processed by Devkrity services

Sign-in and mail broker: auth.kautuka.io handles Google and Microsoft social sign-in exchanges and mail connector token exchanges. It processes authorization data and security state, not agent conversations or mailbox contents.
Updates and catalogue: Kautuka checks GitHub Releases for releases and downloads installers and release files from the selected release. The in-app connector and skill catalogue uses a separate signed catalogue at kautuka.store. These services do not host agent sessions or run history.
Operational diagnostics: Kautuka’s logs, metrics and traces are stored in a local OpenObserve service by default. An administrator can configure an external OpenTelemetry endpoint; if they do, diagnostic data is sent to that endpoint under the administrator’s control.
Websites and infrastructure: Cloudflare and GitHub may process ordinary connection data when you visit the websites, sign in, check for updates or download files, under their own privacy terms.

Kautuka does not send product usage analytics to Devkrity by default. Requests to sign-in or update services still require those services to process operational request information, such as connection and security metadata.

Retention and your choices

Agent data and run records remain on the appliance until you remove them using Kautuka’s available controls or delete the relevant local application data. Backups can retain separate copies. Devkrity does not have a copy of those local records to delete for you.

You can disconnect Google or Microsoft mail in Kautuka’s connector settings and revoke Kautuka’s access from the security settings of your Google or Microsoft account. Disconnecting stops future connector use; it does not automatically remove message content or run records already stored on your appliance, or copies held by a model or other provider you used.

To ask a question about information processed by Devkrity services, email hello@devkrity.com. Please do not email mailbox contents or credentials unless support has asked you to provide specific information.

Security and changes

Kautuka is designed to keep agent execution and its records on your appliance, separate saved credentials from model instructions, and let you configure access and approvals. No software or connected service can guarantee absolute security. This policy will be updated if Kautuka’s data handling changes; the published version will show its effective date.

Contact

Privacy questions: hello@devkrity.com.