Files stay in the browser
Example review processes JSON and XML in memory. It does not send files or use persistent storage.
We publish practices we can stand behind and avoid certifications or guarantees the product does not yet have.
The portal uses phone access and workspace permissions. API docs explain tokens, revisions and submission rules.
Example review processes JSON and XML in memory. It does not send files or use persistent storage.
The page limits bytes, users, depth and item counts. It rejects DTDs and XML entities before parsing.
Results use fixed codes, paths and explanations. Export omits identifiers, names and document values.
WebMCP reads products, questions and links. Its tools do not receive files or act on accounts.
CI installs from the lockfile and checks build, types, local contracts, navigation, accessibility and dependencies.
The API requires workspace permissions and validates revisions before submission.
Send a reproducible description without patient data, credentials or real clinical payloads.