Privacy Policy

Perrie is a personal AI assistant that answers phone calls, manages tasks, and connects to services like Google Calendar on behalf of its owner. This policy explains what data Perrie collects, why, and how it is used — both for the owner who sets Perrie up, and for people who call or are called by Perrie.

Who this applies to

This policy covers three kinds of people:

• Owners — people who sign in to the Perrie dashboard and configure their own assistant.
• Callers and counterparts — people who call an owner's Perrie number, or whom Perrie calls on an owner's behalf. These people have not created an account and may not know Perrie in advance.
• Delegates — people an owner has explicitly allowed to use Perrie on their behalf.

AI call disclosure

Perrie identifies itself as an automated AI assistant at the start of a call, and discloses that calls may be recorded and transcribed. We do this because it is the right thing to do, and because call-recording consent laws vary by jurisdiction — see the Terms of Service for the owner's own responsibility to comply with the laws that apply to their calls.

What we collect

• Account and profile data — name, contact details, timezone, and assistant preferences the owner provides when setting up Perrie.
• Call data — phone numbers, call metadata (time, duration, direction), and a transcript of what was said during the call, including by non-owner callers.
• Task and integration data — tasks Perrie is asked to carry out, and data read from or written to connected services (for example, Google Calendar events or Google Contacts entries) needed to carry those tasks out.
• Guardrail and quality logs — records of things like confirmation prompts before an action, blocked attempts to leak private details to a non-owner, or flagged attempts to manipulate the assistant. These exist to keep Perrie safe and reliable, not to build a profile of callers.

How we use it

• To operate the call itself: understanding speech, generating a spoken response, and carrying out the task requested.
• To show the owner their own calls, tasks, and transcripts in the dashboard.
• To protect non-owners: Perrie actively filters private details about the owner out of anything said to a caller who isn't the owner, and logs (rather than silently ignores) attempts to get around that.
• To improve reliability — for example, understanding why a call failed so we can fix it.

We do not sell personal data, and we do not use call transcripts to train third-party advertising products.

Who we share it with

Perrie's backend calls on a small number of service providers to work. Data flows to them only as needed to do the job the owner configured:

• Telephony (e.g. Twilio) — to place and receive calls.
• Speech services (e.g. Deepgram) — to transcribe speech to text and synthesize speech from text, in real time during a call.
• Language model provider (e.g. Anthropic) — to generate the assistant's responses from the conversation.
• Calendar and contacts (e.g. Google, via OAuth the owner explicitly grants) — only for the specific scopes the owner connects, and only used for the tasks the owner asks Perrie to perform.
• Storage (e.g. Supabase, or local storage on the owner's own server if no database is configured) — to persist profile, call, and task records.

Each of these providers processes data under its own privacy terms as our data processor; we don't hand data to anyone outside this list without telling the owner, except where required by law.

How long we keep it

Call transcripts, task records, and guardrail logs are kept for as long as the owner's account is active, so the owner can review their own call and task history. An owner can delete their account and associated data, or ask us to, at any time by contacting us below.

Your choices

• Owners can review, edit, or delete their profile, facts, connected integrations, and call/task history from the dashboard, or disconnect any integration at any time.
• Callers and counterparts who want a copy of, or to have deleted, data from a specific call can contact the owner directly, or reach us at the email below and we'll pass the request along.

Children's privacy

Perrie is not directed at children under 13, and we do not knowingly collect personal data from them.

Security

We apply reasonable technical and organizational safeguards (access controls, encrypted transport, and the guardrails described above) to protect data in transit and at rest. No system is perfectly secure, and we can't guarantee absolute security.

Changes to this policy

If we materially change how we collect or use data, we'll update this page and change the “Last updated” date above.

Contact us

Questions about this policy, or requests regarding your data, can be sent to privacy@replace-with-your-production-domain.example.

[Your Company / Legal Name] operates Perrie. Replace the placeholders in this document (entity name, contact email, jurisdiction) with your real details before publishing.