Privacy and data choices

Updated October 12, 2026. Simple Load Balancer is operated by Programming Securely.

Accounts and proxy configuration

Supabase Auth processes sign-in credentials and sessions. We store your load-balancer configuration, targets, custom headers, payload formatting and related account settings. Requests sent to your proxy are forwarded to the targets you configure. Those targets receive the request information required by your configuration and follow their own data practices. Do not configure a destination you are not authorized to use.

Traffic and security

Proxy, hosting and security services process request metadata, which may include IP addresses, timestamps, paths and failure details. Redis supports rate limits and caching. Self-hosted Umami provides website usage analytics; the tracker excludes page query strings and fragments. This is separate from data you deliberately configure the proxy to forward.

Error reports and support

Self-hosted Bugsink receives technical error reports. Its configured filters remove identities, request headers, cookies, bodies and breadcrumbs. The footer support form sends your request and technical page context to our central support system; a verified account may be associated with the report. Request titles and references may appear in internal Slack notifications. Do not include proxy secrets or passwords in a report.

Your choices

Use the dashboard controls to remove load balancers you own and revoke or change their credentials. Use Support / Feature Request for access, correction, account deletion or questions about retained data. We verify account ownership before processing requests. Existing backups, logs, cached copies and support notifications are separate from active configuration; there is no single automatic expiration period for all these records and no promise of immediate removal from every copy. Removing data here cannot remove copies already received by configured target services.