Security

All traffic to mediaberry.com is served over TLS 1.2 or newer. Customer data is stored in Supabase's Postgres infrastructure with at-rest encryption managed by Supabase / AWS KMS.

Customer authentication is via passwordless email magic links. Mediaberry does not store passwords.

Production system access is restricted to named employees and audited. We do not grant standing access to third parties.

Mediaberry only ingests publicly available retail-investor conversation — public Reddit threads, public X posts, public Stocktwits messages, public discussion boards on Naver, 5ch, Yahoo!ファイナンス掲示板, moomoo, Tiger, and Seeking Alpha articles. We do not access private posts, direct messages, paywalled content, or anything that requires a logged-in session beyond standard public read access.

We do not store personally identifiable information about the authors of public posts. What Mediaberry retains is the post content, the source platform, a public author handle when one exists, and the post timestamp — all of which are visible to anyone who can read the source publicly.

Our ingestion respects each platform's public robots policies and rate limits. Where a platform publishes an explicit policy on automated access, we follow it; where a platform asks us directly to stop or scope our collection differently, we do so the same day.

Generating briefs and other AI features sends prompt content to our AI providers — currently Google (Gemini) and Anthropic (Claude). We rely on each provider's commitments not to train on customer prompt content, and we will update this page if those commitments change.

If you believe you've found a security issue in Mediaberry, please email security@videoster.com with details. We respond within two business days and credit responsible disclosure.