Architecture & Data Flow

How the Data Flow Works

Unlike traditional SaaS validation tools that require you to upload a .csv or .xlsx file to their cloud storage, Foxentry Data Cleaner operates entirely locally.

Here is the step-by-step lifecycle of a validation task:

1. Local Initialization: The application reads your source file locally into system memory. The file itself is never uploaded.
2. Value Extraction: The tool extracts only the specific columns you mapped in the user interface (e.g., column C mapped as Email, column D mapped as Phone). Any unmapped data (like internal IDs, notes, or prices) remains completely invisible to our servers.
3. Secure API Request: The extracted values are formatted into a JSON payload and sent via secure HTTPS (TLS 1.2/1.3) directly to the Foxentry API endpoint (api.foxentry.com).
4. Processing & Response: The Foxentry API validates the isolated string values and returns the validation status, corrections, or enriched data.
5. Local Write: The application receives the JSON response and appends the new data to a completely new output file on your local disk. Your original source file is never modified or overwritten.

📘

Network Egress Restriction

If you are running the tool in a strict corporate environment (e.g., behind a firewall), you only need to whitelist outbound HTTPS (port 443) traffic to api.foxentry.com. No other external connections or third-party tracking scripts are executed.

Security & Compliance Details

Bypassing Cloud Storage Risks

Because the file is processed locally and only isolated strings are transmitted for a split second, you bypass the need for complex Data Processing Agreements (DPAs) related to file storage. We do not store your database, do not cache your files, and do not retain the context of your data rows.

CSV Injection Protection (Formula Injection)

By default, the application sanitizes the output file to protect against malicious CSV Injection. If a validated string or suggestion begins with a sensitive character (such as =, +, -, or @), the application automatically prepends an apostrophe (') to prevent spreadsheet software (like Microsoft Excel) from maliciously executing it as a formula.

Binary Integrity & Verification

For organizations with strict software supply chain policies, the Data Cleaner's build process is fully transparent and auditable:

• SHA-256 Checksums: Every release on our GitHub includes a checksum file (.sha256) to verify the downloaded binary hasn't been tampered with.
• Sigstore Attestations: The build provenance is verifiable via Sigstore, cryptographically proving the executable was compiled directly from the open-source GitHub repository without unauthorized modifications.

Next step: Ready to run the tool? Head over to the Setup & Prerequisites section to learn how to generate your API keys and handle initial OS security warnings.