Data handling

Privacy Notice

Effective 11 August 2026

This notice separates the local tool, optional free hosted beta, and paid beta.

Local open-source tool

pdf-agent-mcp and the optional pdf-mcp-app browser interface run on the user's own computer. They do not upload documents, make conversion-related network calls, collect telemetry, or send usage analytics. The browser app deletes its temporary local document copy after each conversion and removes prepared downloads within 30 minutes or when the app stops. The person or organization running the tool controls its local files.

Free hosted beta

The free hosted beta is a separate, explicit configuration. Its public bridge uploads the selected file to an authenticated extraction service. Use only redacted or non-sensitive born-digital PDF or DOCX documents. Temporary uploads are deleted when the operation completes or fails. Documents and extracted contents are not used for model training.

The service retains these operational fields for up to 90 days:

• Non-secret API key ID and timestamp.
• Tool name and PDF/DOCX type.
• Upload byte count and page, table, and warning counts.
• Processing duration and success or a bounded error code.

The usage ledger does not store the raw API key, source filename, document contents, extracted text, or table cells. Infrastructure providers may process ordinary network metadata, such as IP address, in security logs. Beta request emails contain the contact, business, and project details supplied by the requester.

Operational data is used to enforce the allowance, secure and debug the service, and measure activation, successful use, and repeat use. To revoke a key or request deletion of associated beta account and operational data, email the address below. See the hosted beta terms.

Paid beta operator

The paid beta is operated by Wessel ter Laak. Contact: wesseltl@gmail.com. Live self-service checkout remains disabled until the operator's business registration details are published.

Information processed

• Business contact details supplied in a purchase request.
• Document descriptions used to decide whether a request is in scope.
• Source files supplied through separately provided secure-transfer instructions.
• Profile and evaluation output, checked expected mappings, review notes, correspondence, and transaction identifiers.

This information is used to assess requests, perform and deliver the service, provide support, prevent misuse, and meet accounting or legal obligations. Documents and expected mappings are not used for advertising, model training, or public test data.

Sensitive information

Redact personal or confidential information that is not required for the pilot. The customer must have the right to share every submitted document.

Providers and retention

Email providers process request correspondence. Stripe processes payment details when live checkout is enabled; the seller does not receive full card details. The secure-transfer provider is identified before any upload. Hosting providers process files only as needed to supply the requested service.

Working source files and generated output are deleted within 14 days after delivery. Purchase and transaction records may be kept for the period required by accounting, tax, fraud-prevention, or legal obligations. Backups may expire on a separate technical schedule.

Website

This static website sets no analytics or advertising cookies. It fetches public offer JSON from GitHub to select the current request or checkout link. GitHub and the visitor's network provider may process ordinary request metadata under their own privacy notices.

Your requests

To request access, correction, deletion, restriction, or a copy of personal data, email wesseltl@gmail.com. Some records cannot be deleted immediately when retention is legally required. You may also complain to the Dutch Data Protection Authority.