Before you write
Tell us the product, account and request type.
That gives ClientAhead enough context to find the right record, confirm who controls it and protect everyone from an unauthorized disclosure.
1. Scope and roles
You may contact ClientAhead about your own information, information you provided to us, or information handled through a ClientAhead product. Authorized business users may also make requests about their organization’s account or product data.
Where a ClientAhead customer uses a product to manage information about its own customers, contacts or team, that customer generally controls the purpose of the information. ClientAhead will work with the customer where needed to process a request accurately and securely.
2. How to submit a request
Email the privacy contact shown on this page. Use a clear subject such as Data request, Correct my data or Delete my data. Include your name, the ClientAhead product or service involved, the relevant business or account if known, the request you are making and any information that helps us locate the record.
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. 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 ClientAhead product or connected service uses information.
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 instruction from the customer that controls the data.
4. 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 an associated email address, account authentication, business-domain confirmation or a request from the organization that controls the information.
We will not disclose information to an unverified requester. If we cannot verify a request safely, we may ask for more information or decline it and explain why.
5. How we respond
We acknowledge and assess requests as soon as reasonably possible, then respond within the period required by applicable law and any relevant platform 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.
Some products may offer account-level privacy controls or exports for authorized users. Those controls complement this contact route; they do not remove the need to verify the requester or protect another person’s information.
6. Business and individual data
For an organization’s account, configuration or operational data, an authorized administrator can usually make a request directly. For information about an individual handled by a ClientAhead customer, the customer may be the best first contact because it knows the purpose of the data and can verify the relationship.
ClientAhead will work with the customer where required or appropriate. For information ClientAhead controls directly, such as a website inquiry or support email, ClientAhead can handle the request directly after verification.
7. Connected platforms
A product can sometimes rely on an ecommerce, calendar, advertising, communication, social or other connected platform. A platform may have its own deletion or data-request route in addition to ClientAhead’s process. The relevant product or connection notice will explain how to disconnect the service and where a request should begin.
Where a platform requires a technical data-deletion callback or compliance workflow, the affected ClientAhead product must provide that workflow. A static policy page explains the process; it does not replace the product controls or platform endpoints required to carry it out.
8. Deletion and retention limits
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.
When a product has a particular retention schedule or deletion path, it will be described in that product’s notice or help documentation. We will not promise a deletion timeframe that our systems and providers cannot actually meet.
9. Questions and complaints
If you have a question about a privacy request, reply to the email thread so we can keep the relevant context together. If you believe we have handled a request incorrectly, tell us why and include the product or service involved so we can review it.
Depending on where you live, you may also have a right to complain to a data-protection authority. We encourage you to contact ClientAhead first so we can try to resolve the issue directly.
10. Changes and contact
We may update this request process when ClientAhead products, 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 or service and account context whenever possible.