Privacy

Privacy and Data Handling

Northstar keeps data collection limited on purpose. Browsing the catalog does not require a form submission, and payment should happen only after the guided order total is clear. The site assigns a short-lived first-party session identifier and records limited operational traffic data—page path, referring host, broad browser family, response status, and timing—to detect failures and understand site use.

The traffic identifier is stored as a one-way keyed value rather than a name or contact detail. Operational traffic events are retained for no more than 30 days and are not sold or used for cross-site advertising.

If you use the checkout or contact forms, the site stores the details you enter so the request can be reviewed and followed up on.

If you use the AI checkout-fill feature, the extracted draft is saved in your browser on that device so the checkout page can load it before you submit anything.

If a phone number is included during AI checkout fill and SMS delivery is configured, the site may send a transactional order-summary text with the generated order number.

Submitted contact, checkout, and checkout-issue records are stored in Northstar's durable service database. Payment-proof uploads are stored once and referenced by transactional email jobs rather than copied into every queued message.

Transactional email bodies are placed in Northstar's shared PostgreSQL delivery database before sending. Failed messages retain their payload while they remain eligible for administrative retry.

Northstar's configured email provider processes transactional messages and attachments for delivery. After the provider accepts a message, Northstar removes its body and attachment payload from that delivery queue job while retaining limited delivery metadata; a separately retained payment-proof record remains available only for its bounded recovery period.

Payment-proof files normally become eligible for removal after the default 180-day recovery period and after every associated email has been accepted for delivery. A proof is retained longer while an associated delivery remains unresolved or eligible for administrative retry. Operational records may also remain longer where needed for order support, fraud prevention, accounting, or legal obligations.

Simple orders can use the guided order chat to collect only the details needed to confirm the total and review payment proof.

Customers should avoid sending unnecessary sensitive, medical, or regulated information through the forms. Only include the details needed to answer the request, review the work, or fulfill shipping.

Current Data Practices

Browsing does not require form submission; a short-lived first-party identifier supports limited operational traffic measurement.
Operational traffic records exclude form contact fields, use a keyed visitor value, and are retained for no more than 30 days.
Forms collect only the information the customer chooses to enter on that page.
AI-generated checkout drafts stay in browser storage until cleared or submitted.
Optional transactional order texts may be sent when a buyer includes a phone number in the AI order flow and SMS delivery is configured.
Contact, checkout, and checkout-issue submissions use the durable order database in production and can trigger transactional email notifications when delivery is configured.
Payment-proof bytes are stored once and referenced rather than duplicated across queued email records; the default recovery period is 180 days, with longer retention while an associated delivery remains unresolved.
The configured email provider processes message and attachment content; accepted queue payloads are pruned while limited delivery metadata remains.
Guided orders can keep data collection limited to products, quantities, contact details, delivery details when needed, payment method, and proof upload.

Use only the amount of information needed for your request. Fill out order information first, pay after the total is clear, and upload proof in the order chat.