Sub-processors
The other companies that handle data for CalMonkey, what each one does, and where.
Last updated 8 October 2026
Current list
| Provider | What it does for us | Data it handles | Location |
|---|---|---|---|
| Amazon Web Services | Hosting: servers, database, backups and encryption keys. | All service data, including encrypted calendar credentials and event content (text, guest lists and meeting links). | Sydney, Australia |
| Stripe | Subscription billing and payments. | Customer billing contact, plan and payment details, and the number of connected accounts. No calendar data. | United States |
Google, Microsoft and Apple are not on this list: they are the calendar providers the end user chose, and CalMonkey connects to the user’s own account there on the user’s instructions. We send each provider only the data its row describes. Before a new sub-processor starts handling customer data, we update this page and email the owner of each customer account at least 30 days ahead.
Calendar providers are not sub-processors
Google, Microsoft and Apple hold the calendars your users connect. CalMonkey reads from and writes to those calendars at each user’s direction; the providers do not handle data on CalMonkey’s behalf, so they are not sub-processors. When an application adds guests to an event, the invitation is sent by the user’s own calendar provider, as part of that user’s calendar. Each user’s relationship with their calendar provider is governed by that provider’s own terms.
Changes to this list
We update this page before a new sub-processor starts handling customer data, and change the date at the top. Customers who want to be emailed about changes, or who object to one, can write to privacy@calmonkey.com.