Updated · Applies to the current website preview
Keep credentials private
This preview has no API-key entry field. Enabled deployments use Clerk’s login form; enter sign-in credentials only through that verified flow. Never paste a real key into a website console or send it to our support inbox. Keep provider keys in server-side secrets or your trusted tool’s credential store. If a key is exposed, revoke it with its issuing provider and review its usage.
Report a vulnerability
Email contact@deepseeksub.com with the affected page, a concise description and minimal reproduction steps. Do not include other users’ data or active secrets. Avoid destructive tests and access beyond what is necessary to describe the issue. No bounty or response-time commitment is offered on this page.
Current service scope
The site serves static pages with optional Clerk authentication. The account service verifies signed Clerk sessions before returning account data. Payments and API-key controls in the dashboard remain illustrative. Security properties of a future backend, including session protection, access controls and key handling, must be tested when those services are connected.
For a privacy concern, see our privacy policy.