Privacy Policy

Trackflow.ai is a standalone software-as-a-service application through which merchants can connect Shopify stores, import orders, manage tracking verification, and maintain related workspace records. The service is designed to support authorized Shopify fulfillment updates after verification, although fulfillment writes, paid tracking purchases, credit spending, and billing are currently inactive.

This policy describes information handled by the Trackflow.ai website, application, and connected workspace. It does not replace a merchant's own privacy policy or the terms between a merchant and its customers. Merchants remain responsible for their authority to provide customer information to Trackflow.ai.

The information handled depends on how you use Trackflow.ai and the permissions you authorize:

Account information

Your name, email address, workspace membership, role, account preferences, and workspace invitation records, including invitation status and related timestamps.

Authentication information

Login and session information, password-authentication records managed by our authentication provider, and Google account information when you choose Google sign-in. Trackflow.ai does not ask for your Google or Shopify account password.

Connected store information

Shopify shop domain, store connection status, authorized permission scopes, installation and synchronization records, and server-side connection credentials.

Shopify order information

Shopify order ID and number, order date, total and currency, fulfillment status, fulfillment-order IDs and statuses, recipient name, and relevant shipping destinations. Where authorized, this may include the customer's shipping city, state or province, ZIP or postal code, and country. The current order-import query does not request street address, customer email or phone, payment-card data, or a customer profile ID.

Tracking and verification information

Tracking candidates or records entered or created in the service, destination-matching results, review decisions, verification history, and related internal job records. An external tracking-data provider is not currently integrated.

Credits and transactions

Workspace credit balances and credit-transaction records. Checkout, paid tracking purchases, credit spending, and payment processing are not currently active; billing records would be collected only if billing is activated.

Technical and security information

Session data, authentication events, synchronization and webhook records, operational and security logs, audit records, and technical request information needed to operate and protect the service. Webhook records may retain the complete received payload, which can contain personal information beyond the fields copied into an order.

We use information for the following purposes, as applicable to the features you use:

• Authenticate users and maintain secure account sessions.
• Create and administer workspaces, memberships, roles, and invitations.
• Connect merchant-authorized Shopify stores and import and manage orders.
• Find and review potentially relevant tracking records using authorized destination information.
• Record shipment verification decisions and maintain verification history.
• Support authorized Shopify fulfillment updates if fulfillment writes are enabled; they are currently inactive.
• Maintain credit wallets and transaction records, and support subscriptions or payments if those features are activated.
• Respond to support requests and communicate about the service.
• Monitor reliability, prevent misuse, investigate incidents, and maintain platform security.
• Meet applicable legal obligations and establish, exercise, or defend legal claims.

Trackflow.ai accesses Shopify data only through the permissions a merchant authorizes during the store connection process. Information is used to provide the application's services, including read-only order synchronization, destination-based tracking review, and workspace administration.

Shopify connection credentials are stored on the server and are not intended to be exposed to the browser. Workspace membership and role-based access controls are used to isolate merchant and customer information between workspaces. Merchants can disconnect their stores through the application.

Customer shipment information is processed only as necessary for authorized services. Matching tracking information to a destination does not, by itself, establish that the tracking record belongs to the actual shipment. A tracking record must be reviewed against the actual shipment before any authorized fulfillment action is taken.

A merchant may receive a Shopify privacy request relating to a customer or store. Depending on the request, the merchant and Trackflow.ai may need to coordinate identity verification, record location, export, or deletion. Request-specific handling is described in the Privacy Rights and Contact sections below.

Trackflow.ai uses the following categories of service providers:

Shopify

When a merchant chooses to connect a store, Shopify provides the store and order information covered by the merchant's authorization and receives API requests needed to provide the authorized service. No real store connection is established until the merchant completes Shopify authorization.

Lovable Cloud and its managed Supabase infrastructure

These services provide application hosting, authentication, database, and related operational infrastructure. They process account, workspace, application, and security information needed to operate Trackflow.ai. Platform error diagnostics may also process technical error information.

Google

