Every third party that handles data for WorkAndGo, what it is used for, and where it operates. We publish this rather than send it on request, because an enterprise review asks for exactly this list and having it already published is a stronger position than producing it when asked.
| Provider | What we use it for | Where |
|---|---|---|
| MyAndGo | Your organisation and your subscription | Australia (Sydney) |
| Google (Firebase Authentication, through MyAndGo) | Sign-in identity: your name, email address and sign-in method | United States |
| Google Cloud | Runs the application; stores your files, screenshots and call recordings; holds our secrets | Australia (Sydney) |
| MongoDB Atlas | The database: messages, HR records, timesheets, rosters and activity records | Australia (Sydney) |
| Our AI assistant | Jeeves, the in-app assistant | Australia (Sydney) |
| AI quiz content | Writes the general-knowledge questions for the daily games. General-knowledge questions only, no customer content. | United States |
| Twilio | The in-app softphone: connecting calls and call records | United States |
| SendGrid | Transactional email: invitations, notifications and digests | United States |
| Apple | Push notifications to iPhones and iPads | United States |
| Google (Firebase) | Push notifications to Android devices | United States |
| Browser push services | Push notifications to a browser, run by the browser's own vendor | Varies by browser |
| Sign-in, and calendar sync if a person connects it | Their global services | |
| Microsoft | Sign-in, and calendar sync if a person connects it | Their global services |
| Xero | Payroll export, if your organisation connects it | Xero's own locations, only if your organisation connects it |
| Giphy | GIF search, when someone searches for a GIF | United States |
| Stripe, through MyAndGo | Subscription payments for your plan. No card details pass through WorkAndGo. | United States |
Two services look as though they belong here and do not, and the reason in each case is that no customer data reaches them.
Our news source. The news feed pulls headlines in on a schedule. Data comes in and nothing about you goes out, so it is a content source rather than a processor of anybody's data.
Accounting providers we support but are not connected to. A provider only appears above once a connection can actually be made. Integration code that cannot authenticate moves no data, and we would rather this list name what is live than what is possible.
A stale list is worse than no list, because it is a published statement about where your data goes. Our build fails if the application talks to a third party this page does not name, so the page cannot quietly fall behind the code. If you would like to be told when it changes, email support@workandgo.com.au.
For where your content is stored, see data residency.
Yes. Every third party that handles WorkAndGo data is named on our sub-processors page, with what it is used for and where it operates. We publish it rather than send it on request.
No. Your content is stored in Australia, in Google Cloud and MongoDB Atlas in the Sydney region. The providers that operate outside Australia handle sign-in, payments, notification email and push notifications, and none of them is where your content is kept.