ShootStrayt Privacy Policy

Effective date:

This policy describes information handled by the current ShootStrayt website features. It is limited to behavior identified in the frontend source and request contracts as of the effective date.

Information you submit

  • Account and signup information. Signup can submit a username, email address, password, first and last name, newsletter choice, an optional saved address and phone number, and a CAPTCHA token when the challenge is active.
  • Account access and password reset. Login can submit a username or email address, password, and a CAPTCHA token when the challenge is active. Password-reset requests can submit an email address and CAPTCHA token; reset confirmation can submit a reset token and new password.
  • Contact information. The About contact form submits a topic, an optional team member, optional name, email address, and order number, and a required message.
  • Newsletter choices. Authenticated profile controls can submit newsletter subscription choices.
  • Checkout information. Checkout can submit contact name and email address, shipping address and phone number, an optional billing address, a shipping-option selection, an optional discount code, and optional guest-account fields. The server supplies authoritative shipping, discount, tax, and total values.

Cookies and browser storage

  • Authentication requests use credentials and CSRF information. Protected profile routing checks for a session cookie.
  • The browser cart is mirrored in localStorage under cart. Stored cart fields include item identifiers, display details, quantity, price, currency, and update time.
  • Catalog cart-panel state, a legacy sort preference, and article-like state use localStorage.
  • The navbar query draft and selected game use namespaced sessionStorage for the current browser tab.
  • Deckbuilder and play screens can store a temporary deck payload in sessionStorage and deck identifiers or names, matchmaking time, a 3D preload preference, and arena tuning values in localStorage.

Cart, checkout, and payment processing

  • The cart can be synchronized with the ShootStrayt backend. The cart-sync request can include the submitted cart body and available cookie or authorization headers.
  • Checkout submits its request through the existing ShootStrayt checkout flow.
  • When a valid Stripe publishable key and client secret are available, checkout mounts Stripe Payment Element. Payment confirmation uses Stripe’s client API and returns to the ShootStrayt order-status route.

Analytics

The site loads a proxied Plausible script for automatic page tracking on shootstrayt.com. Cross-subdomain tracking is configured, and the admin path is excluded.

Contact

Questions about this policy can be sent to support@shootstrayt.com.