Trust center

Built to be understandable, controllable, and easier to trust.

Greywake uses a local-first product posture, explicit external-service boundaries, versioned releases, and public policies designed to reduce unnecessary collection and ambiguity.

Clear reasoning. Practical controls.
Focused technology and tools for real operating environments.
Data posture

Local by default, explicit when external services are used.

Most Greywake applications run entirely in the browser and keep working data in browser storage. Tools that call an external service identify that behavior and restrict requests to the service required for the feature.

Minimal collectionNo accounts are required for the public application library.
Visible boundariesProfessional, contractual, financial, and safety limitations remain stated where relevant.
Portable recordsMany tools support print, JSON, CSV, text, HTML, or other useful exports.
Controlled dependenciesExternal connections are limited by browser controls and page-specific security policy.
Measurement standard

Measure navigation and reliability, not application content.

Public measurement should be limited to aggregate page use, application launches, guide views, form completion, 404 routes, and technical failure categories. Application inputs, prompts, financial assumptions, audio, imported files, IP-test results, and local backups are outside the measurement scope.

The downloadable package contains no advertising trackers. Deployment-level analytics and monitoring must be configured separately and should follow this data-minimization standard.