Contact support
Email info@div3rsa.com. To help us investigate efficiently, include the affected DIV3RSA workspace, the relevant integration, the Vercel team/project name and any deployment ID or timestamp connected to the issue.
Vercel integration support
Connection or installation issues
If Vercel authorization does not complete, confirm that you selected at least one project and approved the requested permissions. DIV3RSA intentionally does not mark an identity-only Vercel login with zero readable projects as a completed resource connection.
Project access changed
If a project was added or removed in Vercel, allow the signed integration webhook to synchronize the updated installation scope. Reconnect from DIV3RSA if Vercel requires a new permission approval.
Deployment or log issue
Provide the Vercel deployment ID when possible. DIV3RSA can use an authorized deployment ID to retrieve current deployment, build and runtime context without requiring you to send credentials to support.
Full setup instructions are available in the Vercel integration documentation.
Account and access issues
For sign-in, verification, workspace membership or access-application problems, contact support from the email address associated with your DIV3RSA account when possible. We may request additional information to verify account ownership before making security-sensitive changes.
Security reports
If you believe you have found a security vulnerability affecting DIV3RSA, contact info@div3rsa.com with the subject DIV3RSA Security Report. Include enough information to reproduce and assess the issue, but do not access data that is not yours, disrupt production systems or expose secrets in the report.
We ask researchers to act in good faith, limit testing to authorized systems and avoid privacy violations, destructive activity, denial of service and social engineering.
Service status and third-party dependencies
Some DIV3RSA functionality depends on third-party providers selected by the user, such as Vercel, GitHub and infrastructure providers. A provider outage, permission change or API change can affect an integration even when DIV3RSA itself is available.
What to include in a useful report
- DIV3RSA workspace or organization name.
- Feature or integration affected.
- Approximate date and time, including time zone.
- Expected result and actual result.
- Relevant project, repository or deployment identifier.
- Screenshot or non-sensitive error text where useful.
- Whether the issue can be reproduced.
Legal and privacy
See the End User License Agreement and Privacy Policy. Privacy requests can also be sent to info@div3rsa.com.