Original stays local
A future in-browser redactor must remove seller, order, item, and free-text identifiers before any transfer. The contributor must see the exact derivative, retained fields, row count, totals, and derivative SHA-256.
Voluntary samples are not being collected yet.
Using the checker never sends your report to Soleram. There is no upload endpoint, background sync, email attachment, or automatic financial-file collection in this preview.
No contribution action is active
Do not email or otherwise send a report. This page documents the minimum process that must exist before Soleram can invite voluntary participation.
Separate consent
A separate unchecked control must confirm authority to share the sanitized derivative and permission to retain it privately for compatibility testing. Marketing consent cannot be bundled.
Second send action
Nothing may leave the browser until an explicit “Send sanitized sample” action after redaction preview and consent. Viewing a result or expressing workbook interest is not consent.
Receipt and deletion
The contributor must receive an opaque receipt ID, consent version and time, retention term, and a deletion-request route. Raw originals are never retained by default.
Separate evidence store
Consented derivatives must live in an access-controlled validation store, never this repository or synthetic-fixture directory. Repository records may contain only opaque evidence metadata and pass/fail outcomes.
No outreach
Acquisition is passive through owned, indexable pages. No cold email, direct message, forum solicitation, customer-list reuse, or required sample contribution.
This draft requires legal/privacy review before collection can start. Until then, the genuine-sample count remains zero and the compatibility release gate remains closed.
← Return to the local checker