Last updated 2026-05-13

Privacy, in plain language.

This is a beta v1 statement. It explains what Palari stores, what leaves the server, what requires permission, and where the beta is still intentionally limited. A fuller policy will come with general availability.

Product data currently lives on Palari infrastructure in the EU.

Model calls leave the server and follow provider-side retention rules.

Use the beta for low-risk administrative work with clear review boundaries.

What Palari stores

Three kinds of product data live on Palari infrastructure.

Conversation history

Messages you send to your coworker and the replies it sends back, kept so the coworker has context across sessions.

Palari Memory

Short structured notes extracted from conversations, such as preferences, ongoing projects, and things you asked to keep in context.

Files created for you

Quick notes, meeting notes, project briefs, and drafts saved under the relevant Palari workspace.

Today, that data lives on a single Hetzner server in Germany. Encrypted backups go to a separate Hetzner Storage Box in the same region. Those product stores do not replicate outside the EU in the current beta setup.

What leaves the server

Model calls leave the Palari server.

When your coworker generates a reply, the server sends the needed prompt to a model provider, today Google Gemini, and receives text back. We send the minimum context needed for the conversation: your message, a small slice of relevant memories, and the persona instructions. Provider-side retention follows the provider's policy.

We do not run ad pixels, sell your data, or share product data for advertising or marketing analytics. The public marketing site may run Google Analytics when a measurement ID is set at build time; that only records page and button events on palari.io. Product conversations, memories, and files are never sent to marketing analytics.

Permissions and outside tools

A suggestion is not a connection.

Without permission, Palari will not:

  • Connect a new outside tool.
  • Subscribe to a new service.
  • Share documents, messages, memories, or company data with another app.
  • Send, change, share, expand access, or take an external action without review.

Approved connections should be reviewable.

Palari may suggest outside tools or specialist AI services for a domain. It will not connect a new tool, subscribe to a new service, or share your data with another app unless you approve that connection and data handoff.

Any approved integration should have a Task Card and Completion Card showing what data was shared, what tool was used, who approved it, and what actions were taken.

Memory and policies

Personal memory, Team Memory, and Team Policies have different scopes.

Palari Memory

Personal memories are scoped to the user and should not be treated as team-wide knowledge by default.

Team Memory

Shared memories are separately approved and visible only to authorized team members.

Team Policies

Policies define approved sources, review duties, and what a Palari can use for a specific kind of work.

Manager boundaries

Palari is designed around work review, not hidden people tracking.

Palari is meant to review work artifacts, task cards, notes, permissions, and shared outputs. It should not be used for employment decisions, unrelated private activity, or covert monitoring without clear policy, consent, agreements, and legal review.

Beta scope

Use the beta for low-risk administrative work.

Good beta uses include funding folders, meeting materials, procedure notes, staff notes, policy documents, internal drafts, and domain planning.

Do not connect protected health information, student records, legal determinations, hiring decisions, tax filings, or other regulated or high-stakes data unless the right agreements, controls, and legal review are in place.

Export and deletion

You can ask us to show, export, or delete your data.

Export product data we control

Your conversations, memories, and saved files, emailed as a single archive after we confirm the request.

Request deletion of product data we control

We handle requests for active product data within 7 days. Backup snapshots age out under the retention schedule, so full deletion propagation takes time.

See what we have

If you want a look at what is actually stored about you, email and we will show you.

Backup retention is currently 14 daily, 8 weekly, and 12 monthly snapshots. We will tell you the specific deletion timeline if you ask.

Security status and limitations

This is still a small invite-only beta.

  • We are not yet certified or audited against a specific compliance framework.
  • If you need GDPR-compliant DPAs or SOC 2 reports, please wait for general availability.
  • We do not have 24/7 on-call support.
  • Your coworker may occasionally surface something from an earlier conversation that you would rather it forgot. The retrieval cutoffs we ship today reduce this; they do not eliminate it.

Contact and changes

Privacy questions, export requests, deletion requests, or anything else: hello@palari.io. This reaches the founder directly.

We will update this page when anything material changes. The full general-availability policy will be a separate document; we will point to it here when it lands.

Palari is not a substitute for human support. If you are in crisis, reach out to a real person or service. In the US, dial or text 988.

Continue exploring Palari

Keep the privacy boundary connected to the work.

Privacy is one part of the trust model. The next pages show how reviewable memory, work trails, and pilot boundaries keep the limits visible during day-to-day work.
Next

Back to trust controls

Review permissions, sources, and work trails before moving work forward.
Continue

Review memory boundaries

Explore how personal memory, Team Memory, and Team Policies are separated.
Continue

Read the pilot FAQ

Find setup, beta, and privacy clarifications before you scale use.
Continue