Privacy Policy

PiPilot (“we”, “us”, or “our”) provides a platform that lets you describe an app and have an AI agent build and publish it — web apps, mobile apps, APIs, CLIs, and more — and host the result live on a *.pipilot.dev address. This policy applies to the PiPilot website and product. By using the Service, you agree to the practices described here.

We collect only what we need to provide and improve the Service:

• Account information. When you sign in with Google, we receive basic profile details from your Google account — typically your email address, name, and avatar image — so we can create and identify your account.
• Connected integrations. If you choose to connect third-party providers such as GitHub, Vercel, Netlify, Cloudflare, Supabase, or Stripe to deploy or wire up your project, we store the access tokens you authorize securely, solely to perform the actions you request through those providers.
• Usage and analytics data. We collect limited information about how you interact with the Service, such as feature usage, request volume, device and browser type, approximate location derived from IP address, and diagnostic logs, to keep the Service reliable and secure.
• Support communications. If you contact us, we keep the messages, email address, and any information you choose to share so we can help you.
• Billing information. If you subscribe to a paid plan, our payment processor, Stripe, collects and processes your payment details. We receive only limited billing metadata (such as plan, status, cloud/build hours used, and the last four digits of a card) and do not store full card numbers.

Your project files live in your own Google Drive — we don’t store them. PiPilot saves your projects to a private application folder in your Google Drive, which you own and control. We do not maintain our own copies of your source code, app files, or project data on our servers. When the AI agent needs to work on your project — including for builds, deployments, or headless and scheduled Missions — your files are loaded transiently into a cloud sandbox to perform the requested task and are not retained by us afterward.

PiPilot’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. When you connect Google, PiPilot requests a small, specific set of non-restricted scopes — we intentionally avoid the broad, restricted drive / drive.readonly scopes. You are asked to grant all of them on Google’s consent screen because core features stop working if any is declined:

• Sign-in (openid, email, profile). Basic profile details — your email, name, and avatar — used only to create and identify your account.
• App data folder (drive.appdata). A hidden, app-private folder in your Drive that PiPilot uses to sync your projects across your devices. It is not visible in your normal Drive and no other app can read it.
• Per-file access (drive.file). Access limited to the files PiPilot itself creates — your published sites, generated videos, podcasts, and exported assets — so they can be stored in your Drive and given durable, shareable links. PiPilot cannot see or touch any other file in your Drive.
• App calendar (calendar.app.created). Permission to create and manage events only on a secondary calendar that PiPilot creates and owns — used for cross-device reminders such as database-expiry and deadline alerts. PiPilot never reads or modifies your primary or existing calendars.

Limited Use. Information obtained through Google APIs is used only to provide and improve the user-facing features described above. We do not sell it, do not use it for advertising, and do not use it to train generalized or foundation AI/ML models. Humans do not read it except where you explicitly request support, where required for security or to comply with law, or in aggregated / anonymized form. You can revoke PiPilot’s access at any time from your Google Account permissions or in Settings → Cloud Sync.

PiPilot is an AI product, so building an app or generating media involves sending content to AI models. When you prompt the agent, the relevant parts of your request and project — your instructions, and the code or files the task needs — are sent to the AI provider(s) that serve your request so the model can respond. Optional tools you invoke may also send data: web and documentation search (to find references) and, if you connect them, third-party MCP integrations.

We route AI requests through our own gateway across a set of providers (which may include Anthropic, xAI, Ollama Cloud, and other inference partners) and use search/retrieval providers such as Exa and Jina for web and docs lookups. We select providers that do not retain prompt content for training under our arrangements. We do not use your private prompts or project content to train foundation models.

When you generate a video, podcast, image, or publish a site, PiPilot runs the work in a transient cloud sandbox and stores the finished output in your own Google Drive, from which it is served over a durable public link (for example a *.pipilot.dev address or a shareable file URL). Anything you choose to publish, or to feature in a public gallery such as the Launchpad, Showcase, or Video Hub, is intentionally made publicly accessible — do not include private or sensitive information in content you publish. You can remove published content by deleting the underlying file from your Drive or unpublishing it in the product.

