Chuganation's 3D Lab Data Privacy Policy

The following outline provides a comprehensive discription of how our lab collects data, utilizes it to provide a great experience for you, and other data related activities. Unless otherwise specified, the data practices below apply to our android, iOS, and web platform applications.

Last Ammended April 15th, 2024 at 8:12 A.M. CT

Payment Data Policy

Stripe handles the creation and management of payment information. See their privacy policy here.

Data Collection Policy - Analytics and Profile Data

You agree to be bound not only by Chuganation's 3D Lab data and privacy policy, but also our business partners privacy policies. See Stripes privacy policy here.

When stated below, "Software" and "Application" are interchangeably used to reference the software platform that our customers visit.

Our lab collects data about how customers browse and interact with the platform. This includes data about which products our customers are viewing and which pages our customers are visiting. This data is not linked to customer accounts and is collected anonymously. This data contains the following properties at some point in the process flow on any mix of our platforms:

  • General Properties
    • Item ID (Product ID, Category ID, Page ID, ScreenID)
    • Item Name (Product Name, Category Name, Page Name, ScreenName)
  • Geographical Data
    • City - The city in which the event took place.
    • Country - The city in which the event view took place.
    • Region - The Region or State in which the event view took place.
  • Platform / Device
    • App Version - The software version of the application the event originated from.
    • Browser - The browser which loaded the website that the event originated from.
    • Device Category - Determines which category of device was used. Typically falls under the 'mobile', 'tablet', or 'web' categories.
    • Language - The language by which the software attempted to render the content as.
    • Device Brand - The brand of device in which the platform was loaded ontowhen the event was originated.
    • Device - A general descriptor (typically the model) of the device in which the platform was loaded onto when the event was originated.
    • Device Model - The model of the device in which the platform was loaded onto when the event was originated.
    • Operating System - The operating system in which the platform was loaded onto when the event was originated.
    • OS With Version - The operating system and the operating system version in which the platform was loaded onto when the event was originated.
    • Platform - Defines a general platform (E.X. iOS or Android) in which the platform was loaded onto when the event was originated.
    • Screen Resolution - Defines the screen size of the environment in which the platform was loaded onto when the event was originated.
    • Stream Name - A descriptor of the name of the software that the event originated from.
    • Language Code - The language code by which the software attempted to render the content as.
  • Date and Time
    • Year
    • Day
    • Month
    • Week
    • Hour

Data Storage Policy - Profiles

We store customer data on a single hosted server which all platforms contact. Customer profiles will be stored with the following data tied to each:

  • Order Generation
    • Abort Reason - The reason by which the customers order failed to generate.
    • Checkout Session ID - An identifier created by Stripe to identify the checkout session.
    • Checkout URL - The url by which the customer is to provide payment for the order with. This is generated by Stripe and references a checkout page hosted by Stripe.
    • Flags for checkout generation - There are three true/false flags that the platform handles order generation around.
  • Cart
    • Cart - A list of prices that a customer has in their cart. The platform knows how to represent these prices by products to the customer.
    • Cart Time - The last date and time that the cart was generated.
  • Stripe
    • Each profile will have the customers' stripe id associated with it in the profiles data. This ID is the customers form of identification to the Stripe platform.
  • Emails and Notifications
    • Enrollments in email programs are store within customer profiles as true/false flags.
    • Enrollments in notification programs are store within customer profiles in the form of a token list.
    • Device token for notifications are stored on the customers profile while signed into the application and the notifications permission is allowed on the device.

Data Storage Policy - Authentication Providers

The following data is stored via a customers authentication provider.

  • Guest (Anonymous)
    • -No data is stored via this provider.
  • Apple
    • Email Address
    • Display Name
  • Google
    • Email Address
    • Account Image
    • Display Name

Data Storage Policy - Orders

Each order contains the following

  • Customer name (display name) (If declared by the auth provider)
  • Customer email (If declared by the auth provider)
  • The stripe identifier of the payment that is expected.
  • A list of ordered products, and data related to those products such as price, and identity are attached to the order.
  • Notes
  • URL by which payment can be made
  • Shipment Information about the order including
    • Estimated or Approximate Delivery Date
    • Tracking link for the shipment
    • Shipping method used (if available)
    • Tracking number for the shipment (if available)
    • Shipping provider used (if available)
  • Status of the order.