Trust Center

ReviewSentinel is designed with least-privilege access, transparent data handling, and operational safeguards for production Slack workspaces.

Last Updated: February 24, 2026

Security Model

Slack requests are signature-verified before processing.
Webhook integrity is enforced for Stripe events.
No channel message-history scopes are used for product functionality.
Production logic is fault-tolerant: per-app failures do not stop other processing.
All data is encrypted at rest via AES-256 (Supabase managed PostgreSQL).
All data in transit is encrypted via TLS 1.2+.
Slack bot tokens are stored encrypted and nulled immediately on uninstall or revocation.

Data Type	Purpose	Stored Fields
Slack Workspace	Authenticate installs and post notifications	team ID, workspace name, bot access token, selected channels
App Tracking Config	Drive routing and filtering	app IDs, platform, country, destination, JSON filters
Public Review Data	Classify and route feedback	review IDs, text, rating, metadata from public stores
Billing Metadata	Plan enforcement and subscription lifecycle	Stripe customer ID, Stripe subscription ID, plan limits

Workspace configuration data is kept while the app remains installed.
Access tokens are disabled/cleared when uninstall or revocation is detected.
Review deduplication metadata is automatically cleaned on a rolling 90-day basis.

Render: application hosting. EU (Frankfurt)
Supabase: PostgreSQL database. EU (eu-central-1)
Stripe: subscription billing and portal. EU (Ireland)
OpenAI: sentiment classification and summarization of public review text. United States
PostHog: website analytics. EU Cloud

We update this list for material subprocessor changes. Business customers may request a DPA at /dpa.

Enterprise compliance requests: support@reviewsentinel.app.

For security reports, incident notifications, or data-rights requests, contact support@reviewsentinel.app.