No invoice upload on the public website.

1. Checkout and contact information

Stripe hosts the published payment checkout and may process business/name, contact, billing, tax-ID and payment information required for the transaction. Solarc Labs does not ask buyers to email card or bank credentials.

We use the checkout contact details and payment reference to verify the order, send intake instructions, deliver the purchased work and handle support, accounting, refund or dispute matters.

2. Representative invoice corpus

Invoice documents can contain names, addresses, tax identifiers and other business information. Provide only the representative invoices needed for the purchased preflight. Minimise or anonymise personal data where practical and do not include unrelated files.

The buyer must have authority to provide the material for the purchased review.

3. Processing boundary

The current InvoiceBatch FR operator workflow is local-first and founder-assisted. The commercial release design uses local factur-x, loopback Saxon and local CodeDB; the release gate must pass before a runtime is treated as commercial-ready.

The verified commercial release gate records zero external invoice-validation requests during its controlled acceptance run. That evidence is bound to the exact tested runtime and does not turn into a blanket promise about an unverified future environment.

The run/evidence model keeps hashes, findings, coverage, mapping/review state and provenance rather than embedding source invoice bodies in the evidence pack. This does not mean the original intake files never exist in the controlled operator workspace; they are required to perform the purchased review.

4. No public SaaS account or public corpus storage

The MVP does not provide a public multi-tenant InvoiceBatch FR account, public invoice-upload portal or cloud invoice corpus database. A future materially different public collection/storage method would require a separate privacy and security review before it is used.

5. Retention and end of processing

Order, support and accounting records are kept only as reasonably needed to deliver and administer the transaction or meet legal obligations. Source invoice material is retained in the controlled workspace only for the operational purpose and period reasonably needed for the purchased review, included re-test, support or dispute handling.

Where Solarc acts as processor for corpus personal data, the InvoiceBatch FR Data Processing Terms provide for return or secure deletion at the end of processing subject to the customer's written choice and applicable legal-retention requirements.

The service does not advertise an automatic cloud-retention/deletion guarantee. Return or deletion is performed through the controlled operator process and the applicable written data-processing terms.

6. Service providers

Stripe processes hosted checkout/payment information. Website hosting and communications providers may process limited technical/contact information needed to operate the public site or communicate with the buyer. The invoice-validation workflow itself is designed not to require a remote validator.

A third party is not appointed to process a customer invoice corpus on Solarc's behalf without the authorisation process stated in the InvoiceBatch FR Data Processing Terms.

7. Privacy requests

For privacy questions or applicable data-protection requests, contact enoch@solarclabs.com. Do not include invoice attachments in the first privacy-request email unless specifically requested through a controlled channel.