Data Handling
The proposed scoped-sale policy suite CF-SCOPED-2026-09-21.1 is pending owner approval and publication; it has no effective date yet. Its sale terms apply only when expressly incorporated into a mutually accepted written order. Canonical publication destinations: Terms, Privacy, Refunds, and Data Handling. Verify the published version before relying on it.
This gateway page retains future automated-checkout review material. Historical receipt identifier 2026-08-11 is preserved and does not make this candidate effective or replace an existing agreement. Privacy rights and duties apply to actual processing regardless of checkout availability.
Automated-checkout review statement 2026-09-21-review-1. This page describes the candidate CEMFORGE gateway behavior and does not establish that every proposed control is operational.
Storage boundary
The gateway stores normalized wallet, payment, commercial-identity, legal-receipt, fulfillment, compliance, and operational usage metadata. It does not store full formulation request payloads or returned formulations by default. Buyer and agent checkout fields are allowlisted. Customer-held trace IDs are the default reproducibility receipt.
Security controls
- Platform secret stores for provider keys and webhook secrets.
- Hashed API keys and device tokens; plaintext shown once only.
- Signed Stripe webhook verification and event idempotency.
- Trade-compliance attestation and CSL screening before API activation.
- Operator routes protected by the operator key and designed to return redacted status.
Traceability
Authenticated customer responses use customer-scoped keyed v2 commitments for receipt integrity. They are not anonymous, are not published, and are not designed as cross-customer comparison identifiers. Public synthetic samples may carry deterministic v1 fixture hashes solely for reproducible public examples. Customers should retain the full authenticated response as their private receipt.
Retention and rights operations
The proposed record schedule and rights-request procedure are documented for operator review, but automated expiry, scoped legal holds, deletion propagation, and restore-tombstone tests are launch gates—not completed claims. Rights requests go to privacy@sunn3d.com; never send an API key, claim token, private key, seed phrase, or raw card data.
Incident response
If a secret may be exposed, Sunnyday rotates affected credentials, verifies service health, and records the incident without storing secret values in tickets or public artifacts.