Privacy Policy

Who we are

Persee is an online service that lets businesses run AI assistants which talk to their clients in messaging channels, take bookings and keep contacts. The service is available at https://persee.ai. You can reach us at hello@persee.ai.

Our role

For your account data, Persee decides how and why the data is processed.

For the data of a business's clients — their messages, contacts, deals and bookings — Persee processes the data on behalf of that business and on its instructions. The business decides what it collects and is responsible for having a lawful basis and for informing its clients. If you are a client of a business that uses Persee, contact that business first; we will help it answer your request.

What data we process

• Account: your name, email address, password (stored only as a hash by our sign-in system), the organizations and workspaces you belong to and your role in them.
• Workspace content: assistant and automation settings, knowledge-base documents and files you upload, and your conversations with the Persee assistant.
• Conversations: messages, voice notes, photos and files exchanged with your clients in the channels you connect (the website chat, Instagram, Facebook Messenger, WhatsApp, Telegram), with the name or username the channel provides.
• Contacts, deals and bookings: names, phone numbers, email addresses, notes and history recorded by you or your assistant.
• Google Calendar data, when you connect it — see “Google user data” below.
• Billing: your plan and subscription status. Payment details are entered with the payment provider and never reach us.
• Technical data: IP address (for rate limiting and security, stored as a salted hash where possible), browser type, pages visited inside Persee, and error reports.
• Visitors of persee.ai: the messages you type into the chat on the home page.

How we use data

• To provide the service: run your assistant, generate replies, transcribe voice notes, search your knowledge base, sync bookings and integrations.
• To keep the service secure and prevent abuse.
• To answer support requests.
• To bill for paid plans.
• To improve Persee using aggregated product analytics.

We do not sell personal data, we do not use it for advertising, and we do not use your data or your clients' data to train AI models.

Who receives data

• OpenAI — generates assistant replies, builds the search index of your knowledge base, transcribes voice notes, and answers the chat on persee.ai. Anthropic — a backup provider for assistant replies. They receive the content needed for each reply; under their API terms they do not use it to train their models.
• Google — delivers invitation emails (Google Workspace) and, when you connect it, Google Calendar.
• Meta (Instagram, Facebook Messenger, WhatsApp) and Telegram — when your business connects these channels, messages travel through them.
• CRMs and other integrations you connect (for example amoCRM, MCP servers or your own connectors) — the data you choose to sync with them.
• Payment provider (Whop) — when you buy a paid plan.
• Everything else — the database, file storage, queues, error tracking and product analytics — runs on our own servers. We do not use third-party analytics or advertising trackers.

We may also disclose data when the law requires it, or to protect the rights and safety of Persee, our users or others.

Google user data

When you connect a Google account to a Persee booking calendar — yourself, or through a link a business sent you — Persee asks Google for the permissions below and uses them only for these purposes:

• See the list of your calendars — so you can choose which calendar receives bookings.
• View and edit events in the calendar you chose — to add bookings as events, update or remove them when a booking changes, and notice when you move or delete a booking event in Google.
• See free/busy information — so clients are not offered times when you are busy. Of your other events Persee reads only when they happen, never their titles, descriptions or guests.
• Your Google email address — to show which account is connected.

If a business connects a shared Google calendar, Persee writes every booking there and shows the business's team the titles of events added to that calendar by hand (private events appear only as “Busy”). These events are read when the team opens the calendar and are not stored.

Google access tokens are stored encrypted. For each booking event Persee keeps the event's ID and technical metadata so it can update the event later; it stores no copies of your other events.

Persee does not sell Google user data and does not use it for advertising. It does not transfer it to anyone except as needed to provide the booking features you use, to comply with the law, or with your consent. The AI assistant that books clients sees only the free time slots Persee has already calculated — neither your Google events nor your busy times are sent to AI providers.

Persee does not use Google user data to develop, improve or train generalized AI or machine-learning models.

Persee staff do not read your Google data unless you ask us to for support, it is needed for security, or the law requires it.

Persee's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements. The policy: https://developers.google.com/terms/api-services-user-data-policy

To disconnect, use “Disconnect” in the calendar's Google section in Persee or remove Persee at https://myaccount.google.com/permissions. On disconnect Persee removes upcoming booking events from your calendar and revokes its access when no other calendar uses that Google account.

How long we keep data

We keep data while your organization exists, unless you delete it sooner. Some data has shorter limits:

• Cabinet chats: as long as the cabinet's retention setting says (from 7 days; by default, until deleted).
• Cabinet guest access: removed after 181 days without activity.
• Cached voice-note transcripts: 30 minutes.

When an organization is deleted, its data is deleted from the live database at once. Backups made for recovery may still contain the data until they are deleted.

Security

Data travels over HTTPS. Access tokens and other secrets are stored encrypted. Every record belongs to an organization, and access is checked against it. Persee staff access customer data only to provide support or keep the service secure.

Your rights

You can ask us to access, correct, export or delete your personal data, or object to its processing: write to hello@persee.ai from the email address of your account. We answer within 30 days. Depending on where you live you may also have the right to complain to a data protection authority.

How to delete your data

• Organization: its owner deletes it in Organization settings → Danger zone. Everything in the organization is deleted and its messaging channels are disconnected.
• Your account: write to hello@persee.ai from the account's email address; we delete it within 30 days.
• A business's client: ask the business. You can also write to hello@persee.ai — we will pass your request to the business.
• Google Calendar: disconnect it as described in “Google user data”.

Cookies and local storage

Persee uses cookies to keep you signed in, to remember your language, and short-lived security cookies while you connect Google. Your browser's local storage keeps unsent product-analytics events and a session ID that changes every 30 minutes. We use no advertising cookies.

International transfers

Our servers and the providers listed above may be located in different countries, including the United States. We use providers that protect data with appropriate safeguards.

Children

Persee is not intended for anyone under 18, and we do not knowingly collect their data.

Changes

We may update this policy. The date at the top shows the current version; we tell users about important changes in the product or by email.

Contact

Persee — hello@persee.ai