Security

The website,
in facts you can check.

This page describes patrium.ai, our public website, not the Patrium platform, which is a separate system.

Last reviewed: 8 November 2026

Report a vulnerability

If you think you have found a security issue in patrium.ai, email amr@patrium.ai with the subject "Security report". Tell us:

  • Where you found it: the address of the page or the request.
  • The steps to reproduce it.
  • What someone could do with it.
Email amr@patrium.aiSubject: Security report

We acknowledge every report within three business days. The full disclosure policy is below, and the same contact is published for researchers at /.well-known/security.txt.

The website, in facts

Served over HTTPS
Every page is served over HTTPS. Browsers are told to use only HTTPS for this site for the next two years (HSTS).
Limited external sources
The site serves its styles, fonts and images from patrium.ai. Its policy also permits PostHog EU analytics scripts and requests when analytics is enabled.
Cookieless analytics
The site sets no cookies. It uses PostHog for usage analytics, without session recordings, heatmaps or surveys. The privacy notice explains what it collects.
Cannot be framed
No other website can show these pages inside a frame.
No accounts here
The site has no accounts and no sign-in. Signing in happens in the Patrium app at app.patrium.ai, which is a separate service.
Hosted with AWS in the EU
The website is hosted with Amazon Web Services (AWS) in the European Union. Its server logs are kept for a few days.

Security headers

The pages on patrium.ai are served with these headers. The values are the ones the live site sends.

Strict-Transport-Security
max-age=63072000

Tells your browser to use only HTTPS for patrium.ai for the next two years.

X-Frame-Options
DENY

No other site can put these pages in a frame.

X-Content-Type-Options
nosniff

Your browser trusts the declared type of each file instead of guessing it.

Referrer-Policy
strict-origin-when-cross-origin

When you follow a link to another site, it learns that you came from patrium.ai, not which page.

Permissions-Policy
camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=()

The page gives up the camera, microphone, location, payment, USB and advertising-topics APIs.

Cross-Origin-Opener-Policy
same-origin

A page on another site that opens patrium.ai in a new window cannot keep a handle on it.

Content-Security-Policy
default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self' data:; connect-src 'self'; worker-src 'self' blob:; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests

Limits page resources to this site and, when analytics is enabled, PostHog EU's ingest and assets hosts. Inline scripts and styles support the page bootstrap; WebAssembly supports its animations.

Check them yourself:curl -sI https://patrium.ai

The Patrium platform

This page describes the website only. The Patrium platform at app.patrium.ai is a separate system, and this page makes no claims about it.

If your organisation needs security information about Patrium for a review, write to amr@patrium.ai and we will answer directly.

For security researchers

Vulnerability disclosure policy

We welcome reports from anyone who finds a security issue in our website, and we want working with us to be simple.

If you make a good-faith effort to follow this policy during your research, we consider your research authorised, we will work with you to understand and resolve the issue quickly, and we will not recommend or pursue legal action related to your research.

Scope

You are authorised to test these systems:

  • patrium.ai
  • www.patrium.ai

Anything not listed is out of scope and not authorised for testing. That includes the Patrium platform at app.patrium.ai: we want to hear about anything you find there, by email, but you do not have permission to test it. If you are not sure whether something is in scope, ask us first.

Out of scope

Services run by other companies are out of scope: the Cal.com booking page, AWS itself and our email provider. Report an issue in one of those to the company that runs it, under its own policy.

On a public website like this one, we also do not treat these as vulnerabilities:

  • Missing DNSSEC or CAA records.
  • Clickjacking on pages with no sensitive actions.
  • Attacks that need physical access to a visitor's device, or a position between the visitor and the site.
  • Email spoofing.
  • Content spoofing or text injection with no attack path.
  • Output from automated scanners with no working proof.

Rules

While you research:

  • Test only the systems in scope.
  • Do not run denial-of-service tests, or anything else that impairs access to a system or damages data.
  • Do not try physical testing, social engineering such as phishing, or any other non-technical attack.
  • Use an exploit only as far as you need to confirm a vulnerability is there.
  • Do not access, change or delete data that is not yours. If you meet personal data during testing, stop and report at once.
  • Do not send a high volume of low-quality reports.
  • Do not ask for anything in return for a report.
  • Give us reasonable time to fix an issue before you tell anyone else.

How to report

Email amr@patrium.ai with the subject "Security report", one issue per email. Details as text in the body are more useful to us than attachments. Tell us:

  • Where you found it: the address of the page or the request.
  • The steps to reproduce it.
  • What someone could do with it.

You do not have to tell us who you are. Email is our only channel, and we do not publish a PGP key.

What you can expect from us

  • We acknowledge your report within three business days.
  • We keep you informed while we work on it.
  • We tell you when the issue is fixed, and you are welcome to check the fix.
  • We credit you publicly if you would like us to.
  • We do not ask you to sign anything.

Safe harbour

If you make a good-faith effort to follow this policy during your research, we consider your research authorised.

For inadvertent, good-faith violations of this policy, we will not take civil action or file a report with law enforcement.

If a third party starts legal action against you and you have followed this policy, we will make it known that your actions were conducted under this policy.

This safe harbour covers legal claims under Patrium's control. It does not bind third parties. If in doubt, ask us first.

No payment

We do not offer payment for reports.

Publication

Tell us before you publish anything about an issue, and we will agree the timing with you. We do not set a fixed window.

Questions

Questions about this policy go to amr@patrium.ai.

Change history

v1.08 November 2026
First version.

See also the privacy notice and the contact page.

Last reviewed 8 November 2026