We use the information we collect to:

• provide, operate, and maintain the Service and your account;
• authenticate you and secure access to AI and compute resources;
• process subscriptions, billing, metered cloud/build hours, and referral rewards;
• perform the actions you request through connected integrations, such as pushing code or deploying to a provider you’ve authorized;
• respond to support requests and communicate with you about the Service;
• monitor, debug, and improve performance, reliability, and safety;
• detect, prevent, and address abuse, fraud, and security incidents; and
• comply with legal obligations and enforce our Terms of Service.

We do not sell your personal information, and we do not use your private project content to train foundation models.

Where the GDPR or similar laws apply, we rely on the following legal bases to process your information: performance of a contract (to provide the Service you request); legitimate interests (to secure, maintain, and improve the Service); consent (where required, such as for certain cookies); and legal obligation (to comply with applicable law). You may withdraw consent at any time where processing is based on consent.

We rely on trusted providers to operate the Service. Each processes data only as needed to deliver its function:

• Vercel — hosting and content delivery for PiPilot, and for sites you publish to *.pipilot.dev;
• Supabase — database and backend infrastructure that powers the Service;
• E2B — cloud sandboxes that run builds, previews, and headless or scheduled Missions;
• Google — sign-in and Google Drive storage for your projects;
• Stripe — secure processing of subscription payments and billing;
• AI & search providers — the inference and retrieval partners behind our AI gateway (which may include Anthropic, xAI, Ollama Cloud, and web/docs search providers such as Exa and Jina) that process your prompts and requested content to generate responses, as described in the AI processing section;
• Zoho Mail — delivery of transactional email such as sign-in, workspace invitations, and account notifications;
• Connected integrations you authorize — such as GitHub, Vercel, Netlify, Cloudflare, or Supabase — used only to carry out actions you request, like pushing code or deploying your app.

These providers are bound by their own privacy commitments and process information on our behalf or, where you connect them directly, as independent controllers under their own policies.

We use cookies and browser local storage to keep you signed in, remember preferences, and understand aggregate usage. Strictly necessary cookies are required for the Service to function; others, such as analytics, are used where permitted. You can control cookies through your browser settings, though disabling some may affect functionality.

We retain account and usage information for as long as your account is active and for a reasonable period afterward to meet legal, security, and operational needs, after which it is deleted or anonymized. Because your project files reside in your own Google Drive, their retention is governed by you and by Google’s policies, not by us.

Depending on your location, you may have the right to access, correct, export, or delete your personal information, to object to or restrict certain processing, and to withdraw consent. You can update much of your account information directly in the product, and your project files are always exportable from your Google Drive. To exercise other rights, contact us using the details below; we will respond within the time required by applicable law.

We use technical and organizational safeguards — including encryption in transit, access controls, and scoped credentials — to protect the limited information we hold. No method of transmission or storage is completely secure, so we cannot guarantee absolute security, but we work to protect your data and to notify you of incidents where required by law.

We and our providers may process information in countries other than your own, including Canada and the United States. Where we transfer personal information across borders, we rely on appropriate safeguards, such as standard contractual clauses or equivalent mechanisms, as required by applicable law.

The Service is not directed to children under 13 (or the minimum age in your jurisdiction), and we do not knowingly collect personal information from them. If you believe a child has provided us personal information, please contact us and we will take appropriate steps to delete it.

We may update this Privacy Policy from time to time. If we make material changes, we will update the “Last updated” date above and, where appropriate, provide additional notice. Your continued use of the Service after changes take effect constitutes acceptance of the updated policy.

For privacy questions or to exercise your rights, contact us at privacy@pipilot.dev. For other legal matters, you can reach us at legal@pipilot.dev.

Back to home