Skip to content

Privacy & Security

Your Data. Your Work. Your Control.

PawOS is built with a privacy-first approach. Your private project data and conversations are not used to train PawOS-managed models. Information is processed to deliver the functionality you request, with access governed by your account and the permissions you authorize.

Our approach

Privacy in the way PawOS works

Clear boundaries for AI processing, project access, and connected accounts.

Your work is not model-training data

PawOS does not use your private project data or conversations to train PawOS-managed models. You can use PawOS's available AI capabilities without training your own model on private project data.

Your content is not for sale

PawOS does not sell customer project content or conversations. Your content may be processed when needed to provide a feature you request, as described below and in the Privacy Policy.

Processing follows the work you request

A request may involve processing your prompt, selected project context, or attachments to provide an AI response or carry out an authorized task. PawOS Web stores chat records and uploaded images in its services so the product can provide chat history and related features.

Account and workspace access controls

PawOS Web requires an authenticated account for private chat and attachment routes. Requests are checked against the signed-in account, and chat records are queried within that account's scope. Organization workspaces use membership and role controls for shared data.

You choose connected services

You decide which integrations to connect and approve the access a provider requests. PawOS applies product and tool permissions to supported actions. A provider grant can cover broader access than one task; disconnecting in PawOS removes its stored connection, and you may also need to revoke access with that provider.

Your private data is not payment

You do not need to surrender project files, conversations, or other private data to use PawOS, and PawOS does not accept that data as payment. Paid features are charged through the plan or usage terms shown in PawOS.

AI request handling

What happens when you ask PawOS for help?

AI features need to process the context required to answer or perform the task you ask for.

01

You make a request

You choose the task and, where applicable, the project, repository, files, or integration involved.

02

PawOS processes relevant context

PawOS Web sends AI requests to Google's Gemini API. The request may include your prompt and context needed for the requested response or task.

03

The result is handled by PawOS

Web chat records and uploaded images are stored by PawOS services for product functionality. Task execution uses the account and integration permissions involved in that task.

Provider data-use terms need production confirmation

Google's Gemini API terms differ between paid and unpaid service. Paid services state that prompts and responses are not used to improve Google products, while unpaid services may use submitted content and responses to improve products and machine-learning technologies. This repository confirms the Gemini API integration, but not the production project's billing status or account-level data settings. We therefore do not make a blanket claim here about Google's training use or retention for PawOS production traffic.

Gemini API Additional Terms·Gemini API data retention information

Storage & choices

Understand where your data lives

PawOS Web uses cloud services for account, chat, and attachment features. Storage and deletion are governed by the current Privacy Policy and service terms.

  • Chat and files. PawOS Web stores chat records and uploaded images with its services to provide chat history and related features. The current Privacy Policy describes account-data retention; no automatic deletion schedule is promised here.
  • Account deletion. PawOS provides an account deletion flow that requires confirmation. The flow removes account records and stored uploads, while billing records or records required by law may be retained. Payment processors and AI providers may have their own records and retention terms.
  • Connected accounts. You can disconnect supported integrations in PawOS. Depending on the provider, you may also need to remove PawOS's authorization in that provider's settings.

Security and privacy depend on the product feature, account configuration, and connected provider. This page describes current PawOS Web behavior and does not claim a certification, end-to-end encryption, or a guarantee against security incidents.