Our security philosophy: useful help with clear limits
Asking for opening hours needs very little personal information. Following up on a service account may involve details that could identify you or unlock access. Those tasks deserve different boundaries. Cleo is built around a specific errand, your instructions, and the permission you give for that call.
Use less information
Give Cleo only what it needs to complete the errand. A simple question should not require your full personal history.
Keep authority limited
Decide what Cleo may ask or agree to, and which decisions need to come back to you.
Make protection understandable
Explain how information is protected, how it is used, and which decisions need your involvement.
What counts as a secret in a phone task?
Sensitive information is more than a password. Your date of birth, a service-account PIN, an account or customer number, or an answer to an identity question can help someone access information about you. A detail that seems harmless on its own can become sensitive when combined with your name and the business you use.
These are examples of information that needs special handling, not a request to put it into a task. Keep login passwords, payment-card PINs, and one-time verification codes out of call instructions and support messages. Only provide other sensitive details when a Cleo flow explicitly supports them and you are authorized to use them.
How Cleo encrypts protected task information
Task answers marked as protected are encrypted at rest using AES-256-GCM. Encryption at rest means the saved value is stored as unreadable ciphertext. For example, a date of birth entered as a protected answer is encrypted before it is saved, rather than stored as readable text in that protected field.
This protection uses a 256-bit encryption key kept separately from the stored values. Each encryption uses fresh randomness, and integrity checks detect changes to the encrypted value. Decryption requires the key and a successful integrity check. If the required encryption key is missing or invalid, protected writes fail rather than silently saving the answer as plain text.
Protected values are kept separate from ordinary call instructions. When preparing those instructions, Cleo replaces known protected values with placeholders. It also applies redaction for known protected values when saving imported call transcripts and results. This reduces unnecessary copies of a secret in the information used to carry out and review a task.
You choose the task and control the call
Review the destination, instructions, and call limits before approving. Saving a task does not dial. Cleo checks requests before calling; requests without clear permission and requests rejected by its safety checks do not proceed. Our responsible calling policy explains those boundaries.
- State what Cleo may ask or agree to, including choices that need your decision.
- Check the call status and stop the call when needed. Every call has a maximum duration.
- Keep your account secure; your tasks and call records require signed-in access.
- Review the result and unresolved questions before relying on an important outcome.
What happens to call information and records?
A phone call necessarily shares information with the person or business on the other end. Services that help deliver Cleo's calls may also process necessary instructions, audio, or transcripts. Encryption of protected stored answers does not mean the whole phone conversation is end-to-end encrypted or that service providers never receive personal information. Our service provider overview explains these roles.
You can delete a call record after it ends. That action does not delete its parent task or the answers saved with the task. Once its calls have ended, you can delete the task and its call history from your account. Limited security and billing records, backups, and provider-held copies may follow separate retention and deletion rules.
We do not sell personal information or use call-task content to create advertising profiles. Read the privacy notice for the information we collect, how it is used, and the limits of deletion.
Common questions about Cleo security
Does Cleo encrypt my date of birth or account PIN?
Task answers marked as protected are encrypted at rest using AES-256-GCM. A date of birth, service-account PIN, or account number can be sensitive information. Simply typing one into ordinary instructions does not guarantee it will be recognized and protected. Only provide sensitive information through a flow that explicitly supports it.
Will the business still need me to verify my identity?
A business may require you to verify your identity directly, especially for account changes or sensitive requests. Do not put login passwords, payment-card PINs, or one-time verification codes in ordinary call instructions. Encrypted storage does not authorize disclosure of your information.
What happens to saved information when I delete a call?
You can delete a call record after the call ends. Deleting that record does not delete the parent task or its saved answers. Deleting the task removes its task and call history once its calls have ended. Limited security, billing, backup, and service-provider records may follow separate retention rules described in our privacy notice.
Report a security concern
If you suspect unauthorized access or find a security issue, email hello@cleopowered.com. Describe the affected page or feature, what happened, and how to reproduce the issue if you know. Keep passwords, verification codes, and other people's information out of your report. Please avoid accessing anyone else's account or disrupting the service while investigating.
No service can eliminate every risk, and Cleo does not currently claim an independent security certification. We do not currently offer a reward program for security reports.