Security

How the data is handled

Neruva holds real working notes, so the basics are covered. This page says exactly what is in place today, and nothing more.

Where it runs

The API runs on Google Cloud Run in the us-central1 region (Iowa, USA). Stored data sits on Google Cloud, which encrypts data at rest by default.

Getting in

Every request goes over HTTPS and carries an API key. A key is tied to one tenant, and requests can only read and write that tenant's namespaces. Keys are issued by me, by hand.

What happens to the data

It is stored, indexed and returned when asked for. It is not used to train any model, mine or anyone else's, and it is not sold or shared.

Deleting it

Records can be forgotten by kind, tag or time, and an entity can be removed from the knowledge graph completely. A whole namespace can also be exported first.

What is not in place

Neruva is a one-person prototype. There is no SOC 2 report, no formal audit and no uptime promise. If that matters for your use, tell me and we can talk about what would be needed.

Reporting a problem

Email kyle@simgen.dev with anything that looks wrong. I will reply directly.