Privacy Policy
Effective August 30, 2026 · Applies to the ESC·ALATE apps for iPhone and Mac
ESC·ALATE is an employee-only operations app for ESCALATE ENTERPRISES and authorized Comparsa team members. Access requires a company-provisioned Microsoft work account. The production app connects only to the ESC·ALATE service operated by the organization. There is no public registration, public demo, or custom server connection.
What the app itself collects
The app contains no advertising, no tracking SDKs, and no third-party analytics. It transmits dashboard and requested feature data to the organization-operated ESC·ALATE service after employee authorization. There is no separate developer telemetry.
Employee authorization
ESC·ALATE uses Microsoft Entra to verify your work identity and whether it has been provisioned in the Comparsa tenant by immutable account ID or assigned ESC·ALATE employee role. Personal Microsoft accounts and unprovisioned identities are not accepted. An email address or domain alone never grants access.
What is processed and where
- Dashboard content you enter: tasks, calendar items, courses, habits, training sessions, job-search records, venture boards, budgets and goals are stored in the organization-operated service and cached on your device so the app opens offline. The local cache is protected by iOS Data Protection on iPhone, and restricted to your user account on Mac.
- Contact details and application answers: job-search records hold contact names, emails, and phone numbers you type in, and the Application Vault holds your own contact details plus the equal-opportunity answers job applications ask for (such as gender, ethnicity, veteran and disability status). Vault answers are encrypted on your device before they are sent to the organization-operated service.
- Voice audio: while you are actively in a voice session with Atlas (the built-in assistant), microphone audio is sent to the organization-operated service for transcription and a spoken reply. The app never records in the background.
- Microsoft authorization: the app uses your work-account identifier and a temporary authorization credential to maintain employee access. The native app stores its current authorization credential in the device Keychain.
Content processed by the organization-operated service is used solely to provide ESC·ALATE, including AI features such as assistant chat, transcription, and text-to-speech. It is never sold, never used for advertising, and never shared beyond the service providers needed to operate those features.
Retention and deletion
Signing out ends the active ESC·ALATE session and hides the dashboard. If no unsynced edits remain, the local dashboard cache is removed. If unsynced edits exist, the app retains a protected local cache on that device to prevent data loss; it is available only after the same authorized employee signs in again. Dashboard content on the organization-operated service is retained until you or your administrator delete it. Contact the address below to request deletion.
Children
ESC·ALATE is a workplace tool and is not directed to children under 13.
Changes
If this policy changes, the updated version will be posted at this address with a new effective date.
Contact
Privacy questions or deletion requests: admin@escalate-enterprises.com
Agent Hub privacy addendum
October 17, 2026 · Applies to the private Agent Hub integration for Microsoft Teams and local coding agents, operated by Escalate Enterprises LLC. The preceding native-app policy continues to describe the ESC·ALATE iPhone and Mac apps.
Teams chat access and purpose
In a personal Teams chat, Agent Hub receives messages sent directly to the bot. When Agent Hub is installed in a Teams group chat with the required consent, Microsoft can deliver that chat’s messages to the bot, including messages that do not mention it. Agent Hub checks the Microsoft-signed request, tenant, configured chat scope and sender’s Microsoft Entra object ID. Only allowlisted human messages from its bound chat are forwarded to the local conversation relay. Other activities are dropped with a generic diagnostic that does not include their message content. An allowlist controls forwarding; group-chat installation permission grants the bot access to receive messages in the selected group chat.
Information processed and stored
The local relay stores accepted message text, sender display names and identifiers, roles, agent names and kinds, routing recipients, thread names, timestamps and message identifiers in a SQLite database on the operator’s computer. Bot state stores the group-chat conversation reference, including conversation, tenant, bot and service identifiers, and the delivery cursor needed to send replies. Credentials are kept separately from the conversation. The Teams app package contains no credentials. Connected agents receive the relay access credential needed for MCP; Microsoft application credentials and the bridge credential are not shared with them.
Who receives the conversation
Authorized local coding-agent sessions can read relay messages through MCP. Agent messages are sent through Microsoft’s bot service into the bound Teams chat, where all chat participants can see them. Recipient labels route agent inboxes; they do not make a Teams card private. Microsoft Teams, Entra, Azure Bot Service and, when enabled, Microsoft Dev Tunnels process authentication and message transport under their applicable terms and your organization’s settings.
Agent Hub’s relay does not itself call a model API. A coding-agent application connected by the operator may send messages it reads to its own AI service under that application’s account, settings and provider terms. The operator must assess those services before connecting an agent or sharing confidential content. Agent Hub does not include advertising or an advertising analytics integration, and its conversation database is not sold or used by Agent Hub for advertising.
Retention, controls and deletion
Local relay history and bot state remain on the operator’s computer until the operator removes them; Agent Hub does not automatically expire this history or encrypt its database separately from the computer’s storage protections. Backups and copies may remain. An allowlisted human can use /stop to pause new agent posts in a thread and /resume to reopen that thread. These commands do not cancel work already running in another application.
Removing the bot from the chat or stopping its tunnel stops that route for future messages. Neither action erases existing local history or messages already posted to Teams. Microsoft Teams retention and deletion follow the organization’s Microsoft settings. Contact admin@escalate-enterprises.com for access, privacy or deletion requests concerning the organization’s Agent Hub instance.