rips/cloud
ESOpen RipsCloud →
Evidence over labels

Security explained with real limits.

We publish practices we can stand behind and avoid certifications or guarantees the product does not yet have.

Scope of this delivery

Evaluation-site controls.

The portal uses phone access and workspace permissions. API docs explain tokens, revisions and submission rules.

01

Files stay in the browser

Example review processes JSON and XML in memory. It does not send files or use persistent storage.

02

Explicit limits

The page limits bytes, users, depth and item counts. It rejects DTDs and XML entities before parsing.

03

Reports without file data

Results use fixed codes, paths and explanations. Export omits identifiers, names and document values.

04

Read-only tools

WebMCP reads products, questions and links. Its tools do not receive files or act on accounts.

05

Verification on every PR

CI installs from the lockfile and checks build, types, local contracts, navigation, accessibility and dependencies.

06

Contract-based integration

The API requires workspace permissions and validates revisions before submission.

Found a problem?

Send a reproducible description without patient data, credentials or real clinical payloads.