Use this route when you want to know what personal data Bluekip holds about you, correct a record, or ask for deletion. It covers data connected with football match notes inquiries, club football news questions, fixture requests, support chat and consent choices.
Choose the request that fits
An access request asks for a copy or description of personal data held about you. A correction request points out an inaccurate name, phone number, email address or inquiry detail. A deletion request asks Bluekip to remove personal data that no longer needs to be retained, subject to a lawful reason to keep a limited record.
You do not need to explain your whole history with the publication. State the action clearly. “Access,” “correct” or “delete” in the first line is enough. If your request concerns advertising measurement, mention the identifier or landing context you saw, such as gclid, msclkid or fbclid, without sending a password or identity document.
What to include so the desk can find the record
Send your name and the email address or phone number used in the inquiry when you are comfortable doing so. Add the approximate page or route, such as Contact, support chat, a football fixture notes inquiry or a cookie choice. A short date range or a description of the question can narrow the search.
- The request type: access, correction or deletion.
- The contact detail that may appear in the record.
- The page, chat or inquiry route involved.
- A correction written in the form you want stored, if correction is the request.
Only send what is needed to identify the record. Bluekip does not ask for a passport, driver license, payment detail or a full identity document through this page. If a request creates a real verification concern, the desk may ask a proportionate follow-up question using an existing contact route.
Inquiry and chat data have different traces
An inquiry can contain the fields submitted to the editorial route: name, phone, email, address, kind, notes, spec, consent, source and the page-render time. The server receives the request so the desk can read it and reply. A support chat uses its conversation token and message history; the token can be saved in local storage on your device while the chat is in use.
Cookie choices are stored after you act on the consent interface. Before a visitor allows storage, Consent Mode v2 holds ad_storage, ad_user_data, ad_personalization and analytics_storage as denied. If the visitor declines, those four states are set back to denied. Paid traffic can carry Google Ads gclid, Microsoft Advertising msclkid or Meta Ads fbclid in a landing URL. These details can matter to a request about advertising measurement.
For the broader explanation, read the Privacy Policy and Cookies Policy. Bluekip links to the Microsoft privacy statement for Microsoft's own handling of information. Bluekip does not decide what those platforms retain in their separate systems.
Verification is narrow and purposeful
The desk needs to avoid disclosing one visitor’s information to another person. It will compare the details in the request with the record it can locate. That may mean asking you to confirm an email address, phone number, message detail or chat context already associated with the request. It does not mean collecting a new bundle of identity documents just because a request was made.
If there is no matching record, the response will say so rather than inventing a data set. A deletion request may not erase a minimal record where it is needed to document the request, handle a dispute, protect the service or meet a legal obligation. The desk will explain the boundary in plain words.
Send the request
Email [email protected] with “Bluekip data request” in the subject, or use the contact route on Contact. The supplied operator contact is +1 (918) 555-0678. Written correspondence may be addressed to 131 Station Road, Office 12, Austin, Texas 85402.
Include a reply route, but do not put sensitive material in the first message. The site is inquiry-only. This page does not take payment, create an account or offer a purchase flow, and a data request is not a request for a football report or a binding quote.