Skip to content

Service providers and processing agreements

Last updated: October 1, 2026

Draft — to be reviewed by a lawyer specialized in privacy law before launch. The "Status" column is maintained by the founder; no agreement is deemed signed until it is checked.

The law requires that information disclosed to a provider (mandatary) be disclosed under a written contract specifying protection measures, use limited to the mandate and destruction at the end of the contract; and, for a disclosure outside Québec, that a privacy impact assessment conclude that protection is adequate (provisions to be verified: ss. 17 and 18.3 of the Act respecting the protection of personal information in the private sector). The platform PIA is kept in docs/legal/EFVP.md.

Provider list

ProviderRoleInformationLocationAgreement to signStatus
Supabase Inc.database, authenticationall database content: accounts, rosters, statistics, audit log, MFA factorsCanada (AWS ca-central-1); staff and subprocessors in the United StatesSupabase Data Processing Addendum (DPA), signed from the dashboard; list of its subprocessors[ ]
Amazon Web Services (Supabase subprocessor)infrastructuresameCanadacovered by the Supabase DPA—
Hostingervirtual private server: application, worker, disk storage of videosvideos, viewing copies, server logs, local backups[Hostinger VPS data centre to be confirmed]Hostinger Data Processing Agreement (terms of service and GDPR annex); confirm the data centre[ ]
Modal LabsGPU computingvideo frames (transient blocks)United StatesModal DPA; confirm deletion of volumes and that data is not logged[ ]
Stripepayments, billingemail, organization name, plan; card data (processed by Stripe only)Canada and United StatesStripe Services Agreement + DPA (accepted with Stripe terms)[ ]
Resendtransactional email (sign-in links, notices)email address, email contentUnited StatesResend DPA[ ]
Google (optional sign-in)identity provideremail, name, Google IDper GoogleGoogle Identity terms; no team data sent[ ]
Cloudflare R2 or OVHcloud (planned)object storage for videosvideos, viewing copiesto be decided (OVHcloud Beauharnois for Canadian residency)DPA of the chosen provider, before going live[ ]
External monitoring provider (planned)uptime checksno personal information (public health endpoint)—none required if no data—

Minimum clauses to check in each agreement

  1. Processing only on UFStats' instructions and for the mandate; no reuse (including no model training by the provider).
  2. Confidentiality of staff and need-to-know access.
  3. Security measures (encryption in transit and at rest, access control, logging).
  4. Incident notice without delay to UFStats (specific deadline, e.g. 72 hours at most).
  5. Subprocessors: list, prior notice of changes, same obligations.
  6. Processing location and transfers; ability to require Canada for the Institution plan.
  7. Destruction or return at the end of the contract, with a certificate on request.
  8. Cooperation with access and correction requests and with investigations by the Commission d'accès à l'information.
  9. Audit right or independent audit reports (SOC 2, ISO 27001).

Record keeping

The founder keeps a PDF copy of each signed agreement (outside Git), the signature date and the annual review date. Any new category of provider requires a PIA update before information is first disclosed.