securick

Privacy policy

Last updated 13 November 2026.

Who we are

Securick is run by the operator of Securick (details on our contact page). We decide how your personal data is used (we're the "controller" under the GDPR and UK GDPR). Questions or requests: support@securick.com.

What we collect, and why

The Chrome extension

If you use the Securick extension, it sends us only the address of the page you choose to scan, when you click Scan (or pick "Scan with Securick" from the right-click menu). It doesn't read the pages you visit, your browsing history or anything you type. In your browser it keeps the key that connects it to your account and the id of your last scan per site; Disconnect (or uninstalling it) removes them, and you can revoke the key under API keys on your account page. Why: to run the scans you ask for (contract).

Cookies

We use only cookies the site needs to work, so we don't ask for consent (ePrivacy Directive Art. 5(3)): lp_session keeps you signed in (30 days, renewed while you use it), lp_scans remembers the scans you ran in this browser so they can join your account when you sign in, and lp_admin is for our own admin page. While you sign in with Google, lp_google (15 minutes) makes sure the sign-in finishes in the browser that started it. We don't use analytics, advertising or tracking cookies, and we don't load third-party trackers.

Who processes data for us

Some of these companies are in the United States. We use them under their data processing terms, which include the EU Standard Contractual Clauses (and the UK addendum) for transfers outside the EEA and UK.

How long we keep it

Your rights

You can ask to see, correct, delete or export your data, object to our use of it, or restrict it (GDPR Art. 15–21). Most of it you can change or delete yourself on your account page; for anything else write to support@securick.com and we'll answer within one month. You can also complain to your data protection authority (in the UK, the ICO).

California residents: we don't sell or share personal information, and we don't use it for targeted advertising.

Children

Securick is for people building and running websites. It isn't meant for children under 16, and we don't knowingly collect their data.

Security

Data travels over HTTPS only; passwords are hashed with scrypt; session ids, sign-in links and API keys are stored only as hashes; the Supabase token is encrypted (AES-256-GCM). Found a security problem? See security.txt.

Changes

If we change this policy in a way that matters, we'll say so on this page and, if you have an account, by email before it takes effect.