Privacy

It is written as product privacy information. Final legal wording should be reviewed before public launch and matched to the deployed environment.

Workspace data is used to authenticate users, check organisation access, retrieve approved source context, generate policy-facing drafts, inspect agent behaviour, and support product operations.

Documents, page images, attachments, organisations, workspaces, sessions, runs, traces, spans, files, and membership records are stored in the Supabase project configured for the deployment.

Protected routes verify Supabase access tokens. Server routes use service-role access only for trusted backend work such as membership checks, storage cleanup, document processing, trace writes, and admin operations.

The chat agent currently uses Anthropic as the main model provider. OpenAI is required for the Agents SDK setup, tracing support, embeddings, optional OpenAI model calls, and optional OpenAI tools such as web search, code interpreter, and image generation.

The document ingestion service can use OpenAI, Anthropic, or Google Gemini models depending on model configuration. It sends document page images and extracted document text for page extraction, document analysis, and embeddings.

The service converts pages to images, extracts markdown, analyses the full document into metadata, creates embeddings, and writes document, page, render, file, and attachment records back to the Parlia schema.

Chat attachments are stored against the active thread and item. PDF attachments are rendered into page images before being attached to the conversation.

Those tools may send search queries, target URLs, task instructions, retrieved page content, browser actions, and tool outputs to the relevant provider. Browserbase sessions can include session recording and debug links when that tool is used.

External websites may receive normal request information such as the requested URL, browser metadata, and network details when browser or fetch tools visit them.

Redis or Upstash Redis can store tool request and result snapshots for debugging and audit-style inspection. Application logs also record counts, text lengths, status changes, and error messages.

Model input logging can be reduced with OpenAI agent logging environment settings, including controls for model data and tool data.

Organisation-scoped records are checked through membership functions and row-level security policies in the Parlia Supabase schema.

Users should only upload material they are authorised to process inside the selected organisation workspace.

Deleting a document removes the document record, linked page records, file rows, organisation links, and related Supabase Storage objects. A service-role-only deletion audit row is retained.

Some operational records, logs, traces, or provider-side records may remain until the relevant retention process or provider configuration removes them.

Provider handling is controlled by the configured provider accounts, model settings, logging settings, and data processing terms used in the deployment.