Security at PANOPTIQ

Help keep
PANOPTIQ secure.

Found a security vulnerability in PANOPTIQ? Report it privately. We pay for eligible findings.

Cash rewards
NOK 500–15,000 per finding
Program operator
PANOPTIQ AS · Norway
Submit a security report

Anyone may read these rules or submit a report. No platform account or invitation is required.

01 / Scope

Where you may test

This program covers our websites, applications and APIs at these exact hostnames, using the testing rules below.

Only the listed hostnames are in scope. A link, redirect, shared IP address or shared owner does not bring another system into scope.

Other services are out of scope. Use dedicated test accounts and organizations you control. Do not test shared admin systems, development or preview environments, other customers’ data, or the underlying services of third-party providers. Ask us for written permission before testing anything outside the list.

02 / Paid rewards

Clear rewards for confirmed impact

We pay the following amounts in Norwegian kroner for the first eligible report of each previously unknown vulnerability.

Reward per validated vulnerability, based on demonstrated impact
SeverityExample impactReward
CriticalRemote code execution or compromise of the entire serviceNOK 15,000
HighAccount takeover or unauthorized access to sensitive dataNOK 5,000
MediumA reproducible security boundary bypass with limited impactNOK 2,000
LowA reproducible security issue with minor demonstrated impactNOK 500

We assess severity using demonstrated exploitability, the access required and the effect on confidentiality, integrity and availability. We explain the severity and reward decision in our reply. You may request a reassessment with additional evidence.

Eligibility and payment

Reports that do not qualify for payment

We do not pay for unverified scanner output, theoretical issues without a working attack, missing headers without demonstrated impact, version disclosures alone, spam, social engineering, denial of service, or issues confined to an out-of-scope system. AI-assisted reports are welcome when you have verified the finding and include reproducible evidence.

03 / Testing rules

Keep testing safe

DoS and DDoS testing is prohibited. Do not flood traffic, run stress or load tests, exhaust resources, spam forms or notifications, or distribute requests across IP addresses or accounts to evade limits. This applies even if an attack would need only a single request. Report suspected availability issues using non-disruptive evidence or a local proof of concept; contact us before any validation that could affect availability.

Authorization for good-faith research

PANOPTIQ AS authorizes good-faith security research on the listed services when it follows this policy. For that research, this policy takes precedence over conflicting testing restrictions in our terms of service.

We will not initiate legal action or request law-enforcement investigation for research that complies with this policy. If a third party takes action, we will clarify that the research was authorized. We cannot authorize activity against another party's systems or waive another party's rights or applicable law.

If you are unsure whether an action is permitted, email us before proceeding.

04 / Reporting

Send us a reproducible report

Email hello@panoptiq.ai with the subject “Security report” and include:

  1. The affected hostname, URL and a short description of the issue.
  2. Steps to reproduce using your own accounts and the smallest possible proof of concept.
  3. The expected behavior, observed behavior and demonstrated security impact.
  4. Redacted evidence and a way for us to contact you.

Do not email passwords, access tokens or customer data. If evidence is sensitive, describe it first and ask for a secure transfer method.

We aim to acknowledge reports within 5 business days and provide an initial assessment within 10 business days. Remediation depends on severity; we will share progress and coordinate next steps with you.

05 / Coordinated disclosure

Give us time to fix the issue

Please keep vulnerability details private until a fix is available, or for 90 calendar days after your initial report, whichever comes first. We may agree a different disclosure date together. Never include personal data, credentials or customer information in a public disclosure.

We credit researchers only with their permission. You may decline public credit without affecting an eligible reward.

Changes to scope or rewards apply to future research; eligible reports already submitted remain covered by the terms in effect when submitted.