1. Overview
This Privacy Policy covers the AppConfig² Suite as a whole — the suite landing page and the shared infrastructure and practices that apply across all tools. Each individual tool in the suite has its own specific Privacy Policy that describes in detail what data that tool accesses and how it handles it. This document is the right starting point if you are new to the suite or want to understand what all tools have in common.
Suite-wide Privacy Principle: Every tool in the AppConfig² Suite operates as a browser-based application. All data processing occurs locally in your browser and directly between your browser and Microsoft services — no tenant data is routed through AppConfig² infrastructure during normal operations. Your Microsoft Entra ID data stays in your tenant.
2. Tools in the AppConfig² Suite
The AppConfig² Suite consists of the following tools. Their Graph API access levels differ significantly — please consult each tool's specific Privacy Policy before granting consent.
| Tool | Graph API Access | Privacy Policy |
|---|---|---|
| AppConfig Full application configuration management, backup & restore, auth flow testing. |
Read + Write Can create, modify, and delete Entra ID objects. Optional backend endpoint for client credentials testing. |
AppConfig Privacy Policy |
| AppTesting Read-only analysis, auth flow testing, token decoding, and permission inspection. |
Read only No write operations on Entra ID. Optional backend endpoint for client credentials testing. |
AppTesting Privacy Policy |
| AppDashboard Security analytics dashboards — credential hygiene, posture scoring, attack surface mapping. |
Read only No write operations. No backend endpoints. Pure static SPA. |
AppDashboard Privacy Policy |
| AppTooling Focused administration tools — consent management, credentials, manifest editor, Graph Explorer. |
Read + Write Write operations require explicit confirmation. JIT scope consent. No backend endpoints. |
AppTooling Privacy Policy |
Each tool's Privacy Policy contains the authoritative and complete description of what that tool accesses, stores, and transmits. This suite-level document covers only what is common to all tools.
3. Common Architecture & Data Practices
The following practices apply to every tool in the AppConfig² Suite:
3.1 Authentication
- All tools authenticate via Microsoft Entra ID using the MSAL.js library with Authorization Code Flow + PKCE — no implicit flow, no embedded client secrets
- Authentication tokens are managed entirely by MSAL.js and stored in browser sessionStorage (per-tab isolation) — never transmitted to AppConfig² servers
- AppConfig² never sees or handles your password, MFA challenge, or Entra ID directory credentials
3.2 Data Access
- All Microsoft Graph API calls occur directly between your browser and Microsoft's Graph API endpoints
- No tenant data passes through AppConfig² servers during normal read or write operations
- The specific data accessed varies by tool — refer to each tool's Privacy Policy for the complete list
3.3 No Server-Side Tenant Data Storage
- No tool in the suite stores your tenant data, application configurations, tokens, or user information on AppConfig² servers
- Exception — AppConfig and AppTesting: Both tools include an optional Auth Flow Tester that uses an Azure Function (
/get-token) to securely proxy client credentials to Microsoft's token endpoint. This is required by the OAuth 2.0 specification and processes credentials in-memory only, never logging or storing them. See the respective tool's Privacy Policy for full details.
3.4 No Third-Party Analytics or Advertising
- No tool in the suite uses third-party analytics, advertising, or tracking services
- No tenant data is shared with any party other than Microsoft for the purpose of authenticating you and executing Graph API calls you initiate
3.5 Tenant Allowlist Access Control
- All tools use a secure allowlist system — only pre-authorised organisation tenants can access each tool
- To request access, email support@appconfig.eu with your tenant ID and organisation details
4. Browser-Side Storage
Each tool uses browser-side storage mechanisms to support its functionality. No browser-stored data is transmitted to AppConfig² servers.
- sessionStorage: Authentication tokens and session state. Isolated per browser tab and automatically cleared when the tab is closed.
- localStorage: Used by some tools for user preferences (e.g., dark/light theme), caching, and — in AppTooling — application configuration backup snapshots. See each tool's Privacy Policy for specifics.
You can clear all browser-stored data at any time through your browser settings.
5. Cookies
The AppConfig² suite landing page and tool pages use essential session cookies required for the site to function. We do not use advertising, analytics, or cross-site tracking cookies.
6. Third-Party Services
The AppConfig² Suite integrates exclusively with Microsoft services:
- Microsoft Entra ID: Authentication and identity management (direct browser-to-Microsoft connection)
- Microsoft Graph API: Accessing and operating on tenant data (direct browser-to-Microsoft connection)
- Azure Static Web Apps: Hosting for all suite tools (static asset delivery only)
- Azure Functions: Optional
/get-tokenendpoint used by AppConfig and AppTesting for client credentials flow testing — processes credentials in-memory only - Azure Application Insights: Application health monitoring where applicable — no personal or tenant data collected
7. Data Retention
No tool in the suite retains tenant data on AppConfig² infrastructure. Session data is discarded when your browser tab is closed. The only exception is operational logs from the optional /get-token Azure Function (AppConfig and AppTesting), which record non-sensitive metadata (client ID, timestamp, success/failure status — never secrets or tokens) and are retained per Azure platform defaults (typically 30–90 days). See the relevant tool's Privacy Policy for full details.
8. Your Rights & Control
- Revoke any tool's access at any time via Microsoft Entra Admin Center → Enterprise Applications → [Tool Name] → Permissions → Revoke consent
- All your data remains in your Microsoft Entra ID tenant — no vendor lock-in
- Contact us for privacy-related questions or data processing inquiries
9. Compliance
The AppConfig² Suite is designed with GDPR's data minimisation and storage limitation principles in mind. Because no tenant data is transferred to or stored by AppConfig² infrastructure (beyond the limited operational logs noted above), there is minimal data controller/processor relationship to establish beyond what already exists between your organisation and Microsoft. The AppConfig² Suite builds on Microsoft's security and compliance foundation, inheriting the certifications that apply to your Entra ID environment.
10. Changes to This Policy
We may update this Privacy Policy to reflect changes in the suite's tools, features, or applicable regulations. Significant changes will be communicated through in-application notifications and updates posted on this page. Continued use of any AppConfig² tool after such updates constitutes acceptance of the revised policy.
11. Contact
For privacy-related questions or concerns about the AppConfig² Suite:
- Privacy: privacy@appconfig.eu
- General Support: support@appconfig.eu
- Response Time: We aim to respond within 72 hours
EU data subjects have the right to lodge a complaint with their local supervisory authority if they believe their privacy rights have been violated.