DRAFT — FOR LEGAL REVIEW. NOT YET IN EFFECT.
Prepared for LeadQor Canada Inc. [incorporation pending]. To be verified by counsel before publication.
Last updated: [DATE] · This page is referenced by Annex C of the LeadQor Data Processing Addendum (DPA).
What is a subprocessor?
LeadQor is the processor of the personal data you store in the platform — your customers' names, contact details, service history, communications, and invoices. To run the platform, we rely on a small number of carefully chosen third-party providers who process some of that data on our behalf. Those providers are called subprocessors.
Every subprocessor is bound by a written contract requiring data-protection and security obligations materially as protective as the ones we owe you under the DPA. We remain responsible to you for their performance.
Our commitment on changes
Before we add or replace a subprocessor, we will:
- update this page, and
- notify your account owner by email and/or post a prominent notice here, at least 30 days before the new subprocessor starts processing personal data (except urgent changes needed for security or service continuity, which we will notify as soon as reasonably possible).
If you object on reasonable data-protection grounds, email [privacy@leadqor.com] within 30 days of the notice. The objection process is described in Section 9 of the DPA.
Current subprocessors
| Subprocessor | What they do for the platform | Data processed | Location of processing |
|---|---|---|---|
| Supabase, Inc. | Primary database, authentication, and file storage | All tenant data stored in the platform (customer records, communications, invoices, files) | United States |
| Vercel, Inc. | Application hosting and content delivery (CDN) | Tenant data in transit through the application; logs | United States |
| Stripe, Inc. | Payment processing (Stripe Connect) | Payment and payout data for tenants and their customers. Note: for payment processing, Stripe also acts as an independent controller under its own terms and privacy policy; card data is handled by Stripe and is not stored by LeadQor. | United States |
| RingCentral, Inc. | SMS and voice communications sent and received through the platform | Phone numbers, message content, call logs, and call recordings (where enabled) | United States |
| Cloudflare, Inc. | Network security, and encrypted offsite backup storage (R2) | Traffic metadata; encrypted backup copies of tenant data | United States |
| [Brevo / Resend — TBD] (placeholder) | Transactional and platform email delivery | Recipient email addresses, email content, delivery metadata | [United States / EU — TBD] |
| Google LLC | Google Business Profile integration (review management) | Review content and business-profile data for tenants who connect their Google account. Per-tenant connection authorized by the tenant; Google acts under its own terms for its services. | United States |
| Meta Platforms, Inc. | Facebook/Meta Lead Ads integration (lead capture) | Lead form submissions (name, contact details) for tenants who connect their Meta account. Per-tenant connection authorized by the tenant; Meta acts under its own terms for its services. | United States |
| [AI model provider — TBD] (placeholder) | Powers optional AI features (e.g., drafting suggestions, summaries) | Only the content submitted to an AI feature when a tenant uses it. Tenant data is not used to train the provider's models. | [United States — TBD] |
Bracketed entries are pending final vendor selection and will be confirmed, with full entity names, before this page goes live.
Change log
| Date | Change |
|---|---|
| [DATE] | Initial publication of this list. |
Future changes will be recorded here with the date, the subprocessor affected, and the nature of the change (added, replaced, removed, or updated details).
Questions about this list or our subprocessors: [privacy@leadqor.com].