WEB2APP

Sheet 03 · Privacy

What we hold, and why.

REV 26 September 2026

  1. What this covers

    Web2App turns a website into a native iOS app and files it to the App Store on your own Apple developer account. This page says what we hold to do that, who else touches it, and how to have it removed.

    It covers the web2app.build website and console. The app we build for you is a shell around your own site; it collects nothing of its own beyond what your site already does, plus push notifications if you turn them on.

  2. What we hold

    Your account
    An email address and a password. The password is stored hashed by our authentication provider; we never see it.
    Your project
    The website address, the app name, the icon, the features you choose, and the answers you give during set-up.
    The conversation
    Every message between you and the operator is stored, so a project can be picked up where it was left.
    What we build
    The generated Xcode project, the compiled builds, the simulator copy, and the App Store screenshots — whether we captured them, you took them in the simulator, or you uploaded them.
    Your Apple credentials
    The App Store Connect API key you paste in (issuer ID, key ID and the .p8 file), and the signing certificate and private key issued for your app. These are encrypted at rest with AES-256-GCM and are used only to act on your behalf with Apple.
    Usage
    How many tokens each message cost, per project, so we can understand what the service costs to run. Nothing about the content of the message is kept for this purpose.

  3. Who else handles it

    We do not sell data and we run no advertising. These are the services the product is built on, and what each one receives:

    Supabase
    Hosts the accounts, the database, the file storage and the server functions. Everything above lives here.
    Anthropic and OpenAI
    Run the operator you talk to and generate icons. Your messages, and a description of your website, are sent to them to produce a reply. They are not used to train their models under the terms we use them on.
    Codemagic
    The build machines. For every build they receive the generated project. For an App Store build they also receive your signing certificate and profile, placed in a credential group that exists for that build only and is deleted when it finishes.
    Appetize
    Runs the simulator you see in the console. It receives the unsigned simulator copy of your app, nothing else.
    Apple
    App Store Connect, under your own developer account, using your own key. What Apple then holds is governed by your agreement with Apple.

  4. Cookies and tracking

    There are no tracking cookies and no analytics scripts. The console keeps one session token in your browser so you stay signed in. That is all.

  5. How long, and how to remove it

    Everything is kept for as long as your project exists. You can delete a project from the sidebar at any time; that removes it and its conversation. To delete your account and every file behind it — builds, screenshots, Apple credentials included — email us from the address you signed up with and it is done by hand, promptly.

    You can also revoke the App Store Connect key on Apple’s site at any time, which makes our copy of it useless immediately.

  6. Contact

    Questions about any of this go to privacy@web2app.build. If this page changes, the date at the top changes with it.