the log is short on purpose.
the rig logs the minimum required for transmission: operator email, hashed password, order history (artifact ids, carrier acknowledgments), retrieval tokens, and the timestamp of each transmission.
the carrier (stripe) holds the payment instrument. the rig never sees the operator's card number, billing address, or related payment data.
the carrier requires the operator email to acknowledge transmission. the order history is required to re-issue retrieval tokens. password hashes are required for terminal authentication.
nothing else is required, so nothing else is logged.
the operator (S.C.) administers the rig. no third-party analytics, no advertising network, no marketing pipeline reads the rig's log.
the carrier (stripe) sees the payment leg of each transmission as required to settle. the rig's email provider sees the destination address of each retrieval dispatch. no other party.
the operations log retains account data while the account is active. on closure, identifying data is purged within thirty days. anonymized order totals may persist for accounting.
the operator can request a dump of their record, a correction, or a purge by contacting the rig. requests are documented in the operations log and resolved within thirty days.
operators in jurisdictions with statutory data-rights regimes (GDPR, CCPA) retain those rights in addition to the above.
the rig sets no advertising cookies. session cookies are used for terminal authentication only. there is no behavioral tracking pixel on any page.
the carrier (stripe) sets its own cookies during checkout. those are governed by the carrier's own privacy policy.
the rig is administered from sector cascadia nw. log data is stored on infrastructure located in the united states. by transmitting through the rig, operators consent to that transfer.
questions, requests, or grievances about the privacy log go to the operator. the address is published on the about page.