Written plainly, because you are being asked to connect an account that reads your transactions. Part of the Terms of use. Last updated 2 October 2026.
Using the reZEN connection you approve — Sign in with reZEN, or an API key you generate — Deal Dates reads the open transactions that account can already see, and only those, within the read-only permissions you granted. In practice that means:
| Deal details | Address, MLS number, side, status, and the condition, firm and closing dates |
|---|---|
| People on the deal | Your client's name, the co-operating agent's name and contact details as recorded in reZEN |
| Checklist | Which required documents are outstanding |
| Contract terms | The typed "Other terms" on the Purchase Contract, and any amendments or addenda, so a possession-week reminder can say what was agreed (a walk-through, a professional clean). Read once per document by software running on our own servers; the documents are not sent to any third party and are not kept. The typed terms read from them are kept with the deal and deleted with it. |
| Activity | The deal's own change log — a date moved, a deposit confirmed — for the "since yesterday" section |
| Your team | Names, reZEN ids and email addresses of team members, so the digest can be addressed and delivered |
| Your own identity | When you sign in with reZEN: your name, email address and reZEN user id, from the consent you approved — to label the connection and so the settings page can say who connected it. Nothing else about your account. |
We do not read commission amounts for any purpose other than ignoring them, and we do not read anything belonging to agents outside your own team — except the published business contact (name, phone, email) of the other Real agent on a double-ended deal, so the closing-day callout has someone to phone.
Deal data is stored in a database in Canada, in a separate area per customer so one customer's records are not reachable from another's. Your reZEN credential — the access and refresh tokens from Sign in with reZEN, or an API key — is held in that same private area, separately from the deal data, on the digest server only. It is never included in a digest, a log, a config file we share, or the settings page.
That database is backed up every night. One copy stays on our own server for 14 days; another is kept for 30 days in Cloudflare R2, Cloudflare's storage service, where it is encrypted at rest and may be stored outside Canada. Each backup is deleted when its period ends, so anything deleted from the database is gone from every backup within 30 days.
Signing in with reZEN finishes on this website, because the one-time code reZEN issues must be exchanged within sixty seconds. The credential is encrypted at that moment to a key that exists only on the digest server, handed over sealed, and discarded here. This website never holds it in readable form.
Your team, in the digest. Deal Dates is run by people, and because we hold your key and your data on our systems we are technically able to see it — we would rather say that plainly than pretend otherwise. What we have done is make sure no routine step requires it: setting a team up, checking that a digest would go out, and delivering it show us who receives a digest and how many deals it covers, not what is in it. Our tools refuse to display another team's digest by default. The one exception is when you ask us to look at a specific problem, and then only at what you ask about.
These are the outside services that handle data for Deal Dates (our subprocessors), what each one sees, and where. Everything else — the database, the digest server, and the software that reads contract terms — runs on servers we operate in Canada. If we add a service that handles your team's data, it will be listed here before we use it.
| Resend | Delivers the email. Sees the message and the recipient address, and keeps its own record of each message for a limited period under its retention policy. United States. |
|---|---|
| Cloudflare | Our nightly database backups (see Where it is stored), plus DNS, this website, the settings page, the sign-in handoff, and the optional calendar feed. The settings page holds your name, email address and delivery preferences (when the digest arrives, how far ahead it looks, whether you receive it), plus who connected reZEN and which permissions were granted — never a deal, never a credential. The sign-in handoff holds the credential only in sealed form, for at most fifteen minutes, until the digest server collects it. If you subscribe to the calendar feed, your own deal dates and addresses are held there under a private link that only you receive. This website also uses Cloudflare Web Analytics — page views and load times, with no cookies and no identification of who you are — so we can tell whether the site works. Nothing else. A United States company with servers worldwide; your data may be processed outside Canada. |
| Real Broker / reZEN | The source of the data, and the identity provider behind Sign in with reZEN: the login and consent screens are theirs, and they see that you connected Deal Dates and what you approved. We are not affiliated with them. |
| Helcim | Processes payments, if and when your team subscribes. The card form on the settings page is Helcim's own, so they see the card number, the cardholder's name, the billing province and the amount; we see a customer reference, the card's brand and its last four digits, and never the number. Helcim is a Calgary payment processor. |
If you ask the home page to email you a sample, your address is held at Cloudflare only until the digest server picks it up — normally within seconds, at most fifteen minutes, and never more than a day — and is then deleted. After the send we keep a one-way hash of the address for 30 days, solely so the same person is not mailed twice; the address itself is kept nowhere. It is not added to any list.
| Open deals | Refreshed from reZEN every day. A deal that is no longer open — closed, terminated, or no longer visible to your connection — is deleted 30 days after it was last seen, with its checklist and the contract terms read from it. |
|---|---|
| Delivery record | Who received a digest, on which day, and how many deals it covered: kept while your team uses Deal Dates. |
| Our logs | When each digest was sent, to which address, and the delivery reference: about three months. Never the contents of a digest. |
| Your reZEN connection | Used until you disconnect, when it is revoked and never used again; deleted when your account is closed. |
| Terms acceptance | Which version of these terms was accepted, when, and by which reZEN account: kept while your team uses Deal Dates. |
| Billing records | If your team subscribes: payment records are held by Helcim and kept for as long as Canadian tax law requires, which is generally six years. |
| Backups | Database backups: 14 days on our server, 30 days in Cloudflare R2, then deleted. Your team's settings (its name, the lead's email address and delivery settings — no deals) are also in our encrypted configuration backup for 90 days. |
When you stop using Deal Dates we delete your stored data within 30 days. It then leaves our database backups within a further 30 days, and your settings leave the configuration backup within 90. Ask sooner and we will do it sooner.
privacy@dealdates.app for anything on this page, or hello@dealdates.app for everything else.