Privacy Policy

Overview

LocalPrivate Tools is designed for private, local-first file work. The App workspace processes user files in the browser. We do not use our servers to read, redact, query, summarize, embed, or answer questions over your file content.

This Privacy Policy explains what data stays on your device, what limited metadata may be processed by our services, and how payment and license flows work.

Who we are

LocalPrivate Tools provides Local PII Redactor, Local Data Workbench, and PrivateDocs AI. Before launch, the operating legal entity, support email, and postal contact details must be added here.

What stays local

The App workspace is not a content-processing backend. Unless you explicitly export a file yourself, the following data is designed to remain on your device during normal product use:

• User files and file contents.
• Parsed text, extracted document text, table data, and SQL query results.
• PII matches, redaction previews, redacted output, and risk report body text.
• Document chunks, embeddings, retrieval context, prompts, answers, and review reports.
• Temporary worker state, in-memory indexes, and local analysis results.

Limited data we may process

To run a paid product and protect the service from abuse, we may process limited non-content metadata:

• Account email, authentication provider, customer id, order id, product SKU, license id, license status, issue date, and major version entitlement.
• Device installation id, device label, activation date, last license sync time, and device count for license limits.
• Free quota metadata such as account id, file size range, file type, scan time, finding count, quota consumption, and abuse-prevention flags.
• Payment, refund, chargeback, tax, invoice, and checkout metadata handled through Creem and reflected in our license records.
• Support messages and any files or screenshots you voluntarily attach to a support request.

Data we do not collect from the App

• We do not collect user files or parsed file content from the App workspace.
• We do not collect SQL query text, SQL output, document chunks, embeddings, prompts, answers, or report bodies.
• We do not load session replay, heatmap, screen recording, or product analytics SDKs inside the App workspace.
• We do not use uploaded user content to train models because the App is not designed to upload that content.

Payments and refunds

Payments are processed by Creem. Creem may act as merchant of record and may receive payment details, tax details, billing information, refund requests, chargeback information, and other transaction data needed to process the purchase.

We receive and store the commercial metadata needed to issue and manage your license. We do not need your local files or analysis results to complete a payment or license activation.

Analytics and error reports

The public website may use Cloudflare Web Analytics for aggregate page views, referrers, conversion paths, browser class, approximate region, and performance metrics. The App workspace must not load this analytics beacon.

App errors are shown locally by default. If remote error reporting is added later, it must be limited to non-content metadata or to a user-reviewed manual report.

Local storage

The App may store preferences, license metadata, cached static resources, WASM files, model weights, non-sensitive templates, and browser capability state locally. Sensitive session content should not be persisted unless a future feature asks for explicit opt-in.

You can clear local App data from product settings or from your browser storage controls. Clearing local data may remove cached models, preferences, and license metadata from that browser profile.

Retention

We keep account, license, order, device, refund, and abuse-prevention metadata for as long as needed to provide the service, comply with payment, tax, accounting, fraud-prevention, and legal obligations, and resolve disputes.

Support records are kept for as long as needed to respond to requests and maintain a useful support history, unless deletion is required by applicable law.

Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, export, object to, or restrict certain personal data. Contact support to make a request.

We may need to keep certain records where required for tax, fraud prevention, chargebacks, legal compliance, or legitimate business recordkeeping.

International use

LocalPrivate Tools is offered to global customers. Service providers, payment processors, hosting providers, and support tools may process limited metadata in countries other than your own. We will use appropriate safeguards where required.

Children

LocalPrivate Tools is not directed to children. You may not use the service if you are below the age required to consent to online services in your location.

Changes

We may update this Privacy Policy as the product, laws, or service providers change. Material changes should be posted on this page with a new last updated date.

Contact

Before launch, add the production support email, legal entity name, and mailing address here.