Privacy Policy
Naapy turns a written description of an app into a working mobile application and backend. This policy explains what we collect to do that, who we share it with, and how you get it back or delete it.
Last updated 10 August 2026
Who we are
Naapy (“we”, “us”) is the service at naapy.app, operated as a sole proprietorship by Sanjay Gopal Mallur, Esteem Kings Court, 5th Cross, 7th Main Road, Dollar Layout, Phase 4, J. P. Nagar, Bengaluru, Karnataka 560078, India. We are the data controller for the information described here.
If you have a question about this policy, about your data, or want to exercise any of the rights below, contact sanjay@naapy.app. That address reaches a person, not a queue.
What we collect
Account information. Authentication is handled by Clerk. When you sign in — with an email address or through Google, Facebook, LinkedIn or X — we receive your email address, your name and profile picture where the provider supplies them, and an identifier for that provider. We never see or store your password or your social account credentials.
What you write. The description of the app you want, project names and descriptions, follow-up messages, design feedback, and any configuration or credentials you supply so a generated app can reach your own services.
Welcome answers. After you first sign in we ask a few short questions: why you came, what you tried before and where you heard of Naapy. With them we keep where you first came from: the campaign tags in the link you followed, the name of the website that sent you (never the full address), the first page you opened, and your time zone and language. Your browser holds this until you answer. You can skip the questions, and the answers are deleted with your account.
What the pipeline produces. Product requirements, design mockups, architecture, source code and other build artifacts, together with a per-project memory we keep so later builds stay consistent with earlier ones.
Operational records. Build history and progress steps, AI usage and cost accounting, security audit entries, request identifiers, and error reports.
Product analytics. We use PostHog, hosted in the EU, to see which pages people visit and which steps they finish, so we can find where Naapy is hard to use. It records pages visited, buttons pressed, the steps of a build, your account ID and your IP address (for a rough location), never your email or what you type. It also records some sessions as a replay of the screen. Every field you type into is hidden in a replay, and after you sign in all text on the screen is hidden too, so a replay shows where you clicked, not your app or your words. PostHog keeps an identifier in your browser’s local storage to tell visits apart.
We do not use advertising cookies or third-party pixels. The only cookie we set is the session cookie Clerk needs to keep you signed in. Our pages do load their typefaces from Google Fonts, so Google receives your IP address and browser user agent when a page loads. The home page can also play a short demo video from YouTube. The player loads from youtube-nocookie.com only after you press play; YouTube then receives your IP address and browser user agent, and may store data in your browser under Google’s own privacy policy.
How we use it
- To run the build pipeline and produce your application.
- To show you build progress, history and results.
- To keep later builds of a project consistent with earlier ones.
- To meter AI usage and apply per-run cost limits.
- To diagnose failures, fix defects and improve reliability.
- To detect abuse and protect the service.
- To send transactional email about your account or builds. We do not send marketing email.
We do not sell your personal information, and we do not share it with advertisers.
AI processing
Building an app means sending your description and project context to third-party AI model providers — currently Anthropic, OpenAI and Google. This is essential to the service; there is no version of Naapy that works without it. Those providers process the content under their own API terms, which do not permit using it to train their general-purpose models. We do not train any model on your prompts or your generated code.
Please do not paste real customer records, health information, payment card numbers or similar sensitive data into a prompt. Configuration secrets for your generated app belong in the dedicated secrets field, where they are sealed with AES-256-GCM encryption rather than stored as plain text.
Who we share it with
We use the service providers below to operate Naapy. Each one receives only what it needs to do its job.
| Provider | Purpose | Data involved |
|---|---|---|
| Clerk | Identity and authentication | Email, name, avatar, social provider ID |
| Supabase | Postgres database and file storage | Account records, projects, generated artifacts |
| Render | Application hosting | Request metadata, server logs |
| Upstash | Redis job queue | Build job identifiers |
| Anthropic | AI model provider | Prompts and project context |
| OpenAI | AI model provider | Prompts and project context |
| AI model provider (Gemini) | Prompts and project context | |
| Fly.io | Ephemeral preview environments | Generated app code, preview traffic |
| MongoDB Atlas | Databases for generated apps | Data your generated app stores |
| Resend | Transactional email | Recipient address, message content |
| Sentry | Error monitoring | Error traces, request identifiers |
| PostHog (EU) | Product analytics and session replay | Pages visited, buttons pressed, account ID, masked screen recordings |
| Unsplash, Pexels | Stock photography for design mockups | Search terms only |
| Google Fonts | Typefaces used on our pages | IP address, browser user agent |
We may also disclose information where the law requires it, or to protect our rights and the safety of our users.
Where your data is held
Naapy is operated from infrastructure in several countries, and the providers listed above operate globally. Using the service means your information may be transferred to and processed in countries other than your own, including the United States.
How long we keep it
Account and project data is kept while your account is open. Deleting a project removes it from your account immediately; ask us and we will erase it from our storage within 30 days. When you close your account we delete your data within 30 days, and backups containing it roll off within a further 30. We keep operational logs and cost records for as long as we need them to run and account for the service.
Your rights
You can access, correct, export or delete your information. Depending on where you live you may also have the right to object to or restrict processing, and to complain to a data protection authority. To exercise any of these, see Delete your data or email sanjay@naapy.app. We respond within 30 days.
Security
Traffic is encrypted in transit. Access to your projects is checked against your account identity on every request. Secrets you store for a generated app are encrypted at rest with a per-secret key. No system is perfectly secure, but if a breach affects your data we will tell you and the relevant authority as the law requires.
Children
Naapy is not intended for anyone under 18, and we do not knowingly collect information from children. India’s Digital Personal Data Protection Act treats everyone under 18 as a child and requires verifiable parental consent, so 18 is our floor everywhere rather than the lower age some other regimes allow. If you believe a child has given us personal information, contact sanjay@naapy.app and we will delete it.
Changes
If we change this policy we will update the date at the top of this page, and for material changes we will notify you by email or in the product before they take effect.