Before you write
Tell us the product, store and request type.
That lets us route a privacy request to the right product workflow, confirm who controls the information and protect everyone from an unauthorized disclosure.
1. Who can make a request
You may contact ClientAhead about your own information, information you provided to us by email, or information handled by a ClientAhead product. Merchant administrators may make requests about their store or team data. A booking customer or supplier contact may also contact us, but the merchant that collected or entered the information usually controls the purpose of that data.
If you are acting for someone else, a business or a Shopify store, include evidence that you are authorized to do so. We may direct you to the merchant where that is the most accurate and secure way to process the request.
2. How to submit a request
Email the privacy contact shown on this page. Use a clear subject such as Data request, Data correction or Delete my data. Include your name, contact method, the ClientAhead product involved, the relevant Shopify store or merchant name if known, the type of request and any details that help locate the information.
Please do not include passwords, payment-card information, API keys or unnecessary sensitive information in the request. If a secure follow-up is needed, we will tell you how to provide it.
3. Merchant and individual roles
For Bookimatic booking information and Recoup supplier or claim information, the merchant is generally the party that decides why the information is collected and used. ClientAhead processes that information to provide the app. We will work with the merchant where needed to verify the request, identify the record and determine the correct response.
For data that ClientAhead controls directly, such as an email inquiry or website contact record, ClientAhead can handle the request directly once identity is verified.
4. What you can request
Subject to applicable law and the information involved, you may ask to:
- know whether we process information about you and receive access to it;
- correct incomplete or inaccurate information;
- delete information that no longer needs to be retained;
- restrict or object to certain processing;
- receive a portable copy where that right applies; or
- ask how a product uses a connected service or AI-assisted workflow.
These rights are not absolute. We may need to retain limited information for legal obligations, security, fraud prevention, financial or audit records, dispute resolution or a valid merchant instruction.
5. Identity and authority checks
Before we disclose, export, correct or delete information, we verify that the requester is the person concerned or has valid authority. Depending on the request, this can include confirmation from the email address associated with the merchant account, Shopify administrator authentication, store-domain confirmation or a request from the merchant that controls the data.
We will not disclose customer, supplier or merchant information to an unverified requester. If we cannot verify a request safely, we may ask for more information or decline it and explain why.
6. How we respond
We acknowledge and assess requests as soon as reasonably possible, then respond within the period required by applicable law and any applicable Shopify compliance process. We will explain what we can do, what we need from you, and any lawful reason that prevents a full request from being completed.
ClientAhead does not currently provide an anonymous public self-service download or deletion portal. Bookimatic privacy exports are temporary and available only to an authenticated merchant administrator. This protects merchant, customer and supplier information from an unauthorized request.
7. Shopify privacy requests
Shopify provides compliance-webhook processes for customer data requests, customer redaction and shop redaction. Bookimatic has registered those product workflows and processes the relevant request through its authenticated merchant and privacy controls.
A customer may also begin with the Shopify merchant that collected their information. The merchant can use the appropriate Shopify process or contact ClientAhead with the store context. This helps ensure that the request reaches the processor and product that actually hold the relevant record.
8. Product-specific boundaries
Bookimatic: may handle booking contact, intake, conversation, waitlist, delivery and merchant configuration information. Its customer-redaction workflow removes or redacts the relevant contact, intake, conversation, waitlist and delivery details, and queues required Calendar cleanup where an optional Calendar connection is involved. Limited compliance records can remain.
Recoup: is an early pilot ledger. Its current Shopify scope is limited to read-only product data for claim line items; it does not intentionally request customer, order, payment or checkout data. It can contain supplier contact details and merchant-entered free text. Recoup’s automated Shopify data-request, redaction and shop-deletion process is not yet complete, so Recoup is not ready for public App Store distribution. Pilot participants can email ClientAhead for a manual record review or deletion request.
9. Retention exceptions
Deleting or redacting personal information does not always remove every record instantly. We may retain limited information where required for legal obligations, security, fraud prevention, financial or audit records, resolving a dispute, preserving a compliance receipt or maintaining an allowed backup lifecycle.
Bookimatic applies product retention rules to chat, delivery, booking and privacy-export data. Recoup does not yet publish a fixed automated post-uninstall deletion schedule. We will state a consistent Recoup retention schedule and implement the required privacy workflow before public distribution.
10. Changes and contact
We may update this request process when a product’s privacy controls, integrations or legal requirements change. The latest version will be published here with a new last-updated date.
Use the email contact shown on this page to start a request or ask a privacy question. Include the product and store context whenever possible.