Skip to main content

This policy sets out how MB „Department 03“ ("Bonfium") protects bonfium.com, the data in it and the systems behind it. It applies to everyone who works for Bonfium, to every system we run, and to the suppliers who run systems for us. We use the OWASP Application Security Verification Standard, level 2, as the reference for the application, and the GDPR's principle of data protection by design for the data.

What we protect

  • Users' money, which never sits with us: it stays with our payment provider, Online Payment Platform B.V. ("OPP"). What we protect is the instruction to OPP to pay a seller or refund a buyer, and the seller's payout account.
  • Personal data: accounts, trades, messages, evidence, payout details and the other data in the Privacy Policy.
  • The service: its code, its database, its configuration and secrets, and its availability.

Who is responsible

  • The head of the company owns this policy and is the security contact for users, suppliers and OPP.
  • Everyone with access to our systems follows this policy, reads it when they start and again every year, and reports a suspected incident at once.

Our systems

SystemWhat it doesWhere
The application and databasebonfium.com, PHP and MySQLHostinger, EU
The codePrivate repository; every change is a reviewed pull request, checked by automated tests before it can go liveGitHub
PaymentsCheckout, the money, sellers' identity checks and payoutsOPP, the Netherlands
SMS codesMobile number confirmationTwilio
E-mail marketingNews and offers, only with consentOmnisend, Lithuania
Error reportsWhat went wrong, with personal data removedSentry, Germany

We keep this inventory current, and we choose suppliers that protect data at least as well as we do, under a written data processing agreement.

Access control

  • Least privilege. People get only the access their work needs, and lose it the day they stop needing it. We review who has access every three months.
  • Administrators use a second factor (an authenticator app or a passkey), must confirm it's them again after 15 minutes of inactivity, and are signed out after 8 hours. Administrator sessions are never restored from a remembered device. Every administrator's view or change of personal data is written to an append-only access log.
  • Decisions that move money (a refund or a release in a dispute) need an explicit choice and a written reason, are logged, and are marked done only when OPP confirms them.
  • Deployment happens only from the main branch, after every automated check has passed, through a deploy key that can do nothing else. Nobody edits files on the live server by hand except in an emergency, which is then recorded.
  • Secrets (API keys, encryption keys, passwords) are kept outside the web root and outside the code repository. The repository is scanned for secrets on every change.

Protecting users' accounts

  • Passwords are stored only as a strong one-way hash (bcrypt), upgraded when the user next signs in, and checked against known data breaches without sending the password anywhere (only five characters of its SHA-1 hash leave our server).
  • Users can add an authenticator app (the secret is stored encrypted, backup codes hashed) or a passkey.
  • Sign-in attempts and forms are rate limited; repeated failed sign-ins lock sign-in for that address for a while.
  • Changing the bank account a seller is paid to needs a confirmed mobile number and an e-mailed confirmation, and sends an alert with a link that locks the account at once.
  • Locking an account, or changing its password, ends every session.

Protecting the application

  • HTTPS everywhere, with HTTP Strict Transport Security, and a Content Security Policy that limits what the pages can load and where forms can be sent.
  • Every form that changes something carries an anti-forgery token, and every action checks that the signed-in person is allowed to do it.
  • Uploaded photos and files are kept outside the web root and served only through access checks. Digital codes entrusted by sellers are encrypted until the buyer has paid.
  • Error reports and analytics go through a scrubber that removes names, e-mail addresses, trade codes and numbers before anything leaves our server.
  • Card details never reach Bonfium: buyers pay on OPP's checkout.

How we build and ship changes

  • Every change goes through a pull request and an automated pipeline: the secret scan, a database schema scan, an access-control scan, syntax checks, type checks, lint, and the unit and security tests. A red check blocks the change.
  • New features ship behind a switch that is off by default, so a problem can be undone at once by turning it off, or by redeploying the version that was live before. A failed health check after a deploy restores the previous version automatically.
  • Tests never use real customer data or real money.

Data protection

  • We collect only what the service needs, and keep it only as long as the Privacy Policy says.
  • The full IBAN of a payout account stays with OPP; we keep only its last four digits and a keyed hash.
  • Identity documents and card numbers never reach us.

Backups and continuity

  • The hosting provider keeps regular automatic backups of the database and files in the EU. We can restore the service and roll back to any earlier release.
  • If Bonfium is unavailable, users' money isn't at risk: it stays with OPP until Bonfium tells OPP where it goes, and trades that stay open for a long time alert us at 250 and 300 days, well before OPP's own one-year limit.

Incidents

  1. Report. Anyone who suspects an incident tells the head of the company at once. Users and researchers can write to bonfium@gmail.com.
  2. Contain. We stop the harm first: lock affected accounts, rotate keys, turn off the affected feature with its switch, or roll back.
  3. Assess. We work out what happened, what data or which trades were affected, and whether people's rights are at risk.
  4. Notify. A personal data breach that may put people's rights at risk is reported to the State Data Protection Inspectorate within 72 hours, and to the people affected without undue delay where the risk is high. Anything that touches payments, payout accounts or OPP's systems is reported to OPP without delay, within 24 hours at most.
  5. Learn. We record every incident, fix its cause, and update this policy if needed.

Vulnerability reports

We welcome reports of security weaknesses at bonfium@gmail.com. Please give us time to fix a problem before telling anyone else, and don't access other people's data or disrupt the service while testing. We won't take action against anyone who reports in good faith.

Review

We review this policy at least once a year, after every serious incident, and whenever our systems or suppliers change. The version and date are at the top.