Privacy Policy

About this notice

“Pania,” “we,” and “us” refer to Pania, which operates the public website and assistant application. This notice covers website visits, inquiries, assistant conversations, uploaded files, and connected Google accounts. Contact hello@pania.ai with privacy questions. Company deployments may also be governed by the customer’s agreement and workplace policies.

Information we process

• Website and account information. Hosting services process technical requests such as IP addresses, URLs, browser information, and request times. The application processes account identifiers and sign-in information to authenticate you and control access. Contact emails include the information you choose to send.
• Conversations and files. Pania processes messages, attachments, assistant responses, tool results, and task history to carry out your requests and let you resume your work. Your assistant may retain useful preferences and context in its memory.
• Google connections. When you connect an account, Pania stores its identifier, address, label, authorization tokens, and granted permissions. Google handles Google sign-in; connecting through OAuth does not give Pania your Google password.

Google data and assistant features

With your authorization, Pania accesses the connected account to perform the features you request, including tasks you schedule. The permissions displayed by Google determine the available access. Visiting the public website does not connect your Google account.

• Gmail: find, read, summarize, and organize email; prepare messages and replies; and send approved email. Relevant content can include addresses, subjects, bodies, labels, and attachments. Sending to non-owner recipients requires your Send click in Pania’s email review form.
• Calendar: read upcoming events, prepare meeting context, and create or cancel events. Event details can include times, descriptions, locations, organizers, and attendees.
• Drive, Docs, and Sheets: find and read files, work with documents and spreadsheet cells, create or upload content, and carry out requested sharing or file-management actions.
• Contacts: look up names and contact details to help identify the people involved in your requests.

Relevant Google content and derived summaries may appear in your conversation history, task files, and assistant memory. Sharing a file, inviting an attendee, or sending a message makes selected information available to the recipients of that action.

AI processing and Google Limited Use

Pania uses OpenAI to generate assistant responses and organize useful context. Relevant messages, Google content, attachments, and summaries may be sent to OpenAI to carry out these features. This is remote AI processing, not a wholly offline assistant. Pania also uses a locally hosted text-embedding model to support memory search; that local step does not send its input to the embedding model’s publisher.

Pania also uses TypeSafe’s Jev model through OpenRouter to interpret WhatsApp requests and select routing actions and reactions. This processing can include your message, quoted text, and recent conversation context, including Google content or summaries already present in that context. OpenRouter forwards these requests to TypeSafe. Prompt and response logging, external trace broadcasting, and OpenRouter’s optional input/output data-use discount are disabled for this integration. These settings are not a promise of zero retention by every provider.

Pania’s use and transfer of information received from Google APIs, including raw data and information derived from it, will adhere to the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including their Limited Use requirements.

Google user data must only be used for authorized, user-facing features. Pania does not sell it, use it for advertising or credit decisions, or use it to train or improve foundational or generalized AI models. This restriction also applies to aggregated, anonymized, and derived Google data. AI providers processing Google data for Pania must be configured and engaged on terms that prohibit such training. Personal assistant memory helps that user; it is not permission to train a general-purpose model.

Human access to Google data is limited to your documented authorization, necessary security investigations, legal requirements, or other uses expressly permitted by Google’s Limited Use policy.

How sensitive information is protected

Pania uses HTTPS for its public application and Google API communications to protect data in transit. Authenticated access and ownership checks restrict access to private conversations, connections, and files. Managed personal assistants use separate operating-system accounts and private file permissions. Administrative operations use restricted services and scoped access rather than exposing organization credentials to assistants.

Saved email draft content and draft attachments are encrypted in the application’s draft store. Signed approval and duplicate-send checks protect the email review flow. These protections do not mean that every stored conversation, file, or backup is encrypted, or that information is retained for zero days. No system can guarantee absolute security.

Service providers and other disclosures

Vercel hosts the public website. Pania’s application hosting processes the application’s stored data and technical requests. Google provides connected Workspace services. OpenAI, OpenRouter, and TypeSafe provide the AI processing described above. Email and messaging providers process content when you use those channels. Additional services you connect or ask the assistant to use receive information for those requested actions.

Transfers of Google data are limited to the user-facing features you authorize and other circumstances allowed by Google’s Limited Use requirements, such as security or legal obligations. A transfer in connection with a sale or merger requires the prior consent required by that policy. Providers may process information outside your country; applicable protections depend on the service and agreement.

Cookies and device access

The public website does not include advertising pixels. The assistant application uses authentication cookies and browser storage for sign-in and application functionality. Infrastructure providers may use their own security mechanisms. Visiting the public website does not grant access to your email, calendar, microphone, screen, or company systems.

Retention, disconnection, and deletion

Conversations, task files, and assistant memory persist to support history and ongoing work. Disconnecting a Google account stops future access through that connection; it does not automatically erase content already saved in conversations, files, memory, or backups. Pania does not promise immediate deletion of every copy when an account is disconnected.

You can manage Google connections in Pania’s Connections settings and revoke Pania’s access in your Google Account. Use available conversation and file controls to manage saved content. For an account-wide request covering history, files, assistant memory, or retained copies, contact hello@pania.ai. We will verify the request and explain its scope and any retention required for security or legal obligations.

Your privacy requests

Depending on applicable law, you may have rights to access, correct, delete, export, or restrict processing of your information, to object to processing, or to withdraw consent. Contact hello@pania.ai to make a request. For a company-managed deployment, your organization may also need to handle the request. You may have a right to contact your local data protection authority.

We will update this notice when relevant practices change. The date above identifies this version. See the Terms of Service for public website terms; customer agreements govern company deployments.