Stored in the EU. Nothing hidden.
Here is everything Makesso keeps, where it lives, how long we keep it, and who else touches it.
Paris, France. In the EU.
Your account, apps, datasets, files and chat history are stored on our servers in Oracle Cloud's Paris region (eu-paris-1). Disks are encrypted at rest. Your data is not copied to other regions.
- Region
- EU · Paris (eu-paris-1)
- Hosting
- Oracle Cloud Infrastructure
- At rest
- Encrypted disks
- In transit
- HTTPS everywhere
Everything we keep, and for how long.
Your account
Name, email address and profile picture from Google sign-in. Your plan and team memberships.
You ask us to delete your account
Your apps
Each app's code, settings and every saved version, so you can undo changes.
You delete the app
Your data and files
Datasets, the files you upload and the images in your apps, with each dataset's change history. Moving to a smaller plan never deletes anything.
You delete them
Staging copies
For apps with staging and production: synthetic test data made from each dataset's shape. It contains no real values, and is kept apart from your real data.
You regenerate it, turn staging off and delete it, or delete the app
Chat history
Your conversation with the AI for each app, so you can pick up where you left off. Visible only to you, not to other people working on the same app. Never used for training.
You reset the chat or delete the app
Your app's users
When your app has its own sign-in: its users' names, emails and roles. Passwords are stored only as Argon2id hashes, never in readable form.
You remove them or delete the app
Your API keys
Encrypted with AES-GCM. Never shown in full again, and never given to the AI agent: the server adds them to each request on its way out.
You remove them
Usage
AI credits and tokens used each month on Makesso's key, to apply your plan's allowance.
Your account is deleted
Product events
What happens in Makesso, so we can improve it: sign-ups, apps created, shared and viewed, builds, which AI model was used and the credits it took, plan limits reached. With your account and the app's name. Never the contents of your chats, apps or data, and never IP addresses.
Your account is deleted
Server logs
Which address was requested, the result and how long it took, plus errors. No IP addresses, and no request contents.
Rotated automatically, kept briefly
Your data is not the product.
No training on your data
We don't train models on your data or chats, and on our AI key we only use providers that don't either.
No selling or sharing
We don't sell your data or share it with anyone beyond the services listed below.
No third-party trackers
We add no ad pixels or third-party analytics: not to this site, not to Makesso, not to the apps you build. Our own product statistics stay on our servers.
No IP logging
Our logs never record your IP address or what you send, only which page was asked for and whether it worked.
What the AI model sees.
To build your app, the AI model needs context. It receives what's needed for the task and nothing else from your account:
- Your messages, and the images you attach
- The code of the app it's building
- Data it looks at while building: dataset columns, and rows it queries to understand them
- When you add a dataset: its columns, simple statistics and up to 12 sample rows, so it can describe it
- To make staging's synthetic data (apps with staging and production): only each dataset's shape, meaning column names and types, row count, number and date ranges, and the labels of short category lists. Never its values.
- In apps whose owner switches on AI: what people send to the app's AI features (a note to summarise, a question to answer). It's off unless the owner turns it on.
If you connect your own AI assistant (Claude, ChatGPT, Cursor) through MCP, it receives what its tools return: app code, data structure, and rows only if you allowed it to read data. That goes to the assistant's provider under your agreement with them, not ours.
Models run at their providers, who may process requests outside the EU. On Makesso's key, requests go through OpenRouter only to providers that don't store prompts or train on them.
Your AI provider, your terms, no limit.
Add an API key from OpenRouter, OpenAI, Anthropic or any compatible provider, on any plan.
- No usage limit. Calls on your key don't use AI credits; you pay your provider directly.
- Your data terms. Prompts go to the provider under your own account and agreement, including zero-retention or regional options your provider offers.
- Kept safe. Your key is encrypted, and the AI agent never sees it. Requests pass through Makesso on their way to your provider; we don't store them.
- Any model. Use your provider's models, or a company gateway or self-hosted model with a compatible API.
Dataset descriptions and image reading use OpenRouter: your OpenRouter key if you add one, otherwise Makesso's, with the same no-training routing.
The services we use
A short list, and each one only gets what its job needs.
Deleting your data
- Apps, datasets and files can be deleted at any time from Makesso. Deleting an app also deletes its chat history and versions.
- Resetting a chat deletes that conversation for good. Your app and its versions stay.
- Your whole account: email [email protected] from your account's address and we'll delete it and everything in it.
How we keep it isolated is on the security page.
The tool your team keeps asking for is one sentence away.
Start free. Describe it, watch it build, and share it with your team before lunch.
No credit card. Free plan forever.