Built to sit next to your source code
Connecting an AI product to your engineering systems is a security decision as much as a productivity one. Here is how we approach it, and how to reach us with the questions your review process needs answered.
How we handle access
Four commitments that shape what Rekogni can and cannot do inside your stack.
You choose what we read
Rekogni only sees the sources you explicitly connect and authorise. Nothing is discovered or ingested outside that set, and a connection can be revoked at any time from the source system.
Encrypted in transit
All traffic between your browser, our services and the systems we connect to runs over TLS. Credentials for connected sources are stored as access tokens, not as reusable passwords.
Teams, not individual scoring
The product is designed to surface workflow friction: stalled reviews, delivery risk, where time is going. It is deliberately not built as a tool for ranking or monitoring individual engineers.
Documented data handling
What we collect, why we collect it, how long we keep it and who processes it is set out in our Privacy Policy, and we will walk your security team through it in detail on request.
Running a vendor security review?
Send your questionnaire or ask for our current documentation set and we will get it back to you with the specifics for your deployment.
Common security questions
What data does Rekogni actually read?
Do you need write access to our repositories?
Can we remove our data?
Do you have a security questionnaire or compliance pack?
Where is data processed?
Bring your security team to the demo.
We would rather answer the hard questions early than after a pilot. Book a session and bring whoever needs convincing.