Identity and access
OAuth and passwordless sign-in, optional user two-factor authentication, session expiry and revocation, role-based access, and single-use hashed invitation tokens protect account and workspace access.
Security at RodGrid
RodGrid is built to protect account, workspace, and interview data without hiding behind vague compliance language. This page explains the controls in place today, how we respond when something goes wrong, and where our assurance program is still growing.
Security controls
These controls describe the current product and operating posture. They are not a claim of certification.
OAuth and passwordless sign-in, optional user two-factor authentication, session expiry and revocation, role-based access, and single-use hashed invitation tokens protect account and workspace access.
Authorization checks, request limits, input validation, security headers, signed billing webhooks, and focused regression tests protect the application boundary.
RodGrid avoids raw card storage, hashes security tokens and audit identifiers where practical, and limits collected information to operating and protecting the service.
Cloudflare, Paddle, OpenAI, Resend, GitHub, and Google support defined parts of the service. Data flows and subprocessors are disclosed in the Privacy Policy.
Account and Grid deletion, backup windows, export options, and configurable interview retention help reduce how long information remains in the service.
Automated tests, secret scanning, dependency vulnerability scanning, operational logging, health checks, and code-level security reviews are used to detect regressions and investigate issues.
Incident response
A lightweight response process gives us a clear sequence to follow instead of improvising during a security event.
We record the report, preserve relevant evidence, determine severity, and identify affected systems and people.
We revoke access, rotate credentials, disable affected paths, or take other proportionate steps while determining the cause and scope.
We fix and verify the issue, monitor for recurrence, and notify affected people or authorities when required by applicable law.
Current assurance
Trust should come from specific, verifiable statements. We do not present future work as a completed control.
Responsible disclosure
If you believe you found a security weakness in RodGrid, please send it privately to our security inbox. We appreciate clear, good-faith reports and will review them as quickly as practical.
security@rodgrid.ioPlease do not access other users' information, disrupt the service, use social engineering, or publicly disclose an unresolved issue.