If you choose Google sign-in, Google participates in authentication and provides information needed to establish your Trackflow.ai account or session. Trackflow.ai also loads its website fonts from Google, so your browser may send technical request information, such as your IP address, when retrieving them.

No external tracking-data provider or payment processor is currently active, and no separate application-configured invitation-email delivery provider is active. Authentication emails may be delivered through Lovable Cloud's managed authentication infrastructure. We will update this policy before adding a provider that materially changes how information is shared.

Trackflow.ai uses necessary browser storage to support authentication and security. Authentication session information may be stored in browser local storage, and a temporary return destination may be stored in session storage during Google sign-in so you can return to the intended page. The private dashboard also stores its sidebar display preference in a cookie.

No application-configured third-party advertising cookies, marketing pixels, or behavioral analytics technologies were identified in the reviewed code. Optional platform error-monitoring hooks may process error, route, and technical diagnostic information when enabled; their public-deployment availability and retention require confirmation. Dashboard analytics are counts and summaries of a workspace's own application records, not a third-party visitor-analytics service.

Trackflow.ai uses authenticated access, workspace-scoped database policies, server-enforced workspace roles, audit records, and server-only Shopify credential storage. Publicly deployed connections use HTTPS. These safeguards are designed to protect information and limit access to authorized users and workspaces.

No online service can guarantee absolute security. You are responsible for protecting your account access, using appropriate workspace roles, and notifying us about suspected unauthorized access.

Account, workspace, Shopify, tracking, verification, credit-transaction, and audit records are retained for as long as needed to provide the service, maintain security and records, resolve disputes, and meet applicable legal obligations. A fixed retention schedule for each record category has not yet been confirmed and must be established before publication.

Disconnecting a store removes the locally stored connection credentials and stops that connection from being used for future synchronization, but it does not revoke authorization at Shopify or delete historical orders and related records. A merchant may also need to uninstall the app in Shopify. Uninstall and redaction events may remove credentials, stop active work, and redact covered order-destination fields; they do not erase every historical order, webhook payload, tracking record, verification note or evidence item, audit record, or store record. Account deletion and any associated workspace, transaction, or audit-record deletion may require a verified request and may be subject to legal or security exceptions.

The precise deletion timeline, backup-deletion timeline, and any records that must be retained after account closure require confirmation. Do not rely on a specific retention period until those details are published.

Depending on where you live and subject to applicable conditions and exceptions, you may have some or all of the following rights:

• Request access to personal information we hold about you.
• Request correction of inaccurate or incomplete information.
• Request deletion of personal information, subject to applicable exceptions.
• Request a copy or portability of personal information where applicable.
• Object to or restrict certain processing, or withdraw consent where processing relies on consent.
• Appeal or complain about how a privacy request was handled where local law provides that right.

These considerations may be relevant under laws such as the EU or UK General Data Protection Regulation (GDPR) and the California Consumer Privacy Act as amended by the California Privacy Rights Act (CPRA), as well as other privacy laws. Their applicability depends on the circumstances; this policy does not claim automatic compliance with every law.

To exercise a right, contact us using the details below. We may need to verify your identity and authority. If your information relates to a merchant's Shopify store, we may direct you to that merchant or coordinate with the merchant, because the merchant may control the relevant records. You may also have the right to complain to your local data-protection authority.

Trackflow.ai uses hosted infrastructure and service providers. Depending on your location and provider configuration, information may be processed in countries other than the country where you live or where a merchant's store operates. Specific hosting regions, destination countries, and contractual transfer safeguards require confirmation before publication.

Trackflow.ai is a business service and is not directed to children. We do not knowingly intend to collect children's personal information through the service. If you believe a child has provided personal information, contact us so the concern can be reviewed. Merchants should provide only customer information necessary and authorized for the service.

We may update this policy to reflect changes to Trackflow.ai, its service providers, or applicable legal requirements. The latest version will be published on this page with a revised Last Updated date. Where appropriate, we may provide additional notice of material changes.

Questions and privacy requests can be directed to Trackflow.ai using the details below. All bracketed details must be completed and confirmed before publication: