Neblla's privacy policy
Controller: Vanessa Vera Kaminskas, tax ID 75170507K, with address at Av. de la Constitución 45, 4.º B, 28890 Loeches (Madrid, Spain) ("Neblla"). Contact: hello@neblla.com.
Neblla is a platform for building apps. It handles data in two different roles, and it helps to keep them apart:
- For your Neblla account, Neblla is the controller. That is what this policy covers.
- For what you give an app made with Neblla, the controller is whoever made it (its developer), and Neblla processes that data on their behalf, as a processor, under a data processing agreement (the DPA). For that, see that app's privacy policy.
1. What data Neblla handles as controller
If you have a Neblla account (to play or in the gallery):
- your email, your public name and your avatar;
- how you sign in: with Google (Google tells us your email and name) or with email and password (we store the password hashed, never in clear);
- your sessions and the permissions you give each app;
- your friendships across apps, and in the gallery your favourites, ratings and reviews.
If you are a developer:
- your email, name and language;
- the date of your first milestones (first app, first publication…) and where you came from to Neblla (the site you arrived from, never more than that);
- your apps and their configuration;
- your subscription and your purchases from Neblla (Stripe identifiers; card data is handled by Stripe, never by Neblla);
- the keys you store (for AI, your database, external APIs), encrypted, and your acceptance of the terms and the DPA.
If you tell us about a problem or something you miss («Report» button, or your AI through the MCP): what you write, the page you send it from (without what follows the «?»), the type of device and screen size, the latest errors of that tab if you leave the box ticked (the window shows what is sent before you send it), and your email only if you write it. We use it to fix it and, if you ask, to tell you when it is fixed. We strip in advance any keys and passwords that slip into the text.
Technical data from anyone: IP address, browser, language and connection and security logs.
2. What for, and on what basis
- Providing the service (your account, signing in to apps, the gallery, the developer's apps): performance of the contract.
- Security and abuse prevention (limits, cheat detection, moderation): the legitimate interest in keeping the service safe.
- Payments and invoicing: the contract and legal obligations.
- Service notices (confirming your email, important changes): the contract.
Neblla does not use your data for advertising, does not build commercial profiles, does not sell it and does not use it to train AI models.
3. What each app receives
When you sign in to an app with your Neblla account, the app receives an id just for that app: different in each one, so no app can cross it with another. Your email only reaches it if you authorise it on the permissions screen; the same with your friends. From then on, what you give that app (progress, messages, purchases, what you publish) belongs to the app's developer, who is responsible for it.
Some apps keep their data in their own database (outside Neblla); then the developer chooses where.
4. Purchases
What you buy inside an app you buy from its developer: the charge is made on their Stripe account, and Stripe handles the payment data. Neblla only keeps what you bought and when, so the app knows.
5. Artificial intelligence
The apps' AI features use Anthropic. Depending on how the app is set up, the call goes with the developer's key or yours, through Neblla or straight from your browser. What you write is sent to get the answer, not to train models.
In an app's community, the developer can turn on an automatic review of content before it is published; the final decision is made by the people who moderate.
6. Connecting Neblla to your AI (MCP)
This only applies to developers who connect their Neblla account to an AI (for example Claude) using the Neblla connector (https://neblla.com/mcp).
- What Neblla receives: the call to each tool and its arguments (for example "publish this app"), to run it with your account's permissions. It never receives the conversation with the AI.
- What is kept: the app's activity log records what the AI did (the tool and the time, marked as done through the AI) for 90 days; after that it is deleted automatically. It is the app's configuration, not its users' data.
- What the login asks for: your Neblla developer account. Of the access tokens only a fingerprint (SHA-256) is kept, never the token. The access token expires after 1 hour and the refresh token after 30 days.
- How to remove access: disconnect Neblla in your AI's connector settings, or from your Neblla account, in "Connected AIs", with "Remove access". Once removed, the token stops working immediately.
- What the AI does not see: cards or bank details. Payments and Stripe verification, paying for Pro, and confirming the deletion of your account always happen on the Neblla website.
- What your AI does with what it reads (for example what the AI provider does with the answers it receives) is covered by that provider's policy, not this one.
7. Who it is shared with
With the providers Neblla uses to run the service (hosting, databases, email, payments, AI, signing in with Google), each only with what it needs. The list, with where they process data and how transfers outside the European Economic Area are protected, is on the sub-processors page.
If a developer or someone on their team connects their Telegram to receive alerts, Neblla keeps their chat identifier (encrypted) until they disconnect it, and Telegram receives the alerts that person chooses; by default they carry nothing written by the app's users (only the type of alert, the app and a button), unless the developer switches the full text on.
And with the authorities when the law requires it.
8. How long
- Your account, while you have it. If you delete it, it is deleted.
- Technical and security logs, as long as needed for their purpose, at most 12 months.
- Reports («Report»), 12 months; your email is deleted as soon as we close the report (fixed or dismissed).
- Invoicing, as long as the law requires.
9. Deleting your account or your data in an app
Deleting your Neblla account (from the gallery) deletes the account: email, credentials, sessions, permissions and friendships across apps. It does not delete what you gave each app, because that belongs to its developer: there you remain as a player without a Neblla account, and nobody can sign in as you again.
If you are a developer, deleting your developer account or one of your apps leaves them in a bin for 30 days, where you can recover them; after that they are deleted for good.
For an app to delete your data, ask from inside the app: Neblla passes your request on, and its developer is the one who deletes it. If you write to us about an app's data, we forward your request to them.
10. Your rights
You can ask for access, rectification, erasure, portability, restriction or objection by writing to hello@neblla.com. If you believe they are not respected, you can complain to the Spanish Data Protection Agency (aepd.es) or your local authority.
11. Cookies and storage
Neblla only uses what it needs to work: your account's session, the language you choose and, in apps, what the SDK keeps in your browser to keep you connected and your guest data. No advertising or third-party analytics cookies.
We measure the use of neblla.com and the panel in aggregate (how many visits and how many steps a day), with no cookies or identifiers: we do not know who you are until you create your account. We count events from a closed list, by day; we do not store your IP (we only use it briefly in memory to curb abuse, on legitimate interest) or your browser. Errors of our own pages are logged without form data.
12. Minors
To have a Neblla account you need to be the minimum age your country's law sets to consent by yourself (14 in Spain). If an app is aimed at minors, its developer is responsible for asking for parental consent when needed.
13. Changes
If something important changes, we will announce it beforehand on the website and, if you have an account, by email.
Last updated: 27 October 2026