Skip to docs content

Reference

Security and data handling

How keys and sign-ins are kept, who can change your books, what 42six records, and what a browser can reach.

API keys

  • 42six stores only a SHA-256 digest of a key. The key itself is shown once, when it is created, and cannot be shown again.
  • Only a workspace owner can create or revoke a key.
  • Keep a key on a server. Never put it in a browser, a public repository, a shared document or a prompt.
  • Give a key only the reads and books it needs, rotate it with an overlap, and revoke it when you are done. See API keys.

Apps signed in with 42six

  • An app never gets your 42six session. It gets its own tokens, which work only on the MCP server and only for the books you approved.
  • 42six stores only digests of those tokens, and checks the token on every call.
  • Disconnecting the app under Settings › Connected apps stops it at once. See Disconnecting an app on the MCP server page.

Who can change your books

  • An API key never changes your books.
  • Only an app you signed in with 42six with books:write, only on the books you approved for it, and only while you can still change those books yourself.
  • Books your accountant operates for you refuse changes from an app.
  • Changes: preview and apply lists what an app can and cannot change.

What 42six records

  • Every read over the REST API or the MCP server is recorded before it is served: the workspace, the key or the app and its user, the route, the book, the outcome and the number of rows.
  • Reads with an API key that are refused, such as for an invalid parameter or a spent rate limit, are recorded too. For an app signed in with 42six, a refusal that names no book it can reach, or a spent rate limit, is not recorded.
  • A read that 42six cannot record is not served: the answer is 503 with Retry-After.
  • Every apply is recorded with the user and the app. Applied and refused plans are kept.
  • Locks and reopenings keep who, when, the dates before and after, and the reason.

Browsers and CORS

  • The REST API and the MCP server send no CORS headers, so a web page on another site cannot read them. Call them from a server, a script or an MCP client.
  • The OAuth discovery documents and the token and registration endpoints allow requests from any origin.