Privacy policy

Clarity about your data.

Effective September 15, 2026

This policy explains what Shadow handles when you use our site, desktop app, and workspace.

01 / Information we collect

Information needed to operate Shadow.

Depending on how you use Shadow, we may process:

  • Account and workspace information, such as your name, email address, organization membership, and authentication records.
  • Captured work evidence you choose to collect, which may include screenshots, application and page context, window titles, URLs, and activity events.
  • Derived results, including batch analyses, reconstructed workflows, recurring patterns, and evidence links.
  • Device, diagnostic, and usage information used to deliver, secure, troubleshoot, and improve the service, including whether the desktop app's screen recording, accessibility, and input monitoring permissions are turned on (yes or no only), and the approximate location (city and country) of the connection a device last used, worked out from its network address when it connects. We do not store the network address itself, and we do not collect precise or GPS location.
  • Website and workspace analytics, including pages visited, referral and campaign URLs, links and controls used, entered noncredential field values, submitted form values, request and action outcomes, error details, and session recordings. These records may include text entered on the public website and in the authenticated workspace, even when no session recording is available.
  • Messages you send when you request support or otherwise contact us.
02 / How we use it

We use information to provide the product.

We use information to authenticate users and devices, deliver captured evidence to the correct workspace, reconstruct work, surface recurring processes, maintain the service, answer support requests, prevent abuse, and comply with legal obligations.

Shadow's suggestions are review tools. They do not automatically execute changes or make employment decisions.

03 / How we share it

We do not sell personal information.

We may share information with infrastructure, hosting, storage, authentication, analytics, and AI service providers that help us operate Shadow; with workspace members according to their access; when you direct us to; or when required to protect rights, safety, and the service or comply with law.

If Shadow is involved in a merger, financing, acquisition, reorganization, or sale of assets, information may transfer as part of that transaction subject to appropriate safeguards.

04 / Your controls

You control collection.

You can pause desktop capture and configure supported exclusions for displays, window titles, and browser URL patterns. Workspace access is tied to authenticated user and organization membership.

Capture can include sensitive material visible on your screen. Review your capture settings and follow your organization's policies before recording.

What Shadow captures, and what it does not

Shadow captures what is on your screen, which can include sensitive material such as banking, health or sign-in details. By design we do not record password-field typing or raw keystrokes. You and your organization can block apps and sites, such as your bank or patient system, and blocked ones are not captured. Screenshots and the text extracted from them are processed by AI providers.

  • Shadow does not record what you type into password fields: not the value, not its length. This matches fields by a label or role containing "password" or "passcode"; an unlabelled field, or a password shown on screen, is not covered.
  • Shadow does not send raw keystrokes or clipboard contents. Grouped text edits and derived actions are sent.
  • Passwords, tokens and credentials in web addresses are removed before capture. This works from a list of key names; paths and other parameters stay.
  • Sign-in and lock screens, system security prompts and DRM-protected video are not captured. Password managers, banks and health sites are not excluded by default.
  • You and your organization can exclude any app or website; excluded visits keep only the app name or site hostname, visible to admins only. Nothing is excluded until it is added, and Shadow does not detect categories of sites.
05 / Retention and security

We limit access and retain data as needed.

We retain information for as long as needed to provide Shadow, maintain legitimate business records, resolve disputes, enforce agreements, and meet legal obligations. Retention can vary by record type, workspace configuration, and account status.

We use administrative, technical, and organizational safeguards designed to protect information. No method of storage or transmission is completely secure.

06 / Your choices and rights

Ask us about your information.

Depending on where you live, you may have rights to access, correct, delete, restrict, or receive a copy of personal information, or object to certain processing. We may need to verify your identity and consider workspace ownership and legal retention duties before completing a request.

Our services are not directed to children under 13. We may update this policy as Shadow changes; the effective date above shows the latest revision.

07 / Slack integration

What Shadow does with Slack data.

Shadow connects to Slack only when an organization owner installs the integration and selects channels. Everything below applies only to organizations that have connected Slack.

Permissions and access

Shadow requests read-only Slack permissions: channel history, file downloads, member profiles (name, email, avatar), and reactions. It requests no posting or messaging scopes; it cannot write to Slack or act on anyone's behalf.

Shadow reads only the channels an organization owner selects in the dashboard. Events from channels outside that selection are dropped without storage.

What is stored

Shadow stores message text, file metadata, and reactions from selected channels, along with member names and email addresses, in Shadow's PostgreSQL database. File content (documents and, when the feature is enabled, image descriptions) is extracted and stored for analysis. OAuth tokens are encrypted at rest with AES-256-GCM before database storage.

AI processing

Slack message content and extracted file text are sent to language models through OpenRouter to reconstruct workflows and recurring processes.

Who can see findings

Slack findings are visible to organization owners and admins. Plain members do not have access to the Slack analysis views.

Disconnection and deletion

When Slack sends an app_uninstalled or tokens_revoked event, Shadow revokes the connection record but does not automatically delete previously ingested messages or analyses. When an organization is deleted through Shadow's admin tools, all service data including Slack findings is deleted and OAuth tokens are revoked with Slack before the records are removed.

Contact

Questions about Slack data: use the contact details below.

08 / Contact

Questions or requests.

Email hello@aalpha.ai with "Shadow privacy" in the subject line.