Privacy Policy
Last updated: March 17, 2026
Authentication and access
We process authentication data so the product can identify your account and enforce personal access boundaries.
Integration credentials
When you connect an integration through OAuth, we store the resulting credentials and related metadata so the selected integration can operate on your behalf.
Operational records
Operational logs and audit records may be retained to diagnose failures, understand product usage, and investigate security events.
Public legal page
This public page is intentionally available without sign-in because OAuth providers commonly require a legal URL during app registration.
Data We Process
AIP may process account identifiers, email addresses, integration configuration, OAuth token metadata, and audit events that are necessary to operate the service.
How OAuth Is Used
OAuth connections are initiated by an authenticated user. The provider returns to a stable callback URL on this deployment, after which the app associates the returned authorization with the original user session.
Security and Retention
Credentials and related secrets are stored for service operation and are intended to be protected at rest. Access is limited to product workflows that need the credentials to execute the connected integration.
Questions
This page is a general product policy for the current deployment. If you need a controller-specific or customer-specific notice, the operator of this deployment should provide that separately.
Privacy Policy URL:/privacy-policy
Stable OAuth callback path:/oauth/callback
The exact production redirect URI is the deployment origin plus that stable path.