Security
Where your data goes.
In plain words: where your data lives when you run Lumbridge, what our model API keeps, who can see what, and what happens when you leave.
01 · Where it lives
Three places your data can be.
Lumbridge is software you run, and builds from source do not report to us. We see data only when you call our model or use this website.
02 · Working with us
Five things to know.
When we train or host a model for you, these are the rules.
01Training data
Your data trains your model.
No model is trained on your data without your written OK. Training sets are kept only for your edition.
02Where it runs
You choose where it runs.
Serverless on our API, on dedicated GPUs at a GPU cloud, or inside your own cloud account. The choice is written into your scope.
03Access
Who can see it.
Agreed in writing, in your scope, before anything is built. Only the engineers working with you.
04Records
Every step leaves a record.
Each dataset, training run, evaluation and release is logged, so you can see what changed and why.
05Exit
When you leave.
Your data, your training set and your model files come with you in standard formats, and we shut down our copy of the endpoint.
03 · Report a problem
Found a security problem?
Email us. Please don’t open a public issue for it.
security@lumbridgecorp.comQuestions
Straight answers.
Do you train AI on my data?
Only your own model, and only with your written OK.
Do you sell or share my data?
We never sell it. The services that process it for us are listed in our Privacy notice.
Can the data stay in our cloud account?
Yes. We can train and host inside your own cloud account, so it never leaves.
What about health or financial records?
They stay out of scope unless we agree in writing how they’re handled.