Legal

Security Policy

How this site is built to keep your payment and your details safe.

Draft. This describes how the site actually works, but it has not been through legal review and does not yet meet the disclosure rules of any particular jurisdiction. Do not treat it as the published policy.

Last updated 21 August 2026

A small shop cannot claim enterprise security, so this describes what is actually in place rather than what sounds impressive. The single most important thing on this page is that we never hold your card number.

01

Payments

Card details are typed into fields that Stripe serves and controls, embedded in our checkout page. They live in Stripe's own document, not ours, so the card number never passes through our servers and is not stored in our database — there is nothing there for an attacker to take.

Stripe is a PCI DSS Level 1 service provider. What we hold is a payment reference, which lets us match a payment to an order and issue a refund, and is useless on its own.

02

In transit

The whole site is served over HTTPS. Requests over plain HTTP are redirected, so nothing you send — an address, a message, a password — travels in the clear.

03

Accounts

  • Passwords are stored only as salted hashes. We cannot read yours, and neither can anyone who takes the database.
  • Sessions are cookie-based and strictly necessary; signing out ends them.
  • Sensitive endpoints are rate limited, so a stolen password list cannot be tried against them at speed.
04

At rest

Orders, addresses and contact messages live in a managed Postgres database that is not reachable from the public internet. Access is limited to the people who need it to run the shop, and the admin area sits behind its own authentication with roles.

05

What we do not claim

Stated plainly, because a security page that only lists strengths is a marketing page:

  • No independent penetration test has been carried out on this site.
  • We hold no SOC 2, ISO 27001 or equivalent certification.
  • There is no bug bounty — reports are welcome and credited, but not paid.
  • Two-factor authentication is not yet available on customer accounts.
06

If something goes wrong

If customer data is exposed we will tell the people affected directly, say what was taken and what was not, and notify the relevant regulator inside the window the law sets. We would rather send an early email that turns out to be cautious than a late one that turns out to be necessary.

07

Your side of it

Use a password you have not used elsewhere. We will never email you asking for your password or full card number — if you get a message like that claiming to be us, it is not, and we would like to know: hello@megaresources.co.

Something here not clear?

Ask us plainly and we will answer plainly — and if the answer shows this page is wrong, we will fix the page.

Write to us