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

CONTACT

Real channels.
No invented inbox.

SubSync Guard does not publish an unmonitored support email or a fake office address. Support, evaluation questions, and security reports go to the repository’s tracked channels.

Response expectations

Best effort, no SLA. This is a staging project. Security reports are prioritized over feature questions, but no response time is guaranteed.

Never send secrets

Product support and bug reports

Open a GitHub issue with the page, the action, the exact error text, and whether it occurred locally or against the staging deployment. Do not include secrets or customer records.

Open an issue

Security disclosure

Use GitHub private security advisories. Do not open a public issue containing exploit details, credentials, or personal data. There is no paid bug bounty.

Open a private advisory

Evaluation questions

Ask about the staging build, connector requirements, or the reconciliation policy model. Questions that require a custom commercial agreement cannot be answered until one exists.

Ask a question

What to include

A minimal reproduction, the expected behavior, the actual behavior, and the exact error string. For a workspace issue, include the role and whether the invitation or connection was created recently. Redact all identifiers.

What not to send

Stripe secret keys, Supabase service-role keys, signing secrets, invitation tokens, customer emails, billing records, or exported CSVs containing real customer data. Use test data and redacted screenshots.

BEFORE YOU WRITE

The docs may answer it faster.

Setup steps, known limits, invitation behavior, connector headers, and troubleshooting are documented in one place.