Privacy Policy

What we collect, why, and what we do with it.

A security agency holds two kinds of data: the account and contact details that run the business, and whatever it comes across while testing a client's systems. Both are covered here, in plain English and without a cookie banner.

Effective 15 November 2026Version 1.0Rules & RegulationsTerms of Service
01

Who We Are, and What This Covers

FindHyde is a cybersecurity agency that tests applications and reports on what it finds. For the data described here, FindHyde is the controller: we decide what is collected and why. For the systems we are asked to test, we are a processor acting on the written instructions in a statement of work.

This policy covers the public site, the contact form, the demo request, the client portal and the data we handle during an engagement. It does not cover a third-party service you reach from a link on this site — that service's own notice applies there.

  • Questions, or a request about your data: write to the address on the contact page. It is read by the person who runs the engagements.
  • The service is sold to organisations, not children; we do not knowingly collect data from anyone under 16.
  • If you write to us about a system you do not own, say so — we route that to the owner rather than storing it as an enquiry.
02

What We Collect

We collect what the service needs to work: who you are, how to reach you, what you asked for, and the record of the engagement itself. Nothing is collected to build an advertising profile, and nothing is sold.

Most of it comes from you. A little of it — a timestamp, an IP address, a browser string — arrives with any request your browser makes and is kept for security and troubleshooting rather than analysis.

  • Account and onboarding: name, email address, company, role, and the plan you chose.
  • Messages: what you send through the contact form, the demo request or the portal, including any file you attach.
  • Engagement record: scope, engagements, findings, report text, retests and the status of each.
  • Checkout: the plan bought, the amount and the reference the payment processor returns — never a card number.
  • Technical logs: timestamps, IP address, user agent and the action taken, kept to detect abuse and to debug failures.
03

Why We Use It

Some of this data is needed to sell you anything at all, some of it keeps the portal safe, and a little of it we ask permission for. The list below says which is which, so you can see where a request would stop us working and where it would not.

Each purpose rests on one legal basis, and we do not quietly reuse data collected for one purpose for another. Where consent is the basis — marketing email, for example — it can be withdrawn at any time and the withdrawal is as easy as the sign-up was.

  • To deliver the engagement and the portal (performance of a contract): the account, the scope, the findings and the report.
  • To answer an enquiry (legitimate interest): your message and the address to reply to, for as long as the conversation lasts.
  • To keep the portal secure (legitimate interest): sign-in events, IP addresses and access logs.
  • To meet the law (legal obligation): invoices, tax records and anything a lawful request requires.
  • To send occasional product news (consent): only if you opted in, with an unsubscribe link in every message.
04

Cookies, Sessions and Sign-In

The site sets the cookies a sign-in needs and nothing else. There is no advertising cookie, no cross-site tracker and no third-party analytics script on the public pages, so there is no cookie banner to dismiss.

  • Supabase authentication cookies keep you signed in and refresh the session; they are essential and cannot be turned off while you hold an account.
  • The page you asked for before signing in travels in the address itself — `/login?next=/demo` — rather than in a cookie, so it is not stored on your device and disappears when you leave the sign-in page.
  • Signing out clears the session cookie; clearing site data in the browser removes all of them.
05

Data Inside the Systems We Test

An engagement is confined to the assets a signed statement of work names — nothing is tested by implication, and production data is read-only unless that document says otherwise.

While testing we may see customer records, source code or credentials that belong to you or to your users. We take the minimum needed to prove a finding, and we do not exfiltrate, copy or keep a dataset to browse later.

  • Test accounts and test objects are used wherever a finding can be proven with them; a real account is used only with your written permission.
  • Proof-of-concept screenshots and videos are cropped or redacted, so a report does not spread the data it demonstrates.
  • Credentials shared with us are held for the engagement, then destroyed with the rest of the engagement material.
  • No customer dataset is copied out of your environment: where a finding needs a sample, it is described rather than retained.
  • Anything you hand over stays yours; we claim no licence to it beyond delivering the engagement.
06

Confidentiality and NDAs

Confidentiality is the default for everything an engagement touches. A mutual non-disclosure agreement is available on request and is signed before credentials, diagrams or screenshots are shared — without one, the Terms of Service and the statement of work are the confidentiality terms.

