Skip to main content

Security

Credential handling​

Partner API credentials are a key/secret pair with no scopes and no expiry, so their handling is what protects your account:

  • Store the key and secret in environment variables or a secrets manager, never in source control.
  • Never expose them to a browser or mobile client. They are deliberately outside the API's CORS header allowlist, so browser calls fail preflight.
  • Use a distinct key per environment and per integration, so one can be retired independently.
  • The secret is returned once at creation and cannot be recovered — store it immediately.

What the platform guarantees​

Filedgr proves integrity: that a file is exactly the file that was notarized.

  • Every artefact is identified by its cryptographic hash (content addressing).
  • Hashes are anchored on-chain, making later tampering detectable.
  • Retrieval is gated by on-chain vault, stream and asset permissions.
  • Permission changes are recorded with actor and timestamp.
note

Integrity and confidentiality are distinct guarantees. A Filedgr proof establishes that a file is exactly the file that was notarized. Where your data carries confidentiality requirements of its own, encrypt it before notarizing, so the proof covers ciphertext that stays under your control.

Permissions​

Access is granted explicitly — there is no "no access" level to assign, and absence of a grant means no access. Vaults and assets use OWNER, ADMIN, EDITOR, VIEWER; vaults additionally support CUSTOM. Streams use ADMIN, EDITOR, VIEWER.

Grants settle on-chain asynchronously, so a freshly granted permission is not immediately effective.

Reporting an issue​

If you believe a credential has been compromised, or you have found a security issue in the platform, contact Filedgr support directly rather than filing it in a public channel.

See also Authentication and Best Practices.