Data Processing Agreement (DPA)
Parties.
- The controller: the developer who creates apps on Neblla ("the Developer").
- The processor: Vanessa Vera Kaminskas, tax ID 75170507K, with address at Av. de la Constitución 45, 4.º B, 28890 Loeches (Madrid, Spain) ("Neblla"). If a company is incorporated, its name, tax ID and address.
1. Purpose
The Developer uses Neblla to give their apps user accounts, saved data, real-time rooms, community, payments, AI and hosting. To do so, Neblla processes, on the Developer's behalf, personal data of the people who use those apps ("the Players"). This agreement governs that processing under Article 28 of Regulation (EU) 2016/679 (GDPR).
Who is responsible for what:
- For the data of each app, the Developer as controller, and Neblla as their processor.
- For each person's Neblla account, Neblla as controller: credentials, sessions, friendships across apps and the gallery. That part is not governed by this agreement. It is governed by Neblla's privacy policy.
2. Duration
While the Developer has at least one app on Neblla. On termination, section 10 applies.
3. Nature and purpose
Neblla hosts, stores, transmits and processes the data only to provide the service the Developer configures: identifying Players, storing their data, connecting them with each other, charging on the Developer's behalf, moderating content and sending the notices the Developer schedules.
Neblla does not use this data for its own purposes: no advertising, no profiling, no sale to third parties, no training of AI models.
4. Data and data subjects
Data subjects: the Players of the Developer's apps, with or without an account.
Data, depending on what each app uses:
- Identification: the Player's id in the app, public name and avatar, and their email if the Player authorises it.
- What the app stores about the Player: progress, preferences and
save()data. - Communication: chat messages, content published in the community, ratings, messages between the Player and the Developer.
- Purchases: what was bought and when. Payment data is processed by Stripe, never by Neblla.
- Technical data: IP address, device and language, and connection and security logs, including anti-cheat flags.
Special categories. Neblla is not designed for them (health, minors without parental consent where the law requires it, etc.). If an app processes them, the Developer is responsible for having a legal basis and adequate measures.
5. Instructions
Neblla processes the data only on the Developer's documented instructions. Instructions are the configuration of each app (back office, MCP, API) and the way it uses the SDK. If Neblla believes an instruction infringes the GDPR, it tells the Developer.
6. Confidentiality and security
Neblla's people with access to the data are bound by confidentiality, and only access it when needed for the service, support or security.
Technical and organisational measures (Article 32):
- Encryption:
- in transit, with TLS;
- at rest, persisted chat;
- end to end, the community's private content, which not even Neblla can read.
- The Developer's secrets (API keys, their database's): stored encrypted and never returned in clear.
- Access to systems and databases restricted and with individual credentials.
- Encrypted backups.
- Isolation between apps: one app cannot read another's data.
- With their own database (BYODB): the app's data lives in the Developer's database, and Neblla only transmits it.
7. Sub-processors
General authorisation. The Developer authorises Neblla to use the sub-processors on the public list at https://neblla.com/legal/subprocessors?lang=en.
Telegram. If the Developer turns on telegramFull, the texts and emails that its users write and that are part of an alert are sent to Telegram, which acts as sub-processor for that delivery; chats with bots are not end-to-end encrypted. By default Telegram receives no personal data of the Developer's users.
Changes to the list. Neblla notifies the Developer 30 days in advance, through their Neblla inbox and by email, before adding or replacing one. The Developer may object on reasonable grounds. If no agreement is reached, they may leave the service and take their data with them (section 10).
Sub-processors' obligations. Neblla imposes on them the same data protection obligations as this agreement, and is liable for them to the Developer.
8. Transfers outside the European Economic Area
Some sub-processors process data outside the EEA. Today these are Neblla's servers, in the US, and the providers marked on the list.
Those transfers rely, as the case may be, on:
- the EU-US Data Privacy Framework, if the provider is certified;
- the standard contractual clauses of the European Commission (Decision 2021/914), with the supplementary measures that apply.
9. Help for the Developer
Players' rights. Neblla provides tools to handle access, rectification, erasure, portability and objection:
- exporting and erasing a Player's data (
neblla_export_users,neblla_erase_user); - the erasure request from inside the app (
neblla.requestErasure()); - the back office.
If a Player asks Neblla directly about an app's data, Neblla forwards it to the Developer.
Security breaches. Neblla notifies the Developer without undue delay and at the latest within 48 hours of becoming aware of a breach affecting their apps' data. It gives them the information available so they can notify the authority within their 72 hours.
Impact assessments and prior consultations. Neblla provides the reasonable information it has.
Audits. Neblla makes available the information needed to show it complies, including its sub-processors' certifications. It accepts reasonable audits, with 30 days' notice, at the Developer's expense and at most once a year, unless an authority requires it.
10. On termination
The Developer can export their apps' data at any time. When they delete an app or leave the service, Neblla:
- erases the app's data within 30 days;
- erases backups as they expire, within at most 30 more days;
- keeps only what the law requires it to keep, such as billing records.
11. Liability, law and jurisdiction
Liability: as set by Neblla's terms of use, without prejudice to what the GDPR does not allow to be limited.
Governing law: Spanish law.
Jurisdiction: the courts of Madrid, unless the law requires others.
Version: 1 (beta) · 27 October 2026