Data Processing Agreement
The version in force today, at its own permanent address.
Published 13 October 2026 · version dpa-2026-10-13
This is the version in force today, at an address that will keep showing these exact words after the document next changes. Every version.
This Data Processing Agreement ("DPA") is between JOLIVE Labs Inc., 95 King William Court, Cambridge, Ontario N3C 4J3 ("SourceSecure") and [Firm legal name], [address] ("the Firm"). It forms part of the SourceSecure Terms of Service and any Order Form between the parties (together, "the Agreement"), and takes effect on the date it is signed or accepted at checkout. Where it is accepted at checkout, the Firm's name and address are those given on that checkout.
Version dpa-2026-10-13, published 13 October 2026.
1. Roles and laws
1.1 The Firm controls the personal information of its clients and staff that is handled through the Service. SourceSecure handles it only on the Firm's behalf and on its instructions, as set out in this DPA.
1.2 "Privacy Laws" means the Personal Information Protection and Electronic Documents Act (PIPEDA), Quebec's Act respecting the protection of personal information in the private sector (as amended by Law 25), the privacy laws of Alberta and British Columbia where they apply, and any regulations under them.
1.3 "Personal Information" means information about an identifiable individual that SourceSecure handles for the Firm under the Agreement.
2. Instructions
2.1 SourceSecure will handle Personal Information only to provide the Service as the Firm has configured it, as described in Schedule A, and on the Firm's other documented instructions. The Firm's use of the Service's settings (seat types, firm policies, feature switches) counts as its instructions.
2.2 SourceSecure will not sell Personal Information, use it to train AI models, use it for advertising, or combine it with other customers' information, except as counts that identify no firm or person.
2.3 SourceSecure will tell the Firm if it believes an instruction breaks Privacy Laws.
3. Confidentiality and staff
SourceSecure will limit access to Personal Information to the people who need it to run the Service, and bind them to confidentiality.
4. Security
SourceSecure will maintain the safeguards in Schedule B, appropriate to the sensitivity of the information, and will not materially weaken them during the term.
5. Subprocessors
5.1 The Firm authorises the subprocessors listed in Schedule C. SourceSecure will bind each by written contract to protect Personal Information at least as well as this DPA requires, and remains responsible for them.
5.2 SourceSecure will email the Firm's admins at least 30 days before adding or replacing a subprocessor. If the Firm objects on reasonable privacy grounds and the parties cannot resolve it, the Firm may terminate the affected Service and receive a refund of fees prepaid for the period after termination.
6. Security incidents
6.1 If SourceSecure learns of a breach of security safeguards involving Personal Information, it will notify the Firm's admins without undue delay and in any case within 72 hours, with what is known at the time: what happened, what information and whose, the likely consequences, and what is being done.
6.2 SourceSecure will update the Firm as it learns more, cooperate with the Firm's assessment of whether there is a real risk of significant harm (or, under Law 25, a risk of serious injury), and help the Firm notify regulators and individuals where required. SourceSecure will keep a record of every breach for at least 24 months. How it responds is set out in its incident and breach response policy at sourcesecure.ca/incident-response.
6.3 Notice of a breach is not an admission of fault.
7. Requests from individuals and regulators
7.1 If an individual asks SourceSecure to access, correct or delete their Personal Information, SourceSecure will refer them to the Firm and help the Firm respond within the time Privacy Laws require.
7.2 If a regulator or law enforcement body asks SourceSecure for Personal Information, SourceSecure will tell the Firm first unless the law forbids it, and disclose no more than is legally required.
8. Location and transfers
8.1 SourceSecure stores Personal Information in Canada (Montreal). It will not move stored Personal Information outside Canada without telling the Firm at least 30 days beforehand.
8.2 Some subprocessors process information in the United States, as listed in Schedule C. In particular, redacted text for the optional AI features is processed by OpenAI in the United States, email delivery by Resend, and payments by Stripe. The Firm acknowledges this and confirms it has given any notice its staff and clients require. A Firm that does not want any such transfer can buy Guard seats, which include none of these features; each person can switch prompting tips off for their own browser, which stops all of them except a question that person chooses to put to Ask SourceSecure; and a Guard Enterprise team head can switch the Living Vault off for the Firm, which stops Ask SourceSecure and the other Living Vault features.
8.3 SourceSecure will provide the information the Firm reasonably needs to complete a privacy impact assessment.
9. Return and deletion
Within 30 days after the Agreement ends, SourceSecure will delete Personal Information from its systems, except invoices and records the law requires it to keep, which it will continue to protect under this DPA. Until then, the Firm's admins may download an export of the Firm's records, as one file, from the team page. The Firm's owner may also delete the Firm's records at once from the team page, which ends the Agreement. What is kept after deletion is set out in Schedule A. The Living Vault is held only on people's own computers and is not in SourceSecure's systems.
10. Assurance
Once a year, on written request, SourceSecure will answer the Firm's reasonable security questionnaire and provide a current summary of its safeguards. Any further audit will be at the Firm's cost, on 30 days' notice, during business hours, and subject to confidentiality.
11. Liability and precedence
11.1 Each party's liability under this DPA is subject to the limits in the Terms of Service.
11.2 If this DPA conflicts with the rest of the Agreement on the handling of Personal Information, this DPA wins.
11.3 This DPA lasts as long as SourceSecure handles Personal Information for the Firm.
Schedule A: Processing details
| Category | Details |
|---|---|
| Individuals concerned | The Firm's staff who use the Service; the Firm's clients and other people named in what staff type or attach on AI chat sites |
| Purpose | Detecting and redacting sensitive information before it reaches AI chat tools; coaching; reply marks; the Living Vault, Ask SourceSecure and Add notes; team administration; billing; support |
| Content of messages and files | Read on the person's own computer. Files are not sent to SourceSecure. Message text is sent only as the redacted extracts below |
| Redacted extracts | For coaching, reply marks, vault facts, the weekly note, Ask SourceSecure, saved chat and meeting summaries, and Write background in Add notes: text from the person's messages, the AI's replies and, for the Guard Enterprise features, passages from their Living Vault, with the names and numbers found replaced by stand-ins on the device. Processed by SourceSecure's server and OpenAI. Not stored by SourceSecure. Sent to OpenAI with OpenAI's storage option off. OpenAI may keep its own abuse-monitoring logs of these requests for up to 30 days under its standard API terms; SourceSecure has asked OpenAI for zero data retention |
| Staff account information | Email address, team, seat type, invitations, and a request a person makes to their admin for a better seat. Kept until the person is removed from the team or the Firm's records are deleted (section 9) |
| Catch records | When, which AI site, the kind of detail, the action taken, and a masked form made on the device (for example •••• 4242), which keeps the last few digits of a number or the initials of a name. Kept 90 days from receipt |
| Protection records | When protection was paused or switched off, and for how long. Kept 90 days from when the pause began |
| Usage and habit counts | Daily counts of catches and feature use per browser, including counts per supported AI site and the habit each person is working on; no text. Shown to the Firm's admins for the Firm or for one person. Kept while the Firm's account is active |
| Firm records | Firm profile (with version history, and facts staff suggest for it), shared terms, firm playbook (no client information permitted), all as typed by the Firm's admins. Kept until the Firm's records are deleted |
| Billing and agreement records | The Firm's billing name and address as given at checkout; the versions of the Terms of Service, this DPA and the Acceptable Use Policy the Firm agreed to, when, and the email address of the admin who agreed; whether a payment is being retried; and which notices of a change SourceSecure emailed the Firm's admins, when, and to which addresses. Kept until the Firm's records are deleted |
| Record of a deleted Firm | The Firm's name, its Stripe identifiers, what it bought and when, the versions it had agreed to, and how many records were deleted. Names no person. Kept 7 years after the deletion, as the record of a sale |
| Trial marker | Where the Firm had the free trial, a one-way key made from the buyer's email address, so the trial is given once. Kept 3 years |
| Browser credential | A per-browser secret, stored only as a one-way hash |
| Living Vault | Encrypted on the person's own computer. Not held by SourceSecure. Passages are processed only as redacted extracts, above |
| Server logs | Request counts, timings and errors; no message text. Kept 30 days, in Montreal |
Schedule B: Security measures
- Encryption of all traffic (TLS) and of stored data at rest; the Living Vault encrypted on the device with a key the browser does not release.
- Detection, redaction and file reading performed on the user's device; only redacted text is sent for AI features, and the server checks again for an email address, a phone number or a long number and refuses the request if it finds one.
- Hosting on Google Cloud in Montreal, with database delete protection and 7-day point-in-time recovery.
- No downloadable server credentials; secrets held in Google Secret Manager; two-step verification on all administrative accounts.
- Access to production limited to SourceSecure's operators; every firm's data separated, with automated tests that one firm cannot reach another's records.
- Security headers on the website, a published vulnerability disclosure policy (security.txt), and periodic automated security scans.
- A written incident and breach response policy, published at sourcesecure.ca/incident-response, and a breach register, with breach records kept for at least 24 months.
Schedule C: Subprocessors
| Subprocessor | Purpose | Information | Location |
|---|---|---|---|
| Google LLC (Google Cloud, Firebase) | Hosting, database, sign-in, server functions, logs | All stored records in Schedule A; redacted extracts in passing, not stored | Database and server functions: Montreal, Canada. Website delivery and sign-in: Google's network |
| OpenAI, L.L.C. | AI features: coaching, reply marks, vault facts, weekly note, Ask SourceSecure, chat and meeting summaries, Write background | Redacted extracts only; sent with OpenAI's storage option off. OpenAI may keep its own abuse-monitoring logs for up to 30 days under its standard API terms; SourceSecure has asked OpenAI for zero data retention | United States |
| Stripe, Inc. | Payments and subscriptions | Buyer name, email, card and billing address | United States and Canada |
| Resend (Plus Five Five, Inc.) | Sign-in, invitation, report, subscription, payment and notice emails | Recipient email addresses and email contents (no chat text) | United States |
| Cloudflare, Inc. | The domain's addresses (DNS), and forwarding of email sent to support@sourcesecure.ca to SourceSecure's mailbox | Whatever a person writes to support@sourcesecure.ca, in passing | United States, and Cloudflare's global network |
Signatures
| JOLIVE Labs Inc. (SourceSecure) | [Firm legal name] | |
|---|---|---|
| Signature | ______________________ | ______________________ |
| Name | Jacob Oliveira | [name] |
| Title | President | [title] |
| Date | [date] | [date] |
Getting in touch
Email support@sourcesecure.ca. SourceSecure is operated by JOLIVE Labs Inc.