Rynn

Security & Compliance

The short version: we built the product so the riskiest things simply can’t happen. We don’t hold your social credentials, we don’t automate your accounts, and every placement is disclosed.

No automated posting from your accounts

Rynnnever posts from a customer’s social account and never automates one. Self-serve engagement is posted by you, by hand, from your own browser — Rynn drafts a reply in your calibrated voice, and you decide whether and what to post. Because the action happens in your browser, under your control, we never need (and never request) your account passwords or OAuth tokens for posting.

Human-in-the-browser by design

This isn’t a setting you can switch off — it’s the architecture. There is no API path for Rynnto publish to your social accounts on your behalf, so there’s no credential to leak and no bot to get your account flagged. A human decides, a human posts. That’s the whole point.

Editorial standards that hold up to scrutiny

Editorial placements arranged through Rynnare paid relationships, and they are disclosed clearly and conspicuously, consistent with the FTC’s Endorsement Guides (16 CFR Part 255) — both in the article and site-wide on the publication.

Comparison coverage always includes non-paying brands, superlatives require stated criteria, and every article passes human editorial review before it publishes. The full posture lives on our disclosure page.

How we handle your data

On certifications — straight talk

We don’t claim formal certifications we don’t hold. As our compliance program matures, any attestation we earn (and the report behind it) will be named here in plain language — not implied with a badge. If you have a specific security or compliance requirement for an evaluation, email hello@rynnhq.com and a person will answer.

Reporting a vulnerability

Found something? Email hello@rynnhq.com with the details. It’s read by a person, not a queue, and we’ll acknowledge promptly.