1. What We Collect

Website analytics

aidenapp.org uses two analytics tools. Umami, self-hosted on infrastructure we control, counts page views without cookies. PostHog, a product analytics service, records page views, clicks, scroll depth and time on page, plus session recordings with every form field masked, so we can see where the site is confusing. PostHog sets a first-party cookie to recognize a returning browser and derives an approximate location (country and city) from your IP address. When you buy a plan, we attach the purchase to your email address so we know which pages lead to sales.

Desktop app usage analytics

The desktop app sends anonymous usage events in the background. You can turn this off at any time in Settings → About ("Share anonymous usage data"); once it is off, nothing more is sent.

The events go to PostHog: app opened, which coding CLIs are installed (name and version), project created, chat message sent, story status changes, pull request opened or merged, paywall and checkout buttons, and account sign-in. Each event carries the app version, operating system and processor type. Events never contain your code, prompts, model output, file or folder names, repository names, email address, keys, or IP address.

Events are tied to a random identifier created for your installation. To know which page led to an installation, our download server keeps, for each download, the browser's analytics identifier and a keyed hash of your IP address (never the address itself). On its first launch the app sends its identifier to our server, which matches it with a download from the same network in the previous 14 days, then erases the hash.

When you open aidenapp.org from the app (pricing, checkout, sign-up), the app adds the identifier to the link, so we can connect the visit and a purchase to the installation. If you sign in to an AIDEN account in the app, we connect the installation to your account. Turning analytics off stops all of this.

Account information

Creating an account is optional and only required if you want to subscribe or manage a team. When you sign up, we store your email address, an optional display name, and — if you use email-and-password sign-in — a securely hashed password (we never store your password in plain text). If you sign in with Google or GitHub instead, we receive your email address and name from that provider rather than a password. Each account gets a personal workspace so you can manage your license and, if you invite others, your team. We also send a verification email to confirm you own the address. You can delete your account at any time from Account Settings on the web or from Settings in the iOS app.

License key validation

When you activate a paid license in AIDEN, the app sends your license key to our license API (aidenapp.org/api/activate) to verify it is valid and has not been activated on more machines than permitted. We store the license key and the number of active activations. We do not store your machine hardware ID or any personally identifiable information as part of this process.

Download metadata

When you download AIDEN, our server logs a standard HTTP request log entry (timestamp, IP address, user agent). These logs are rotated every 30 days and are not linked to any account. The server also keeps the download record described under Desktop app usage analytics.

2. What We Do Not Collect

AIDEN is designed around the principle that your work stays on your machine. We do not collect:

Your source code, files, or project contents, these never leave your machine.
Your Anthropic API key, OpenAI API key, or any other credentials, AIDEN reads them from your local environment and passes them to Claude Code and Codex CLI running locally.
Your git history, repository names, or commit messages.
Your name or email address — unless you choose to create an account, subscribe, or contact us directly.
Crash reports from the desktop app.

3. Third Parties

Stripe (payments)

Payments for the Unlimited license are processed by Stripe. We do not store your payment card details. Stripe may collect and store billing information in accordance with their own privacy policy. After a successful payment, Stripe sends us your email address and a license key, this is used to email you your license.

Single sign-on (Google, GitHub)

If you choose to sign in with Google or GitHub, that provider shares your email address and name with us so we can create or log you into your account. We do not receive your password for those services. Each provider's own privacy policy governs the data they hold.

Analytics

Website analytics and desktop app analytics are processed by PostHog, Inc. in the United States (PostHog privacy policy). Umami page-view counts stay on infrastructure we control. We don't sell analytics data or use it for advertising.

Anthropic and OpenAI

When you use AIDEN to run Claude Code or Codex CLI sessions, those CLIs make API calls directly from your machine to Anthropic and OpenAI respectively. AIDEN does not intercept or proxy these calls. Anthropic's and OpenAI's own privacy policies apply to those interactions.

4. Data Retention

Server access logs: 30 days, then automatically deleted.
Account data (email, name, hashed password, workspace): retained until you delete your account from Account Settings on the web or in the iOS app.
License activation records: retained for as long as your license is active. You can request deletion by emailing support@aidenapp.org.
Analytics events (website and desktop app): 12 months. Website session recordings: 30 days.
Download records: the IP hash is erased as soon as the download is matched to an installation; unmatched records are deleted after 30 days, matched ones after 90 days.
Payment records: retained by Stripe per their legal obligations.

5. Your Rights (GDPR / CCPA)

If you are located in the European Union, the UK, or California, you have the right to request access to, correction of, or deletion of any personal data we hold about you.

Because AIDEN collects very little personal data, exercising these rights is straightforward. To make a request, email support@aidenapp.org with the subject line "Data Request". We will respond within 30 days.

We do not sell personal data. We do not use personal data for advertising or profiling.

6. Children

AIDEN is a developer tool intended for users aged 16 and older. We do not knowingly collect information from children under 16. If you believe a child has provided us personal information, contact support@aidenapp.org and we will delete it.

7. Changes to This Policy

We may update this Privacy Policy from time to time. The "Last updated" date at the top of this page reflects the most recent revision. Continued use of AIDEN after a policy update constitutes acceptance of the revised policy.

8. AIDEN iOS (Mobile Companion)

AIDEN iOS is an app for iPhone and iPad. It can pair with a running AIDEN desktop and can optionally sign in to an AIDEN account for shared Team Mode. The iOS app is governed by this privacy policy in addition to Apple's App Store policies.

What AIDEN iOS collects

AIDEN iOS does not run advertising, tracking, or product analytics SDKs. If you choose Team Mode, AIDEN stores your name, email, account identifier, APNs device token, shared project and story metadata, specifications, comments, assignments, and collaboration activity. This data is linked to your account and used only to provide app functionality. Pairing-only users do not send this Team Mode data to AIDEN.

What AIDEN iOS talks to

Your paired AIDEN desktop, using mutual authentication and a paired bearer token kept in iOS Keychain. A configured peer-to-peer relay or remote desktop endpoint may carry this encrypted traffic when direct LAN access is unavailable.
The AIDEN account and Team Mode service, when you choose to sign in, for authentication and shared collaboration data.
Apple Push Notification service (APNs), to receive push notifications. In Team Mode, the APNs device token is registered with AIDEN so the service can address notifications to your account; paired mode may also register it with your desktop.

What stays on your iPhone or iPad

Paired bridge credentials, Keychain, encrypted by iOS.
Local caches used to keep recently viewed content responsive. Team Mode content in those caches also exists on the AIDEN coordination service.
Source code, local paths, git operations, terminal processes, MCP configuration, and agent execution remain on your paired desktop. Widget definitions are stored by the desktop and their HTML is rendered in an isolated, non-persistent web view on your device.

Demo Mode

The iOS app ships with a Try Demo mode that exercises representative features using bundled, scripted fixtures. Demo Mode is fully offline and makes no outbound network calls.

iOS permissions we request

Local Network, required to discover your paired AIDEN desktop on your LAN.
Notifications, required to receive push notifications from your paired desktop.
Camera, optional, used only when you tap the QR scanner during pairing.
Photo Library, optional, used only when you attach a photo to a chat message.

The App Privacy nutrition label on the App Store listing reflects this policy. Data linked to you for App Functionality includes Contact Info, User ID, Device ID, User Content, and Product Interaction. AIDEN declares no tracking.

9. Contact

For any privacy-related questions or requests, contact us at support@aidenapp.org. AIDEN is developed and operated by Lekiks, founded by Kylian Migot.