Privacy Policy
Last updated: November 19, 2026
Promptli Inc ("Promptli", "we", "us") makes software for businesses and developers. This policy describes the personal information we collect, how we use and share it, how long we keep it, and the choices you have. It covers these products:
- The Promptli receptionist: an AI voice receptionist and booking platform used by service businesses ("Businesses") to talk with their customers ("End Users").
- Promptli Desk and Promptli ID: an AI front desk workspace and the single sign-in used for it.
- Promptli Comms: email addresses, phone numbers, calls and SMS for AI agents, through the console at comms.promptli.com, the API at api.comms.promptli.com, the hosted MCP server at api.comms.promptli.com/mcp, the Promptli voice assistant, and our plugins for AI tools such as Claude Code, Codex, Hermes, Grok and Rakazo.
Promptli Inc is the data controller for the personal information described in this policy, except where section 3 says we act for a Customer.
1. Promptli receptionist
Information we collect
When a Business signs up, we collect account information: name, email, team and workspace settings, billing information processed by Stripe, and operational data required to run scheduling, voice calls and team collaboration.
When an End User calls or books with a Business that uses Promptli, we collect and store the phone number they call from or provide, their name (as given to the AI agent or entered on the Business's booking page), their appointment details, and a recording and transcript of the call for quality assurance and follow-up purposes.
How we use data
We use personal information to operate the service, deliver product functionality, improve reliability and provide support. Specifically, End User phone numbers are used to send appointment-related SMS messages (confirmations, reminders, follow-ups and change notices) and to identify returning callers so the AI agent can personalize the conversation.
We do not sell End User data. We do not share End User phone numbers with third parties for their own marketing or promotional use. Phone numbers collected for SMS purposes are used only to communicate with that End User about their interaction with the Business that collected them.
SMS and text messaging
Promptli sends SMS messages on behalf of Businesses for appointment confirmations, reminders, post-call follow-ups and booking changes. End Users opt in to receive these messages either (a) verbally, by providing their phone number to the Business's AI voice agent during a call, or (b) through a web booking form where they check a box agreeing to receive text messages about their appointment.
Message frequency is limited to 1–5 messages per End User per booking cycle. Message and data rates may apply. End Users can reply STOP at any time to opt out of future messages, or HELP for assistance. SMS opt-in data is never shared with third parties for marketing, and opt-in consent for SMS is not transferred or sold under any circumstance.
Receptionist retention
Receptionist call recordings and transcripts are retained for the duration of the workspace's active subscription plus a 30-day grace period, after which they are deleted on a rolling basis unless a Business has requested earlier deletion.
2. Promptli Desk and Promptli ID
A Promptli Desk is a Business's AI front desk workspace. Each Desk runs on a server chosen by its Business, such as a computer at the Business or a server Promptli operates for it. Messages, photos, files and voice messages you send in the Promptli Desk app, and the conversations the Desk handles, are stored on that Desk. The app sends data only to the Desk you sign in to and, if you choose "Continue with Promptli", to Promptli ID.
Promptli ID is our single sign-in for Desks. It stores your name, email address and profile picture from the sign-in method you choose (Google, Apple or an email code), the Desks you belong to and your role on each. A Desk you sign in to receives your name, email address and an identifier that is unique to that Desk. Desk owners can invite people by email; an invite is linked to whoever opens it and signs in.
Desks reached at addresses ending in -desk.promptli.com, and Promptli ID at id.promptli.com, are connected through Cloudflare's network. Cloudflare decrypts this traffic at its edge to route it to the right server and to protect it from attacks.
The app also sends the screens you open to your Desk so its owner can see how the app is used, and stores a push token on the Desk so it can send you notifications through Expo and Apple's or Google's push services. The app contains no advertising and does not track you across other companies' apps or websites.
3. Promptli Comms
Promptli Comms gives AI agents their own email address, phone number and SMS. A customer (a developer or business with a Comms account, the "Customer") creates one or more agent identities. Each identity can have a mailbox (for example name@agents.promptli.com or an address on the Customer's own domain), a phone number, and settings that decide how calls are answered: by the Customer's own AI agent (connected through Agent Link, the API, the MCP server or one of our plugins), by the Promptli voice assistant, by forwarding, or by voicemail.
Our role. For the Customer's account, login, billing and usage data, Promptli Inc decides how the data is used (we are the "controller"). For the content of the agent's communications (emails, texts, calls, recordings, transcripts and contacts) we act on the Customer's instructions (we are a "processor" or "service provider"), and the Customer is responsible for having a lawful basis and giving any notices required to the people its agent communicates with.
Test mode. Every Comms account has a separate test environment. API keys and OAuth tokens that
start with psk_test_ work only in test mode. Test-mode email, SMS and calls are simulated: they go to
sandbox mailboxes and fake numbers, do not reach real carriers or recipients, and do not call our real speech or
AI providers. Test-mode data is stored separately from live data.
4. Comms: information we collect
- Account data: your name, email address and profile picture from Google sign-in, or your email address if you sign in with an emailed code; your organization's name; team members, their roles and pending invites.
- Billing data: your plan, subscription status, billing period, spend cap and invoices. Payments are handled by Stripe; we store a Stripe customer and subscription reference, not your full card number.
- Agent configuration: identity handles, display names and descriptions, avatars, mailbox addresses and signatures, custom mail domains, call settings, voice and language choices, and the persona, instructions and policies you give the Promptli voice assistant.
- Phone numbers: the numbers we provision for you, and, for US SMS, the business and campaign details you submit for carrier (10DLC) registration.
- Email content: messages your agents send and receive, including sender and recipient addresses, subject, text and HTML bodies, attachments, headers needed for threading, delivery status (delivered, bounced, complaint) and drafts. The raw form of each incoming email is also stored.
- SMS and MMS content: message bodies, media, the phone numbers involved, delivery status, and an opt-in and opt-out record for each number (updated automatically by STOP and START keywords).
- Call data: the numbers involved, direction, timestamps, duration, outcome, answering-machine detection result, and the reason, context and opening line your agent gives for a call. Call audio is streamed in real time to the speech and AI providers described in section 5. When you turn recording on, we also keep a recording (see section 5).
- Transcripts, summaries and notes: a transcript of each call handled through Promptli's voice pipeline and of voicemails; a call timeline (for example guidance sent by a supervisor, transfers and tool use); post-call summaries and action items; and a short running summary of each contact that an AI model writes from recent activity so agents have context.
- Contacts: names, companies, titles, notes, email addresses and phone numbers that you or your agent save, contacts we suggest from your agent's conversations, and allow and block rules.
- Scheduled actions and webhooks: calls and texts scheduled for later, the webhook URLs you register, and a log of webhook deliveries (status code, latency and a short snippet of the response).
- Usage data: call seconds per tier, messages sent, and other counts used for billing, plan limits and spend caps.
- Credentials: API keys (stored only as salted hashes; we cannot show a key again after it is created), OAuth clients, grants and tokens for connected apps, and the time and IP address a key was last used.
- Logs and diagnostics: server logs (request paths, status codes, timing, IP addresses and request IDs), an audit log of administrative actions in your organization, and error reports.
- Console analytics: page views in the console, linked to an internal user ID (see section 14).
5. Comms: calls, recordings, transcripts and AI disclosure
How call audio is processed
- Calls answered by the Customer's own agent: we transcribe the caller's speech in real time with Deepgram, send the text to the Customer's agent, and turn the agent's replies into speech with Cartesia.
- Calls answered by the Promptli voice assistant ("Hosted"): the same speech pipeline, with the conversation handled by an OpenAI language model, guided by the Customer's instructions and, optionally, steered live by the Customer's agent.
- Realtime calls: call audio is streamed to OpenAI's Realtime API, which listens and speaks directly.
- Forwarded calls are connected through Twilio to the number the Customer chooses.
- Members of the Customer's organization can listen in to a live call in the console and take it over by voice.
Recordings
Call recording is off by default. A Customer can turn it on for an agent identity. When it is on, Promptli's voice engines play the announcement "This call may be recorded." before recording starts, and Twilio records the call in two channels (one per party). Recordings are stored by Twilio and are available to the Customer through the API.
Transcripts
Transcripts are stored with the call in the Customer's account whether or not recording is on, because the voice pipeline works from text. They are used to show the conversation in the console, to give the Customer's agent context, and to write post-call summaries.
Telling people they are talking to an AI
Comms agents are AI systems. Our Terms require Customers to tell the people their agents call or text that they are dealing with an AI where the law requires it, and to obtain any consent the law requires before recording a call or placing an automated or AI-voice call. People who receive a call from a Comms agent can ask the agent whether it is an AI, and can contact us at the address below.
6. Comms: data from AI clients (MCP and OAuth)
Customers can connect AI clients such as Claude, ChatGPT, Claude Code, Codex, Grok, Hermes or Rakazo to Promptli Comms through our hosted MCP server (api.comms.promptli.com/mcp) or our plugins. Connecting uses OAuth: you sign in to Promptli, choose an agent identity and live or test mode, and approve the connection.
What we receive from the AI client:
- the client's registration details (the name it gives itself and its redirect URL);
- the OAuth tokens that authorize each request (access tokens expire after one hour; refresh tokens are replaced every time they are used);
- the arguments of each tool the AI client calls, for example the recipient, subject and body of an email to send, or the number and reason for a call;
- standard request metadata such as IP address and time.
What we do not receive: the connector does not read your chat history, the AI client's memory, or your files. It only sees what the AI client sends in a tool call.
What we send back: tool results, such as messages, call details and transcripts from the connected agent identity. Once returned, that data is processed by the AI client's provider under its own terms and privacy policy.
No model training. Promptli does not use data received from AI clients, or the content of your agents' communications, to train AI models. We use the AI providers listed in section 9 through their business APIs to run the service. Each provider handles the data under its own terms. Every request we send to our speech-to-text provider, Deepgram, opts out of its Model Improvement Program, so Deepgram does not use your call audio to train its models.
You can disconnect an AI client at any time in the console under API keys → Connected apps. Revoking a connection stops its tokens from working.
7. Comms: people who contact or are contacted by an agent
If you email, text or call a Promptli Comms agent, or an agent contacts you, we process your communication on behalf of the Customer that operates the agent. This includes your email address or phone number, your name if you give it, the content of your messages, the audio and transcript of the call, a recording if the Customer has turned recording on, and notes or summaries the agent keeps about your conversations. The Customer decides how its agent uses this information, and the Customer's AI agent (which may run on another company's AI service) may receive it.
- Opting out of texts: reply STOP to any text from a Comms agent. We block further texts from that Customer's numbers to you until you reply START. Reply HELP for help.
- Calls and email: ask the agent or the Customer to stop contacting you. Customers can block addresses and numbers for their agents.
- Your data: to access or delete information about you, contact the Customer that operates the agent. If you cannot identify or reach them, email us at info@promptli.com with the agent's email address or phone number and we will pass your request on or help directly.
We do not sell this information, and we do not use it for our own marketing.
8. Why we use information, and legal bases
We use personal information to:
- provide the service: send and receive email, texts and calls, run the voice assistant, transcribe and summarize calls, store your agents' history and deliver webhooks (legal basis: performance of our contract with you; for third parties' data, the Customer's instructions);
- bill you and enforce plan limits: measure usage, charge through Stripe, apply spend caps (contract; legal obligation for tax and accounting records);
- keep the service secure and lawful: authenticate requests, rate-limit, prevent spam and abuse, honor opt-outs and blocks, meet carrier rules such as 10DLC, and investigate misuse (legitimate interests; legal obligation);
- operate and improve reliability: logs, error reports and console analytics (legitimate interests);
- communicate with you: sign-in codes, service notices such as an agent going offline, and support (contract; legitimate interests);
- record calls only when a Customer turns recording on (the Customer is responsible for consent where the law requires it).
We do not sell personal information and we do not use it for targeted advertising.
9. Service providers and subprocessors
Receptionist, Desk and ID: Twilio (telephony and SMS), LiveKit (real-time audio), Convex (database), Amazon Web Services (hosting), Cloudflare (network and Desk connections), Resend (email), Expo (app push notifications), Stripe (billing), and providers for speech-to-text, text-to-speech and large language model inference.
Promptli Comms uses these providers:
| Provider | What it does for Comms | Data involved |
|---|---|---|
| Amazon Web Services (ECS, SES, S3, SQS, Secrets Manager, CloudWatch), US East | Runs the API, voice and worker services; sends and receives agent email; stores raw incoming email; queues; logs | All Comms service data in transit; email content; logs |
| Convex | Primary database and file storage | Account, agent, message, call, transcript, contact and usage data |
| Twilio | Phone numbers, calls, SMS/MMS, call recording, 10DLC registration | Phone numbers, call audio, recordings, text content |
| OpenAI | Language model for the voice assistant; Realtime voice calls; call and contact summaries | Call audio (Realtime), transcripts, instructions, message excerpts for summaries |
| Deepgram | Speech-to-text on calls and voicemail | Call audio |
| Cartesia | Text-to-speech on calls | Text the agent speaks |
| Stripe | Payments, subscriptions, invoices, metered usage | Billing contact, payment details, usage totals |
| Resend | Sign-in codes and platform notices | Your email address and the notice |
| "Sign in with Google" | Name, email address, profile picture | |
| Vercel | Hosts the console at comms.promptli.com | Console requests |
| Cloudflare | DNS for promptli.com domains | DNS lookups |
| Sentry | Error reporting (personal data scrubbed before sending) | Error details, internal user ID |
| PostHog (US) | Console usage analytics | Page views, internal user ID |
We also share data when a Customer directs it, for example with the Customer's own AI agent, the webhook URLs the Customer registers, people its agent emails, texts or calls, and the AI clients it connects. We may disclose information if required by law, to protect people or our service, or as part of a merger or acquisition, in which case this policy will continue to apply.
10. Where data is processed, and international transfers
Promptli Comms runs in the United States: our services and email storage are in AWS's US East (N. Virginia) region, and our providers process data mainly in the United States. If you use Comms from outside the United States, or communicate with a Comms agent from outside it, your information is transferred to and processed in the United States. Where the law requires a transfer mechanism (for example for data from the EEA, the UK or Switzerland), we rely on the European Commission's Standard Contractual Clauses or another lawful mechanism.
11. Retention
| Data | How long we keep it |
|---|---|
| Emails, texts, call records, transcripts and summaries | 6 months, then deleted |
| Contacts, contact notes and contact summaries, and agent settings | Until the Customer deletes them or asks us to |
| Raw form of incoming email (stored in S3) | 90 days, then deleted automatically |
| Call recordings (stored by Twilio) | 6 months, then deleted |
| Mail, texts and calls of a deleted agent identity | 6 months from when each was created, like any other (deleting an identity frees its handle and revokes its keys) |
| Webhook delivery log | 7 days |
| Idempotency keys (used to avoid duplicate sends) | 24 hours |
| Server logs | 30 days |
| OAuth access tokens | 1 hour; refresh tokens until the connection is revoked |
| API keys | Until revoked or expired (only a hash is stored) |
| Billing and tax records | As long as the law requires |
A Customer can ask us to delete any of this sooner, as described in section 12. Closing an account does not delete its Comms data automatically; to have it deleted, email info@promptli.com.
12. Deletion, export and your rights
Export. Comms Customers can read their agents' messages, texts, calls, transcripts and contacts in the console, and download all of these, plus call recordings, through the API at any time. For a complete export of your account, email info@promptli.com.
Deletion. Customers can delete contacts, drafts, webhooks, phone numbers, custom domains and agent identities themselves. To delete stored messages, calls, recordings or transcripts, or your whole account, email info@promptli.com from the account owner's address. We will confirm and complete the request within 30 days, except for data we must keep by law (for example billing records).
Your rights. Depending on where you live, you may have rights to access, correct, delete, export or restrict the processing of your personal information, to object to processing based on legitimate interests, and to withdraw consent. To exercise them, email info@promptli.com; we will respond within 30 days. If we process your data on behalf of a Customer, we will refer your request to that Customer or help them answer it. You can also complain to your local data protection authority.
13. Security
We apply technical and organizational safeguards including access controls, encryption in transit (HTTPS/TLS for the console, API and MCP server), and audit logging. For Comms specifically: API keys and OAuth secrets are stored only as hashes; OAuth uses PKCE and rotates refresh tokens; service secrets are kept in AWS Secrets Manager; webhooks are signed so Customers can verify them; each API key can be limited to one agent identity and specific scopes; and requests are rate-limited. Error reports are scrubbed of personal data before they are sent to Sentry. No method of transmission or storage is completely secure, so we cannot guarantee absolute security. If you find a vulnerability, please email info@promptli.com.
14. Analytics and cookies
The Comms console uses cookies and local storage to keep you signed in. It uses PostHog to count page views, linked to an internal user ID (never your name or email), with session recording and automatic click capture turned off, and it honors your browser's Do Not Track setting. We do not use advertising cookies.
15. Children
Promptli Comms accounts are for businesses and developers and are not intended for anyone under 18. Our services are not directed to children, and we do not knowingly collect personal information from children under 13. If you believe a child has given us personal information, email info@promptli.com and we will delete it.
16. Changes to this policy
We may update this policy from time to time. When we do, we will update the "Last updated" date at the top of this page. Material changes will be communicated by email to account owners before they take effect.
17. Contact
For any privacy question or request, contact us at info@promptli.com, or by post at Promptli Inc, 131 Continental Drive, Newark, DE 19713, USA.