Privacy Policy

Summary

Proxima Gateway is a management tool. It stores the minimum information needed to install, configure, and authenticate the proxy on your server. It does not see, store, or process your end users' traffic — that flows directly between your end users and the servers you operate.

1. Data we store about you (the operator)

When you have a dashboard account, we store the following on our servers:

• Your username and a bcrypt hash of your password
• Optional display name and login slug
• Your role (Admin or Customer)
• Account creation and last-update timestamps
• Your server's SSH host, port, and user (the SSH password is encrypted with AES-256-GCM using a key that is never logged or returned by any API)
• A randomly generated license key and a randomly generated dashboard auth secret
• The version your proxy reports, the time of its last heartbeat, and a hash of your current config (no plaintext config in the heartbeat — just a fingerprint)
• Audit log entries: timestamp, action, actor, target, request IP, and a small JSON metadata blob describing the action (e.g. "regenerate license", "save SSH credentials")

2. Data we do NOT see

The proxy binary runs on your server, not ours. We do not see, log, store, or have access to:

• The HTTP / HTTPS requests flowing through your proxy
• Request bodies, response bodies, or headers
• The IP addresses of your end users
• Cookies, tokens, or any other content in transit
• Your backends' data
• Any files on your server beyond what the installer writes

The proxy's log file (/var/log/proxima-gateway/gateway.log) lives on your server. The dashboard's log viewer fetches this log over your proxy's HTTP API on port 6060 — it is not relayed back to us in the heartbeat.

3. Data we collect on the dashboard

The dashboard logs the following per request, like any web app:

• The request URL and method
• Your IP address (from x-forwarded-for)
• Timestamp
• HTTP status code

We do not use third-party analytics, advertising, or tracking scripts on the marketing site, the dashboard, or the docs.

4. Cookies

The dashboard uses two cookies:

• next-auth.session-token — your authenticated session, set when you sign in
• selected-server-id — remembers which server you're currently managing (only relevant for admins; for customers there's only one server)

Both are first-party. We do not set marketing or analytics cookies.

5. Data shared with third parties

We do not sell your data. We share data with third parties only in the following narrow cases:

• Cloud hosting — the dashboard runs on infrastructure provided by our hosting partner. They have access to disks and database snapshots as part of their normal operations.
• R2 / Cloudflare — we host the proxy binary and GeoIP databases on Cloudflare R2 behind a gated worker. Your installer authenticates with a token, downloads the artifact, and Cloudflare logs the request as part of normal CDN operations.
• Legal compliance — we may disclose data if required to do so by law, valid court order, or to protect our rights.

6. Retention

• Account data — kept for the lifetime of your account. Deleting your account via your administrator removes the row.
• Server & SSH credentials — kept while the server exists. Deleting the user cascades to the server row; the encrypted SSH password is deleted with it.
• Audit log — kept indefinitely for security and compliance. Old rows can be pruned manually by an administrator if needed.
• Heartbeat data — last-heartbeat timestamp and version are overwritten on each heartbeat (no historical time series is kept).

7. Security

We take reasonable steps to protect your data:

• Passwords are stored as bcrypt hashes (work factor 12)
• SSH passwords are encrypted at rest with AES-256-GCM using a key encryption key that is held in environment variables and never written to the database
• License keys are stored as plaintext in the database; they are bearer tokens with a single purpose (heartbeat auth) and can be regenerated by an administrator at any time
• The dashboard is served over HTTPS
• SSH connections from the dashboard to your server use standard SSH transport encryption

No system is perfectly secure. If you suspect a security issue, contact your administrator immediately.

8. Your rights

Depending on your jurisdiction (GDPR, CCPA, etc.), you may have the right to:

• Access the data we hold about you
• Request correction of inaccurate data
• Request deletion of your data
• Object to processing
• Request a copy of your data in a portable format

Contact your platform administrator to exercise any of these rights.

9. End user data is your responsibility

Anything your proxy collects about your end users (logs, IP addresses, cookies you set on your own backends) is governed by your privacy policy with your end users — not ours. The proxy is a transit layer in your application; your obligations to your end users (notice, consent, retention, data subject rights) flow through you.

10. Changes

We may update this Privacy Policy from time to time. The "Last updated" date at the top of this page reflects the most recent revision.

11. Not legal advice

This Privacy Policy is a starting point and not legal advice. If you have specific compliance questions (GDPR, CCPA, HIPAA, PCI-DSS, etc.), consult a qualified attorney in your jurisdiction.