ClearCast
ClearCast

Security Practices

Last updated: June 7, 2026

ClearCast holds delegated access to the social accounts you connect, so protecting that access is core to the product. This page describes the controls we have in place today. We describe only what is actually true; planned items are listed separately on our Trust Center.

Encryption

Protecting connected-account tokens

Tenant isolation

Every API request is scoped to the authenticated user and their workspace. Access to another customer's posts, media, analytics, or connected-account tokens is not possible through the application. We verify this isolation as part of our development process.

Payments

Billing is processed by Stripe, a PCI-DSS Level 1 service provider. ClearCast never receives or stores full payment-card numbers.

Privacy by default

ClearCast uses a single essential, first-party session cookie and no third-party advertising or analytics trackers. We do not sell or share personal information, so there is nothing to opt out of. See our Cookie Policy.

Access & operations

Reporting a vulnerability

If you believe you've found a security issue, please see our Responsible Disclosure policy or email security@clear-cast.net. We support good-faith research and will not pursue researchers who follow that policy.

Certifications such as SOC 2 Type II and ISO/IEC 27001 are on our roadmap and are not claimed today. We will publish them here only once independently audited. Our infrastructure providers (Supabase/AWS, Stripe) maintain their own such certifications for the layers they operate.
ClearCastTrust CenterPrivacyDisclosure