Security & trust
How Ravelets protects your business and your customers
Ravelets handles two assets: your business data and your customers' words. This page states plainly how both are protected — and what we have not (yet) done. No security theater, no claims we cannot back.
Maintained by the Ravelets team · Last updated October 16, 2026.
Security & consent practices
Customer feedback stays yours
Reviews, comments and generated content are scoped to your organization. Data isolation between organizations is enforced server-side on every request and covered by a dedicated automated test suite. Customer names and feedback are never published verbatim without your review.
Consent is recorded, granular and revocable
Every quoted review or comment carries its permission basis — for example that the feedback is public, or that the customer submitted it for reuse. We recommend honoring a customer's preference not to be featured; revocation requests you receive pause scheduled content that quotes them and start removal for published items.
Credentials are encrypted at rest
OAuth tokens for connected publishing destinations (Facebook Page, Instagram, TikTok) are encrypted with AES-256-GCM before they touch the database. Passwords are hashed with scrypt and never stored in readable form.
Human approval gates every post
Nothing publishes without explicit approval — including Autopilot, which only schedules content you already approved. There is no auto-posting of unreviewed material, and no automated engagement (auto-comments, auto-DMs) at all.
Multi-factor authentication for accounts and admins
Accounts support TOTP-based multi-factor authentication, and platform-admin actions are protected behind MFA with rate-limited verification. Sensitive admin actions (like suspending a user) are audited.
Minimal cookies, no ad trackers
We use a strictly necessary session cookie and store your local preferences on your device. No third-party advertising trackers. Details in the cookie notice.
Payment data never touches our servers
Subscriptions run through Stripe Checkout. Card details are entered on Stripe's hosted page and stored by Stripe — Ravelets stores only subscription status references. Until Stripe credentials are configured, checkout runs in a sandbox invoice mode and no card fields appear anywhere in the product.
Deletion is real and self-serve
You can permanently delete your account and associated business data from Settings → Danger Zone, or by contacting support. Provider connections can be revoked from inside the product at any time.
Honest limitations
- No SOC 2 report or formal certification yet — we are an early-stage company; the controls above are the controls we actually run.
- Connected-provider states are shown honestly inside the product: until a provider app is configured and you authorize it, that integration is disclosed as not connected.
- No system is bulletproof: report anything suspicious to security contact below and we will act on it.
Reporting a security concern
Found something? Email security@ravelets.com with details and we will investigate and respond. Please do not test against accounts you do not own.