Tomas·5 min read

What happens to your prompt, your app and your data

Your prompt is processed to build your app; your app's users keep their data on their device. Tomas explains what Leanfinit sees and what it never receives.

0kinds of data, three different paths
0entries from your app’s users ever reach Leanfinit

When you build with Leanfinit, three different things exist: the prompt you write, the app we generate from it, and the data people later enter into that app. We process your prompt to build the app. The app itself has no backend by default, so the data its users enter stays on their device and does not reach our servers. This post walks through each of the three, so you can decide what to put in a prompt and what to keep out of it.

I'm Tomas, Leanfinit's CTO. I designed the pipeline described here, so if something below is unclear, it is my job to fix the explanation.

Three kinds of data, three different paths

Most confusion about AI app builders comes from treating "your data" as one thing. It is not.

WhatWhere it goesWho can see it
Your prompt and follow-up messagesProcessed by Leanfinit to generate the appLeanfinit; possibly the blog (see below)
The generated app and its codeBuilt and stored so you can preview, edit, export and publish itYou, and anyone you publish it to
Data entered into the app by its usersStored on the user's deviceThe person using the app

The first two pass through our systems because that is how the app gets built. The third does not, and that is a design decision, not a setting.

Your prompt

A prompt is the description you type in the studio: what the app should do, what screens it needs, what to call things. We process it to generate the app and every revision you ask for.

During the beta there is one more thing you should know. When you sign in and send prompts, you agree that your prompt and the app built from it may be shown on the Leanfinit blog, without your personal data. That is how many of the examples on our blog exist. We show the idea and the result, not who you are.

The practical rule follows from this: describe the app, not your private records. "A tracker for my mother's blood pressure readings, morning and evening" is a good prompt. Pasting last month's actual readings into it is not needed, because the app will hold those later, on the phone, where they belong.

Your app

The app we generate is a real project with real code. It is built on Flutter, and we keep it so you can preview it, keep editing it with new prompts, export the code and publish it.

When you press Publish, the app goes live on the web. During the beta we do not submit apps to the App Store or Google Play. If you export the code, you can run, change and publish that copy elsewhere.

Your users' data

This is the part people ask about most, and the part I'm most careful with.

A generated app has no backend by default. There is no Leanfinit database collecting the workouts, expenses, notes or readings people enter. When someone logs a set or adds an expense, the entry is written to storage on their own device. We do not receive it, so we cannot read it, analyze it, sell it or lose it in a breach.

I explain the architecture and its trade-offs in No backend by design: how generated apps keep data on the device. The short version: with no backend, there is no sync across devices by default.

What this means for common situations

You build a personal tracker. Your prompt describes the tracker. Your entries live on your phone. We see the description, not the diary.

You build a tool for a small business. The app's structure passes through us; the records your staff type in stay on their devices. If you later need shared data across staff, that needs a backend, and that is a separate decision you make deliberately, not a default you discover later.

You build an app for a client. The same rules apply. Your client's customers' data is not stored by Leanfinit, which simplifies the conversation about who is responsible for it.

What to keep out of prompts

Because prompts are processed and may appear on the blog without personal data, keep these out of them:

passwords, API keys and access tokens;
real health, financial or ID records;
other people's names, addresses or phone numbers;
anything a client gave you under confidentiality.

None of these makes a better app. A description of the field ("a field for the account number") works as well as the value itself.

How to judge any AI app builder

Whether you use us or not, ask three questions of any builder:

1Is my prompt used for anything beyond building my app, and do I agree to it?
2Where does the data my app's users enter actually go?
3Can I export the code and run it without the builder?

The insights page on data safety in AI app builders goes deeper into the questions to ask. For Leanfinit, the answers are above: the prompt builds the app and may illustrate the blog without personal data, user data stays on the device, and the code is exportable.

If you want to see how this works with your own idea, start in the studio: studio.leanfinit.com.