Privacy Policy

This policy explains what appflight collects, what it does not, and why. appflight is a product of IQ Digital LLC ("appflight", "we", "us"). It covers four things: the appflight.dev website, the appflight desktop application for macOS (including beta builds), the appflight web app, our cloud service where you design and build apps in your browser ("appflight cloud"), and the AppFlight iPhone and iPad app. Where they behave differently, we say which one we mean.

1. The short version

• The Mac app is local software. Its prompts, code and keys stay on your Mac. See section 2.
• appflight cloud stores your work on our servers. To design and build an app for you in the cloud, we must keep your account, your projects, your chat, your designs and your generated code. See sections 3 and 5.
• The AppFlight iPhone app opens your designs on your phone. It has no ads, no analytics and no third party code, and it does not track you. See section 4.
• AI models run at third party providers. In appflight cloud, what you type is sent to AI model providers to produce your design and code. See section 6.
• You can export and delete. Deleting your account has a 30 day grace period, and a small amount of history is not erased automatically yet. We explain exactly what in section 9.
• We do not sell your data or use it for advertising.

2. The Mac app: what stays on your Mac

When you use the appflight desktop app, your prompts, the Swift code that gets generated, your project files, and your API keys never travel to our servers, because there is no server of ours in that path.

• Your prompts. What you type into the Mac app goes to the AI tool installed on your Mac. It never reaches us.
• Your source code. Generated apps live in a folder on your Mac. We never upload, read, or store them.
• Your API keys and credentials. Keys you connect (RevenueCat, Supabase, Stripe, App Store Connect, Apple Ads, and others) are encrypted using your Mac's own secure storage, which is backed by the macOS Keychain, and stay on your machine. They are sent only to the service that owns them, directly from your Mac.
• Crash and error logs. If the Mac app hits an error, it writes an entry to a log file in its application support folder on your Mac. An entry holds the time, the kind of error, the error message and stack trace, the appflight version, and the platform. The file stays on your Mac and is not transmitted to us. You can delete it at any time.

Third party AI tools you connect to the Mac app. The Mac app works by driving an AI coding tool that you install and sign into yourself, such as Claude Code from Anthropic or Codex from OpenAI. Your prompt is handled by that tool under your account and their terms and privacy policy, not ours. We are not a party to that exchange and we do not receive a copy of it.

What the Mac app sends to us.

• Update checks. When "Check for updates automatically" is on in Settings (it is on by default), the Mac app asks appflight.dev on launch whether a newer version exists. It does the same when you check for updates by hand in Settings. This is a request for one small public file. Like any web request it includes your IP address and basic request details such as the app's user agent, which our hosting provider, Cloudflare, sees in standard server logs. It contains no information about you, your projects, or your prompts. You can turn the automatic check off in Settings.
• Feedback you choose to send. If you use Send feedback (in the gear menu), the Mac app sends your message, the name of the appflight screen you were on, and the name of the project you had open, if any, to Web3Forms, a form service that forwards it to us by email. Like any web request, it also reaches Web3Forms with your IP address. If that request does not go through, the Mac app opens your own email app with the message filled in and addressed to [email protected], and nothing is sent unless you press send. Nothing is sent as feedback without you writing it and choosing to send it.

That is the complete list of what the Mac app sends to us on its own. It does talk to the services you connect, such as App Store Connect, RevenueCat, Supabase, or OpenAI, but those requests go straight from your Mac to that service using your own account, and we never see them. If we ever add anything else, such as opt in analytics or crash reporting, we will ask you first and update this page.

3. appflight cloud: your account

You sign in to appflight cloud with your email address. We email you a one time code and you type it in. We keep your email address, an optional name, and the dates you joined and last signed in. Your signed in session is kept as a token in your browser's local storage (see section 11). We do not use passwords.

If you pair a phone or another device to open your preview, we also keep the device name, model, system version and screen size. We do not currently collect push notification tokens. You can see your devices and remove them in your account.

