Security

Company state needs clear access boundaries.

Loreflow checks who is requesting access, which workspace and resource they can use, and what action is permitted. This overview explains the product's access model and its limits.

Workspace authorization

Company data is scoped to a Loreflow workspace. Server authorization checks verified identity, organization membership, action permissions and resource ownership.

  • A browser-supplied workspace identifier does not grant access
  • Roles govern supported member actions
  • Read-only MCP uses authenticated, authorized workspace context

Source access and company memory

Connecting a source does not imply universal access or exact source-permission mirroring. Supported deep imports retain permitted source evidence in company memory, readable under Loreflow workspace authorization.

  • Review the source scope before importing
  • Deep memory can include stored content, references and relationships
  • Exact per-document source ACL mirroring is not provided
  • Disconnecting source access does not automatically erase retained company memory

Live access is a separate mode

Member-authorized live retrieval uses request-scoped evidence. Federated content is not silently promoted into durable company memory. Availability depends on the source, permissions and supported operations.

  • Live access and deep imports have different coverage
  • Provider credentials stay with managed connector execution
  • Stale, incomplete or unavailable evidence must be shown as such

Investor recipient access

Recipients sign in to the Investor Portal. Server grants limit access to the published updates shared with that identity; recipients do not become workspace members.

  • Published snapshots are separate from working drafts
  • Recipient access can be revoked
  • Recipient access does not open workspace APIs or company memory

Security reviews

Contact us to review your requirements and request current evidence. Do not assume certification, regional residency, SCIM, legal hold or private-model support from a plan name. Confirm required controls with the team before purchase.

Report a vulnerability

Send findings to security@loreflow.app with enough detail for the team to reproduce the issue. Please avoid including unnecessary personal or company data.

How data flows

Source access,
company memory,
authorized use.

The source mode determines what is retained and which evidence is available.

01 / 03

Authorize source access

Connect an account through a supported workflow and review the available scope.

Account authorizationSupported operationsSource scope
02 / 03

Use the appropriate mode

Deep imports retain permitted evidence. Live retrieval uses evidence within the request.

Durable memoryLive evidenceProvenance
03 / 03

Authorize product access

Loreflow checks workspace membership, permitted actions and resource ownership before serving company data.

Workspace boundaryAction permissionsRecipient grants

Discuss your security requirements.

Ask for current evidence about the controls your organization needs before connecting sensitive sources.

FAQ

About security.

Authorization and evidence handling.

Open the live demo

Server checks bind verified identity and organization membership to a Loreflow workspace, permitted action and resource ownership.

Supported deep imports retain permitted source evidence and derived company memory. Live retrieval uses request-scoped evidence. Review each workflow before connecting a source.

No. Deep imported evidence is governed by Loreflow workspace authorization; exact per-document source ACL mirroring is not provided.

After signing in, recipients can open published updates granted to their identity. Recipient access does not grant membership in the company workspace.

Contact the team for current evidence and confirm required controls before purchase. Plan names do not establish certifications or enterprise controls.