curatedapi

Security

If you think you have found a security problem, please tell us at security@curatedapi.com. We reply to every report, and we will not take legal action against good-faith research that respects our users' data and availability.

How we protect you

  • API keys are stored only as keyed hashes and shown once, when created. Revoking a key takes effect on the next request.
  • Public (website) keys work only from the sites registered for them, and secret keys are refused when sent from a web browser.
  • Your calculation inputs and results are never written to disk or to a log (a recent answer may be kept in memory for a short time, so a repeat is faster). The usage ledger records which calculator was called, when, and the outcome; idempotent retries are matched by a one-way hash of the request.
  • The usage ledger is append-only at the database level: billing history cannot be edited, only corrected by separate, explained adjustments.
  • Every calculation runs in an isolated worker process with time and memory limits, and expressions are parsed by our own parser, never evaluated as code.
  • The servers accept no connections from the internet: web traffic reaches them only through an outbound tunnel to Cloudflare, and server administration works only over a private network.
  • Dashboard passwords are stored as Argon2 hashes, and two-factor sign-in is available for every account.

Machine-readable contact: security.txt