Privacy Policy

PREFIX's correction path is local. This policy also explains the local records PREFIX can create and the separate data handled by website hosts and the checkout provider.

1. Core Software Processing

The PREFIX for Python 0.1.0 engine and VS Code correction path process Python text on the customer's computer. The shipped correction sources contain no cloud-inference call, telemetry client, analytics client, or network transmission path. The VS Code extension sends the open document text to the installed local PREFIX engine through a local child process.

This does not mean PREFIX "collects nothing." Local files and records described below can contain source code and user-provided information.

2. Local Files and Receipts

When the customer uses CLI apply or rollback features, PREFIX can create JSON receipts. By default they are stored in a.prefix-python-receipts directory next to the target file unless the customer chooses another directory. Receipts can include:

• the absolute target-file path;
• full before-and-after source text;
• hashes, proof data, engine results, and receipt lineage; and
• the PREFIX and Python version boundary.

The optional operator-console commands can store names, email addresses, team or cohort details, notes, issue summaries, and evaluation records as JSON in a local workspace selected by the user. The inspected release sources do not automatically transmit those local records.

Customers decide which files to analyze, whether to apply a change, where optional receipt or operator records are stored, and whether those records are later shared.

3. Product Website

The product website contains no analytics script, tracking pixel, form, cookie-setting script, or browser-storage code. A hosting provider may still process standard request information such as IP address, browser details, requested page, timestamps, and security logs under that provider's terms.

Links to GitHub, the checkout provider, or other sites open services with their own privacy practices.

4. Purchases and Digital Delivery

When sales are activated, the authorized checkout provider will separately process order, identity, payment, tax, fraud-prevention, receipt, and fulfillment data under its own terms and privacy notice. Fast Industries may receive transaction and customer information needed to administer the license, provide access, handle order support, prevent abuse, and meet legal obligations. Payment-card details are handled by the checkout provider rather than the PREFIX correction engine.

5. Retention, Security, and Customer Choices

Local product files remain under the customer's control and local security practices. Customers should protect receipts because they can contain source text and paths. Deleting local receipts can remove the evidence needed for receipt inspection, replay, or rollback.

Order-data retention and privacy requests are handled through the private contact method shown on the checkout receipt and any rights supplied by the checkout provider. Do not publish personal, order, payment, receipt, or proprietary source information in a public GitHub issue.

6. Changes

This policy may be updated when the hosting or checkout configuration changes or when product data handling changes. The "last updated" date will identify the current version.