Skip to main content

Authentication

There are no passwords. Accounts sign in with Google or a one-time link emailed to the address, handled by Supabase Auth — so there is no password for Surnex to store or leak, and an account can’t be used without access to its mailbox. The dashboard authenticates each request with a short-lived JWT issued at sign-in.

API keys

Keys are prefixed smx_ and shown once, at creation. Only a SHA-256 hash of the key is stored, compared in constant time; keys created before that change keep their bcrypt hash and verify the same way. A key is random, not a chosen password, so there’s nothing for a slow hash to protect. The plain key is never persisted, which is why it can’t be shown again — Surnex genuinely cannot retrieve it. Alongside the hash, a 12-character prefix is stored so you can identify a key in the list without exposing it.
A key carries the organization’s full access, not the access of the person who created it. Only admins and owners can create one, and the key can then do anything an owner can — including deleting a project, but not changing the plan. There are no read-only or scoped keys.
Practical consequences:
  • One key per consumer, so revoking is surgical
  • Store keys in a secrets manager; never commit them
  • Removing someone from Users does not revoke keys they created. Review the key list when someone leaves
  • Revoke anything unused — the last-used column shows what’s dormant

MCP uses OAuth, not keys

The MCP server deliberately does not accept API keys. It’s an OAuth 2.1 resource server; Supabase is the authorization server and issues every token. Surnex operates no /authorize or /token endpoint and holds no signing keys of its own. The reasoning is the difference in accountability. A key is a bearer secret living in an agent’s config indefinitely, belonging to the organization and bound by nobody’s role. An OAuth session belongs to a person who approved it, expires, and can be revoked from their account — and since the tools can create projects, start billable crawls, and delete data, that should be traceable to someone who consented. An MCP token therefore acts as you: it carries your role, reaches only organizations you’re a member of, and can never mint an API key, change billing, or manage members. Tokens are verified on every call — signature against the issuer’s JWKS, audience, subject, and expiry. A token with no expiry is refused, as is one addressed to a different resource.

Organization isolation

Every query is scoped by organization at the database layer. This isn’t a UI filter — a resource from another organization returns NOT_FOUND, and the API doesn’t confirm it exists elsewhere. Membership is checked on every scoped request, and role is checked additionally on privileged operations. See Organizations and scoping.

Roles

Three roles per organization — owner, admin, member. The creator is the owner, and owner is never given to anyone else: nobody can be invited as owner or changed to it. An admin can do everything an owner can except delete the organization or change or remove an owner, so no admin can ever reach the one action that deletes everything. Only an owner can demote or remove another owner, and the last owner can’t be demoted or removed at all. The database enforces that inside the write, so an organization always has someone who can administer it. The Users page also doesn’t offer changing your own role or removing yourself. An invitation grants nothing until the invited person clicks its link, which signs them in as the address it was sent to. There is no read-only role and no per-project access. Every member can view and edit every project in the organization. If someone must not see a project, it belongs in a separate organization. Full breakdown: Roles and permissions.

Rate limiting

Requests are rate-limited per credential — per API key, per user, or per IP for anonymous traffic — in a fixed 60-second window. Anonymous requests are limited far more tightly than authenticated ones. See Rate limits.

Transport and CORS

All traffic is over HTTPS. Cross-origin requests to the API are restricted to the Surnex frontend.

Shared reports

Share links grant access to one report and nothing else — no project access, no organization access.
A share link defaults to no password and never expires. Anyone with the URL can read the report indefinitely, and it shows live data for the report’s date range rather than a frozen snapshot. Set a password and an expiry for anything confidential, and review your active links periodically.
Revoking a link takes effect immediately. Deleting a report also kills its links.

Data deletion

Deletions are permanent and there is no archive or trash. Ranking and backlink history accumulates day by day and cannot be rebuilt or back-filled. Export anything you need before deleting.

Reporting a vulnerability

If you believe you’ve found a security issue, contact Surnex directly rather than opening a public report.