AEPilotProduct overview

aepilot / privacy

Local execution and explicit data boundaries.

AEPilot is designed around user-owned model access, minimal collection, inspectable context, and clear separation between the website, After Effects, and external providers.

The public website

The marketing website does not need access to After Effects projects, provider credentials, chat transcripts, or local AEPilot data. Visiting public pages sends the ordinary technical information required to deliver a website, such as an IP address, request headers, requested URL, and timing information. This may appear in short-lived infrastructure logs used for reliability and security. The site does not advertise third-party tracking or behavioral advertising.

The private-preview form currently validates an email address in the browser and displays a confirmation state. It does not submit the address to a server or subscribe the visitor to a mailing list. Until a real enrollment backend and retention policy are published, use the contact page to request access.

The AEPilot application

AEPilot is BYOK-first. Provider credentials are stored locally by the application, and requests go from the user's machine to the provider or compatible local endpoint the user selected. AEPilot does not operate a mandatory cloud relay for project execution.

When a cloud provider is used, prompts and selected project context are processed under that provider's terms and privacy policy. Users should review those policies before sending confidential client information. Tool calls that inspect or change a project run through the local After Effects integration, and the product is designed to expose the context sent to the model and avoid logging secrets.

Your choices and contact

Users remain responsible for protecting local files, provider accounts, exported transcripts, reports, and any project data shared for support. For privacy questions or deletion requests concerning information deliberately sent by email, contact maksesipov@gmail.com. Do not include passwords, provider keys, access tokens, or confidential project files in the first message.

Last updated: 2026-09-03.