Privacy

Updated September 13, 2026

This notice describes information handled by Apollo App Builder, operated by James Zampa, when you visit this website, contact support, or use the Apollo service.

This public website

This website presents product information and links to customer support. It has no account registration, checkout, or contact form. The restricted Operator page lets authorized operators sign in through AWS Cognito to view and manage waitlist admissions. Sign-in tokens and loaded account details stay in page memory and are cleared on sign-out or when the page closes; they are not saved in browser storage. Operator actions are recorded by the Apollo API. We do not add advertising trackers or marketing analytics scripts to it. Our hosting provider may process technical information such as your IP address and browser details to deliver and protect the website. Fonts are loaded from Google Fonts, which receives the network information needed to serve those files.

Account and project information

The Apollo app processes account identifiers, sign-in information, project source and files, prompts and conversation history, build records, and usage information needed to operate the service. It also processes the provider and developer-account information you choose to connect.

Your prompts, project context, or source may be sent to a selected AI provider or build service as part of the work you request. Avoid submitting material you are not authorized to share. If you enable build-ready notifications, the service processes a device notification token and related delivery records.

Data licensing and AI training

Apollo's optional data-licensing program allows us to earn revenue by selling or licensing eligible project source code and limited app-usage data to third parties, including AI model developers, researchers and commercial software companies. Buyers may use eligible data for training and evaluating large language models and other AI systems, research, and commercial uses covered by the license.

The program initially allows source-code and usage-data licensing in supported app versions, subject to the acknowledgment described here. The data-selling opt-out covers both categories. Existing accounts without a recorded acknowledgment are excluded until the customer saves a licensing preference for the current policy version. Viewing this policy or continuing to use the app does not by itself enroll an existing account. Previously saved opt-outs remain in effect.

Source-code licensing covers reviewed project source files you have authority to license. Usage-data licensing currently covers only per-project counts of completed app creations and successful builds. Buyer datasets exclude account identifiers, contact and payment details, connected-account credentials, conversations and raw analytics records. Source files can themselves contain personal or confidential information; we require review of the specific source snapshot and its licensing rights before export. File filtering alone does not make source anonymous.

Your licensing choices

In the app, open Account > Privacy Policy and turn on Opt out of data selling. This disables sales and licensing of both your source code and usage data. Waitlisted users can open Privacy Policy directly from the waitlist screen. Choices apply across your account to future exports, including previously reviewed projects. If the controls are unavailable, contact support privately with your opt-out request; do not post account details in public channels.

Opting out or requesting account deletion stops future licensing exports. It cannot recall copies already delivered to buyers or reverse completed model training. We keep internal export records identifying the buyer, purpose, relevant source snapshot and applicable saved preferences. Account deletion removes our account-linked licensing preferences, reviews and export mappings; buyer-held copies and contract or delivery records may require separate handling. See the licensing terms for source ownership and permitted uses.

App safety checks

To enforce our safe-for-work app policy, Apollo sends app requests, follow-up answers, project descriptions and source files to AWS Bedrock Guardrails for automated screening. Checks may run before development, when generated or edited source is saved, and before building, sharing or submitting an app. These checks use AWS infrastructure in the United States and can route across US regions. Do not put passwords or secret keys into prompts or project source; use the connected-account controls instead.

The safety checker keeps temporary hashes of approved content to avoid repeating unchanged checks. It does not add a separate log of submitted content. Project and conversation records are still handled as described above. A declined action returns a safety message; contact support if you believe it is a mistake.

Discord support

Customer support is available through our Discord server. Joining or contacting us there shares your Discord profile and messages with Discord and their intended recipients. Public server channels are visible to other members. Use a private conversation with the server owner for account, billing, and privacy requests. Discord handles information under its privacy policy.

Payments and support

Stripe handles payment details for Stripe purchases through its hosted checkout and customer portal. Apple and Google handle payment details for purchases through their stores when those checkout options are available. Apollo uses RevenueCat to validate and track store subscriptions. This involves your Apollo account identifier, product and transaction identifiers, purchase receipts or tokens, subscription status, and related device and app information. Apollo uses these records and billing events to determine access and support purchases and restoration. Apollo does not collect or store full payment-card details.

If you contact support, we receive the contact details, message, and any attachments you send. We use that information to respond and address your request. Please do not send passwords, full payment-card details, or secret API keys.

Service providers

Apollo uses service providers for hosting, identity, infrastructure, payments, build services, and optional notifications. These include AWS for this website, Apollo infrastructure, and account sign-in, Stripe, Apple and Google for their respective payment channels, RevenueCat for store subscription verification and management, and Google/Firebase for enabled notifications. AI providers and Expo process information when you connect and use those services. Their own terms and privacy notices also apply.

See RevenueCat’s privacy policy, Apple’s privacy policy, Stripe’s privacy policy, AWS’s privacy notice, OpenAI’s privacy policy, and Google’s privacy policy.

Retention and protection

Account records, saved projects, usage records, and connected-service records support ongoing operation, recovery, billing, and abuse prevention. Retention depends on the type of record and the reason it is held. Deleting a project does not automatically delete all account, usage, billing, or signing records. Information may need to be retained for security, legal obligations, or resolving disputes.

The service uses access controls and protected infrastructure, but no internet service can guarantee absolute security. Keep your sign-in and provider credentials secure.

Your requests

Contact support to request access, correction, or deletion of your information, or to ask a privacy question. We may need to verify your identity before acting on a request. Third-party accounts and subscriptions may require separate action with those providers.

Updates

We may update this notice as the service changes. The date at the top identifies the current version.