How I handle your systems and data

I work with the least access the job needs: read-only for reviews, scoped credentials for builds. Access is removed when the engagement ends.

Client data stays in your accounts and systems wherever possible. I don’t copy production data to personal devices, and I don’t use your data to train models.

I sign NDAs on request, and I don’t name clients or show their work without written permission. Employer work on this site is described without internal names or screenshots.

When a system calls a hosted model, we choose the provider and its data-retention settings together and write them down.

The systems I ship use the same safeguards described in the case studies: verified webhooks, idempotent writes, per-tenant isolation, role-based access and audit logs.

qantara.dev is served over HTTPS with HSTS and a strict Content Security Policy, sets no cookies and uses cookieless analytics. The privacy policy has the details.

Found a security issue in this site or in something I built? Email carlossalguero@qantara.dev and I’ll respond within 48 hours.