Skip to content
ADVISORY RECONCILIATION · STRIPE ↔ ENTITLEMENTSRun the browser-only CSV audit

SECURITY MODEL

Trust should be legible.
Including its limits.

SubSync Guard handles billing identifiers and access metadata, not card numbers. The security model is narrow on purpose. This page separates what is implemented from what has been verified and what is still an operational responsibility.

Disclosure

Found a vulnerability? Use GitHub’s private security advisory flow. Do not open a public issue with exploit details.

Open a private advisory

Read-only by design

The reconciliation service never needs write access to Stripe or your database. Stripe connections use restricted test keys with read scopes. Entitlements arrive as signed snapshots from infrastructure you control.

Credential isolation

Connector secrets are encrypted with AES-256-GCM under a server-side key. The plaintext secret is returned once at creation and never again. The browser never receives a stored secret.

Two authorization layers

Every browser-facing action verifies the Supabase JWT and the caller’s workspace role on the server. Row-level security in Postgres provides a second boundary for direct client queries.

Explicit data lifecycle

Workspace owners can export findings and snapshot metadata as JSON and can erase findings, snapshots, or all audit data. Destructive actions require the workspace name or an explicit scope.

CONTROLS & VERIFICATION

What is implemented.
What has actually been tested.

A control that exists only in a document is not a control. The status column deliberately distinguishes code, test coverage, and live-environment verification.

ControlImplementationStatus
AuthenticationSupabase JWT verified server-side with getUser(); no client-supplied user IDs are trusted.Implemented
Workspace authorizationServer-side role lookup for every action; owner-only billing and destructive operations.Implemented
Row-level securityWorkspace-scoped policies in the hardened schema, plus revoked default grants.Migration authored; live cross-tenant test pending
Encryption at restConnector secrets encrypted with AES-256-GCM using CREDENTIAL_ENCRYPTION_KEY.Implemented
Invitation bindingSingle-use, 7-day expiry, authenticated email must match the invitation; raw tokens excluded from client grants.Fix included in the release candidate
Stripe webhooksRaw-body signature verification and replay protection for platform billing events.Implemented; sandbox execution pending
Snapshot replay protectionTimestamp window plus a nonce inserted under a unique constraint in the same transaction.Implemented; live test pending
SSRF controlsHTTPS-only destinations, no credentials or custom ports, Slack host restriction, and an administrator allowlist for custom webhooks.Implemented
CSV formula injectionExported cells beginning with =, +, -, @, tab, carriage return, or % are prefixed with a quote.Implemented and tested
CORSAllowlist from APP_BASE_URL; no wildcard fallback when configuration is missing.Hardened in this release
Security headersFrame denial, nosniff, referrer policy, permissions policy, and a restrictive CSP in public/_headers.Implemented for the static host
Error hygieneUnexpected failures return a generic message; internal details are not returned to the browser.Implemented

WHAT WE DO NOT CLAIM

No badge without
an examination.

Compliance theater is a security problem. These claims are absent because the underlying work is absent or not yet verified.

SOC 2

No SOC 2 Type I or Type II examination has been completed. No report is available.

ISO 27001

No certification exists. The controls described here are not an ISO management system.

PCI DSS

SubSync Guard does not process card data. Stripe hosts the payment pages. That does not make this product PCI certified.

Uptime SLA

No SLA is offered in the staging build. No uptime percentage is published without measurement.

Penetration test

No third-party penetration test report is available at this time.

Zero risk

No system has zero risk. The goal is a narrow blast radius, explicit limits, and fast disclosure.

Implemented

Code-level controls

Authentication, role checks, encryption, replay protection, SSRF allowlists, CSV sanitization, and header policy are present in the release candidate.

Pending verification

Environment-level proof

Cross-tenant RLS tests, deployed webhook execution, cron delivery, and the live invitation flow require a staging database and deployed secrets. They are not claimed as passed.

Operator responsibility

Your side of the boundary

Protect your Supabase project, rotate signing secrets, restrict Stripe keys, monitor alert delivery, and review findings before acting on them.

RESPONSIBLE DISCLOSURE

A private path for
security reports.

Use GitHub Security Advisories to report a suspected vulnerability. Include the affected path, a minimal reproduction, and the impact you believe is possible. Do not include real customer data, live credentials, or destructive proof-of-concept steps.

This is an independent staging project without a bug bounty or paid disclosure program. Reports are handled on a best-effort basis, and no response-time SLA is offered.

Scope reminder

The browser CSV audit processes data locally. A report that requires uploading real customer data is out of scope. The staging Supabase project is a test environment; do not use production credentials or real customer records when evaluating it.

SECURITY QUESTIONS

Ask before you connect a source.

If a control on this page is unclear, open an issue or a private advisory. A precise question is better than an assumed guarantee.