Skip to main content
Superdata applies account-level controls to every connected client. Codex, Claude, direct MCP connections, and API-key connections use the same credit allowance and usage history.

Intelligence credits

1 accepted intelligence tool execution = 1 intelligence credit
Credits are reserved before provider work begins. Active grants that expire first are consumed first. Plan allowance and reset details shown in your dashboard are the source of truth. Read How intelligence credits work for the complete charging model and View credit usage for dashboard guidance.

Usage records

Every accepted tool call creates a durable account usage record containing the tool, outcome, credit charge, timestamp, and duration. Usage records are not saved leads, and MCP result records are not currently copied into dashboard workspaces automatically.

Credential safety

  • Prefer OAuth browser sign-in for supported interactive clients.
  • Use a separate API key for each machine, script, or environment.
  • Store keys in a secret manager or secure client credential store.
  • Rotate credentials when their storage or audience changes.
  • Revoke a key immediately if it may have been exposed.
  • Never include secrets in URLs, chats, screenshots, logs, or source control.

Data handling

Superdata returns provider-supplied company and professional data. Unavailable fields are null; Superdata does not invent contact details. Review returned data before acting on it and use it in accordance with applicable privacy, marketing, and data-protection requirements. Do not send unrelated sensitive personal data in prompts or support requests. For privacy or removal requests, email hey@superdata.so and state the request type in the subject.
Public policies are available in the Privacy Policy and Terms of Service.