Trust Center

Security Hoku can stand behind

Hoku may be the friendly face at the front door, but approval rests on serious repository protections: intentional access, isolated processing, and clear data boundaries.

Friendly reviewer. Strict boundaries.
HokuFetch puts clear authorization and purpose-limited handling at the center of every repository scan.

Our approach

Protection at every stage

From access through cleanup, HokuFetch is designed to make source protection a deliberate part of the scan experience.

Explicit authorization
HokuFetch is designed to keep repository access intentional and scoped to the scan at hand.
Isolated processing
Repository analysis is separated from the product experience to keep scan work purpose-limited.
Private workspace
Every scan is designed around a private workspace and read-only handling of repository content.
Restricted network access
Network access is intentionally constrained so scan activity remains purpose-specific.
Bounded retention
Repository data is handled with defined retention boundaries and an independent cleanup approach.
Privacy-conscious telemetry
Operational insight is designed to focus on the health of a scan, not the contents of your code.

Ongoing assurance

Built to verify the boundaries

Strong source protection depends on more than one control. Our approach brings access, isolation, network boundaries, cleanup, and privacy into the same security conversation.

Security checks
A trusted scan experience depends on checking the boundaries that protect your repository.
  • Access boundaries are reviewed for every scan flow.
  • Workspace isolation and read-only handling are validated together.
  • Network and resource constraints are tested under normal operation and failure.
  • Cleanup and retention behavior are checked independently of scan work.
  • Operational signals are reviewed for privacy-sensitive detail.

Designed around trust

Your repository deserves clear boundaries

HokuFetch is designed to help teams learn from their code while keeping access intentional, handling constrained, and privacy at the center of the experience.

Reviewed public guidance · September 8, 2026