Source state before generation
Users see freshness, parser warnings, missing metadata, and caveats before a draft is trusted.
Security and trust
Helvabase makes the trust layer visible: what source supports an answer, what remains unresolved, and who approved the output.
Users see freshness, parser warnings, missing metadata, and caveats before a draft is trusted.
Snipara credentials, OAuth secrets, and email credentials are configured as server-only environment variables.
Helvabase stores workflow state around Snipara rather than duplicating document indexing or retrieval.
Customer documents are used to operate the requested workspace workflow, not to train Helvabase-owned models.
Pilot workspaces can request source removal and workspace deletion; production retention periods are handled as part of customer onboarding.
DPA, subprocessor, and data-location details are prepared for buyer review before sensitive production onboarding.