Where Snipy stands on security and reliability
How Snipy handles your audience, your data, and your money — with transparent standing, self-serve data rights, and a public component status page.
Your money, always
Payouts go directly to your own Stripe account via Stripe Connect. Snipy never holds your revenue.
Your data, portable
Export or delete everything, any time. GDPR and CCPA requests are self-serve — no support ticket required.
Transparent standing
Plain-language account standing, transparent payout holds with reasons, and a complete audit log.
Compliance
SOC 2 Type II
Not heldSnipy holds no SOC 2 report and has no audit to cite. If you need one for procurement, we do not have it.
Data rights (GDPR, CCPA)
Self-serveAccess, export and erasure run from the dashboard without a support ticket. That capability is what Snipy claims — not a compliance certification.
PCI DSS
Via StripeCard data is handled by Stripe — Snipy never touches it.
ISO 27001, HIPAA
Not heldSnipy holds no ISO 27001 certificate and signs no HIPAA BAA.
Availability
Snipy publishes no contractual uptime SLA, and no plan includes one. There are no per-plan uptime targets and no committed support-response times.
What is published is component status, at /status. Those states are maintained by operations, and a component reads unknown until its state has been published — an unknown component is not a claim in either direction.