4. The AppFlight iPhone and iPad app

The AppFlight iPhone and iPad app is a free companion app to appflight cloud. It opens the designs you made in appflight cloud, full screen on your phone, so you can try them by hand. It draws a design with components that are built into the app. It does not download or run code, and it is not a store for other apps.

• Without an account. Three sample designs are built into the app. They open with no sign in and no network, and they send nothing to us.
• Pairing your phone. To see your own designs, you pair the phone with a code from the web app (scan the QR code, or type the 8 character code). The app then sends us that code, and your phone's name, model, iOS version and screen size. We answer with a sign in token that the app keeps in your phone's Keychain. The pairing gives the phone read-only access: the app cannot change your projects.
• Your designs. The app downloads the list of your designs and the description of their screens, which is the same design data described in section 5. It keeps a copy on your phone so a design you opened before opens again without a connection. Designs run on sample data, and nothing you do inside a design is saved or sent back to us.
• Camera. The camera is used only to read the pairing QR code. Nothing is recorded, photographed or stored. If you do not want to allow the camera, type the code instead. The app asks for no other permission: no photos, location, contacts, notifications or tracking.
• No tracking, no third party code. The app has no advertising, no analytics and no third party SDKs. It does not track you across other companies' apps or websites, and it does not share data with anyone for tracking. It talks only to our servers, over HTTPS.
• Removing your data. "Clear Saved Designs" in the app and signing out delete the copy on your phone, and signing out also removes the phone from your account on our server. You can see and remove paired phones in the web app. The app creates no accounts. You delete your account and data in the web app, as described in section 9.

