Skip to content
Dowelifyby Reachability LabsOpen Dowelify

Trust / Security

Protect the record. Preserve the boundary.

Dowelify is built around a record people can inspect and continue. Security means protecting access to that record while keeping model proposals distinct from actions only people can take.

Founding pilot
Current controls
No certification claims

The Job record

Job events are append-preserved. A correction adds a superseding entry rather than silently overwriting the earlier event, so participants can inspect how the record changed.

Contributions carry their producer and time. The record distinguishes a person's observation or attestation from a document, instrument reading, or AI proposal.

Access is checked on every request

Requests to read or change a Job are evaluated against the current participant and their role. Possessing an identifier is not treated as permission. Unauthorized callers do not receive details that distinguish a Job they cannot access from one that does not exist.

Media and the AI boundary

Raw media is sent to the current AI provider only after a user starts an operation that requires it. Simply viewing media does not send it to a model.

Dowelify currently calls the OpenAI API with store: false. OpenAI states that API data is not used to train models by default, while limited provider retention can still occur for security, abuse monitoring, or legal obligations. Dowelify does not claim Zero Data Retention.

Manuals, documents, transcripts, and other outside material are treated as information—not instructions that can grant permissions or alter a participant's authority.

Human authority is a tested product boundary

AI output remains a proposal. In the current application, recording work as performed, accepting completed work, and releasing something back into service require an authorized person's explicit action.

This prevents a fluent model response from becoming a false claim that physical work occurred or was approved. It does not guarantee that a person's decision is correct; safety still depends on qualified human judgment, applicable rules, and the physical evidence.

Sessions and controlled change

Enrolled participants use signed, expiring sessions rather than a public or shared application credential. Database changes use versioned migrations, and application authorization is enforced on the server rather than trusted to the visual interface.

What we don't have yet

Dowelify is pilot-stage software. We would rather identify incomplete controls than decorate the site with trust marks we have not earned.

  • We do not hold SOC 2, ISO 27001, or another third-party security certification.
  • We do not yet claim routine, scheduled, media-complete production backups with a tested restore cadence.
  • We do not yet offer automated whole-account export or deletion; verified pilot requests are handled manually.
  • Durable private-media storage is still in development and is not presented as an enabled public capability.

Report a vulnerability

Send enough detail to reproduce a suspected security problem to security@dowelify.com. We will acknowledge a report within three business days, keep the reporter informed as we investigate, and not pursue good-faith research conducted without harming people, accounts, or data.

Please do not access another person's information, degrade the service, or publish an unresolved issue before we have had a reasonable opportunity to investigate.