The report itself is confidential client information. It is seen by the people delivering the engagement rather than the whole company, and it does not become a reference, a case study or a slide without your written agreement.

  • Everyone who works on an engagement — including anyone brought in for it — signs an individual confidentiality undertaking.
  • Access is need-to-know: a tester sees the systems and findings of the engagement they are working on, not every client's.
  • Disclosure is made where the law compels it, limited to what is required, with notice to you unless we are barred from giving it.
  • The obligation continues after the engagement ends, and outlives the account.
07

Who We Share It With

We share data with the service providers that make the portal work, and with nobody else unless you ask us to or the law requires it. Each provider is bound to use it only for the service it supplies.

  • Supabase — authentication, database and file storage for accounts, engagements and reports.
  • A payment processor — checkout and receipts; card details are entered there and never reach our servers.
  • An email provider — sign-in links, notifications and replies.
  • Professional advisers and authorities, where the law or a court order requires it.
  • Never sold, never rented, never handed to an advertising network.
  • A successor on a merger or acquisition, under the same confidentiality terms and with notice to you.
08

How Long We Keep It

Data is kept while the account exists, and for as long afterwards as the document it belongs to is still needed — an invoice for the tax years it covers, a report for its retest and support windows, a contact message until the conversation is closed.

  • Contact and demo messages: 24 months after the last reply, then deleted.
  • Portal messages, findings and reports: the plan's retest and support window, then a further 12 months so a follow-up question can be answered, then deleted unless you ask us to keep them.
  • Engagement material — test accounts, notes, proof-of-concept files: deleted or handed back when the engagement closes, except what the report itself needs.
  • Invoices and payment records: kept for the period the tax law requires.
  • Security logs: 90 days, unless they are evidence of an incident that is still being handled.
09

How We Protect It

The discipline we sell is applied to the portal: least privilege, encrypted transport, and a database where row-level security decides which rows an account can read rather than the page it happens to open.

No system is perfectly secure, and a security agency claiming otherwise would be the last one to trust. If data is exposed, we tell the people affected and the regulator where the law requires it, and we say what happened rather than what would have been convenient.

  • TLS on every request, and data at rest encrypted by the providers we use.
  • Multi-factor authentication on the accounts that can reach client data, and access removed when someone stops working with us.
  • Row-level security in the database, so one client's engagement is unreadable from another client's session.
  • Only the personal data an engagement needs is collected — the cheapest security control there is.
10

Your Rights

You can ask what we hold about you, why, and who has seen it; ask for a copy; ask for a correction; and ask for it to be deleted. Write to the address on the contact page from the email address on the account, and we answer within 30 days.

Two limits are worth stating plainly: a deletion request cannot remove a record the law requires us to keep — an invoice, or evidence in an open dispute — and it cannot remove a report that is part of a delivered engagement until that report's retention period ends.

  • Access: a copy of the personal data we hold about you, in a readable format.
  • Correction: fix a name, a company or an address that is wrong.
  • Deletion: remove what we are not required to keep, and confirm when it is gone.
  • Portability: receive the data you gave us as a machine-readable export.
  • Objection and restriction: stop a processing activity, including marketing email, which needs no explanation at all.
  • Complaint: raise it with your local supervisory authority if our answer does not satisfy you.
11

Where It Is Stored

The portal and its database live in the Supabase project's region, and email is delivered through a provider that processes it in transit. Where a provider stores data outside your country, the transfer relies on that provider's standard contractual clauses.

If a data-transfer review needs the specific region or the provider's sub-processor list before you sign, ask — it is confirmed in writing as part of the statement of work rather than guessed at here.

12

Changes to This Policy

This policy carries a version and an effective date at the top of the page. It changes when how we handle data changes — a new provider, a new portal feature, a new retention window — not on a schedule.

A material change is announced by email to the address on the account, or as a notice in the portal, before it takes effect. The previous version is kept and can be requested.

13

Contact

For a question about this policy, an access or deletion request, or a security concern about the portal: write to the address on the contact page, or use the form and say it is a privacy request. Data requests are answered within 30 days, and a security report is acknowledged faster.

Something unclear?

Ask before you sign. If your review needs a data-processing agreement, the storage region or the sub-processor list, ask for it — it is agreed in writing, not assumed.