> security
How we enter your environment
You are about to give an outsider access to the most sensitive asset in the company. It is fair to know exactly what happens there, before the first credential. These six rules apply to every project, and they go into the contract.
Minimum access, read-only at the start
We start with read permission on what is needed to measure. Write access only in a separate environment, with your explicit approval.
Your data stays in your cloud
We work inside your environment. What leaves are reports, scripts and proposals, plus any sample you authorize in writing.
Your database does not go into an AI model
What goes through a model is schema, consumption metadata and code, never the content of your database. We use enterprise plans where submitted material does not train models.
NDA before the first access
A confidentiality agreement signed before any credential. If your company has its own template, we use yours.
LGPD in practice
We process only what is necessary, agree retention periods, and return or delete what stayed with us at the end of the project.
A record of what was done
A log of actions taken in the environment and a handoff of what changed, so your team can reproduce and audit without depending on us.
Still have a question that is not here?
Ask before any proposal. If your company has its own access policy, we work inside it.
Related documents: privacy policy and terms of service.