Kalibrate Opt Out: Privacy Email and Intalytics Requests

To opt out of Kalibrate data use or request deletion, email privacy@kalibrate.com and state the relevant privacy right and record. Kalibrate's policy uses that contact for group requests, including questions involving Intalytics and eSite Analytics.

Identify the entity and interaction when you can. The policy says it tries to respond to legitimate requests within one month, while its California section separately describes a 15-day sale-opt-out period.

Identify the Kalibrate entity holding your information

Kalibrate's privacy policy names separate controllers for the three group websites: Kalibrate Technologies Ltd, eSite Analytics and Intalytics. It also says a relevant group entity may act as controller or processor for information obtained through vendors, partners or customers.

The shared contact makes one practical starting point. It does not make every group company the same legal controller. Include the product, website or business relationship connected to your concern and ask which entity is responsible if you are unsure. The broader data broker removal process explains how that identification helps prevent requests being sent to the wrong holder.

Step 1: Prepare a focused email request

Use the privacy contact published in the current policy: privacy@kalibrate.com. A subject such as “Privacy request – deletion and applicable sale opt-out” helps state the action without putting unnecessary identifiers into the subject line. Use an email address you can monitor for a reply.

Identify your name, residence jurisdiction and the relevant relationship or record. If a message or business interaction reveals a specific group entity, mention it. If you are requesting correction, describe the inaccurate category rather than attaching a broad collection of personal documents.

The policy does not prescribe one mandatory email template or list of identity documents for every request. Start with enough information to explain and match the issue, then let the company specify any justified verification requirement. Do not include payment data, a national identification number or unrelated household information by default.

Step 2: Separate deletion, opt-out and objection

A request can ask for more than one applicable action, but the actions should be named separately. Deletion concerns existing personal information. A sale opt-out concerns future sales covered by the relevant right. An objection to direct marketing addresses that particular processing purpose.

For example, ask Kalibrate to identify the responsible entity, delete eligible personal information, apply an applicable sale opt-out and explain any retained exceptions. Ask it to confirm which actions were completed. This wording is a practical structure, not a claim that every person has every right in every jurisdiction.

If you are investigating a business contact list, compare the scope with the Buxton opt-out guide only when Buxton is another identified holder. Analytics companies can use different data sources and matching methods. One company's response cannot establish another company's deletion.

Step 3: Handle verification without oversharing

Kalibrate says it may request information to confirm your identity and your right to make the request. Its California section describes matching information already on file or contacting you through a previously supplied method, such as phone or email. It may use another verification method depending on the circumstances.

Check that a follow-up relates to your original request. If it asks for sensitive evidence, ask why it is needed and how to provide it securely. A message that appears to come from a privacy team should not automatically receive every document it asks for without that context.

The policy says information supplied for verification is used for that purpose, and additional verification information is deleted when verification is complete. That statement does not mean all other records disappear at the same time. Read the final response for the separate deletion or opt-out outcome.

• Save your sent message and any acknowledgement.
• Record a case identifier if one is provided.
• Track outstanding verification separately from the substantive decision.
• Ask which entity is responding when the group relationship is unclear.

Understand the published timing

The general policy says Kalibrate tries to respond to legitimate requests within one month. Complex requests or multiple requests can take longer, and it says it will notify you and keep you updated. This is a response statement, not evidence that every request finishes in a month.

In its California section, the policy says future-sale opt-outs are acted on as soon as feasible and no later than 15 days after submission. Keep that specific scope attached to the figure. Do not apply it to every deletion request, other jurisdiction or separate controller.

If the relevant response period passes without a useful update, reply in the original thread with the submission date and case identifier. Ask whether verification is complete, which actions are pending and when the next response is expected. The data broker opt-out directory can help maintain a separate log for each company.

What deletion may leave behind

Kalibrate's policy describes exceptions to erasure, including legal obligations and other permitted processing. It also says deidentified consumer information need not be provided or deleted in response to a consumer request, and it need not reidentify data simply to verify that request.

That matters for analytics. A report about an area, a modeled audience or an aggregate business measure may not be a retrievable personal profile. Ask whether Kalibrate can match a record to you and what action applies. Do not assume a request removes every derived model, business report or historical aggregate.

The policy distinguishes controller and processor roles. If another customer controls a record, ask where to direct the request and what Kalibrate can do under that arrangement. A reply that refers you to a controller is a routing outcome, not confirmation that every copy has been erased.

Reappearance and your next check

New interactions and later data supplied by partners or customers can create new records. Ask whether an opt-out applies to future matching information and whether a limited preference record remains. Do not treat a single response as indefinite removal from every analytics source.

Where a different location-data source is identified, the Foursquare opt-out guide describes that separate provider's controls. The opt-out guide hub groups other company-specific routes without implying that those companies share your particular data.

A privacy scan can help check supported public exposure. It does not inspect Kalibrate's internal systems or prove the absence of nonpublic analytics information. Keep the company's response and any independent public checks as separate evidence.

Frequently asked questions

Do Intalytics and Kalibrate need two identical requests?

The policy supplies a shared privacy contact while naming different entities. Begin with one clear request identifying the relevant entity and ask whether another controller needs a separate request. Avoid unnecessary duplicate submissions.

Is email unsubscribe enough to delete all my information?

It addresses marketing messages. Deletion, sale opt-out and other privacy rights should be requested explicitly through the policy's privacy contact.

Is the 15-day figure a promise that deletion is finished?

No. The policy places it in the California future-sale opt-out section. Its broader response statement and deletion exceptions must be read separately.

Can I request deletion of an aggregate report about my neighborhood?

You can ask about identifiable information and your applicable rights. The policy distinguishes deidentified information, and the existence of an aggregate report does not establish a personal record that can be deleted.

Sources and review scope

Kalibrate's live privacy policy and published privacy email were checked November 14, 2026. The review inspected the controller, rights, timing and verification language without sending a request or measuring removal results. The screenshot records the public source, not a completed deletion. This guide is practical information rather than individualized legal guidance.