.svg)
Last Updated: Sep 2026
Application Data & Functionality
This document supplements the Logbase Privacy Policy and provides detailed information about the application-specific data accessed, processed, and stored by Logbase applications.
Different Logbase applications access and process Shopify store data based on the functionality provided by each application and the features enabled by the Merchant.
The information below describes:
- Data accessed by each application
- Purpose of access
- Purpose of retrieval
- Storage purpose
Where Logbase processes Personal Data on behalf of Merchants as a data processor, such processing is governed by the Logbase Data Processing Addendum (DPA), available at: https://logbase.io/dpa
When a Merchant installs, accesses, or uses one of our applications, Logbase accesses information from the Shopify platform through Shopify APIs as necessary to provide the Services.
Depending on the permissions authorized by the Merchant, the specific application installed, and the features used within the Services, such information may include categories of store data such as:
- Product and catalog information
- Inventory information
- Order information and transaction-related details
- Shipping, delivery, and fulfillment information
- Customer information necessary to provide the functionality of the Services
The specific information accessed varies depending on the application installed and the features enabled by the Merchant. Logbase accesses and processes such information only as necessary to operate, maintain, support, and improve the Services and in accordance with the permissions granted by the Merchant through the Shopify platform. We access Shopify data only after the Merchant authorizes the required permissions during the installation of the application. Unless otherwise stated, Personal Data is stored only for as long as necessary to provide the applicable application functionality and in accordance with our Data Retention Policy.
Selleasy (Upsell & Cross-Sell)
Selleasy generates upsell and cross-sell recommendations, enables merchants to create targeted campaigns based on customer segments, and calculates usage-based billing.
Merchant Data
| Field | Details |
|---|---|
| Purpose of Access: CRM and merchant communication Purpose of Retrieval: To contact merchants and support communication workflows Storage Purpose: Communication and CRM purposes | |
| Phone | Purpose of Access: CRM and merchant communication Purpose of Retrieval: Not retrieved by the application Storage Purpose: Not stored |
| Name | Purpose of Access: CRM and merchant communication Purpose of Retrieval: Not retrieved by the application Storage Purpose: Not stored |
| Address | Purpose of Access: CRM and merchant communication Purpose of Retrieval: Not retrieved by the application Storage Purpose: Not stored |
Merchant Customer Data
| Field | Details |
|---|---|
| Purpose of Access: To receive order webhooks and support customer-targeted campaign creation Purpose of Retrieval: To enable merchants to filter and select customers within the admin panel Storage Purpose: Not stored | |
| Phone | Purpose of Access: Not required Purpose of Retrieval: Not retrieved by the application Storage Purpose: Not stored |
| Name | Purpose of Access: To receive order webhooks and support customer-targeted campaign creation Purpose of Retrieval: To enable merchants to filter and select customers within the admin panel Storage Purpose: Stored temporarily as part of campaign configuration. Not retained in identifiable form after campaign processing. |
| Address | Purpose of Access: Not required Purpose of Retrieval: Not retrieved by the application Storage Purpose: Not stored |
| Order Information | Purpose of Access: To track order volume for subscription billing Purpose of Retrieval: To calculate usage-based billing Storage Purpose: Only aggregated order count is stored to determine billing within a defined period |
Pickeasy (Pickup & Delivery Date)
Pickeasy enables merchants to manage pickup scheduling, delivery slot allocation, order fulfillment workflows, and order-related notifications.
Merchant Data
| Field | Details |
|---|---|
| Purpose of Access: CRM, location management, analytics, and communication Purpose of Retrieval: To manage merchant communication, send order status updates, and support in-app location configuration Storage Purpose: Stored for CRM, communication, and operational management, including notification workflows and system logs | |
| Phone | Purpose of Access: CRM and location management Purpose of Retrieval: To support merchant communication and in-app location configuration Storage Purpose: Stored for CRM and location management |
| Name | Purpose of Access: CRM Purpose of Retrieval: To identify the merchant and support CRM activities Storage Purpose: Stored for CRM purposes |
| Address / Location | Purpose of Access: CRM and location management Purpose of Retrieval: To configure and manage pickup and delivery locations within the application Storage Purpose: Stored to support location setup and operational workflows |
Merchant Customer Data
| Field | Details |
|---|---|
| Purpose of Access: To display order details and send status updates Purpose of Retrieval: To display customer contact details within order views and support communication workflows Storage Purpose: Stored to provide historical visibility in the admin interface and support troubleshooting. | |
| Phone | Purpose of Access: To display order details Purpose of Retrieval: To display customer contact details within order views Storage Purpose: Stored to support historical visibility and troubleshooting |
| Name | Purpose of Access: To display order details Purpose of Retrieval: To display customer contact details within order views Storage Purpose: Stored to support historical visibility and troubleshooting |
| Address | Purpose of Access: To display order details and calculate delivery eligibility Purpose of Retrieval: To determine delivery zones, calculate distance or zipcode-based rules, and apply slot and rate logic Storage Purpose: Stored to support delivery calculations, historical visibility, and troubleshooting |
| Order Information | Purpose of Access: To display order details and support scheduling logic Purpose of Retrieval: To display order information and support slot selection and delivery workflows Storage Purpose: Stored to support processing, historical visibility, and troubleshooting |
ShipX (Shipping Rates)
ShipX calculates shipping rates, manages delivery options, and supports logistics workflows at checkout.
Merchant Data
| Field | Details |
|---|---|
| Purpose of Access: Account management, CRM, analytics, and communication with merchants Purpose of Retrieval: To perform analytics, manage merchant accounts, and send operational updates Storage Purpose: Account management, analytics, and communication | |
| Phone | Purpose of Access: CRM, analytics, and emergency contact Purpose of Retrieval: To support account management, analytics, and communication Storage Purpose: Account management and communication |
| Name | Purpose of Access: CRM and analytics Purpose of Retrieval: To identify the merchant and support CRM and analytics activities Storage Purpose: Account identification and communication |
| Address | Purpose of Access: Analytics and operational context Purpose of Retrieval: To provide contextual insights for analytics Storage Purpose: Not used for core application functionality and not stored for application use. |
Merchant Customer Data
| Field | Details |
|---|---|
| Purpose of Access: Scenario execution Purpose of Retrieval: To evaluate conditions and execute application logic Storage Purpose: Historical visibility and troubleshooting | |
| Phone | Purpose of Access: Scenario execution Purpose of Retrieval: To evaluate conditions and execute application logic Storage Purpose: Historical visibility and troubleshooting |
| Name | Purpose of Access: Scenario execution and customer identification Purpose of Retrieval: To evaluate conditions and identify the customer (including test scenarios) Storage Purpose: Historical visibility and troubleshooting |
| Address / Location | Purpose of Access: Scenario execution Purpose of Retrieval: To determine the destination shipping zone Storage Purpose: Historical visibility and troubleshooting |
| Order Information | Purpose of Access: Scenario execution and rate calculation Purpose of Retrieval: To validate conditions and calculate shipping rates Storage Purpose: Historical visibility and troubleshooting |
AskTimmy (AI Customer Assistant)
AskTimmy offers human-like AI live chat to automate customer support. It handles customer queries, recommends products, and promotes offers through AI-driven interactions.
AskTimmy processes data solely to provide application functionality. Customer and merchant data, including uploaded content, is not used to train general-purpose AI or machine learning models.
Merchant Data
| Field | Details |
|---|---|
| Purpose of Access: Support identification, CRM, and application notifications Purpose of Retrieval: To identify merchants in support tools, manage communication, and send operational updates Storage Purpose: Stored for merchant identification, communication, and support workflows | |
| Phone | Purpose of Access: Store configuration and location management Purpose of Retrieval: To support store setup and configuration workflows Storage Purpose: Stored as part of store configuration data |
| Name | Purpose of Access: Support identification and store setup Purpose of Retrieval: To identify merchants and support configuration and support workflows Storage Purpose: Stored for merchant identification and configuration |
| Address / Location | Purpose of Access: Store location configuration Purpose of Retrieval: To configure store locations and operational setup Storage Purpose: Stored as part of store configuration data |
Merchant Customer Data
| Field | Details |
|---|---|
| Purpose of Access: Personalization, lead capture, and order lookup Purpose of Retrieval: To identify returning customers, enable order lookups, and capture leads Storage Purpose: Stored as part of conversation history and analytics for merchant review and troubleshooting | |
| Phone | Purpose of Access: Lead capture and chat personalization Purpose of Retrieval: To capture customer contact details for lead generation Storage Purpose: Stored as part of conversation records and lead data |
| Name | Purpose of Access: Chat personalization and customer identification Purpose of Retrieval: To personalize interactions and identify customers Storage Purpose: Stored as part of conversation records and analytics |
| Address | Purpose of Access: Order-related support Purpose of Retrieval: To provide order-related information during customer interactions Storage Purpose: Stored as part of conversation records where required |
| Order Information | Purpose of Access: Order lookup and customer support Purpose of Retrieval: To validate and display order status, fulfillment details, and tracking information Storage Purpose: Stored as part of conversation history and support workflows |
| Customer Uploaded Images (Photo Search) | Purpose of Access: Visual product search Purpose of Retrieval: To extract visual attributes from uploaded images and match against the product catalog Storage Purpose: Stored for processing, search history, and analytics. |
BookX (Booking & Appointment)
BookX enables merchants to manage appointments and service bookings, including scheduling, confirmations, and reminders.
Merchant Data
| Field | Details |
|---|---|
| Purpose of Access: CRM, merchant communication, and support tools integration Purpose of Retrieval: To identify merchants, manage communication, and support CRM workflows Storage Purpose: Stored for merchant identification, communication, and CRM-related activities | |
| Phone | Purpose of Access: CRM and user analytics Purpose of Retrieval: To support communication and analytics Storage Purpose: Stored for CRM, analytics, and operational communication |
| Name | Purpose of Access: CRM and merchant identification Purpose of Retrieval: To identify merchants and support CRM workflows Storage Purpose: Stored for merchant identification and communication |
| Address | Purpose of Access: CRM and user analytics Purpose of Retrieval: To support analytics and operational context Storage Purpose: Stored for CRM and analytics purposes |
Merchant Customer Data
| Field | Details |
|---|---|
| Purpose of Access: Booking management and communication Purpose of Retrieval: To create and manage bookings and send booking confirmations Storage Purpose: Stored as part of booking records to support application functionality | |
| Phone | Purpose of Access: Booking management and communication Purpose of Retrieval: To display booking details and enable merchant-to-customer communication Storage Purpose: Stored as part of booking records to support application functionality |
| Name | Purpose of Access: Booking management and customer identification Purpose of Retrieval: To display booking details and identify customers Storage Purpose: Stored as part of booking records to support application functionality |
| Address | Purpose of Access: Booking management and customer interaction Purpose of Retrieval: To display booking details and support customer interaction Storage Purpose: Stored as part of booking records to support application functionality |
| Order Information | Purpose of Access: Booking reference and navigation Purpose of Retrieval: To display order or booking identifiers in the UI Storage Purpose: Stored to support navigation and booking reference within the application |
Dealeasy (Volume Discount)
Dealeasy enables merchants to create volume discounts, tiered pricing, product bundle offers, and buy-one-get-one (BOGO) promotions to increase average order value.
Merchant Data
| Field | Details |
|---|---|
| Purpose of Access: Merchant identification, CRM, and support tools integration Purpose of Retrieval: To identify merchants, support communication workflows, and enable CRM-related activities Storage Purpose: Stored to support merchant identification and display within support tools | |
| Phone | Purpose of Access: Analytics and reporting Purpose of Retrieval: Not retrieved or used by the application Storage Purpose: Not stored |
| Name | Purpose of Access: CRM and communication Purpose of Retrieval: Not retrieved or used by the application Storage Purpose: Not stored |
| Address | Purpose of Access: Analytics and reporting Purpose of Retrieval: Not retrieved or used by the application Storage Purpose: Not stored |
Merchant Customer Data
| Field | Details |
|---|---|
| Purpose of Access: To receive order webhooks and support eligibility-based discount logic Purpose of Retrieval: To evaluate customer eligibility for discount rules and display relevant customer details within the application Storage Purpose: Not stored. Used only for real-time processing | |
| Phone | Purpose of Access: Analytics Purpose of Retrieval: Not retrieved or used by the application Storage Purpose: Not stored |
| Name | Purpose of Access: To receive order webhooks and support eligibility-based discount logic Purpose of Retrieval: To evaluate customer eligibility and display customer details within the application Storage Purpose: Not stored. Used only for real-time processing |
| Address | Purpose of Access: Analytics Purpose of Retrieval: Not retrieved or used by the application Storage Purpose: Not stored |
| Order Information | Purpose of Access: To track order volume for analytics and subscription billing Purpose of Retrieval: To support analytics and usage-based billing calculations Storage Purpose: Only limited data (e.g., order ID and country code) is stored in aggregated form for analytics and billing purposes |
Dibs (Preorder)
Dibs enables merchants to manage preorders and backorders for pre-launch and out-of-stock products. It supports features such as partial deposits, "book now, pay later," and automated payment reminders.
Merchant Data
| Field | Details |
|---|---|
| Purpose of Access: Email notifications and CRM Purpose of Retrieval: To send order and payment-related notifications to customers using the configured sender email Storage Purpose: Stored to support notification workflows and display within support tools | |
| Phone | Purpose of Access: Not required for application functionality Purpose of Retrieval: Not retrieved or used by the application Storage Purpose: Not stored |
| Name | Purpose of Access: Email notifications and CRM Purpose of Retrieval: To support notification workflows and merchant identification Storage Purpose: Stored to support notification workflows and display within support tools |
| Address | Purpose of Access: Supporting partial payment configuration Purpose of Retrieval: To determine country-level eligibility for partial payment functionality Storage Purpose: Stored to support configuration and operational validation |
Merchant Customer Data
| Field | Details |
|---|---|
| Purpose of Access: Email notifications Purpose of Retrieval: To send order and payment-related notifications to customers Storage Purpose: Not stored. Used only for real-time notification processing | |
| Phone | Purpose of Access: Not required Purpose of Retrieval: Not retrieved or used by the application Storage Purpose: Not stored |
| Name | Purpose of Access: Not required Purpose of Retrieval: Not retrieved or used by the application Storage Purpose: Not stored |
| Address | Purpose of Access: Not required Purpose of Retrieval: Not retrieved or used by the application Storage Purpose: Not stored |
| Order Information | Purpose of Access: Order management and analytics Purpose of Retrieval: To display preorder and backorder data in the Orders page and support metrics Storage Purpose: Not stored. Used only for real-time processing within the application. |
DecorGenie (Shop Minis)
DecorGenie enables users to visualize room designs by generating outputs based on user-uploaded images and displaying past results for reference.
Data Accessed:
- Uploaded Content: User-uploaded images and generated visualization results.
Storage:
- Uploaded images and generated results are stored to support displaying past visualization history to users.
- No merchant or merchant customer personal data is accessed or stored.
FitGenie (Shop Minis)
FitGenie enables users to generate virtual try-on results using uploaded images and allows users to view their past try-on history.
Data Accessed:
- Uploaded Content: User-uploaded images and generated try-on results.
Storage:
- Uploaded images and generated results are stored to support displaying past try-on history to users. No merchant or merchant customer personal data is accessed or stored.
The data accessed and processed by each application may change as new features are introduced or existing functionality is updated. This document will be updated periodically to reflect material changes in application functionality and data processing practices.
.svg)
.svg)
.svg)
.svg)