Emberly
Privacy, in plain words
This is what Emberly does with what you put into it. It is short on purpose, and it says what the product actually does today.
Emberly stores what you type
That includes what you type about other people — a name, a date, something someone told you. It is not screened, not categorised and not judged. Emberly looks for a person, a date and an amount so it can set your follow-up; the rest is kept exactly as you wrote it.
It only ever knows what you told it
No scraping, no enrichment, no social-network import, nobody looked up anywhere. If you did not tell Emberly something, Emberly does not know it.
You can delete it
You can delete a person, and everything you noted about them, from their screen; or your whole account, and everything in it, including your chat history. Deleting your account signs you out on every device and cannot be undone.
One thing worth knowing: deleting a person removes their details, their follow-ups and anything you recorded about money with them, but your chat history is separate and is not removed by that. Deleting your whole account does remove it.
What leaves the app, and why
Your message may be sent to Azure OpenAI so Emberly can understand what you want. When you ask a question across your book, your saved people, details, notes, follow-ups and deal facts are sent with that question so the answer can be grounded in what you recorded. Operational data such as sessions, audit logs, feedback and bug reports is not included.
The memory-reading call has no action tools: text stored in your book cannot instruct Emberly to change anything. Azure OpenAI processes this data to provide the answer; it is not made available to other Azure customers or used to train foundation models.
We never message anyone on your behalf
Emberly reminds you. It does not send messages to your clients, your contacts, or anyone else. When it drafts something, you are the one who sends it.
If someone asks us to remove what a user wrote about them
We handle it by hand. Message us on Telegram at @AskEmberly_bot and a person will read it. We would rather say that than describe an automated process we have not built.