Document where the model executes and what network calls are required in the target environment.
Local-first browser companion
Design a local-first browser companion with an explicit privacy boundary
How to scope a non-medical companion or productivity workflow around the actual browser/model/runtime boundary.
Best fit
Product teams exploring a browser-based local-first companion experience without medical, therapy, device-certification or app-store claims.
What the focused offer actually does
Configure one non-medical companion or productivity workflow on the current web surface with the actual model/runtime/privacy boundary documented for the target environment.
Current commercial scope: from US$500
Practical workflow
Four checks before you add more software.
The useful unit is a bounded operating workflow: explicit input, evidence, human judgement where needed, and a visible handoff.
List exactly what user content is retained, transmitted or cleared.
Keep the product positioned as a non-medical companion/productivity workflow unless it has the evidence and regulatory basis for more.
Test the privacy boundary in the deployed environment rather than assuming development behavior carries over.
Boundary
Do not turn a useful check into an unsupported claim.
Test the privacy boundary in the deployed environment rather than assuming development behavior carries over.