Treez data disclosure

In this article we'll talk through all the data we access and sync through your Treez integration

TABLE OF CONTENTS

• What does Appature Access?
• What data does Appature store?

What does Appature Access?

By providing Appature with an API key to your dispensary, we are able to access much of your dispensary info. Please note this is information that we will have ACCESS to, but much of this data either does not get synced and stored on our database, is anonymized before its stored, or gets transformed in a way that effectively anonymizes it. Below is what we have access to; further below you can see how we handle the data:

• Customer information, including:
  •  Names
  • Address(es)
  • Reward balance
  •  Order history
• Product information, including:
  • Basic product information like name, category, price, and ecommerce menu settings
  • Barcode and SKU Information
  • Product quantities and their location
  • Lab results associated with those items
• Ticket / order information, including
  • Basic ticket info like customer, total amount, date and time
  • Method of payment
  • Discounts applied and rewards issued
  • products in the ticket including their amount, quantity
• General dispensary information, including
  • Name of dispensary
  • Total sales
  • Employee names
  • Customer groups
  • Discounts

What data does Appature store?

While Appature will have access to the above information, we will not store all of it. Below is the information Appature actually stores. Any transformations of data will be noted:

• Products:
  • ALL product information (name, category, price, ecommerce settings, lab results, etc)
• Tickets 
  • ALL ticket information EXCEPT:
    • Any identifying customer information like customer name or delivery address
    • Any detailed payment information beyond amount and method (i.e. no card numbers)
• Customers:
  • No specific customer information will be kept. The only customer information to be kept will be:
    • General age (age brackets will be calculated based on birthday)
    • Gender
    • Customer ID (for purposes of being able to identify unique customers)