Skip to main content

Security & data protection

Last checked: 2026-10-01

ObligoBoard is built for compliance professionals, so vendor due-diligence answers should not require an email. This page states — factually and checked against our current configuration — where your data is hosted, how it is encrypted, how it is backed up, who our sub-processors are, and what happens to your data when you cancel.

Every statement below was checked against the platform on the date shown above. Where a claim could not be verified, it is omitted. This page is a factual disclosure, not a certification or audit report.

Where is your data hosted?

ObligoBoard’s application and its primary PostgreSQL database are hosted in the European Union (Frankfurt) on Vercel and Neon (eu-central-1), and our cookie-scanning service runs in the European Union (Amsterdam). A small number of sub-processors — for example transactional email and payment processing — may process or route limited personal data outside the EU. Separately, some providers execute entirely inside the EU but are incorporated outside it; the GDPR treats that as an international transfer even though the data does not leave the EU, and so do we. In both cases the transfer is governed by an appropriate Article 46 safeguard — in most cases EU Standard Contractual Clauses (Module 3). The full list, with each provider’s region and transfer mechanism, is published on our Sub-processors page.

How is your data encrypted?

  • In transit: all platform endpoints are served over TLS, with HSTS (including preload).
  • At rest: personal data in the production database and in object storage (uploaded evidence files and generated PDF documents) is encrypted at rest by our database and storage providers.
  • Passwords: account credentials are stored only as bcrypt hashes, and sessions use signed, expiring JSON Web Tokens.

How is your data backed up?

The production database has continuous point-in-time recovery with a restore window of at least seven days, and our migration procedure takes a snapshot before each production schema migration. Uploaded evidence files rely on the storage provider's redundancy and are not separately backed up; keep your own originals (Terms §8.3). When personal data is deleted, residual copies in backups are purged on the regular backup-rotation schedule, with a maximum residual retention of ninety (90) days.

Who are your sub-processors?

The third parties that process personal data on our behalf are listed below. This table is generated from the same single source of truth as our Sub-processors page and the DPA Annex III, so the surfaces are kept in step.

Sub-processor list last updated: 2026-09-30

Sub-processorServiceRegionTransfer mechanismUK transfer mechanism
Vercel Inc.Application hosting, CDN, edge runtime, blob storageEU (Frankfurt) primary; global edgeEU SCCs (Module 3) for any US fallback; Vercel DPA in placeUK Addendum to the EU SCCs (ICO version B1.0), incorporated in the Vercel DPA (Schedule 3 §2; Schedule 5)
Neon Inc.Managed PostgreSQL database hostingEU (Frankfurt)EU SCCs (Module 3); Neon DPA in placeUK Extension to the EU-U.S. Data Privacy Framework (UK adequacy regulations for the United States, SI 2023/1028; Neon, LLC is a covered entity on the Data Privacy Framework List, verified 2026-10-29)
Stripe Payments Europe Ltd.Payment processing, subscription billingEU (Ireland) primary; some routing to US via Stripe global infrastructureStripe DPA + EU SCCs (Module 3); Stripe is also an independent Controller for fraud-prevention purposesUK Extension to the EU-U.S. Data Privacy Framework (UK adequacy regulations for the United States, SI 2023/1028; Stripe, LLC self-certified, verified 2026-10-29); otherwise the UK Addendum to the EU SCCs (ICO version B1.0, Modules 1 and 2 only), per the Stripe Data Transfers Addendum §§2, 3 and 5
Resend Inc.Transactional email deliveryEU (Frankfurt) and USEU SCCs (Module 3) for US-region processing; Resend DPA in placeUK Addendum to the EU SCCs, incorporated in the Resend DPA (§6.4); Addendum version not stated by Resend
Railway CorporationCookie-scanner execution (automated website cookie/tracker scanning)EU (Amsterdam)EU SCCs (Module 3) plus the UK Addendum, in place under the Railway DPA executed 2026-07-31; Railway Corporation is US-incorporated, so Chapter V applies notwithstanding EU-only processing in Amsterdam. A transfer impact assessment dated 2026-08-01 concluded essentially equivalent protection with low residual risk; available to customers on request.UK Extension to the EU-U.S. Data Privacy Framework (UK adequacy regulations for the United States, SI 2023/1028; Railway Corporation self-certified, verified 2026-10-29); otherwise the UK Addendum to the EU SCCs (ICO version B1.0), completed at Exhibit D of the Railway DPA executed 2026-07-31 (§9.4)
Vercel Inc.Evidence file & generated PDF document storage (Vercel Blob)EU (Frankfurt) primary; global edgeEU SCCs (Module 3) for any US fallback; Vercel DPA in placeUK Addendum to the EU SCCs (ICO version B1.0), incorporated in the Vercel DPA (Schedule 3 §2; Schedule 5)

"UK transfer mechanism" is the instrument in the provider's terms that covers personal data subject to UK data-protection law when it is transferred to that provider. Where it is the ICO Addendum, the version shown is the one the provider's terms incorporate. Where a provider relies on the UK Extension to the EU-U.S. Data Privacy Framework, that is a UK adequacy route and depends on the provider's certification, which we re-verify periodically.

For DPA links and the authoritative version, see the Sub-processors page.

What happens to your data when you cancel?

On termination, you choose in writing within thirty (30) days whether we return all your personal data in a structured, machine-readable format, or delete it. After that period, deletion is the default. We confirm completion of the return or deletion in writing within sixty (60) days. Backup copies are then removed on our regular rotation schedule, within a maximum of ninety (90) days.

This is set out in full in Section 6.8 of our Data Processing Agreement.

These commitments restate our Data Processing Agreement, which is the governing text in the event of any conflict.

How is this verified?

Security is checked automatically on every pull request, not just asserted:

  • An automated tenant-isolation test suite exercises the boundaries between customers' data on every pull request and nightly. It is a control against cross-customer access, not a guarantee.
  • Every code change reaches production through a pull request; direct pushes are blocked. Each must pass automated lint, type-check, unit-test, tenant-isolation and migration-integrity checks. Substantive changes also receive an automated, AI-assisted code review, which is a working practice rather than a merge requirement. ObligoBoard is operated by one person; there is no second human reviewer.
  • Dependency vulnerability alerts (GitHub Dependabot) are reviewed before each production release.
  • A migration-integrity check blocks any change to already-applied migration files.
  • Security headers, including HSTS and a Content Security Policy on pages, are set by the application.

Questions from a data-protection or security review? Contact us and we will respond. Contact