Seeing more is not permission for everything. You define the limits on using intelligence in security: which data gets used, what is never done and how the people who appear on a camera are protected.
The role
- Define which data gets used in security, for what and for how long.
- Write what the platform must never do, even if it technically can.
- Review every new security case before it operates.
- Bring that judgment into the governance and into client contracts.
Your first 90 days
- Day 30
You learn the platform, computer vision and the governance.
- Day 60
You review a complete security case and put its limits in writing.
- Day 90
Your limits are in the governance and the platform respects them.
Stack and tools
Governance documentsComputer visionPlatform log
What we look for
Must have
- Law, human rights, ethics or data protection.
- You know the LFPDPPP and Mexico's security framework.
- You write precisely and without filler.
- You say no when it shouldn't be done.
Nice to have
- Experience in transparency or in human rights organizations.
- Curiosity about how vision models work.
What working here is like
What you build goes into products that operate real organizations. You work directly with the founders, with no layers between your code and production, under the same rule we give the intelligence: a person signs what is critical.