Personal Data & DPAs

The short version

Jaina is a place for your content, configuration, and application data. It is not a place to store personal data about other people. Because you may not put third-party personal data into Jaina, we never act as your data processor, and we do not offer a Data Processing Agreement (DPA), because you don't need one.

What you can and can't store

You can store the things a schema platform is for: your models, records, files, and configuration. You can include incidental personal information about yourself and your own team, for example the author byline on a blog post you publish.

You may not store personal data about your end users or any other third party: no customer lists, form submissions with people's details, player or user accounts, contact databases, or similar. The full rules, including other prohibited data classes (health data, payment-card data, government IDs, biometrics), are in the Acceptable Use Policy.

Why we designed it this way

Privacy laws draw a line between a controller (who decides why personal data is processed) and a processor (who processes it on someone else's behalf). For your account data (your email, billing, and usage), Jaina is the controller, and our Privacy Policy explains how we handle it.

We deliberately do not take on the processor role for the content you store. Keeping personal data about other people out of Jaina keeps the product simple, keeps your compliance burden low, and keeps us from holding data we have no need to hold. It's a smaller, safer surface for everyone.

"Do you have a DPA?"

No, and by design you don't need one. A DPA governs how a processor handles personal data on a customer's behalf. Since our Terms and AUP prohibit you from putting third-party personal data into Jaina, there is no such processing for a DPA to govern.

How we enforce this

We do not proactively scan Your Content. We act on violations we become aware of, following the enforcement process in the Acceptable Use Policy. If you believe someone has stored your personal data in Jaina, tell us (see below) and we will handle it as a policy violation.

If you need to handle personal data

If your use case genuinely requires storing personal data about other people, Jaina is not the right tool for that part of your system. If you think you have a specific need, reach out through our contact page and we can talk about whether there's a fit. But the default answer is that this data does not belong in Jaina.