Where is my data and is it safe? What happens under an AI-built app
"The AI built my app in five minutes" is exciting right up to the moment a customer types their phone number into it. Then the questions start: where does that go? Who can see it? What if I leave? This post answers them for apps built with Malpera, in plain language.
Where the data lives
Every app gets its own isolated schema in a PostgreSQL database hosted by Supabase in Frankfurt, Germany (EU). Your tables, your users and your uploaded files are separated from every other app's, with row-level security switched on for every table. Malpera's own servers run in Germany as well. Nothing is stored in the US unless you connect a US service yourself.
Who can see what
Access rules are not a filter on the screen; they are enforced by the database:
- A customer sees only their own orders, bookings or messages.
- An admin (you) sees everything in your app.
- A visitor who is not signed in sees only what you made public.
- Server functions — the code that creates orders or sends e-mails — run with their own identity and check the rules themselves.
Before an app can be published, Malpera runs a security check: it creates test accounts that should not be able to see or change things and tries anyway, directly against the data API, not just through the pages. If anything leaks, publishing is blocked until it is fixed. The check also scans the code for secrets that must never reach the browser.
What Malpera can see
Malpera's staff can see your project files and settings when you ask for support. Your app's user data is stored in your app's schema; our systems access it only to run the security check (with test accounts) and nightly backups. We do not read, sell or train on your users' data. Details are in the privacy policy.
AI and your data
When your app uses AI features (reading an uploaded PDF, summarising text), the file or text is sent to the AI provider for that request and not stored by them for training under our agreements. The AI never receives your database wholesale — only what the specific feature needs.
Backups and outages
Databases are backed up nightly and copies are kept off-site, encrypted. Published sites are served from a frozen snapshot: an edit in the builder cannot break the live site until you publish again, and every published version is kept so you can roll back in one click.
Leaving
You can download the complete source code of your app at any time, export your data tables, and delete the project — which deletes its database schema, files and published site. If you want to run the app yourself, it is a standard React + TypeScript project on a standard PostgreSQL database; nothing proprietary is required.
What you should still do
- Use the owner role for yourself only; give staff accounts, not your password.
- Tell your customers what you collect — the generated apps include a privacy page you can edit.
- If you handle health or payment data, read the rules that apply to your business; the tool enforces access, it does not replace your obligations.