Security
Security and privacy
Borrower documents are sensitive. This page says plainly how they’re handled today and how to reach us. We’d rather be accurate than impressive.
At a glance
- Stored in Montréal Documents, the database and the AI reader run in Canada.
- Read by AI, approved by you Every figure is yours to check.
- Nothing reaches Finmo until you approve TheBrokerMate sends only when you say so.
- Each brokerage’s files kept apart A folder of your own, in Canada.
- Your own Finmo credentials Stored encrypted. Remove them any time.
What’s in place now
-
Documents are stored and read in Canada
Google Cloud Storage and Vertex AI in Montréal; the app runs in Montréal and the database is in Canada (Central). If the Canadian reader is down, a document may be read by Anthropic’s Claude in the United States.
-
Finmo is reached with your own credentials, stored encrypted
You can remove them at any time in Settings > Integrations.
-
Each brokerage’s files are kept in their own folder
And each submission arrives as its own package, named for its applicants.
-
Client names, notes and held submissions are encrypted
On top of encryption in transit (HTTPS) everywhere.
-
Every document view and download is logged
Who opened which document, and when.
-
Data is deleted on a timetable when you leave
30 days read-only to export everything, then client data is deleted within 30 days.
On our roadmap
Not in place yet. We add a date only when we commit to one.
-
Two-step sign-in for every broker account
-
An independent security test before general availability
-
A deletion period you choose for your clients’ documents
Your responsibilities as the broker
Where borrower documents go
These services process borrower information when the app is used:
| Service | What it receives | Why | Where |
|---|---|---|---|
| Google Cloud (Vertex AI) Canada (Montréal) | While a borrower uploads: each file (first 3 pages), the applicants' names, the loan purpose and income types | Recognize each document and sort it into the broker's checklist; the result isn't stored | Canada (Montréal) |
| Anthropic (Claude, backup reader) United States | Only when Vertex refuses, fails or times out: the same document and context Vertex would have read | Read the document so the broker is not kept waiting | United States |
| Google Cloud (Vertex AI image generation) Google's global network (outside Canada) | No personal information: a city or neighbourhood name and a description of a scene (a street, a home), when a broker asks for a sample photo for their website | Make sample photos for brokers' websites | Google's global network (outside Canada) |
| Google Cloud (Cloud Storage) Canada (Montréal) | Submitted documents and application details (names, emails, phone numbers, income types, notes, consent); broker profile photos | Store each submission for the broker | Canada (Montréal) |
| Resend (email) United States | Broker names and emails for sign-in links; submission emails to the broker with client names, emails, phone numbers, file names and notes | Send sign-in links and tell the broker when documents arrive | United States |
| Supabase (database) Canada (Central) | Broker accounts and profiles, encrypted Finmo credentials, sign-in sessions, audit and delivery records, encrypted copies of delayed submissions, brokers’ client lists (client names and broker notes encrypted; email and phone only as keyed hashes) | Run broker accounts and deliver submissions | Canada (Central) |
| Google Cloud (Cloud Run, app hosting) Canada (Montréal) | All app traffic, including uploads in transit, and server logs | Run the app | Canada (Montréal) |
| Cloudflare (network in front of the app) Cloudflare's global network | All app traffic, including uploads in transit, on its way to the app | Route visitors to the app and protect it from abuse | Cloudflare's global network |
| Google (Google Fonts) Google's global network | IP address and browser details of anyone who opens the app | Load the app's fonts | Google's global network |
| Finmo Canada, according to Finmo | Borrower details and documents, when the broker sends a file | Fill in the broker's Finmo deal, using the broker's own credentials | Canada, according to Finmo |
| Finmo (read back, Pro brokers who switch it on) Canada (Cloud Run and the database in Montréal) | After the broker pulls credit in Finmo: the borrowers' credit scores, the debts on the credit report, and the deal's price, down payment and income as Finmo holds them. Stored as figures and counts only (no creditor, account number or name); the deal page and the broker's "credit pulled" email are computed from them | Check the client's debt ratios against lender limits again with the credit report's figures, and remove the portal's own duplicate debt entries from the Finmo deal | Canada (Cloud Run and the database in Montréal) |
| Google Drive (the broker's own, if they link it) Outside Canada (Google's global storage) | A copy of each client's documents, in a folder TheBrokerMate creates in the broker's Drive | Give the broker a copy in their own Drive; TheBrokerMate's storage in Canada stays the system of record | Outside Canada (Google's global storage) |
On thebrokermate.com itself
These services receive visitors’ information when the website is used:
| Service | What it receives | Why | Where |
|---|---|---|---|
| Cloudflare (website hosting) Cloudflare's global network | IP address and request details (browser, page, time), kept in Cloudflare's request logs | Serve the site and protect it from abuse | Cloudflare's global network |
| Cloudflare (Workers KV, testimonials) Cloudflare's global network | Testimonial invitations (name, profile link, company) and what each person sends: name, role, company, city, photo, profile link, their words, and the date and wording of their consent | Keep invitations and testimonials until we approve, use or remove them, and serve approved ones and their photos on the home page (/api/testimonial, /api/testimonials, HQ > Testimonials through the Cloudflare API) | Cloudflare's global network |
| Resend (email) United States | Contact-form fields: name, work email, brokerage, chosen plan, message; testimonials as they are sent (name, role, company, city, profile link, words) | Deliver enquiries and testimonial notices to the sales inbox (/api/contact, /api/testimonial) | United States |
| Cloudflare Turnstile (form check) Cloudflare's global network | IP address and browser details, sent to Cloudflare when a visitor sends the contact, sign-up or partner-invite form; no form content | Check, without showing the visitor anything, that the sender is a person (invisible mode) | Cloudflare's global network |
| Google Analytics (website analytics) United States and Google's global network | Pages visited and time on them, approximate location from the IP address, device and browser, referring site, and the sign-up steps reached. Cookies whose names start with _ga. Nothing typed into a form. Unless the visitor turns analytics off on /privacy/#cookies | Measure visits and see where visitors leave the sign-up form (public/analytics.js, src/lib/analytics.ts) | United States and Google's global network |
| Cal.com (call booking) United States | When a visitor books a call on /book-a-call/: name, email, brokerage, phone if given, notes, the time chosen, and the IP address and browser details of the request | Show the booking calendar (cal.com/thebrokermate), keep the booking, and send the confirmation, reschedule and cancel emails | United States |
| Google Calendar and Google Meet (calls) Google’s global network | The booker’s name, email and notes, as an event in our team’s calendar with a Google Meet link; the call itself on Google Meet | Offer only times when we are free, hold the booked call, and run the video call | Google’s global network |
Privacy contact
Questions about personal information: Arash Zare, President, info@thebrokermate.com.
Report a security problem
Email info@thebrokermate.com. Please include what you found, how to reproduce it, and any accounts or URLs involved. Don’t include borrower documents or personal information.
We’ll acknowledge your report and keep you updated. We won’t pursue legal action against good-faith research that avoids harming people’s data and gives us reasonable time to fix the problem.
Machine-readable contact: security.txt