Security & data
Your data stays yours.
How I handle your data and your code when I build something for you.
The diagram applies each rule to a made-up record.
How I work
Six rules I follow.
- i
Your accounts, your keys
Where I can, I build on your accounts, your cloud and your API keys, so the data, the code and the bills stay with you.
- ii
Private when it needs to be
Sensitive work can run entirely on your own infrastructure with self-hosted models, so protected data never leaves your hardware.
- iii
Redaction before anything leaves
When a feature does call a public model, personal data is identified and redacted first, so only what is needed crosses the boundary.
- iv
Least-privilege access
Integrations get the narrowest scope that works. Credentials are stored in a secrets manager, never in code or chat.
- v
A log of what ran
Anything a model or an automation does is logged, so you can see what ran, when, and on what data.
- vi
No training on your data
I do not train models on your data, and I configure providers to disable retention and training wherever the option exists.
Security reviews and DPAs
I’ll sign an NDA, fill in your vendor questionnaire, or walk your team through how a system handles data. Write to privacy.officer@marain.space.