What Mekkapp keeps, and how to leave.

What to expect from an alpha

Things will break, and we will change them without notice. Your projects are stored, but the database behind the alpha is on a free plan with no provider backups; we take our own backups, and we have rehearsed restoring them, but we cannot promise that nothing is ever lost. Keep a copy of anything you would miss: the source of every project can be downloaded at any time from its App settings.

Some buttons and steps in Mekkapp send what you write about your app to an AI model run by another company. Who handles it lists each of them and says what they send. Everything else is worked out by our own code and sends nothing anywhere.

What we store

Your account: first name, last name, email address, a hash of your password (never the password), whether your address is confirmed, and the times you registered and last logged in.

Your projects: everything you build in them, as structured data, plus any app icon or splash image you upload, and nothing else.

If you connect an Expo account to a project, its access token, stored encrypted and used only to send that project's builds to Expo. You can disconnect it at any time, which deletes it.

If you connect a project with Supabase, the access Supabase grants Mekkapp to your Supabase account, stored encrypted. Mekkapp uses it only to list your Supabase projects, read the publishable key of the one you choose, and set that project's tables up from your Data area. It never reads a secret key. You can disconnect at any time, which revokes it at Supabase and deletes it here.

Short-lived tokens for confirming your address and resetting your password, stored as hashes and deleted once used or expired.

The invite that let you in: your address, the code, and who accepted it.

What we record when you use it

A log line per request to our server: the method, the path, the outcome, how long it took, your account id, your network address (which we need to limit abuse), and a request id. Request bodies are never logged, and email addresses and tokens are removed from log messages by the code that writes them. Our hosting provider keeps these logs for a short time.

If the app fails in your browser, it sends the error message, the code location, and the page path to our own server so we can fix it. There is no analytics script, no advertising, and no third-party tracker on any page.

The public landing page's update form is separate and asks for its own consent.

Who handles it

Cloudflare serves the web app from its network and, if you upload an app icon or a splash image, stores the file in its R2 storage. Render, in Oregon, USA, runs our server and holds the database. Resend delivers account email, which is the only email we send you: an address confirmation, and a password-reset link when you ask for one.

DeepSeek runs that model. We send it something only in these places. On the creation page: “Improve my text”, and “Plan my app” with the steps after it, until the project is created. When you choose a look: “No, suggest some for me”, “Suggest the rest for me”, and “Read it” for a DESIGN.md with no design tokens. In Reusable pieces: “Suggest pieces for my app”, which a project planned on the creation page also asks by itself, just after it is created. In App settings: “See what this changes”, after you edit what your app is. In the Builder: “Ask”, “Design the row with AI”, and “Design this screen with AI”, which a project planned on the creation page also asks by itself, just after its pieces.

We send what you typed, a DESIGN.md you gave us, and what your app is made of: its name and description, the kinds of people who use it, what it keeps, its look, its pieces, and its screens with the words on them. We never send your name, your email address, or anything else about your account. DeepSeek may keep what we send and use it to improve their own models; we have no model of our own, so we cannot prevent that. If you would rather an idea never left our server, do not use those places: nothing else in Mekkapp uses a model.

If you connect a project with Supabase, Mekkapp sends Supabase the migration it writes from your Data area, to set up the tables in your own Supabase project. It sends none of your account details.

Apart from those, nobody else receives your data. We never sell it, and we train nothing on it ourselves.

What is yours

What you build is yours. Mekkapp claims no rights over your projects or the source generated from them. Formal terms will be written before any paid plan exists; until then, this sentence is the promise.

How to leave

Delete your account from Settings at any time. It asks for your password and then permanently deletes the account and every project in it, immediately. Download your source first if you want to keep it.

At the end of the alpha we may close tester accounts. We will tell you first, and delete your data on request.

If you cannot log in, write to us and we will delete the account for you after confirming it is yours.