What Apple is told. In its App Privacy details, the app declares that it collects three kinds of data, all linked to you and used only for the app to work (app functionality): a user ID (your account id and the phone's sign in session), other user content (the designs the app opens), and other data (the device name, model, iOS version and screen size sent when you pair). It declares no tracking. Apple's privacy manifest for the app also lists the two system APIs it uses for settings storage and timing.

TestFlight. While the app is in beta, you install it through Apple's TestFlight. Apple collects its own information about your use of TestFlight, such as your Apple ID email, which builds you install, crash reports, and any feedback or screenshots you send, under Apple's privacy policy, and Apple shares some of it with us. Apple, not appflight, controls that data.

5. appflight cloud: what we store

We also receive the ordinary technical information every web request carries, such as your IP address and browser, which our hosting provider logs for security and reliability. We use it to run the service, to keep it secure, to prevent abuse, to provide support, and to improve appflight. We do not sell it.

6. AI processing and the keys you bring

Third party model providers. To create your design and your code, appflight cloud sends the relevant parts of your project (your prompt, your answers, the plan and design, and the code that needs changing) to AI model providers, today Anthropic and OpenAI. They process that content on our behalf to return a result. We send what is needed for the step, not your whole account. The provider's own terms and privacy policy also apply to that processing, so please read Anthropic's and OpenAI's. AI output can be wrong, so do not put secrets or other people's personal data into your prompts.

Provider keys you bring. You can add your own Anthropic or OpenAI key so that AI usage for your builds is billed to your own provider account.

• Your key is encrypted before it is stored. Only its last four characters are ever shown back to you.
• We use it only to run your own builds. It is passed to the build machine for your job and not used for anyone else's.
• It is kept out of our logs, error reports and usage records.
• It is wiped immediately when you remove it, and when your account deletion starts, without waiting for the 30 day grace period.

A key you bring covers the AI. Building still uses our build machines, so building still needs a plan or credits.

7. Anonymized design reuse

appflight gets better at layouts when it learns which designs people pick. To do that, we may keep a text free skeleton of a design: its layout, theme and component choices, stored as plain tags and numbers. A skeleton has no screen text, no names, no prompts, and no raw design file. We never keep the raw design for this purpose. A skeleton is only used for a design that you have allowed or that has been anonymized this way, and it is not linked back to you. Designs that are not allowed stay private to your account and are never shown to anyone else.

You can opt out in your account settings. When you opt out, new designs from your account are not added to the library.

8. Who else sees your data

We share data only with the service providers listed in section 12, which process it for us, and when the law requires it. If appflight is ever sold or merged, your data may go to the new owner, who must honor this policy. We do not sell your personal data, and we do not share it with advertisers.

9. Exporting and deleting your data, and how long we keep it

Export

You can download a copy of your account data as a JSON file. You can do this a few times an hour. The file lists your account details and your projects and files as records (names, sizes and dates). It does not include your app's source code, which is not available for download. If you cannot export, email us and we will help.

Deletion

You can delete your account from your account settings. This is what happens:

1. Right away, your account is hidden and your provider keys are wiped.
2. For 30 days you can change your mind: signing in again with the same email restores the account.
3. After 30 days an automatic job erases your files (generated code, builds, previews, icons), your prompts, your answers, your plans, your job inputs and results, and your name and email address.

What is not erased, stated plainly

• Chat messages, revision prompts, job events and the security audit log. These are stored in append only tables that the automatic erasure cannot change. Until we encrypt this text per user and destroy the key when you delete (a technique called crypto shredding), the text of these records stays after the 30 days. We can remove it on request by a manual, reviewed process, so if you want it gone, email us and tell us your account email. We will tell you when it is done.
• Credits ledger, cost and usage events, and product events. These hold numbers, dates and identifiers, not your content. They are kept for accounting, abuse prevention and understanding costs, and they refer to an internal user id after your name and email are gone.
• Anonymized design skeletons. They contain no text and are not linked to you, so they are not removed with your account.
• Payment records. Stripe keeps its own records of payments under its own terms and the tax and accounting laws that apply to it.
• Backups and recovery. Our database provider can restore the database to any point in the last 30 days, and we take our own encrypted backups. Deleted data can therefore remain in a backup until it ages out, and a restore could bring it back. We have not yet set a fixed deletion period for our own backups. If we ever restore a backup, we will erase again anyone who had asked to be deleted.

Other retention

We keep waitlist emails, ideas, feedback, and contact emails until you ask us to delete them, or until they are no longer needed. Login codes and pairing codes are deleted shortly after they are used or expire. Google Analytics data follows the retention setting in our Google Analytics account. Cloudflare keeps its logs and analytics under its own retention periods. Anything on your Mac, including the Mac app's error log, stays on your Mac and is yours to delete.

10. Security

• Encryption in transit. The website, the web app and our API are served over HTTPS.
• Encryption at rest for keys. Provider keys you add are encrypted before storage, with a secret held separately from the database. Keys can be rotated without involving you.
• Isolation of your account. Our API only returns a project, design or file to the account that owns it, and signed links expire.
• Build machines. Your code is compiled on machines we operate. We are building stronger isolation between users' builds, and we are not yet at the point of one separate virtual machine per user. Do not put production secrets or highly sensitive data in an app you build with appflight cloud.
• Limits and checks. We apply rate limits to parts of our API, and we plan to use a bot check at sign in.
• Reporting a problem. See our security reporting section.

No system is perfectly secure, and we cannot promise that nothing will ever go wrong. If a breach affects your data, we will tell you as the law requires.

11. Cookies, tracking and third party requests

We checked the site on 2026-10-01. This section is what we found, not a hope.

The website (appflight.dev)

• Google Analytics. Most pages of appflight.dev load Google Analytics (Google LLC) to count visits and see which pages people read. It collects standard information such as the pages you view, your browser and device type, the site that referred you, and an approximate location derived from your IP address. It sets two first party cookies: _ga, which tells visits from different browsers apart, and _ga_P8L9JKGX4C, which keeps track of your session. By Google's default they last up to two years. They do not tell us who you are. Google Analytics is not loaded on the Acceptable use, Refunds, Status and Support pages, or on the page you land on after buying a Mac app license. See how Google uses information from sites that use its services and Google's privacy policy.
• How to opt out of Google Analytics. Install Google's Google Analytics opt out browser add-on, block or delete cookies for appflight.dev in your browser settings, or use a content blocker or your browser's tracking protection. The site works the same without it.
• Cloudflare. Our host, Cloudflare, serves every page and keeps standard server logs, including IP addresses, for security and reliability. We did not find a Cloudflare analytics script in the pages we serve. See Cloudflare's privacy policy.
• Waitlist and signup forms. If you join the list, the form sends your email address to Web3Forms (api.web3forms.com), which forwards the submission to us by email. We use your address to invite you to the beta and to contact you about appflight. See Web3Forms' privacy policy.
• Mac app license purchase. When a buy button is shown on the site, it calls our own API at api.appflight.dev and then sends you to Stripe's hosted checkout. Stripe sets its own cookies on its own pages.
• Storage in your browser. The demo on the home page runs entirely in your browser: what you type into it is not sent anywhere and is not stored. The prompt box at the top of the home page keeps what you type in this tab's session storage (af_idea), so it is still there if you come back to the page, and removes it when you close the tab. Nothing is sent while you type. Pressing send opens the appflight web app at app.appflight.dev with your idea in the link (at most 500 characters), so the web app can fill it in for you; that request reaches our host like any page you open. The signup form can also offer Google or Apple sign-in; it does not today. When it does and you use it, your browser keeps your email address and the provider you chose in local storage (af_user) so the form remembers you. Clearing this site's data removes both.
• Email. If you email us, we receive your address and your message.

The four pages added for appflight cloud (Acceptable use, Refunds, Status and Support) set no cookies and load no third party scripts, fonts or images. The Status page makes one request to our own site for status.json.

The web app (appflight cloud)

• We set no cookies of our own and use no advertising or cross site tracking. Our product events (section 5) are sent to our own API, not to an analytics company.
• Your browser's local storage holds your signed in session token and a few preferences, so you stay signed in. Signing out removes the token.
• An idea that arrives from the home page link is read once, put in the prompt box as plain text, and removed from the address bar. Until you start building, it is kept in that tab's session storage. If the private beta stops you from starting, the web app keeps your idea in this browser's local storage, so it is still there when you are let in. Starting a build, or clearing the site's data, removes it.
• When you pay, you go to Stripe's hosted checkout, which has its own cookies and policy.
• If we turn on Cloudflare Turnstile (a bot check) at sign in, Cloudflare processes a small amount of browser information to run that check.

12. Service providers (subprocessors)

These companies process data for us. "Planned" means we expect to use them for the cloud launch and have not yet finished contracting with them. We will update this table as that changes.

13. Where your data is processed

appflight is operated from the United States, and our providers process data in the United States and in other countries. If you are in the EU, UK or elsewhere, your data is transferred to and processed in the United States.

14. Your rights

You can ask us what we hold about you, ask for a copy, ask us to correct it, or ask us to delete it. Much of this you can do yourself in the web app (export, delete, remove keys and devices). For anything else, email [email protected] and we will take care of it. If you are in the EU, UK, California or another place with a privacy law, you have rights under it (for example the GDPR or the CCPA), and we honor them regardless of where you live. You can object to us using your data in certain ways, and you can complain to your local data protection authority. We will not treat you worse for using these rights.

15. Children

appflight is not for children under 13, and we do not knowingly collect their information. If you are under 13, please do not create an account or use the waitlist. If we learn we have data from a child under 13, we will delete it. If you believe a child has given us information, email [email protected].

16. Changes

If we change this policy we will update the date at the top of this page. If a change is significant and you have an account or are on our list, we will tell you by email.

17. Contact

Questions about privacy: [email protected]. For help with anything else, see Support. appflight is operated by IQ Digital LLC, United States.