Privacy Policy

Effective date: July 25, 2026

Provider: Austin Sonoma Holdings, LLC ("we", "us"), developer of the ClaimTag Shopify app ("the App").

1. Scope

This policy explains what data the App accesses, stores, and shares when a merchant installs it on their Shopify store. It covers two groups:

• Merchants — the Shopify store owner and staff who install and use the App.
• Repair customers — the merchant's own customers, whose details the merchant records when they drop off an item for repair.

Shopify is the system of record for orders, payments, and customer accounts. The App stores only the repair-workflow data described below.

2. What we collect

From the merchant / their Shopify store:

• Store domain and the Shopify session/access token needed to run the App.
• Store settings you configure: business name, ticket numbering, pipeline statuses, notification templates, logo, and accent color.

Repair-ticket data the merchant enters or captures:

• Repair customer contact details: name, email address, phone number, and the linked Shopify customer ID when one is selected.
• Item and job details: description, problem reported, serial/IMEI number, condition at drop-off, included accessories, and internal notes.
• Photos of the item, captured at intake.
• Estimates and their approval history, including the name the customer types to approve or decline, and the IP address and browser/device user-agent recorded at the moment of that decision.
• Money and order references: deposit and balance amounts and the Shopify order IDs they map to.
• Whether the customer opted in to SMS updates, and a message-delivery log for each notification we attempt (recipient and delivery state).
• An append-only audit history of ticket changes.

Automatically: when a repair customer opens their status page, we record the time of that view. Status-page links are unguessable and are not indexed by search engines.

We do not collect payment card numbers — payments are handled entirely by Shopify. We do not use this data for advertising, and we do not sell it.

3. How we use it

Only to operate the repair workflow: create and track tickets, produce estimates and record approvals, print claim tags, send status and estimate notifications by email and SMS, show delivery proof, maintain the audit history, and provide backups and data export. We subscribe to the orders/paid webhook solely to advance a ticket's status when its deposit or balance is paid.

4. Who we share it with (subprocessors)

We share data only with these providers to deliver the service, or where required by law. Mobile phone numbers are never sold or shared with third parties for their own marketing.

5. Storage, location, and security

Data is stored on Cloudflare's infrastructure. Access tokens are held encrypted and are never placed in source code. Photos and nightly backups are stored in private object storage that is not publicly reachable. We keep an append-only audit log and run idempotent writes to prevent silent data loss.

6. Retention and deletion

• Merchant-initiated: merchants can export all ticket, audit, and message data as CSV at any time from the App's settings.
• Customer data request (customers/data_request): the merchant fulfills the request; everything we hold for a repair customer is visible on their tickets in the App.
• Customer redaction (customers/redact): we remove that customer's personal fields from their tickets. The de-identified repair record is retained.
• Shop redaction / uninstall (shop/redact): when the App is uninstalled we delete all data held for that store. We never hold data hostage.

7. Data-subject rights

Repair customers should direct requests to access, correct, or delete their data to the merchant they did business with, who controls that data. We support the merchant in fulfilling those requests through the mechanisms in Section 6.

8. International transfers

Data may be processed in countries other than where the customer is located, including via the providers listed in Section 4. We rely on those providers' safeguards for cross-border transfers.

9. Changes to this policy

If we change how the App handles data, we will update this policy and its effective date. Material changes will be noted in the App's release notes — we do not make silent changes.

10. Governing law

This policy is governed by the laws of the State of Colorado, United States, without regard to its conflict-of-laws rules.

11. Contact

Questions about this policy or your data: support@claimtag.app (Austin Sonoma Holdings, LLC, Denver, Colorado, USA).