Skip to content
Trust & Legal

Providers & subprocessors

The services involved in the current application and infrastructure.

Montréal, Québec, CanadaUpdated

Know who supports the service.

Google / Firebase — authentication

Integration in the application: sign-in, account identity, and password recovery. Information can include email address, display name, account identifiers, and authentication-related technical information. Actual use depends on the configured Firebase project.

Google Cloud — application infrastructure

Role: application hosting, PostgreSQL storage, operational logging, secrets, and backups. Cloud Run, Cloud SQL, and database exports are configured in Montréal (northamerica-northeast1). Learning and account records are processed by these services. Firebase Hosting uses global delivery; authentication and other provider processing may occur elsewhere. No Canadian-only residency commitment is made by this list.

Stripe — payments when enabled

Integration in the application: hosted subscription checkout, invoices, payment-method updates, and cancellation. Stripe receives the information necessary to process payments and manage the billing relationship. LetsConfigure stores related identifiers and subscription state instead of full card numbers.

Roles and changes

This is a service-provider disclosure for the launch configuration, not a claim that every provider is a subprocessor in every legal context. The provider’s role depends on its service and applicable agreement. Confirm the active providers, regions, and contractual roles before a business deployment; this list should be updated when that configuration changes.