Barbara·4 min read

Private by architecture, not by policy

Most apps protect your data with a policy: a document that says what the company will and won't do with what it collects. Leanfinit apps take a different route. Generated apps have no backend by default, so the data people enter stays on their device and does not reach us. There is nothing to promise about data we don't receive.

01

A policy is a promise. Architecture is a fact.

Read the privacy policy of almost any app you use daily and you will find careful language: data "may be shared with partners", "used to improve services", "retained as long as necessary". None of this is necessarily bad faith. It is what happens when a company holds your data and needs room to run its business.

The problem is that a promise can change. Policies get updated, companies get acquired, partners change, breaches happen to careful teams too. When the data sits on someone else's server, your privacy depends on every future decision that company makes.

When the data never leaves your phone, those decisions don't touch it. That is the whole idea, and it is why we made it the default rather than a premium option.

A policy is a promise. Architecture is a fact.
02

Why this matters for small, personal apps

Small personal apps are often the most private ones people would ever use:

a log of a parent's medication and how they reacted to it;
a budget that tracks every purchase, written the way someone thinks about money;
a mood or sleep journal;
a symptom diary to show a doctor;
a list of customers who owe a small shop money.

These are exactly the categories where people hesitate to use a generic app. Many money apps ask you to link a bank account before you can do anything. Many health apps want an account, an email and permission to send notifications before you log a single entry. Our guide to an expense tracker that doesn't link your bank covers that case.

When the data stays on the device, these apps become safer to build and to use.

03

What we see, and what we don't

Being private by architecture doesn't mean we see nothing, and I'd rather be precise than reassuring.

When you build an app, we process your prompt to generate it, and we keep the app so you can edit, export and publish it. During the beta, when you sign in and send prompts, you agree that your prompt and the app built from it may be shown on our blog, without your personal data.

What we don't receive is the data entered into the finished app. If you build a symptom diary, we see "a symptom diary with these fields". We don't see your symptoms.

Tomas explains the full path of each kind of data in What happens to your prompt, your app and your data, and the engineering behind it in No backend by design.

04

The honest costs

Choosing architecture over policy has consequences, and we would rather state them than discover them in a support ticket.

Data doesn't follow you between devices by default. Your phone and your laptop each keep their own copy.
Backups are in your hands. If you lose the phone, the app can't restore data from a server that doesn't exist. Asking for an export or backup feature in your prompt can help.
Shared apps need a deliberate choice. A list two people edit together needs something in the middle.

For the kind of app most people build for themselves, these costs are small. For a shared business tool, they are a design decision to make upfront.

05

Why privacy isn't an add-on here

There is a common pattern in software: the free version collects data, and the private version costs extra. We think that gets it backwards for personal tools. The people who most need privacy, for health, money or family matters, are often the people least likely to pay for a premium plan to get it.

So the private version is simply how apps are built here. There is no switch to turn it on.

06

A useful test for any app

Whether or not you use Leanfinit, you can ask one question of any app that handles sensitive information: if this company disappeared tomorrow, where would my data be?

If the answer is "on their servers, under whatever happens to the company next", the protection is a policy. If the answer is "on my phone", it's architecture. Our insights page on data safety in AI app builders lists more questions worth asking before you trust a tool with something personal.

07

What we want this to change

The deeper reason we care: a lot of useful software never gets used because people don't trust it with what matters. A tracker for a parent's recovery, a log of debts, a private journal. If building those apps becomes easy, and using them becomes safe by default, more people will have tools that actually fit their lives.

That is the kind of software we want to exist. Describe the private app you've been putting off: studio.leanfinit.com.