# Privacy

Every action is explicit. Inspect and Clean use the private deterministic engine without Azure OpenAI; Refine may use Azure OpenAI.

Canonical: https://watermarkslayer.com/privacy
Markdown alternate: https://watermarkslayer.com/privacy.md
Last reviewed: 2026-08-12

## Deterministic inspection and cleanup

Inspect and Clean send the exact source through the public entry point to the private processing engine. Those deterministic actions do not call Azure OpenAI and do not store the source or result.

## Azure processing after an explicit action

Pressing Refine sends the draft and selected writing controls to the Watermark Slayer service and may send them to its Azure-hosted model for transient processing. The request is used to produce the requested editorial result.

Azure content filtering and abuse monitoring may inspect prompts and completions. Under applicable Azure configurations, flagged samples may be retained for abuse review. This provider-level handling is separate from the Watermark Slayer application boundary.

## No draft history in the launch design

The Watermark Slayer application itself retains no drafts: it uses no database, object store, queue, temporary file, server result cache, or staff-retrieval path for source or generated text. Clear session removes browser-held draft and result state.

A production no-retention assurance is published only after deployment logging and telemetry are verified with a synthetic content canary.

## No content-derived request state

The browser and service do not derive content hashes, cache results, or create processing receipts. The browser keeps only the active tab's source and review state until the writer clears it or closes the tab.

## Evidence

- [Microsoft Azure Direct Models data privacy](https://learn.microsoft.com/en-us/azure/foundry/responsible-ai/openai/data-privacy)