Security & trust
You're giving us access to your code. Here is exactly what that access allows, what we do with it, and what we never do.
What we access
| What | Why | How | You can stop it |
|---|---|---|---|
| Your repository's code, only repos you select | To scan it and prepare fixes | GitHub App with read access, plus rescue/ branches and pull requests | Remove the app in GitHub settings |
| Your live site's public pages | To run live checks | Ordinary read-only requests, slowly, identified as our scanner | Contact us; we stop within one business day |
| Optional read-only token | Deeper checks, such as backup settings | A time-limited token you create, stored encrypted | Revoke it, or ask us to delete it |
| Optional backup file | Restore drill | Encrypted, restored only in a temporary environment, deleted after | Ask us to delete it |
| Your email and GitHub username | Your account | GitHub or an email link | Delete your account |
What we never do
- Ask for your passwords.
- Merge pull requests or push to your main branch.
- Deploy to your live app or switch your domain.
- Write to your database, submit forms or try to break in to your live site.
- Change your payments or billing settings. Refunds we give you are approved by a person.
- Sell or share your code or data.
- Call your app "secure". We report which checks passed, on which commit.
How we handle your code
Your code is scanned inside a temporary, isolated environment. The environment is deleted when the job ends. We don't keep a copy of your code. We keep short, redacted snippets around each finding. When we find a secret, we store its type, a few characters and a fingerprint, never the full value.
AI is used to explain findings and draft fixes only after you agree. Prompts are redacted first. We store how much AI was used, not what was sent.
Data handling
Form entries and free scan results are stored on our hosting provider's servers (Hetzner, Helsinki, Finland) and in their encrypted backups. Free scans are deleted after 30 days. Waitlist entries and contact messages are deleted 12 months after they were last sent or updated. We keep short-lived access logs, including IP addresses, to keep the site running and spot abuse. Access logs are kept for 14 days.
This policy is governed by US law and the laws of the State of Wyoming. You can ask to see, correct, export or delete your personal data. You can object to processing that is based on legitimate interests, and you can withdraw consent. If you have a concern about your data, email hello@rivyva.com and we will reply within 30 days. To ask us to delete your personal data, email hello@rivyva.com or use the contact form and choose the topic Privacy / delete my data. We reply within 30 days.
How we run our own operations
People who can see customer data use two-factor authentication. We keep short-lived access logs, including IP addresses, to keep the site running and spot abuse. Changes go through code review. Creating or rotating a key needs a second person's approval. We do not hold an independent audit today. We plan to pursue one once the product is established.
Report a vulnerability
Email hello@rivyva.com with "Security report" in the subject. Please don't access other customers' data or disrupt the service while testing. We'll reply within 3 business days. Our policy is on the disclosure page, and security.txt is published for this site.
Disclosure policy → · Sub-processors → · Privacy policy → · DPA →