Data separated by broker
Each broker has a separate space. The separation is enforced by the database itself (row-level security), on top of the application's checks. A broker can neither read nor guess another broker's data.
Security and privacy
Trust is built in the code.
Here is what is actually in place in Zoé's prototype, what isn't yet, and what we don't claim.
In place in the prototype
Six protections already built and tested.
Verified by automated tests in our development environment.
Sensitive information encrypted
Client names and contact details, record and file contents, and access tokens for connected services are encrypted (AES-256-GCM) by Zoé before they are stored. The database never sees them in plain text.
Minimal access to connected services
For Google Calendar, Zoé asks to read your calendars and — only if you enable changes — access to events. Never access to Gmail, Drive or your contacts through this connection. Tokens stay on the server: the phone app never receives them.
Confirmation before any external action
Creating, moving or deleting an appointment, sending a message: Zoé shows exactly what will be done. Your confirmation covers that exact content, expires quickly and can be used only once.
Careful with uncertainty
Uncertain information never replaces confirmed information. If a provider's response is lost during a change, Zoé checks before trying again, to avoid duplicates.
Action log
Important actions are logged (what, when, result) without personal content, so we can explain what happened.
Artificial intelligence
What the AI sees — and what it doesn't.
To understand a sentence like “Marc is looking for a condo in Laval”, Zoé uses an artificial intelligence model from OpenAI (United States). It receives:
- the message you type in the conversation;
- the latest exchanges of the conversation, which may include Zoé's earlier answers, for example about your appointments;
- for the general conversation, the record of the client concerned.
For calendar questions, only the text of your question may be sent to the model; the answers are computed by Zoé from your calendars.
Daily caps limit the number of model calls. We sell no data and do not use your data for advertising.
Not in place yet
What we don't claim.
- Production hosting: not in place yet. It is planned in Canada (Amazon Web Services, Montréal region).
- Certifications and audits: no certification (for example SOC 2 or ISO 27001) and no external security audit has been obtained to date.
- Google verification: Google's verification of the app has not been obtained yet.
- Self-service deletion: not offered yet; requests are handled by email.
We will update this page at each milestone — never before it is actually in place.
A security question?
Let's talk about it directly.
Brokers' and agencies' privacy questions are welcome, even before a pilot.