Eureka Insight

Security

Trust boundaries are enforced on the server, not implied by the interface.

Insight is designed around verified identity, scoped ownership, defensive file handling, payment integrity, and clear production controls.

Security overview · September 4, 2026

01

Identity and sessions

Connected accounts use identity tokens verified by the API.

  • Expired, invalid, and revoked tokens are rejected.
  • Authenticator-app 2FA is available for verified Google and password accounts.
  • Sensitive exports and deletions require a recent primary sign-in.

02

Product and user isolation

Ownership is keyed by both account and product.

  • Insight subscriptions never activate Health.
  • Files, runs, artifacts, wallets, and checkout metadata are product-scoped.
  • Guessed resource identifiers do not bypass ownership checks.

03

Uploads and generated files

Files are inspected before their contents enter the research workspace.

  • Type, size, package structure, and decompression limits are validated.
  • Macro-enabled, embedded-object, traversal, and malformed packages are rejected.
  • Generated artifacts are authorized before download.

04

Payments, secrets, and operations

Sensitive provider credentials stay server-side.

  • Payment events are signature-verified and idempotent.
  • Checkout redirects do not grant entitlements by themselves.
  • Monitoring, backups, retention, and incident-response ownership are explicit operational controls.