Data and privacy
Your agents talk to your customers, so Peki holds customer data on your behalf. This page explains what is stored, how personal data is kept away from the AI models, what deleting erases, and what is kept for how long. Use it when you answer your own customers' privacy questions or fill in a data-protection review.
What Peki stores
About your workspace and team
| Data | What's in it |
|---|---|
| Workspace | Name, default language, time zone, business hours, plan and credit balance. |
| Members | Each member's email address and role, and who invited them. |
| Agents | Every draft and published version: instructions, tools, Functions, skills, model and guardrail settings. |
| Secrets | Keys your tools use, encrypted. After saving, only the last four characters are ever shown. |
| API keys | Only a fingerprint of each key, its name, first and last characters, access and when it was last used. The key itself can't be read back. |
| Variables | The names and values you set. |
| Credit history | Every charge and grant, with what it was for. |
| Audit log | Who changed what, and when. See Audit log. |
About your customers
| Data | What's in it |
|---|---|
| Customers | One entry per person per channel: name if known, Telegram handle, language, the tags and notes your team adds, first and last seen. For the Sessions API, your own user id; for the website chat, only a fingerprint of the visitor's browser id. |
| Conversations and messages | The full text of every message as written by the customer, the agent and your team, with any files. |
| Files | Photos and documents customers send and your team sends back, stored privately in Europe. |
| Records | What the agent or the records fill saved in your tables, for example a booking or an order number. |
| Knowledge | The documents, pages and files you add, and the text the agent searches. |
| Traces | One record per reply: the model, the tools and skills it used, tokens and timing. |
| Analytics | Ratings, and the analysis of finished conversations (answered or not, topics). |
| Webhook requests | For each request: time, status, size and a short preview with personal data masked. Never the full body. |
Your team sees customers' real data in Peki: in the Inbox, in customer details and in records.
How personal data is protected from the AI
AI models answer your customers, but they don't need to know who your customers are. With Protect personal data on (it's on by default for every agent), Peki removes personal data from each message before the model sees it.
What is hidden
| Data | Example | The model sees |
|---|---|---|
| Turkish ID number (TC kimlik) | 12345678950 | [TCKN_1] |
| Payment card number | 4111 1111 1111 1111 | [CARD_1] |
| IBAN | GB82 WEST 1234 5698 7654 32 | [IBAN_1] |
| Phone number | +1 212 555 0100 | [PHONE_1] |
| Email address | [email protected] | [EMAIL_1] |
| The customer's name (optional) | Maria Lopez | [NAME_1] |
ID, card and IBAN numbers are checked with their checksums, so random numbers like order numbers aren't hidden by mistake. Names are hidden when Also hide the customer's name from the AI is on (on by default).
How it works
- The real values are kept encrypted, in a vault for that one conversation only.
- In the reply, the customer sees their own data, either As written or Masked (
123******50), as you choose under In replies, customers see their own data. - Your tools get the real value only for inputs you mark Needs the real personal data, for example a TC kimlik number your booking system needs. The AI only ever sees the placeholder.
- Personal data in tool responses is replaced with placeholders too, before the model reads them.
- Text inside documents gets the same treatment as messages.
- Images can't be masked. A photo goes to the model as it is, so choose carefully which agents read images.
See Guardrails and privacy to change these settings per agent.
Model providers
Every model call goes only to providers that don't keep your data. The analysis of finished conversations also runs with personal data hidden.
Deleting data
Deleting is permanent. There's no trash and no undo.
Delete an agent
Admins and owners can delete an agent (Delete agent). It erases the agent and everything that belongs to it:
- every draft and version, its notes and the agent document,
- its channels: the website chat key stops answering and the Telegram bot stops,
- its automations and their schedules, runs, state and webhook request logs,
- its conversations and messages, and the AI's memory of them,
- traces, analytics and conversation analyses,
- its knowledge sources and their indexed text,
- the secrets that belong to it,
- its Copilot chats and test runs, Function run logs,
- its record tables and records, their change history and pending approvals,
- the files of its conversations, knowledge and records,
- calls it made to other agents in its team.
Customers who only talked to this agent are deleted. Customers who also talked to another agent stay, with their other conversations.
What changes elsewhere:
- Other agents' drafts drop it from their team. Their published versions stay as they were and skip it.
- Records another agent saved stay with that agent, but lose their link to this agent's conversations and customers.
What is kept:
- the credit history, which is the workspace's billing record,
- the audit log entry saying who deleted the agent.
Delete a workspace
Owners can delete the workspace in Settings → Workspace (see Workspace settings). First, membership ends for everyone, so nobody can reach it any more. Then every agent is deleted as above, followed by all workspace-wide data: members, API keys, variables, customers, all stored files, the credit history and the audit log.
Peki's own tests check that every kind of data with a workspace is covered: a new kind of data can't be added without deciding how it's erased.
Delete one customer
Peki has no button to delete a single customer today. You can change a customer's name, tags and notes in their customer details. A customer's conversations and data are deleted when you delete every agent they talked to, or the workspace. If you need to erase one person's data, for example after a request under GDPR or KVKK, contact us.
How long data is kept
| Data | Kept |
|---|---|
| Conversations, messages, customers, records, knowledge, files sent with messages | Until you delete the agent or the workspace. |
| Credit history | Until you delete the workspace (it survives deleting an agent). |
| Audit log | Until you delete the workspace. |
| Automation runs | 30 days. |
| Function run logs | 30 days. |
| Webhook request log | 30 days (the automation shows the last 20). |
| Duplicate check for webhooks | 24 hours. |
| Uploaded files never sent with a message | 24 hours. |
Audit log
Peki writes an audit entry for changes that matter for security and accountability. Each entry says who acted (a member, or an API key), what they did, on what, and when. For example:
- members invited, role changes, removals,
- API keys created and revoked,
- secrets added, assigned, removed, and changes to where a key may be sent,
- agents renamed and deleted,
- channels connected, changed, moved or disconnected,
- knowledge added and removed,
- variables created, changed and deleted,
- record tables created, changed and deleted, record imports,
- customer details changed (which fields, not their values),
- approvals rejected, expired or failed,
- rejected webhook signatures, Function tests and Copilot undos.
The log stores what changed, not the secret values or record contents. It's deleted with the workspace. The audit log isn't browsable in Peki today.