Privacy Policy

This policy explains what Trellaris (the “Service”) collects about you, why, where it goes and how long it stays. It covers the web application at trellaris.app, the API at api.trellaris.app, the documentation site and the agents, automations and channels that run through them.

Trellaris is a platform for organisations. When you use it inside an organisation, that organisation decides what data enters the Service, which members can see what, which AI providers and connectors are used, and how long records are kept. In privacy terms your organisation is the controller of the content it puts in; we process it on its behalf. For the account data we need to run the Service at all, and for the shared demo organisation, we are the controller.

Account data. When you sign in with Google, GitHub or your company’s single sign-on we receive your email address, display name and, where the provider supplies one, an avatar image. We never receive or store your password.

Organisation data. Your organisation, teams, workspaces, role, and the settings your administrators choose.

Content you bring. Messages you send to agents, documents you upload, knowledge collections, memories an agent stores for you, canvas documents, agent and skill definitions, policies, and the answers, charts, forms and files agents produce.

Run records. Every agent run keeps a record: which agent ran, when, for how long, which tools and models it called, what it cost, and a trace of each step. Traces store the text that crossed each step after data-loss-prevention redaction, truncated at four kilobytes per step. An organisation administrator can switch step payloads off, which keeps the timings and outcomes and drops the text.

Audit log. An append-only record of governance actions: who published, promoted, approved, connected, paused or killed what, and when. The audit writer refuses content by construction; it records identifiers, kinds and rings, never what a person said.

Connector credentials. When you connect Google Calendar, Google Drive, Gmail, ServiceNow or another service, the access token that service issues for you is stored encrypted with an envelope key and used only when an agent acts for you through that connector.

Technical data. Server logs with request paths, timings, status codes and the IP address of the request, kept for operations and security. We do not use advertising trackers or third-party analytics on the Service.

• to run the Service: sign you in, show you your organisation, run the agents you ask for, deliver their answers;
• to enforce your organisation's controls: visibility by ring and workspace, allow-lists, budgets, approvals, data-loss prevention, autonomy floors and kill switches;
• to give you and your administrators the record the platform promises: traces, cost, audit and analytics;
• to keep the Service secure and available, including rate limiting, abuse detection and incident response;
• to tell you about changes to the Service or these terms.

We do not sell your data, and we do not use your content to train AI models, ours or anyone else’s.

When an agent answers, the text of the conversation, the tool results it gathered and the relevant parts of your knowledge collections are sent to the AI model provider your organisation has configured. Data-loss-prevention rules run on that text before it leaves and on the answer before it is shown to you. Providers we support are Anthropic, Google (Gemini), OpenAI and Azure OpenAI; an organisation may bring its own provider key, in which case that provider’s terms with the organisation apply.

We use these providers under agreements that do not permit them to train on the data we send. Embeddings computed for search are derived values stored with your organisation’s data and are deleted with it.

A connector acts as you. An agent that reads your calendar or files a ticket does so with the credential you granted, and only within a run you started or a colleague started on a surface you can see. Connector writes ask a person to approve them before they execute unless your organisation has raised the agent’s autonomy.

Where you connect a Google service, Trellaris’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google data is used only to provide the feature you connected it for, is never used for advertising, and is never transferred to others except as needed to provide that feature, to comply with law, or with your consent.

You can disconnect any service from Settings. The stored credential is revoked immediately and the next attempt to use it fails.

Visibility follows the three rings. What you build and say in your personal ring is yours; a named workspace is visible to its members; the team and organisation rings are visible to the people in them. Runs and conversations belong to a workspace, so a colleague in a shared workspace can see runs started there.

Organisation administrators see metadata by default: which agent ran, when, at what cost, with what outcome. They do not see the text of your conversations. That changes only under a legal hold, which needs two administrators to activate and applies to the people named in it, or if the organisation raises its privacy tier to full access, in which case every member is notified and a banner is shown to them while it is in force.

Your avatar agent answers questions from colleagues using only the profile, knowledge and memory you chose to give it, with private fields stripped for anyone who is not you.

By default the Service keeps conversations, run records, artifacts and the audit log until your organisation sets a retention period. Once a period is set, a daily sweep removes records older than it, except records pinned by an active legal hold. Live event streams used to render a running turn expire after one hour on their own.

When you leave an organisation or are deprovisioned, your connector credentials are revoked, your automations are disabled, your running agents are cancelled and your memberships are removed on the same cascade. When an organisation is closed, its data is deleted within 30 days, and from backups within 90.

The shared demo organisation may be reset at any time; treat anything you put there as public and temporary.

The hosted Service runs on Microsoft Azure. Durable data lives in a managed PostgreSQL database and a storage account, secrets in a key vault, and short-lived queues and event streams in a managed Redis cache, all in one Azure region chosen at deployment (the hosted demo runs in India). Data is encrypted in transit and at rest.

AI model providers and the connectors you use process data in their own regions under their own terms. An organisation that needs data to stay in one place can run Trellaris in its own cloud with the published deployment; see the deployment guide.

The Service sets one session cookie to keep you signed in, plus the short-lived cookies the sign-in flow needs to complete safely. It uses your browser’s local storage for preferences such as the theme, the collapsed state of panels and drafts you have not sent. None of these are used for tracking, and there are no third-party cookies.

If you use dictation or read-aloud in chat, your browser’s own speech engine handles the audio. In Chromium-based browsers that means the microphone audio goes to the browser vendor’s servers, not to Trellaris. An organisation administrator can switch voice features off for everyone.

We share data only:

• with the AI providers and connectors your organisation configured, as described above;
• with the infrastructure providers that host the Service (Microsoft Azure) and deliver email notifications, under data-processing terms;
• with your organisation's administrators, within the privacy tier and legal-hold rules above;
• when the law requires it, in which case we tell your organisation unless we are prohibited from doing so;
• as part of a merger, acquisition or sale of the Service, with notice to you.

You can see and edit your profile and preferences in Settings, export your memories, delete your own memories and conversations, and disconnect any service you connected. Your organisation’s administrator can export the audit log and, on request, your organisation’s data.

Depending on where you live you may also have rights to access, correct, delete, restrict or port your personal data, to object to certain processing, and to complain to a supervisory authority. Requests about data your organisation controls go to that organisation; we will help it respond. Everything else, and any request about the demo organisation, can be sent to us at the address below. We respond within 30 days.

Every request is scoped to one organisation at the database layer; visibility is enforced in the query, not in the page. Secrets are envelope-encrypted, connector tokens never leave the server, agent code runs in an isolated sandbox with no network, and every governance action is audited. We test with an independent security review before major releases and welcome reports at the address below.

No system is perfectly secure. If we learn of a breach affecting your data we will notify your organisation without undue delay and within any period the law sets.

The Service is for organisations and their adult members. It is not directed at anyone under 18 and we do not knowingly collect data from them. If you believe a child has an account, write to us and we will remove it.

We will update this policy as the Service changes. For material changes we give notice in the application or by email at least 14 days before they take effect. The effective date at the top of this page is the current version, and earlier versions are available on request.

Privacy questions and requests go to privacy@trellaris.app. The Terms of Service describe the rest of the relationship.