HOME / PRIVACY

Effective August 3, 2026

Privacy that matches how the tools actually work.

This policy explains how DocReviewKit keeps document processing local while using limited, cookie-free analytics to improve the tools.

Files and generated output

Word, PowerPoint, and PDF files are parsed in your browser. Source files, file names, document text, comments, authors, replies, tracked changes, slide content, generated workbook bytes, generated Markdown, extracted images, and generated ZIP packages are not uploaded to DocReviewKit.

Closing or reloading the page removes the in-memory processing state controlled by the tool. You are responsible for saving any workbook, Markdown file, or ZIP package you want to keep.

Privacy-safe analytics

The tools create a short-lived event buffer and send limited product events to a DocReviewKit Cloudflare Worker. These events use categories such as tool started, task completed, result action, size bucket, duration bucket, result type, and stable error code.

Events may include the tool and route, an anonymous random ID limited to the current browser tab, a broad source category, recognized campaign labels, and bounded result categories. They do not contain file names, document content, comment text, authors, workbook content, Markdown output, images, or generated ZIP content. The custom event collector also respects the browser's Do Not Track setting.

Cloudflare Web Analytics provides aggregate page, referrer, device, country, and performance reporting. It is used without analytics cookies or cross-site user profiles.

Hosting and network data

Like most websites, the hosting and domain infrastructure may process standard request data such as IP address, browser type, requested URL, timestamps, and security or delivery logs.

DocReviewKit is hosted on Vercel and uses Cloudflare for domain and DNS services. Their handling and retention of infrastructure data is governed by their own policies and service settings.

Cookies and advertising status

DocReviewKit does not currently load Google AdSense or third-party advertising tags. Cloudflare Web Analytics and the DocReviewKit event collector do not use advertising or analytics cookies.

A random analytics session ID and first-touch attribution categories may be stored in `sessionStorage` for the current browser tab. They are not shared across sites and are removed when that tab session ends. See the Cookie Policy for details.

Future Google advertising

If Google advertising becomes active, Google and other authorized advertising vendors may use cookies, web beacons, IP addresses, or other identifiers to serve and measure ads, including ads based on prior visits where permitted.

Google explains this processing in How Google uses data on partner sites. Users can manage personalized advertising in Google Ads Settings.

Retention and sharing

DocReviewKit does not receive or retain source documents, generated workbooks, generated Markdown, extracted images, or generated ZIP packages. Aggregate tool events are stored in Cloudflare Workers Analytics Engine, which currently retains this dataset for up to three months.

DocReviewKit does not sell document content or personal information. Vercel and Cloudflare may process limited network and analytics data to deliver, protect, and measure the site. Any future advertising vendors will be disclosed before their code is activated.

Children and sensitive documents

The site is not directed to children, and it is not designed to collect personal information from children. Do not use the tools with files you are not authorized to process.

Browser-local processing reduces disclosure risk but does not replace your organization's security, confidentiality, retention, or records-management requirements.

Questions and requests

Privacy questions and requests can be sent to privacy@docreviewkit.com. Do not attach source documents, comments, exported workbooks, Markdown or ZIP output, passwords, or other confidential material.

This policy may change when the site's data practices change. Material changes will be reflected on this page with a new effective date.