Last updated October 2026
Privacy Policy
Verilay is a security analysis tool built by Moses Ekbote, free to use with an optional paid deep scan. This policy explains what we collect, why, and how you can delete it — for both the free tool and the paid tier.
What we collect
- The GitHub link, live address, or ZIP file you submit for analysis. We read your code to run the analysis. We do not keep your project's files (see “How your data is stored”)
- If you scan a live address: Verilay asks for that address the way a browser does (the page, its http:// version and the standard /.well-known/security.txt), reads the dates on its public certificate, and looks up the public email records (SPF and DMARC) of the domain you typed. It never looks for hidden files. The report keeps only plain facts from this: header names and values, the names and protection flags of cookies (never their contents), and yes or no answers
- If you use the private-repository beta: you install the Verilay GitHub App on your account, with read-only access to code, and choose one repository. Verilay reads that repository once and then removes its own access. We keep the report, marked private (findings, score, file names and a summary, as for any report). To apply the daily limit we keep a count tied to a scrambled version of your GitHub account number, not your name, email or repository, for about two days
- The analysis results — findings, score, and layer breakdown
- Your IP address, to limit how many requests one person can make. For free scans the hourly limit is kept only in the server's memory and is lost when it restarts; the daily limit of free scans is a counter stored in our database under a scrambled version of your IP address (the address itself is not kept), deleted automatically the next day. For the Ask AI box, a counter is stored in our database under a scrambled version of your IP address (the address itself is not kept), and counters older than two hours are deleted automatically whenever the box is used
- If you join the waitlist — your email address
- If you rate a report — your thumbs up/down, and any comment or email you choose to add
- If you answer the feedback question after a scan that improved — whether the fix prompts helped, anything you choose to write (your opinion and, only if you want, how you fixed it), any email you add, and the two ticks (whether we may quote you and whether you want early access to fix sessions)
- If you buy a deep scan or sign in — your email address, so we can identify your purchase and let you sign back in
- If you subscribe to the monthly newsletter — your email address, used only to send the newsletter. Every issue has an unsubscribe link
- For each scan, the country it came from (a 2-letter code worked out by our network provider, Cloudflare). We don’t keep your IP address or city, and the country is never shown on a report
- For each scan, the name of the website that sent you to Verilay, if your browser says (for example “Google” or “LinkedIn”). Only the site’s name, never the page you were on, and it is never shown on a report
- If you scan a private repository — your email address (you sign in with it) and the report, which is kept private to your account and removed after the private-report period; never your code
- If you list an app in the app directory — what you write about it, your name (shown on the listing) and your email (never shown; messages from visitors are sent to it)
- If you contact an app’s builder through the directory — your email and message, which we email to the builder and keep
What we do not collect
- The free analysis of public code or a ZIP needs no account — we don't know who you are unless you buy a deep scan, scan a private repository, or sign in
- No advertising or analytics trackers
- If you register interest in monitoring, we store your email and your answers and use them only to tell you about monitoring
- If you register interest in private repository support, we store your email and your answers and use them only to tell you about that
- No payment card details — Stripe handles payment directly and Verilay never sees or stores your card number
- No access to your GitHub account beyond what you explicitly submit or approve — public repositories are read through GitHub's public API, a private repository only when you connect it in the private-repository beta (see below), and Verilay never writes to or modifies any repository
How your data is stored
Analysis reports are stored in Supabase (hosted in the EU) linked to a random report ID. Reports are accessible only via your unique share link. We do not publish, share, or sell individual report data.
The share link of a free analysis keeps working for 90 days after the scan. After that the link stops working and the report is no longer shown to anyone. The stored copy is not erased automatically, so email [email protected] if you want it erased. We may look at stored reports (not your project's files, which we do not keep) to improve the product. You can delete your report at any time using the Delete Report button on your report page, which removes the report (its findings, score and file names).
A saved report contains the findings, the score, the names of the files that were read, a summary, and the detected tools. A finding can mention a function name or a short piece of code, and a key that was found is shown only in part (for example the first few characters). A report never contains your project's files. Anyone who has a report's link can open it, so share it only with people you trust.
Private reports (beta). A report from the private-repository beta opens only in the browser that ran the scan, and for the site's admin. Its link stops working after 30 days, and you can delete it at any time with the Delete Report button. As with other reports, the stored copy is not erased automatically when the link stops working, so email [email protected] if you want it erased. Private reports are never shown in the app directory and are never reused for another visitor's scan.
Services that help us run Verilay
- AI analysis. To analyse your code, parts of it are sent to Claude, an AI service made by Anthropic. Under Anthropic's business terms, content sent this way is not used to train its models.
- Storage. Reports are stored in Supabase (hosted in the EU).
- Hosting and network. The site runs on Railway and is served through Cloudflare, which see your IP address in the normal way. When you scan a live address, the domain you typed is also looked up through Cloudflare’s public DNS service.
- Payments. For the deep scan, Stripe.
- GitHub. If you use the private-repository beta, GitHub lets Verilay read the one repository you choose, with your permission and read-only access. Verilay never uses its own GitHub access to read private code.
Accounts and the deep scan
Signing in uses a passwordless email link — we never ask for or store a password. Buying a deep scan records your email, the app it was purchased for, the amount paid, and the purchase date; this comes from Stripe, which does not verify the email it collects, so a payment on its own does not sign you in. Signing in with that same email afterward links your purchase to an account so your reports are still there when you come back. When you sign in, the reports this browser made earlier (and any comparison saved on them) are linked to your account as well, so they stay on your account page instead of expiring after 90 days; you can still delete any of them.
Deep-scan reports are tied to your account rather than a share link alone, and are kept for as long as your account exists. You can request account and purchase-record deletion at any time by emailing [email protected] — note that Stripe keeps its own transaction records independently, for tax and accounting purposes, which we cannot delete on your behalf.
Statistics
We track aggregate statistics — total analyses run, score distribution (how many A/B/C/D/F grades), and analysis method. This data is anonymised and used to improve the product.
Waitlist emails
If you join the waitlist, your email is stored in Supabase and used only to notify you when new features launch. You can request deletion by emailing [email protected].
App directory
When you list an app, your name and what you write about the app are shown publicly on verilay.dev/apps once the listing is approved. Your email is never shown: when a visitor uses “Contact the builder”, we email their message to you with their address as the reply-to, so you can answer them directly. We keep each visitor’s email and message so we can see which apps people are interested in; they are never shown publicly. You can ask for a listing or a message to be removed by emailing [email protected].
Feedback
If you rate a report and choose to leave a comment or email, these are stored with that report in Supabase. Email is optional and used only to follow up about the feedback you left — for example to let you know an issue was fixed. You can request deletion by emailing [email protected].
If you answer “did Verilay’s fix prompts help?” after a scan that improved, your answer is stored with that report and emailed to us. Saying how you fixed it is always optional. It is never shown on the report. We quote it on verilay.dev only if you ticked that box, and never with your name. An email is optional; if you also ticked early access, it joins our waitlist for fix sessions. You can request deletion by emailing [email protected].
Your rights
- Delete your report anytime using the Delete Report button
- Request deletion of your account, purchase record, waitlist entry, or feedback email at [email protected]
- If you've never signed in or paid, there's no account data to delete — the free tool remains fully anonymous
Contact
Questions about privacy: [email protected]