SwissBorg
Skip to content
Log InSign UpGet Started

Don’t invest unless you’re prepared to lose all the money you invest. This is a high-risk investment and you should not expect to be protected if something goes wrong. Take 2 mins to learn more.

Vulnerability disclosure policy

Last updated: Nov 17, 2026

If you think you've found a security issue in SwissBorg's app, website, systems or smart contracts, we want to hear about it.

How to report

Email security@swissborg.com, in English. Our security team reviews every report. To help us act quickly, include:

  • what the issue is and what an attacker could do with it
  • the steps to reproduce it, with any script or proof of concept
  • the affected page, endpoint, app version or contract address

If you'd like to encrypt your report, use our PGP key, also published on keys.openpgp.org. Fingerprint: F000 0EC7 98DE 5FE6 333B 24F7 3A5A 1B67 C4AC 5C69

What you can expect from us

  • We'll confirm we've received your report, keep you updated while we investigate, and tell you when it's fixed.
  • We'll tell you if we already know about the issue.
  • We don't publish a list of reporters, but we're happy to credit you on request once the issue is fixed.

In scope

  • the SwissBorg app, downloaded from the official app stores
  • the websites and services we run under swissborg.com, and the APIs behind them
  • the smart contracts we've deployed
  • the way we configure and integrate third-party services
  • takeover of a swissborg.com subdomain: prove it with a harmless page and go no further

Out of scope

  • vulnerabilities in third-party services and protocols, including ones we use or host under a swissborg.com address: report those to whoever runs them
  • hardening suggestions without a working attack, such as missing security headers or cookie flags, TLS settings, email settings (SPF, DKIM, DMARC) or visible software versions
  • automated scanner or AI-generated output with no demonstrated impact
  • self-XSS, clickjacking on pages with no sensitive action, and login and logout CSRF
  • attacks that need a rooted, jailbroken or already compromised device

Rules for testing

  • Test only with accounts and funds that are yours. We can't refund fees or losses from testing. If you need a second account to show an issue, ask us first.
  • If you reach another member's data, stop. Tell us what you saw, don't copy or share it, and delete anything you captured once we've confirmed we've received your report.
  • Never change or delete data that isn't yours.
  • Don't run tests that slow down or interrupt our services, such as denial of service or high-volume automated scans.
  • Don't use phishing, social engineering or physical attacks against members, staff or offices.
  • For smart contracts, review the code and test on your own local fork. Never send a transaction to mainnet or to a public testnet.

Disclosure

Please keep the issue private until we've fixed it or 90 days have passed since your report, whichever comes first. If a fix needs longer, we'll explain why and agree a new date with you. Tell us before you publish, so we can coordinate.

Rewards

We don't run a bug bounty programme and don't promise rewards. For a serious issue, such as one that puts members' crypto-assets or personal data at risk, we may offer a reward. We decide that after we've confirmed the issue; it isn't negotiated, and any payment goes through our usual identity and sanctions checks. A report that holds back details until we agree to pay isn't one we can act on.

Not a security issue?

For suspected fraud on your own account, a scam using our name, or a lost or stolen phone, contact support@swissborg.com.