The DOCX inspector reads a selected file in this browser page. The detector demo also runs locally after an explicit model download. Neither feature sends filenames, document contents, entered text, metadata, marker identifiers, counts, scores, or report results to Draft Record analytics.
DOCX processing
- The selected file is read into browser memory; the current product has no document-upload request.
- The generated PDF report remains local and is offered through a browser object URL.
- Closing or resetting the page discards the in-page result. Draft Record does not put it in the URL or browser storage.
Detector-model download
The detector page makes no model request until its labelled button is pressed. On first use, the browser requests the disclosed quantised model file from Hugging Face. The entered text is processed locally and is not included in that model request.
Property-free analytics
Pages use a self-hosted Umami tracker. Umami's documentation says Umami works without cookies. Its tracker configuration page says a site can set data-do-not-track to disable tracking when the browser has Do Not Track enabled, and Draft Record sets it. Draft Record allows only the property-free product events work_started and work_completed. The bridge accepts an allowlisted event name and no properties, so those events cannot carry a filename, document content, entered detector text, marker, score, count, or report result. When Do Not Track is enabled, the bridge sends neither event. The tracker also records page-loading and interaction performance timings (such as LCP, INP and CLS) with the page address and device type, to help find slow pages; these timings contain nothing you type, paste or upload.
Advertising status
The current build reserves advertising space, but both ad-unit identifiers are empty. Its lazy loader therefore does not request the AdSense library, and no advertising identifier is set by that inactive surface.
Google's publisher requirements explain the Google-certified consent platform required for personalised ads in the EEA, United Kingdom, and Switzerland. Any later activation must provide that choice before personalised advertising and must leave the local tools usable when consent is declined.
Contact
Write to support@draftrecord.com. Do not attach a document or paste its contents, filename, metadata, detector text, score, or Draft Record result into a support message.