Customer Trust Pack

reRoute is a multi-tenant SaaS application. It creates QR codes and dynamic shortlinks, and it records scan analytics. The application runs on Vercel. It stores data in Supabase-managed PostgreSQL. It uses Stripe for billing, Upstash Redis for rate limiting and caching, and Resend for transactional email.

Each customer belongs to a workspace, which is the tenant boundary. Every link, QR code, scan event, conversion, API key, webhook, and setting carries a workspace identifier. The application scopes every read and write to the active workspace at the query layer, and Supabase Row Level Security applies at the database layer as a second control. One workspace cannot read or change another workspace's data. Agency client sub-workspaces are isolated the same way.

All traffic uses HTTPS/TLS. Data at rest is encrypted by our infrastructure providers (Supabase-managed PostgreSQL and Vercel). Link passwords are stored as salted scrypt hashes. API keys are stored as SHA-256 digests of high-entropy random tokens. Webhook signing secrets are stored in plain text because HMAC signing needs the original secret; they are redacted from data exports.

Supabase Auth handles account authentication. Each workspace uses four roles: owner, admin, member, and viewer. A viewer has read-only access. Roles are enforced in server actions, not only in the user interface. REST API and MCP access use per-workspace bearer tokens. API keys carry permission scopes (links:read, links:write, analytics:read, track:write) that the application enforces on every call.

The application writes security-relevant actions to an append-only, tenant-scoped audit trail. Audited actions include role changes, credential lifecycle, domain changes, data exports, billing changes, link deletions, retention changes, and scan-data purges. Owners and admins can review the audit trail in the dashboard.

Scan IP addresses are anonymized at write time (IPv4 to /24, IPv6 to /48). Owners and admins can export all workspace data as JSON, with credentials redacted. Owners can permanently delete a workspace. Owners can also set an optional scan-data retention window and purge scan events older than that window. The default is to keep scan data until the customer removes it.

Public endpoints are rate limited with a distributed limiter, so limits hold across serverless instances. The application validates redirect destinations and outbound webhook targets to block internal and private network ranges (SSRF protection), and it escapes user-supplied content in interstitial pages.

• Supabase — PostgreSQL hosting and authentication.
• Vercel — application hosting and edge routing.
• Stripe — billing and payments. Stripe processes card data directly; reRoute does not store full card numbers.
• Upstash — rate limiting and link caching (Redis).
• Resend — transactional email.

reRoute holds no third-party security certifications today. It is not SOC 2 audited, and it does not claim to be. reRoute does not offer single sign-on (SAML or OIDC) today, and it does not present an SSO login flow that is not connected to a real identity provider. Contact the team to scope an SSO engagement.

Report a suspected vulnerability to loading... before any public disclosure. Send enterprise security and procurement questions to loading.... The team will respond promptly and can review the current security posture under NDA.