Privacy policy

This page explains what App Builder Agent (appbuilderagent.com) collects, why, who processes it, how long it is kept, and what you can do about it. It is written to be read, not skimmed; if anything is unclear, ask us.

Last updated: September 2026.

1. What we collect

• Account: sign-in is with Google. We store the email address, name and account id Google gives us, and the time you signed up. We never see your Google password.
• Your projects: the prompts you type, the conversation with the agent, the files the agent writes, project names, app icons and signing keys (signing keys are stored encrypted). Published websites and built APKs are stored so they can be served and downloaded.
• Usage: which pages you open, clicks inside the builder, the AI tokens each request used, build starts and results, errors the app or the builder hit (with the browser type, IP address and the file involved) — so we can fix problems and see which features matter. To reproduce bugs we also record how the builder's screen changes during a session (an interaction recording of the interface, not your camera or microphone).
• Payments: plan, order id, amount and payment status. Card or UPI details are entered on the payment provider's page and never reach our servers.
• Support: what you write in the Support panel.
• Technical: IP address, browser user agent, time zone (used to apply country rules and show local prices), and a random visitor id stored in your browser.

2. Why we use it

• To run the service: build what you asked for, save your projects, serve your published sites, deliver your APKs.
• To bill you and prevent abuse of the free allowance (for example, several free accounts from one device).
• To improve the product: which features are used, where people get stuck, what errors occur.
• To answer support requests.

3. Who else processes it

• AI model providers: your prompts and the relevant project code are sent to the AI models through OpenRouter and the model providers it routes to, so the agent can answer. We strip API keys and secrets before sending. Do not paste passwords or personal data of other people into the chat.
• Google: sign-in. Optional analytics (Google Analytics) only when enabled by us; it is configured to anonymise IP addresses.
• Payment providers: Razorpay and Dodo Payments handle card and UPI payments under their own policies.
• Hosting: the platform runs on servers we rent; backups are stored with the same hosting provider.

We do not sell personal data and we do not show third-party advertising.

4. How long we keep it

• Projects, published sites and builds: until you delete them or delete your account.
• Usage and error records: kept for product analysis; the admin can set a retention period, and records are pruned when it passes.
• Payment records: as long as accounting rules require.

5. Your rights (GDPR, UK GDPR, CCPA and similar laws)

You can ask for a copy of your data, correct it, export your projects (paid plans include full source export; every plan can download built APKs), delete individual projects yourself, or ask us to delete your account and everything attached to it. Write to us through the Support panel; we answer within 30 days. If you are in the EU or UK you can also complain to your data-protection authority.

6. Cookies and local storage

We use your browser's local storage for your session token, your visitor id, first-touch attribution (which page or campaign brought you here) and editor preferences. There are no advertising cookies. Clearing site data signs you out.

7. The apps you build

Apps and websites you build and distribute are yours. If they collect personal data from their users, you are responsible for their privacy notice and compliance (Google Play requires a privacy policy URL for every app). Our guide on privacy policies for your app explains what to include.

8. Children

The service is not directed at children under 13 (or the age of consent in your country), and we do not knowingly collect their data.

9. Changes

When this policy changes materially we update the date above and, for significant changes, tell signed-in users in the builder.

See also Terms of service · About · Contact.