Collect less. Explain it clearly.

The final notice will cover the Curbidz website, customizer, checkout and order flow, transactional communication, customer support, consented marketing, and related administrative systems. It will identify the responsible business and explain which practices apply when someone merely browses, builds a preview, places an order, requests support, or chooses marketing.

It will not claim that Curbidz “owns” a customer's personal information. Any limited rights needed to process a customization, fulfill an order, prevent fraud, provide support, or meet legal obligations will be described by purpose and duration.

• Render, validate, save, and reproduce a customer-approved customization.
• Calculate the order total and operate a hosted payment and fraud-prevention flow.
• Create, produce, quality-check, ship, track, support, refund, or replace an order.
• Send confirmations, service notices, delay choices, support responses, and other transactional messages.
• Protect accounts and systems, diagnose errors, prevent abuse, preserve evidence, and recover service.
• Maintain tax, accounting, dispute, warranty or claim records where applicable.
• Send marketing only after a separate, voluntary choice and preserve the suppression record after opt-out.
• Comply with valid legal obligations and establish, exercise, or defend legal claims.

A materially new use that is incompatible with the disclosed purpose will not be smuggled into the system merely because the information already exists.

Access will be limited by role and contract where appropriate. Information may also be disclosed when required by valid legal process, to protect rights and safety, or as part of a reviewed business transaction with legally required notice and choices. The final notice will describe the actual practice—not a hypothetical permission to disclose information for any reason.

The intended launch position is not to sell personal information or share it for cross-context behavioral advertising. The finished preference system will recognize applicable browser-based opt-out signals, including Global Privacy Control, and will not use a dark pattern to reverse a choice.

Different records need different retention periods. An abandoned preview, unpaid checkout, paid order, production artifact, tax record, support case, security log, backup, and marketing suppression record should not all live forever under one generic rule.

Before launch, Curbidz will assign each record a documented trigger, period, deletion or anonymization action, legal-hold exception, backup behavior, and responsible owner. Exact periods will be confirmed with operational, tax, warranty, dispute, and legal requirements and then summarized in the final notice. Information that is no longer needed will be securely deleted or de-identified under that schedule.

The final request page will explain identity verification, authorized-agent treatment, search systems, processor propagation, response timing, exceptions, and appeals. Curbidz will not ask for more verification information than the request reasonably requires.

The published notice will carry an effective date and version. A material change will receive notice appropriate to the change and applicable law. Code, consent surfaces, vendor configuration, retention rules, and customer-rights operations will be reviewed against the text before a new version takes effect.

The responsible seller/controller name, monitored privacy contact, and mailing address have not been finalized and therefore do not appear as placeholders. See the contact status page for the current state.