Skip to content
Trust & Security Architecture

Tenant isolation enforced by the database, not just the application.

This page describes how BuyerCite is actually built — the controls below are implemented in our codebase and infrastructure today. We describe them plainly so your security team can evaluate them.

Tenant tables under RLS
60
Secret encryption
AES-256-GCM
Passwords stored
0
Backup cadence
Every 6 h
Data isolation

PostgreSQL 18 forced row-level security

Every one of BuyerCite's 60 tenant tables has row-level security both ENABLEd and FORCEd, with a tenant_isolation policy keyed on the workspace or organization. FORCE means the policy applies even to the table owner, so a missing filter in application code returns zero rows instead of another customer's data.

Each request runs in one transaction whose first statement binds only the workspaces and organizations the signed-in user belongs to. On a workspace URL, only that workspace is bound. Anonymous requests bind nothing, so tenant queries fail closed. Operator tooling runs under a separate database role.

Encryption

Envelope encryption for every stored secret

AES-256-GCM envelopes

Each secret — for example a WordPress pull token or a webhook signing secret — is sealed with its own random 256-bit data key, which is wrapped by a master key held outside the database. Master keys are identified by key id, so they can be rotated.

Hashed credentials

Public API keys (bc_sk_live_* / bc_sk_test_*) are stored as hashes only and shown once at creation. WordPress pull tokens are looked up by SHA-256 hash; their encrypted copy is revealable only to organization Owners and Admins, and reveals are audited.

In transit

Traffic is served over TLS behind Cloudflare, with HTTPS redirects, HSTS (one year, including subdomains, preload), secure and HTTP-only session cookies, and nosniff content-type protection.

Authentication

100% passwordless sign-in

6-digit codes & magic links

  • No passwords exist to leak, reuse or phish.
  • Codes are stored as keyed HMAC-SHA256 digests and expire after 10 minutes.
  • 5 wrong codes lock that code, with an additional cumulative cap per email over 24 hours and rate limits per IP and per email.

Scanner-safe magic links

Corporate email scanners often open links before people do. Opening a BuyerCite magic link (a GET) never signs anyone in — it only shows a confirmation page. The link is consumed by an explicit POST from that page, exactly once.

Crawler sandbox

A crawler that cannot touch your data

Zero database access

The crawler runs as a separate process that refuses to start if a database URL or credential is present in its environment, and it is forbidden by an automated import check from loading any application code.

SSRF guard

Before every fetch and redirect hop, scheme, port and host are checked and every resolved address must be public — private, loopback and metadata addresses are refused.

Honest by design

No stealth plugins, CAPTCHA solvers or fingerprint spoofing — a dependency denylist check fails the build if one appears. Read the BuyerCiteBot/1.0 policy.

Integrations

Signed webhooks you can verify

Every webhook delivery is signed with HMAC-SHA256 over the timestamp and the raw body using your endpoint's secret. Receivers should reject timestamps more than 300 seconds old and de-duplicate on the delivery id. Secret rotation keeps the previous secret valid for a 24-hour dual-signature window.

Reference verifiers for Node.js and PHP ship with the BuyerCite integration packages.

X-BuyerCite-Event: article.published
X-BuyerCite-Timestamp: 1795000000
X-BuyerCite-Delivery-Id: 3f2c…
X-BuyerCite-Signature: sha256=HMAC(secret, timestamp + "." + body)
Privacy by design

Minimal data, short retention

Zero-IP attribution pixel

The first-party pixel customers can place on their own sites stores no IP addresses and uses a random per-tab session id in sessionStorage — no cookies.

24-hour IP scrubbing

Client IPs in imported crawler logs are transient: an hourly maintenance job nulls them within 24 hours.

Read the details

See our Privacy Policy and Cookie Policy for categories, retention and your rights.

Resilience

Verified backups & atomic releases

The database is backed up every 6 hours. Each backup set carries a SHA-256 manifest of every file, and the restore procedure verifies that manifest before anything is restored.

Releases are deployed atomically with a health-check watchdog, and module boundaries, banned dependencies and schema changes are checked automatically on every change.

BuyerCite does not currently hold third-party certifications such as SOC 2 or ISO 27001. If your review needs more detail, email [email protected].

Responsible disclosure

Found a vulnerability? Tell us first.

How to report

Email [email protected] with steps to reproduce, the affected URL or component, and the impact. We aim to acknowledge reports within a few business days.

Safe harbour

If you act in good faith, stay within these rules and give us reasonable time to fix the issue before disclosure, we will not pursue legal action against you for your research.

Please don't

  • Access, change or delete other customers' data — use your own test accounts.
  • Run denial-of-service, load or spam tests.
  • Use social engineering or physical attacks.