Skip to main content

Privacy and sanitization guarantees

The API never returns the following under any scope:
  • Secret values.
  • Key hashes or raw keys.
  • OAuth tokens, client secrets, and encryption keys.
  • Entity records.
  • Enum values, defaults, and descriptions from entity schemas.
  • Backend function source.
  • Agent instructions and tool configuration.
  • Custom integration headers.
  • End-user (app-user) identities.
  • Message, chat, and conversation content.
  • File contents.
  • MFA factor values, meaning phone numbers, TOTP secrets, and hashed backup codes.
  • Invitation tokens.
  • Base44-internal URLs and employee identities.
In almost every case this is enforced at the database read rather than at the response. The material is never loaded into the process that serves your request. Member emails are returned by the members endpoint, because you need them for identity joins. That’s exactly why people data sits behind its own consent scope.

Gap register

Where a field a scanner usually expects doesn’t exist in Base44, this table shows what arrives instead.