Security & Trust
Last updated: 2026-06-05. This page documents the controls TapStellar runs in production. It is written for the business owner evaluating us and the security reviewer doing due diligence. For the live operational picture, see our system status page.
Tenant isolation (Row-Level Security)
TapStellar is multi-tenant. Every table that holds customer data (accounts, establishments, reviews, plates, mini-sites, billing, audit logs) has Postgres Row-Level Security enabled with account-scoped policies. A signed-in user can only ever read or write rows belonging to an account they are a member of; the policy is enforced by the database, not just the application layer. Infrastructure tables (for example the cron-lock table) have RLS enabled with no policy, so only our service role can touch them. Anonymous and authenticated callers see nothing.
We test this continuously: a cross-tenant RLS suite signs in as one account and asserts it cannot read another account's reviews, plates, or links. That suite runs in CI on every change.
Encryption
- In transit: all traffic to the dashboard, public pages, and API is served over TLS (HTTPS) by our hosting provider.
- At rest: the primary database (Postgres on Supabase) is encrypted at rest by the provider.
- OAuth tokens: Google Business Profile access and refresh tokens are additionally encrypted by TapStellar with AES-256-GCM before they are written to the database, using a key held only in our server environment. The tokens are stored in dedicated
*_encryptedcolumns and are never exposed to the browser; they are decrypted server-side only when the review-sync job needs to call Google on your behalf.
Audit logging
Every state-changing action in TapStellar writes an immutable audit-log entry: who did what, to which entity, and when. That covers establishment imports and edits, Google connect / revoke, account lifecycle changes, plate activations, review replies (drafted, posted, failed), and billing changes. The audit log is account-scoped under RLS so you can review your own workspace's history, and we retain audit entries referencing a user id (in anonymised form) for 12 months for security forensics even after account deletion.
Error reporting without PII
We use error monitoring (Sentry) to detect and fix problems quickly. Our reporting pipeline strips personally identifiable information (email addresses, phone numbers, and names) from breadcrumbs before anything leaves our servers. We never log review bodies to our analytics pipeline, because review content can contain personal data. Operational logs (request IP, path, status, user-agent) are retained for 30 days and are never sold or shared.
Access & least privilege
The Supabase service-role key, the only credential that can bypass RLS, lives exclusively in server-side environments and is never shipped to the browser or embedded in client code. User-facing API routes operate under the anonymous key with RLS enforced. Roles within an account (owner, admin, editor, viewer) gate who can change what.
Payments
Billing runs through Stripe (PCI-DSS Level 1). We never see or store your card details. Stripe holds them. Our system only records your plan, status, and Stripe customer reference.
Subprocessors
We keep a current, public list of every third party that processes your data, with what they do and where they operate, at /legal/subprocessors. We notify customers by email at least 14 days before adding a new subprocessor, and you may object during that window.
Your data rights (GDPR / UK GDPR / CCPA)
- Export / portability: download every row TapStellar holds about you and your workspace from Settings → Data.
- Erasure: request account deletion from Settings → Data. We soft-delete immediately and hard-delete after a 30-day grace window that lets you cancel the request; a daily purge job performs the hard delete.
- Rectification: the dashboard lets you edit every customer-facing field directly.
Full detail lives in our Privacy Policy and Terms of Service.
Responsible disclosure
Found a vulnerability? Email security@tapstellar.com. We will acknowledge your report, work with you on a fix, and credit you if you wish. Please give us a reasonable window to remediate before any public disclosure.