Menu

Privacy

Privacy and data handling for Stornamics docs.

Stornamics docs should help readers evaluate private beta products without exposing customer data, credentials, payloads, or sensitive operational details.

Privacy Boundaries

Docs content

Published examples, commands, payloads, identifiers, and screenshots should be public-safe and synthetic.

Do not copy customer identifiers, secrets, raw payloads, private topology, or proprietary logs into docs examples.

Search and docs feedback

Search terms and docs feedback reports should be treated as reader-provided data.

Use the approved feedback route for public-safe reports, and keep inline page rating controls hidden until a separate reviewed workflow exists.

Support evidence

Support bundles and diagnostic output can contain sensitive product, customer, or environment details.

Use redaction guidance before sharing operational evidence through a support path.

Analytics And Cookies

No third-party analytics tags are enabled on the public docs site at launch. The docs site does not load Microsoft Clarity, Google Analytics, Google Tag Manager, or similar tracking scripts, and it does not set analytics cookies for docs readers.

Browser-local page health signals stay on this device. Search no-result records, broken-journey checks, low-rated page summaries, and stale-review dashboard state use browser storage for reviewer diagnostics and are not sent to a remote analytics service by the docs site.

Stornamics requires privacy/legal approval before enabling analytics, cookies, consent prompts, remote telemetry collection, or retention language for the docs site.

  • Feedback

    Route docs gaps, product questions, sensitive evidence, and launch signals through approved intake paths.

  • Support

    Choose the right support path before sharing product questions or operational evidence.

  • Support bundle privacy

    Review what to include, exclude, redact, and route before sharing a diagnostic bundle.

  • Terms

    Review docs-site use boundaries, product-claim limits, and private beta agreement precedence.