We keep on your device only what is strictly necessary to run the app and — only if you allow it — we measure how it performs and follow your visits to our website. Refusing is as easy as accepting. Read our privacy policy.
Policy version: cookie-policy-2026-10-14
This policy explains what personal data Lume CRM collects, why, how it is protected, and what your rights are. It is designed to comply with Québec Law 25, PIPEDA, and the GDPR.
Lume CRM is operated by William Hébert (sole proprietor), based in Québec, Canada.
Lume plays two distinct roles. For accounts, meaning the owners and members of the businesses that use Lume, their subscription and billing, Lume is responsible for the personal information. For the information a business enters in Lume about its clients, leads and employees, Lume is its service provider: it processes that information on the business's behalf, following its instructions, under the written mandate of the Terms of Service, Law 25 section 18.3. For that information, contact the business first; it remains responsible for collecting it.
Our Data Protection Officer (DPO) can be reached at [email protected].
We collect and process the following categories of data:
Technologies that locate, measure or use artificial intelligence
We only process your data when we have a legal basis to do so:
Account follow-up by our team, on the basis of legitimate interest: every day, aggregated indicators of how your account is used — last sign-in date, number of invoices sent over 7 and 14 days, number of active employees, use of Lumi — and the state of your Lume subscription — failed payment, renewal date, cancellation reason — are sent to GoHighLevel, our team’s tool, so we can help when usage drops. None of your clients’ data, no invoice and no text you typed is part of it.
At any time, you may:
You can exercise these rights from the Privacy Center in your account, or by email at [email protected]. We respond within 30 days.
We only keep your data for as long as necessary:
We share data with the subprocessors below, each bound by a Data Processing Agreement, except the two public services built on OpenStreetMap, OpenStreetMap Foundation and FOSSGIS:
| Subprocessor | Purpose | Location |
|---|---|---|
| Supabase Inc. | Database, authentication, storage | Canada, AWS ca-central-1, Montréal |
| Railway Corp. | Application hosting | United States |
| Cloudflare, Inc. | Delivery network in front of all traffic, attack protection, CAPTCHA | Global, US company |
| Stripe Inc. | Payment processing | United States and international |
| PayPal Holdings | Alternative payments | United States and international |
| Twilio Inc. | Sending and receiving text messages | United States |
| Amazon Web Services, Amazon SES | Transactional email | Canada, AWS ca-central-1 |
| Anthropic, PBC | AI: Lumi, support, website assistant, import assistant | United States |
| Google LLC | Maps, geocoding, voice transcription with Gemini | United States and international |
| Mapbox, Inc. | Maps, fallback geocoding, directions | United States |
| OpenStreetMap Foundation | Last-resort geocoding | Europe |
| FOSSGIS e.V. | Route travel times | Germany |
| Functional Software, Inc., Sentry | Crash reporting, performance measurement | United States |
| Slack Technologies, LLC | Routing support requests | United States |
| HighLevel, Inc., GoHighLevel | Following up demo requests, account usage as aggregated indicators and, with your consent, website visits | United States |
| Upstash | Rate-limiting cache, when enabled | United States and international |
Full, up-to-date list: /subprocessors. We notify you 30 days in advance before adding a new subprocessor that receives personal data.
Integrations you turn on. If your business owner or an admin connects Zapier or Make to Lume, those services receive what your scenarios ask for: your clients’ and leads’ contact details, and the status, amounts and dates of your quotes, invoices and jobs, never your internal notes, custom fields or payment data. They are then your providers, chosen by you, not Lume subprocessors. You can remove this access at any time in Settings › API & MCP.
Our primary database is hosted in Canada, in the AWS ca-central-1 region in Montréal. Our application server and several of our subprocessors process data in the United States. For data subjects in Québec, these transfers are subject to a Privacy Impact Assessment as required by Law 25, art. 17, which we keep on file and make available upon request.
Data is encrypted at rest (AWS KMS / AES-256) and in transit (TLS 1.3). Access is gated by Row-Level Security, role-based access control (RBAC), and optional two-factor authentication. Security incidents are handled per our Breach Response Plan.
Lume connects to Google in two ways, both optional: to sign you in to Lume with your Google account, and to connect Google Sheets, Google Drive and Google Calendar to your automations. Lume only requests permissions limited to your identity, to the files you choose or that Lume creates, and to the calendar Lume creates. Lume requests no access to Gmail: we cannot read, send, or modify your email.
Google permissions requested
Lume requests no other permission from Google. Connecting a Google account is entirely optional, and we only access the data required by the features you enable. The access tokens Google gives Lume for a connected app are stored encrypted and are used only for these operations.
Limited Use (Google API Services User Data Policy). Lume's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Lume uses this information only to provide the features you see: signing you in, reading and writing the files you chose or that Lume created, and keeping the “Lume” calendar up to date. Lume does not transfer it to anyone except to provide these features, for security, when required by law, or with your consent. Lume never uses it for advertising, does not sell it, and does not use it to develop, improve or train artificial intelligence models. No one at Lume reads it, except with your agreement, for security, or when required by law.
Revoking access. You can revoke Lume's access at any time from your Google account, at myaccount.google.com/permissions. The tokens Lume holds then stop working right away, and we delete them on request.
Connecting QuickBooks Online, by Intuit, is optional. Only the owner and admins of a business can connect it, from the Apps page. Lume requests a single permission from Intuit, com.intuit.quickbooks.accounting, which gives access to the accounting of the QuickBooks company you choose when you connect.
What Lume sends to QuickBooks: your invoices (lines, quantities, prices, taxes, number, date, due date and subject), payments received, applied to their invoice with their payment method, and your clients (name, company, email, phone and billing address). An invoice voided in Lume is voided in QuickBooks.
What Lume reads in QuickBooks: only what is needed to avoid duplicates and to offer you the settings, that is, the clients and invoices already there, and your lists of products and services, tax codes, income accounts and payment methods. Lume does not read your other transactions, your reports or your bank accounts.
Retention: the access tokens Intuit gives Lume are stored encrypted and are used only for this sync. Lume also keeps the QuickBooks identifier of the records it created or matched, to update them later, and the status of each send. On disconnect from Lume, Lume revokes access at Intuit and deletes the tokens; after a disconnect from QuickBooks, Lume deletes the tokens as soon as Intuit refuses them. Nothing more is sent. Nothing is deleted in QuickBooks. QuickBooks data is never sold, never used for advertising, and never used to train AI models.
Lume CRM is a professional tool for businesses. The service is not intended for individuals under 16, and we do not knowingly collect personal data about them. If you believe a minor has provided us with data, contact us so we can delete it.
Any material change is announced in-product at least 30 days before it takes effect. The version identifier shown at the top of this page lets you track which version you accepted.
William Hébert
Data Protection Officer
Québec, Canada
Version : privacy-policy-2026-10-28 — Last updated : 2026-10-28.