Privacy Policy
The version in force today, at its own permanent address.
Effective 11 November 2026 · version privacy-2026-11-11
This is the version in force today, at an address that will keep showing these exact words after the document next changes. Every version.
Effective 11 November 2026 (version privacy-2026-11-11). This policy explains what JOLIVE Labs Inc. ("SourceSecure", "we") collects when you use SourceSecure, why, where it goes and how long we keep it. Our privacy officer is Jacob Oliveira, 95 King William Court, Cambridge, Ontario N3C 4J3, support@sourcesecure.ca.
1. The short version
- What you type and attach on AI chat sites is checked on your own computer. We never receive your files, and we receive no message text until it has been through redaction there.
- We never store your prompts on our servers. Your vault (on a Guard Enterprise seat, also your notes, files and short summaries of your AI chats and meetings), with your own list of names to catch and your list of things marked not sensitive, is encrypted on your computer, and an encrypted copy is kept on your SourceSecure account, so it comes back if you remove and add the extension again and is the same on every computer you sign in on. It is never used to train AI models.
- When you ask your vault to learn from a document, a copy with names and client details replaced by stand-ins is read once by our server, which keeps nothing. The document itself is never sent to be read; it and what was learned are kept in your vault.
- For the optional AI features, text is sent to us and to OpenAI with the names and numbers found in it already replaced by stand-ins. We do not store it, and it is sent to OpenAI with OpenAI's storage option switched off. What OpenAI may keep is set out in 4.2.
- On a Guard Enterprise firm, short facts about the firm's work and the names of its clients that your vault learns are shared with your firm's team vault (see 5.3). Facts about you or your own life are never shared.
- While SourceSecure is on, an AI site's own microphone is held. Dictation is done by SourceSecure on your computer, and your voice is never recorded, kept or sent to us. Voice mode, which sends your voice straight to the AI site, is let through only once at a time when you choose, unless your firm has turned it off.
- Your firm's admin sees what kind of detail was caught and a masked form of it (such as the last four digits of an account number), and when you paused protection, switched it off, or set it to check only when you ask (manual) or not at all; never your messages.
- Our database is in Canada (Montreal). We do not sell information or use it for advertising or to train AI models.
2. Who this policy is for
SourceSecure is sold to businesses ("firms"). The firm decides who gets a seat and which features are on, and is responsible for its clients' information. We handle that information on the firm's behalf under a Data Processing Agreement. This policy also covers visitors to sourcesecure.ca.
3. What we collect, and why
| What | Why | How long |
|---|---|---|
| Your email address, your team and seat type | To sign you in and give you the features your firm bought | Until you are removed from the team, or the firm's records are deleted (30 days after its subscription ends, or at once if its owner deletes it) |
| Sign-in records (through Google Firebase Authentication) | To keep your account secure | As Firebase keeps them |
| For each detail caught: when, which AI site, the kind of detail, what you chose to do (or, if checking was set to manual, that it went without a check), and a masked form made on your computer (e.g. •••• 4242 or Rob••• Ch••). The masked form keeps only the last few digits of a number; the first half of each word of a name, an address or other words; the start of an email's name and of its domain, with its ending (e.g. jane••••@smit••••.ca); or the first part of a postal or ZIP code (e.g. N3C •••) | So your firm can see the tool is working and where client details come up | 90 days from when it is received |
| When protection was paused or switched off, or checking was set to manual (only when you ask) or off, and for how long | So your firm knows when messages were not being checked | 90 days from when the pause began |
| Daily counts of what was caught and how often each feature was used, for each supported AI site how often SourceSecure started there, and the habit you are working on, from a fixed list (counts only, no text) | To show your firm's admins how SourceSecure is being used, for the firm or for one person | Until the firm's records are deleted. If you leave the team, the counts stay as the firm's and stop being linked to you |
| A summary of your week, once a week: counts, labels from fixed lists, how many chats fell in the morning, afternoon and evening, how many minutes a chat lasted, the short headlines of your last few notes (written by the AI model, not by you) and, on Guard 360 seats and above, a few short facts about your work from your vault (no message text, clock times or sites) | To write your private weekly note, which is kept on your computer. It is sent to OpenAI for that (see 4.2) | Not kept by us |
| A secret that proves your browser belongs to your seat, stored only as a one-way hash | To stop seats being copied | While the browser is connected |
| The firm profile, shared terms and firm playbook your admins write | To apply your firm's settings | Until the firm's records are deleted |
| Earlier versions of the firm profile, each with the email address of the admin who made the change | So a change can be undone | The last 100 changes. An admin's address is taken off them if they leave the team |
| An encrypted copy of your vault, your own list of names to catch and your list of things marked not sensitive (see 5.1) | So your vault is not lost when you remove the extension or change computer, and is the same on every computer you sign in on | Until you delete it from your vault, you are removed from your team, or your firm's records are deleted |
| On a Guard Enterprise firm, the team vault (see 5.3): short facts about the firm's work and the names of its clients, sent from Guard Enterprise seats' vaults or added by an admin; how many people's vaults agreed on each, counted under a one-way key for each person; what only one person's vault has sent so far, shown to nobody, while it waits for a second; and, for anything taken out, the email address of the person who took it out | To share how the firm works and who its clients are with everyone in the firm | Until it is taken out of the team vault, or the firm's records are deleted. What your vault sent stays if you leave the team |
| A request you make to your admin for a better seat: your email address, which seat, and when | So your admin can answer it | Until your admin answers it, or you leave the team |
| For a firm with Guard 360 seats or above, how many AI replies its people had checked each month, as one number for the whole firm | To keep the firm's monthly allowance | Until the firm's records are deleted |
| For each firm, each month: each request to the AI features as numbers only (which feature, which model, how many tokens and pages, what it cost), and the month's totals, including how many pages of documents its people had read. No text, and no person named | To keep the firm's monthly AI allowance and, on Guard Enterprise, its monthly pool of document pages, and to show the firm's admins what was used | Until the firm's records are deleted |
| Billing details (name, email, card, address), entered on Stripe's own page. We never see the card | To take payment | As Stripe and tax law require |
| The firm's billing name and address as given at checkout, the versions of our terms the firm agreed to, when, and the email address of the person who agreed | To make out the agreement to the firm, and to show what was agreed | Until the firm's records are deleted. The address of the person who agreed stays with this record even if they leave the team |
| Whether a payment has failed and is being retried | To tell your firm's admins, by email and on the team page | Until the payment goes through or the subscription ends |
| Which notices of a change we emailed your firm's admins, when, and to which addresses | To show that the notice our terms promise was given | Until the firm's records are deleted. An address is taken off them if that person leaves the team |
| After a firm's records are deleted: the firm's name, its Stripe identifiers, what it bought and when, which versions of our terms it had agreed to, and how many records were deleted. No person is named | The record of a sale that tax law expects, and proof that the deletion happened | 7 years after the deletion |
| A one-way key made from the buyer's email address, when a firm has had the free Guard 360 trial. It cannot be turned back into the address | So the free trial is given once to each buyer | 3 years |
| When each person's free Guard 360 trial began, filed under a one-way key made from their email address. It cannot be turned back into the address | So each person gets the trial once at a firm, even if they are removed and invited again | Until the firm's records are deleted |
| Server logs: request counts, timings and errors, with no message text | To run and secure the service | 30 days |
4. What happens to your messages and files
4.1 Detection happens on your computer. The extension reads what you type or attach on supported AI chat sites, finds sensitive details with models that are part of the extension, and offers a redacted version. None of this sends your text or files to us.
4.2 Optional AI features send a redacted extract to our server and on to OpenAI. Names, numbers and other details found are replaced with stand-ins such as [PERSON_1] first, and our server checks again for an email address, a phone number or a long number and refuses the request if it finds one. Redaction replaces what it finds; a name it does not recognise can pass through. We do not store the extract. We send it to OpenAI with OpenAI's storage option switched off, and OpenAI does not use it to train its models. OpenAI may keep its own abuse-monitoring logs of these requests for up to 30 days under its standard API terms, and does not use them to train its models. The features are:
- Prompt coaching (Guard Pro and above): parts of the conversation, yours and the AI's, and for Help me and Sharpen my prompt the whole conversation on the page and your unsent draft. Help me starts when a tip appears, and Sharpen my prompt when your pointer rests on its button for a moment, so the redacted conversation can be sent before you click. If you set Sharpen to Auto or Review, pressing Enter on a message also sends the redacted conversation and your draft to be sharpened. On Auto, the sharpened message is then sent to the AI site without a stop to look at it first; on Review, it waits for you.
- Weekly note (Guard Pro and above): once a week, the summary of your week described in section 3, to write your note. The note comes back to your computer.
- Reply marks (Guard 360 and above): your message, the AI's reply, a few earlier messages, and up to 25 facts from your vault (those closest in meaning to your message, picked on your computer) and your firm's profile.
- Clean-up questions (Guard 360 and above): at most once a week, up to 25 short facts from your vault, to ask which are worded too vaguely to check a reply against. Every answer is applied on your computer and nothing about it is sent.
- Chat and meeting summaries (Guard Enterprise): when an AI chat ends (you switch to another chat, close its tab, or leave it for 3 minutes), its last 40 messages, yours and the AI's, are sent once to be summarised for your vault. Until then, a copy with the names already replaced is held in your browser's memory, never on disk, so a chat can still be summarised after its tab is closed. At most 50 chats a day are sent per person. You can switch this off for yourself ("Remember my chats automatically"), for one chat ("Don't remember this chat"), or your firm can switch it off. A meeting transcript is sent as soon as you add the file.
- Ask SourceSecure (Guard Enterprise): your question, an overview of your vault, and the passages of your notes found for the question, sent only when you ask. A question asked on the team vault sends the team vault's facts and client names found for it instead of your own notes.
- Document reading (Guard Enterprise): when you add a document in your vault's Documents tab with "Teach my vault from it" ticked, its words, once, in parts, with names and client details replaced by stand-ins on your computer first, together with your note about it if you write one; and once for each batch, the short facts found in it with the facts your vault already holds. "Just keep it, send nothing" sends nothing, and your firm can switch document reading off. The document itself is never sent. Your firm shares a monthly number of pages, counted by our server from what it receives.
You can switch prompting tips off at any time. With it off, prompt coaching, the weekly note, reply marks, clean-up questions, chat and meeting summaries, and document reading all stop. Ask SourceSecure is separate: a question is sent only when you ask it, whether prompting tips are on or off, and stops when you or your firm switch your vault off. While SourceSecure is paused, none of these features sends anything, Ask SourceSecure included.
4.3 Real names in replies. When an AI's reply contains stand-ins we sent, the extension puts the real names back on your screen, using a list kept in your browser for up to 12 hours. The list is never sent to us.
4.4 Your voice. An AI site's own dictation and voice mode send your voice to the AI company before there is any text to check. So while SourceSecure is on (not paused or switched off), the extension holds the AI site's microphone on supported sites:
- Dictation. When you press the site's microphone or dictation button, SourceSecure listens instead, using your browser's built-in speech recognition set to work only on your computer. The words go into the message box and are checked like anything you type before you send them. No recording is made, kept or sent to us or to the AI site. Before first use, your browser may download its speech pack from its maker (for Chrome, Google); no recording is sent with that download. If your browser cannot recognise speech on your computer, SourceSecure does not listen at all, and says so.
- Voice mode. A spoken conversation with the AI site cannot be checked. It is held, and you may let it through once at a time; what you then say goes from your browser straight to the AI site, under that site's own terms, and SourceSecure receives none of it. Your firm's admin can turn this off, so voice mode stays held.
5. Your vault
5.1 Your vault is kept in your browser on your own computer, and an encrypted copy of it is kept on your SourceSecure account.
- On Guard 360 it keeps short facts about your work and firm, to check AI replies against. If you switch on Remember personal details, it also keeps lasting facts about your own life; while that switch is off, facts about your own life are not sent.
- On Guard Enterprise it also keeps notes, files, captures, people and company pages, summaries of your AI chats and meetings, and the documents you add with what was learned from them, encrypted.
Every computer you sign in on with the same address keeps the same vault: what you add or delete on one reaches the others within minutes. Your browser sends the copy every 10 minutes and about 30 seconds after a change, whatever your seat, and your own list of names to catch and your list of things marked not sensitive are copied with it, the same way. Before anything leaves your computer it is encrypted with a key made for you alone; our server keeps only the encrypted copy, never the key, and makes the key again from a secret held in Google's secret store when one of your signed-in browsers asks for it. So the copy in our database, or a backup of it, cannot be read on its own. We do not open it, share it with your firm, or use it to train AI models. If you are removed from your team, or your firm's records are deleted, the copy is deleted with your other records; the vault on your computer stays until you delete it. Only you can see it, and you can change or delete any of it; after a chat is summarised, Undo removes what was just added. Passages from it are sent, redacted and not stored by us, only for the features in 4.2, and, on a Guard Enterprise firm, the short work facts and client names described in 5.3 are shared with your firm's team vault. If you remove the extension or clear your browser data, it comes back from the copy when you sign in again. Delete everything, on your vault page, deletes it on every computer and from the copy. An export is not encrypted.
5.2 It may hold any fact you choose to keep, including a health fact you mention. On our servers it is held only as the encrypted copy in 5.1, apart from what is shared with a team vault under 5.3. A fact you keep may be sent, redacted, for the features in 4.2.
5.3 The team vault (Guard Enterprise). A firm with Guard Enterprise seats has one team vault: short facts about how the firm works and the names of its clients. It is held on our server, in Montreal, with the firm's other records, because the whole firm shares it.
- What is sent. About once a day, each Guard Enterprise seat's browser sends the short work facts its vault has learned about the firm, and the names of the clients it knows, at most 80 work facts, 80 facts from documents and 80 client names. Facts about you or your own life are never sent, and our server never opens your vault's copy to look for them. Nothing from a chat you set to "Don't remember this chat" is sent. A fact with an email address, a phone number or an account number in it is dropped. What is sent is not encrypted like your vault's copy: our server can read it, because it compares it and shares it with your firm.
- How something goes in. A fact or client name goes in once the vaults of two or more people in the firm have learned it. A work fact from a document a Guard Enterprise member adds goes in at once; a client name always waits for a second person. Until a second person's vault agrees, what only one person's vault sent is kept by our server, shown to nobody. The firm's admins can also add facts and rules themselves. The comparing is done by our server; nothing is sent to OpenAI for it. Nobody approves an entry first.
- Who sees it. The firm's team heads and Guard Enterprise members can see it, and any of them can take an entry out or put it back; each removal records the email address of whoever made it. Every seat in the firm uses it without seeing it: its facts help Sharpen and the reply check, and its client names are added to the list of names every seat in the firm catches and replaces before a message is sent.
- How long. An entry stays until someone takes it out or the firm's records are deleted. If you leave the team, what your vault sent stays in the team vault.
- Switching it off. A Guard Enterprise team head who switches the vault off for the firm stops every seat sending to the team vault and stops showing it.
6. Who else handles information
We use Google Cloud and Firebase (database and server functions in Montreal; website delivery and sign-in on Google's own network), OpenAI (redacted text for AI features, in the United States), Stripe (payments, in the United States and Canada), Resend (the emails we send, in the United States) and Cloudflare (our domain's addresses, and forwarding of email sent to support@sourcesecure.ca, on its global network). The current list is at sourcesecure.ca/subprocessors. We do not sell or share information with anyone else, except where the law requires it.
7. Where information is kept
Our database and the server functions that handle your information are in Montreal, Canada. Sign-in accounts are held by Google's Firebase Authentication, which is not tied to that region. Redacted text for AI features (OpenAI), the emails we send (Resend) and payments (Stripe) are processed in the United States, where they may be subject to US law. Email you send to support@sourcesecure.ca passes through Cloudflare's network on its way to us.
8. Your rights
You can ask to see the information we hold about you, have it corrected, or have it deleted, and (in Quebec) receive it in a structured format. Because your firm controls your account, we may pass your request to your firm's admin. Write to our privacy officer, Jacob Oliveira, at support@sourcesecure.ca; we reply within 30 days.
Your firm's admins can download everything we hold for the firm, as one file, from the team page, and can remove you from the team there, which deletes your records. The firm's owner can delete all of the firm's records there at any time. Two things stay if you are removed: if you agreed to our terms on your firm's behalf, the record that you did (your email address and the date) is kept with the firm's agreement; and if you had the free Guard 360 trial, when it began is kept under a one-way key made from your email address, so it is not given twice. Both are kept until the firm's records are deleted.
If you manage a team, we email you a monthly report; the link in it stops it in one click. If you are not satisfied, you can complain to the Office of the Privacy Commissioner of Canada (priv.gc.ca) or, in Quebec, the Commission d'accès à l'information.
9. Security
We encrypt information in transit and at rest, keep no downloadable server credentials, require two-step verification for our administrative accounts, and keep the database protected against deletion with 7-day recovery. The copy of your vault is encrypted before it leaves your computer, and the secret its keys are made from is held apart from the database. If a breach affects your information, we will tell your firm within 72 hours and help it notify you where required, as our incident and breach response policy at sourcesecure.ca/incident-response sets out.
10. Cookies
sourcesecure.ca uses no advertising or tracking cookies. Signing in stores a session in your browser so you stay signed in.
11. Children
SourceSecure is for businesses and is not meant for anyone under 18.
12. Changes
If we change this policy in a way that affects what is collected or who receives it, we will email firms' admins before the change takes effect. The date at the top shows the last change.
Getting in touch
Email support@sourcesecure.ca. SourceSecure is operated by JOLIVE Labs Inc.