Skip to content
ScanPry

Privacy Notice

Last updated November 23, 2026

This notice explains what personal data ScanPry handles, why, who processes it for us, and how long it is kept. ScanPry is responsible for it; write to support@scanpry.com with any question or request.

1. What we collect

  • Your account: your email address, the name you choose to show (if any), and your password and second-factor secret, which our authentication provider stores in a form we cannot read back.
  • Your organization and team: the names of your organization, workspaces and projects, who belongs to them and in which role, and the email addresses invitations were sent to.
  • What you ask us to test: the addresses of your targets and the proofs of control you publish, and the source archives you upload.
  • What scans produce: findings, the evidence engines captured from your targets, the hosts, pages and technologies they observed, and reports. Evidence can contain whatever your systems returned, including personal data about your own users.
  • Security records: which account did what and when, the network address a request came from, and the address and browser of each sign-in.
  • Technical data: the few cookies listed below, and the service's operating logs.

2. How we use it

  • To provide the service you signed up for: run the scans you start and show you their results.
  • To keep it secure: require a second factor, limit repeated sign-in attempts, and keep a record of who added each target and started each scan, which is how we answer a complaint that a scan was not authorized.
  • To send the emails the service depends on: invitations and sign-in codes.

We do not sell personal data, use it for advertising, or build profiles of you. The service has no analytics or advertising trackers.

3. Who processes it for us

  • Supabase, which hosts the database and handles sign-in, in its Singapore region.
  • Cloudflare, which runs the application, stores uploaded archives, evidence, reports and the database's encrypted backups, carries all traffic to and from the service, and delivers its email: invitations, sign-in and reset codes, and security notices. It keeps a log of each email it sends, including the address it went to, that can be read for 30 days, and does not keep the email's text. An address that email cannot reach, or whose owner reports an email as spam, goes on its list of addresses not to send to, for the times in section 4.
  • Have I Been Pwned, which we ask whether a new password appears in known breaches. It receives only the first five characters of a one-way hash of the password, never the password or who is setting it.

The scanning engines run on infrastructure we control and send their requests only to targets whose control you have proven, with one exception. To tell which versions of its libraries a Java (Maven) project uses, the dependency scanner asks Google's public mirror of Maven Central for the published description of each library the project's build files name. Each of those requests carries one library's group, name and version, which can be the name of a library your organisation keeps private, and nothing else from your code.

4. How long we keep it

  • Uploaded source archives: 24 hours after the last scan that read one finishes, or 48 hours after that scan began if it never finishes; 24 hours after upload if no scan reads it; one hour after an upload that was never completed.
  • Secrets found in your code: never stored. We keep where each one is and a redacted fingerprint.
  • Scans, findings, evidence and reports: for as long as your organization uses the service, or until you ask us to delete them.
  • The network address an audited action came from: 90 days.
  • The audit trail of actions: for as long as the service runs. It is the evidence that each scan was authorized, and the application has no permission to change it.
  • Per-minute limits on sign-in attempts: 60 seconds.
  • Counts of consecutive failed sign-ins, kept under a one-way hash of the email address or account they were for: deleted after 30 days without another failure. A lock after 100 consecutive failures stays until the account is recovered.
  • The service's operating logs, at Cloudflare and Supabase: at most 7 days.
  • Cloudflare's log of each email it sent: 30 days.
  • An address on Cloudflare's list of addresses not to send to: 24 hours after a temporary failure, such as a full mailbox; seven days after some permanent ones; and with no end date when the mailbox or its domain does not exist, when delivery keeps failing, or when its owner reported an email as spam.
  • Your account and profile: until you delete your account, or ask us to. Your name and email address then go for good; what remains is an identifier that names no one, kept so that your organization's records still show that someone did the work they record.
  • Backups of the database, encrypted so that only we can open them: one a day, each kept 36 days. Something deleted from the service stays in the backups taken before it until they are deleted in turn, and we open a backup only to restore the service.

5. Cookies

  • A session cookie that keeps you signed in, until you sign out or the session ends.
  • NEXT_LOCALE, the language you chose, for a year.
  • USER_TZ, the time zone dates are shown in, for a year.
  • sidebar_state, whether the sidebar is open, for 7 days.

All four are needed for the service to work as you set it. There are no advertising or analytics cookies.

6. How we protect it

Traffic is encrypted in transit. A second factor is required for any account that can start a scan. Each organization's data is separated from every other's by rules in the database itself, and uploaded code is analysed without ever being run. The audit trail is protected from change by the database's permissions, not by convention.

7. Your choices and rights

You can change the name you show, your password and your second factor in your account settings, and delete your account there (Settings, then Profile). Deleting it signs you out everywhere and removes your name, your email address and your place in every organization; what you did there (targets, scans, uploaded code, triage decisions) stays with the organization, attributed to no one. The last owner of an organization cannot delete their account until the organization has another owner or is closed; write to support@scanpry.com for either. To get a copy of your personal data, to have it corrected or deleted, or to object to how it is used, write to support@scanpry.com. We answer within 30 days. Some records — the audit trail above all — are kept because the security of the service and of other people depends on them; if we cannot delete something, we will tell you why.

8. Where it is processed

The database is in Singapore. Cloudflare runs the application on its global network, so a request is handled in the location nearest to whoever makes it, and stored files are kept in its object storage. Cloudflare, which also delivers the service's email, is a company in the United States. Using the service means your data is processed outside the country you are in.

9. Children

ScanPry is a professional tool for organizations. It is not meant for anyone under 18, and we do not knowingly hold their data.

10. Changes to this notice

When this notice changes, the date at the top changes.