Cyclosa web scraping service logoCyclosa
HOW IT WORKSSERVICESHOW IT WORKSPRICINGABOUTBLOG
LOG INGET STARTED
TRUST

Security

How accounts, credentials and your results are protected — and, just as usefully, which protections we do not have yet.

LAST UPDATED 14 SEPTEMBER 2026

Every claim on this page describes something the software does today. Where we have not built a thing, it is in the list of what we do not have rather than left out.

Your password

  • Stored as a bcrypt hash and nothing else. We cannot read it, we cannot email it back to you, and neither could anyone who walked off with the database.
  • Never written to a log, never sent to a third party, and never included in an export.
  • Checked against a decoy hash when the address is unknown, so the time a sign-in takes does not reveal whether an account exists.
  • A wrong password is counted against the account. Five in a row locks it for fifteen minutes, and retrying a locked account does not push the release further away.

Getting in, and staying out

Guessing arrives in two shapes, and one counter catches only one of them. So there are two.

SHAPEWHAT STOPS IT
Many guesses at one accountThe per-account counter above. Five failures and the account is locked.
One guess each at many accountsA per-address counter. Thirty failures from one network and it stops answering for fifteen minutes. Signing in successfully does not reset it — otherwise anyone with an account of their own would hold the reset button.
Opening accounts in bulkA daily cap per network, a lockout after repeated refusals, a block on known disposable mailbox providers, and a field no person can see that only an automated submission fills in.
Signing in to the operator consoleSeparate credentials, a separate counter, and its own signed eight-hour cookie. A run at the customer form cannot lock operators out, and vice versa.

Confirming an address

  • No account is created until the code is entered. A signup that is never confirmed leaves no user row behind and releases the address after 24 hours.
  • The code is six digits, drawn from a cryptographic source, and stored only as a SHA-256 digest — the same way the password is.
  • It expires in 60 seconds, and five wrong guesses spend it. A million possibilities against five attempts is not a code anyone grinds through.
  • Reset links work once, expire in two hours, and using one retires every other outstanding link on the account — so if a stranger asked for one, the real owner acting cancels it.
  • Signing in with Google is refused unless Google itself reports the address as verified, because an unverified one could otherwise claim an existing account.

Data and payments

  • Everything travels over HTTPS. There is no plain-HTTP path into the service.
  • Card details go to Polar directly. They never reach our servers, so there is nothing of that kind here to take.
  • Your jobs and results are scoped to your account. The 24-hour page cache is shared between customers, but only the fetched public page is shared — never a list, a job or a result set.
  • Internal calls between the web tier and the API carry a service key compared in constant time, so the endpoints that verify credentials are not reachable from a browser.
  • What we hold, and for how long, is set out in the privacy policy rather than summarised loosely here.

What we do not have yet

A security page that lists only strengths is a marketing page. These are the gaps, stated plainly so you can decide whether they matter for your use case.

  • No two-factor authentication yet. It is the next thing we want to add to accounts.
  • No SOC 2 or ISO 27001 certification. We are too small to have been through either, and we are not going to imply otherwise.
  • No third-party penetration test has been done. When one has, this page will say when and by whom.
  • No contractual uptime guarantee. If you need one, talk to us about it separately.

Reporting something

If you have found a vulnerability, write to hello@cyclosa.studio with enough detail to reproduce it. We will acknowledge within three working days and tell you what we are doing about it.

Report it in good faith and we will not pursue you for it. Test only your own account, stop as soon as you have shown a problem exists, and do not access, change or keep anyone else's data. We have no paid bounty, but we will credit you if you would like us to.

If a breach ever affects your data, we will tell you what happened, what was reached and what we did — within 72 hours of establishing it, and without waiting until we have a tidy story.

Related pages

Privacy policyWhat we hold and for how long.Cookie policyThe cookies a session needs.Acceptable useWhat the agent will and will not fetch.

Found something? Tell us.

Reports in good faith are welcome, acknowledged within three working days, and never met with a lawyer.

REPORT AN ISSUE