These are the third parties that process personal data on our behalf so myChap can run. Each is bound by contract to use the data only to provide the service it provides to us.
We give at least 30 days' notice before adding a new sub-processor that handles personal data. Chapters that want that notice by email should write to legal@mychap.net.
| Provider | What it does | Data involved | Region |
|---|---|---|---|
| MongoDB Atlas | Hosts the primary database | The records described in section 3 of the Privacy Policy | India |
| Amazon Web Services — S3 | Stores files and images uploaded to the Service | Profile photos, gallery images, program documents, Knowledge Library files, CVs | India (Mumbai) |
| Amazon Web Services — Simple Email Service | Delivers sign-in codes, service notifications, billing emails and chapter broadcasts | Your email address and the content of the message | India (Mumbai) |
| Razorpay (including Razorpay Route) | Collects subscription payments and program registration fees, and settles collected fees to chapter accounts | Payer name and contact, amount, gateway payment identifiers; chapter account holder name, account number and IFSC code | India |
| Google Firebase Cloud Messaging | Delivers push notifications, when you have enabled them | Your device's push token and the content of the notification | Global |
| Cloudflare | Domain routing and protection against attacks | IP address and request metadata in transit | Global edge network |
Caching and internal messaging layers run as part of our own infrastructure rather than as third-party services, and are not sub-processors.
When a provider is added, replaced or removed, we update this page, change the effective date above, and keep the previous version in our archive. Material changes are also notified to chapters in advance under the Master Service Agreement.
Questions about this list — legal@mychap.net
How each category of data is used is explained in the Privacy Policy.