|The free version||The complete version||On-demand version|
This article describes Waldo's architecture and data privacy.
1 - Architecture.
Waldo is a multi-tenant SaaS application. To simplify, think of Waldo as a website that is displayed in your Microsoft Teams.
Waldo's architecture relies on the following components:
- Microsoft Azure Active Directory
- Microsoft Azure Storage
- Microsoft Azure Bot Service
- Microsoft Azure App Service
- Power BI
- Microsoft Graph
- Microsoft App Insights
- Microsoft Event Hub
- Microsoft Azure functions
Users interact with Waldo via a Teams Personal App composed of a tab and a bot.
The Azure Events Hub dispatches events to subscribers and processes the events (change seats, change parking spot, check-in). Third-party integration (e.g. Exchange Calendar integration) can also generate events.
Data is stored in specific containers for each tenant.
Users can view and analyze data via a Power BI connector.
2 - Data
Data is stored on Microsoft Azure (as explained above) in a multi-tenant environment. Still, we do not store any information related to customers or users (neither email nor names).
We only store User IDs. Once a user is authenticated through its Azure Active Directory, they make the relation between User Azure IDs and usernames. The same logic applies for areas and offices.
3 - Encryption and network.
3.1 - Data at rest:
3.2 - Data in transit:
3.3 - Network:
4 - Consent.
You can refer to this documentation if you want to learn more about consent.
5 - URLs.