Privacy
Checked against our code on 5 November 2026.
Stored
| What | Why |
|---|---|
| The messages, rows, emails, events and documents we read | So every number can show where it came from |
| Files and photos | So your team can open the original |
| Records of each visit, tick or call, with the words they came from | They are what we count |
| Each person's code, initials and the ways your team writes their name | So each person is counted once |
| Each person's name, as your team first wrote it | So an owner or admin can look someone up |
| Your staff and volunteers' names | So they're never counted as people served |
| Sign-ins for the accounts you connect | So we can keep reading on schedule |
| Members' email addresses, names and roles | To sign you in, decide what you can do and see how Evidently is used |
Files are private, and a link to one stops working after 5 minutes. But anyone with a shared report's link can open its photos and PDF, until it expires or you turn it off.
The people who run Evidently have a page showing each account's email, name, organisations and roles, when it joined and was last active, and counts of what it has used. It never shows your records, messages or files.
Encryption
Supabase, our database host, encrypts everything we store on its disks. We also encrypt each person's saved name, and the sign-ins of accounts you connect, with AES-256-GCM and a key our app server holds, not the database. We don't add our own encryption to message text or files, to names inside messages, or to the spellings we match people by.
Claude
Claude, an AI model made by Anthropic, reads your messages and files to find records.
Before any text is sent, we hide phone, NRIC, FIN and passport numbers, in Bengali, Tamil, Burmese and Chinese writing too. Emails, postal codes and street addresses are hidden too. Work permit, birth certificate and bank account numbers are hidden only when a word beside them says what they are. This works by matching patterns, so an unusual format can slip through.
Claude still sees names, because it needs them to tell people apart. We remove a photo's embedded location, time and device details. The image itself is sent to Anthropic, including any names or numbers written on it.
Claude also gets your programmes, team names, glossary, rules and source notes. Report drafts get the figures, the report's title and the funder's name. Drafts and “What changed” sentences also get your organisation's and programmes' names, but no message, record or name of someone you help.
We check Claude's answers, report drafts too, and hide any ID number or email again. The shared sample's made-up records were read by simple rules, not by Claude. In a copy of your own, what you add and any report draft go to Claude.
Names
Each person you help appears as a code and initials, like P-0042RK. Your messages and files keep names as your team wrote them. On screen, your team sees them as codes and initials. An owner or admin can show the names in an item they are checking in Review, and each time is logged. Volunteers you add as viewers see the records but not the original messages.
Summaries name people by code, but a name we haven't matched can still appear. Phone and ID numbers, emails and addresses are taken out of every summary.
On a person's page, only owners and admins can show their name. Each look is written to the audit log.
A report never lists the people you help, by name or by code. It shows a photo or quote only if you tick that you have consent. An export leaves names out. An owner or admin can ask for them, and that is logged.
An owner can choose never to keep names. Claude reads each new item once to find them, and only the codes are stored. An owner or admin can also hide one person's name for good, which deletes their photos and files too. Neither can be undone. Your own sheets and chats don't change.
Logs
Our server logs keep ids, counts, timings, error types, error messages and stack traces. A failed database query is logged with its SQL, without the values in it. Fields holding message text, quotes, names, emails or tokens are blanked before writing.
The audit log records actions like showing a name, deleting or exporting. Only owners and admins read it, and it names people by code. Each record's page shows its history and any reason your team typed, but viewers see only that a reason was given.
Deleting
| You delete | What goes |
|---|---|
| A source | You choose to keep what we read from it, or delete all of it. |
| A person | Their records, but messages naming them stay with their source. |
| The organisation | Its data and files. Only an owner can do this. |
Each of these waits 10 seconds, so you can undo it. Then your numbers are counted again. You can set a retention period in Settings. It's off until you do. With it on, older messages and files go each night at 3am Singapore time, and the numbers stay. An uploaded chat or spreadsheet is one file, so it stays until all of it is older than your setting.
Our database host's backups can hold deleted data until they expire. A deleted organisation leaves a note of its name, web address, date and members, shown to them at its old address.
Hosting
Your data is stored by Supabase, in Singapore. The app and its background jobs run on Railway, also in Singapore. Sign-in links and invitations are sent through Resend, from Tokyo. Nothing about the people you help is ever in an email. What we send to Claude, text and photos, is processed by Anthropic. Anthropic deletes what we send within 30 days and doesn't use it to train its models. It keeps something longer only if it breaks Anthropic's usage policy or the law requires it.
The law
We built Evidently with Singapore's Personal Data Protection Act in mind, but no lawyer has checked it. We're new, so we have no security certification or independent audit yet. Settings has a notice you can adapt for the people you serve. To ask about your data, email williamyang0013@gmail.com.