Privacy policy

Who operates this service

Anatoly Levenchuk operates fpf.tools, including its public website, search, HTTP API and MCP endpoints. For privacy questions or a request concerning your data, email ailev@asmp.msk.su with the subject “fpf.tools privacy”. You do not need an account to use the service.

What we process and why

To deliver a page or answer a tool call, the server receives the requested URL, network address, HTTP headers and any submitted search text or tool arguments. These are processed to route the request, search the local Library index and return the selected public material. MCP does not automatically send us your entire chat, but your client may include parts of it in a tool argument. Please send only information needed for your search.

We do not create user profiles, save a history of your searches or tool calls, or store successful response bodies. The service does not set advertising or analytics cookies.

Minimized service logs

Before application and reverse-proxy output is written to the service journal, a filter keeps only predefined technical fields: time, component, event category, severity, HTTP method, a broad route category, response status, response size, request size, duration and process exit code, when available. Route categories are fixed labels such as “search” or “mcp”; they do not contain your URL or search terms.

The filter does not retain IP addresses, request or session identifiers, HTTP headers (including X-OpenAI-Subject and X-OpenAI-Session), URL parameters, tool arguments, response bodies or free-form error text. Unknown diagnostic fields are discarded. We use the remaining records to detect failures and maintain the service.

Retention and automatic deletion

Service diagnostics are retained for no more than seven days while the server and scheduled cleanup are operating. The journal is rotated and expired automatically every hour; size limits can remove older records sooner. If the server is stopped, cleanup resumes after startup. The service journal is not forwarded to the general text syslog.

Separate operating-system security logs can contain IP addresses, ports, times and information about blocked connections or administrative access attempts. These support server security. Network and authentication text-log records are automatically removed within 30 days; the shared system journal has the shorter seven-day limit. These security logs do not intentionally record MCP argument or response bodies.

Transition from the previous configuration: service records made before this policy took effect may contain IP addresses, headers, identifiers and error details. Old service entries in text logs and the former dedicated FPF access-log files were removed during migration. Remaining entries in the shared binary system journal expire within seven days of the change, by 24 October 2026. This deadline does not describe copies held independently by the hosting provider or previously used diagnostic tools.

Hosting, access and other recipients

The service runs on an AdminVPS virtual server in Germany under its “All inclusive” service model. There is no separately configured external CDN or WAF in front of our HTTPS proxy. The operator and authorized administrators can access server diagnostics. The hosting provider has infrastructure and administrative access under its service arrangements.

We do not send searches to an external search or AI service to answer them. Results go back to the requesting client. Administrative work can use Codex/OpenAI; diagnostic information supplied for that work is limited to the minimized records described above. The request body and full client headers are not exported for troubleshooting.

ChatGPT, another MCP client, or an application's own intermediary may process and retain requests under its own policy. AdminVPS may separately keep network, protection or support records. Section 15.11 of its service agreement permits retention of technical data for contractual, incident-response and legal purposes, subject to applicable law and company documents. Sections 5.1–5.2 of its privacy policy tie processing periods to purposes and contractual terms. These provisions do not specify a numerical retention period or field list for the provider's own infrastructure logs. Our seven- and 30-day limits apply to the logs we control.

Backups

Our standard encrypted configuration backup excludes the server log directories. We do not maintain a separate backup archive of the new service logs. Provider-level full-server backups and snapshots can contain logs.

Backup is included in the “All inclusive” service model used for this VPS. AdminVPS's VPS-specific instructions describe a weekly full-server backup with one copy from the latest week, with up to seven copies available for an additional charge. Its snapshot instructions specify automatic deletion 72 hours after creation. Section 3.6 of the service agreement specifies 60 days after deletion of a VPS service when free remote backup space is provided. These are different retention conditions, not a single period for all provider data. We have not independently verified the latest completed provider backup, any additional paid copies or separately created snapshots for this VPS. Provider documents and the service model were checked on 17 October 2026.

Restoring a server backup requires reapplying the logging filter and running expiry before normal service is resumed.

Requests about your data

Use the email above to request information, correction or deletion concerning data you believe we hold. If relevant, include an approximate time and the affected service or tool; do not send passwords, tokens or your complete chat. We will assess what records can be located and removed, explain any limitation, and distinguish our records from those controlled by your client or hosting provider. Because new service logs contain no user or session identifiers, we may be unable to associate a diagnostic entry with you. There is no automatic account-deletion interface.

Information you choose to send in a privacy or support email is handled to respond to that request and is separate from automated service logs. Email-provider retention is not covered by the log-deletion timers above.

Changes

Changes to this policy are published at this address with a new effective date. The logging and retention settings must be checked before a changed policy is presented as operational.