When a directory appears not to respond, start by verifying the correspondence before sending another request. The original message may have gone to the wrong contact, a clarification may be waiting in another folder or a provider may have received an answer you have not seen. Silence needs to be established, not assumed.
Once the record is clear, check the applicable response framework and prepare a concise follow-up. A response and the removal you hoped for remain different outcomes. The purpose of organizing the case is to make the next step proportionate and well supported, whether you continue directly, seek assistance or examine an authority route.
Verify where and when the request was sent
Find the original sent message or form confirmation. Record the destination, date, relevant URLs and substance of the request. If you used a form without receiving a copy, save whatever reference or confirmation was displayed and reconstruct the facts accurately. Do not claim delivery based solely on remembering that you started a form.
Check the recipient against the site's current privacy or rights information. A general sales address, an outdated help article and an actual rights contact are different channels. If you used the wrong one, acknowledge that and locate the verified route. Do not assume the clock for a particular legal request began merely because an unrelated department received a message.
Review technical delivery information available to you. A bounce, failed upload or unfinished form may explain the absence of a reply. Preserve those messages rather than deleting them to simplify the chronology. If the publisher's current contact method differs from the one originally used, note that uncertainty and ask for appropriate routing.
Where someone acted for you, request the submission reference and who receives replies. A provider's status saying “sent” should be connected to a particular action. You need enough evidence to establish what happened, not access to every internal system. Confirm whether the request included the necessary page details and a usable reply address before treating the lack of a substantive answer as an unexplained refusal to engage.
If the original request mentioned several sites, confirm that each intended recipient received a message concerning its own publication. A copied address or shared thread does not establish that every organization accepted responsibility for the whole list. Separate the publisher entries and record delivery individually. This matters especially when one organization replied and another did not: the answer from the first should not accidentally close the second in your tracking sheet. A simple recipient-to-URL mapping can reveal a gap before any escalation is considered.
Look for a missed request for clarification
Search the mailbox used for the request, including spam and archived threads. Check for the domain, case reference and sender variations. If the form used a different email address from the one you normally read, inspect that account through its ordinary authorized access. A message can exist without appearing in your main inbox.
Read any reply for what it asks. A request for a URL, company identifier or identity clarification is not the same as silence. Nor is it necessarily a refusal. Record the question and decide what information is relevant before answering. Our guide to directory responses explains those distinctions.
If you supplied further information, keep the date and reference. Do not lose the connection between the supplement and the original request. If a publisher says it cannot identify the page, sending the exact URL in the same thread may be more useful than preparing a new long letter.
Be careful with identity requests. Verify the sender and channel before sharing documents, particularly where an unexpected message follows a public enquiry. Ask for clarification if the purpose or required information is unclear. The goal is to resolve a genuine missing fact without making unnecessary disclosures. If no relevant response exists after these checks, you can describe the situation as no response found as of a stated date, supported by a reliable correspondence record.
Check the applicable response period and its limits
For requests exercising GDPR rights, Article 12 sets an in-principle one-month response framework, with qualifying extensions and related information requirements. Consult the official regulation and applicable authority guidance before applying it to your circumstances. Do not turn that framework into a guaranteed removal date.
Establish what request was actually made and received. A broad customer-service enquiry may not match the rights request you now believe you submitted. A subsequent clarification, representation question or source referral may also need examination. Avoid calculating an alleged breach from a date without checking the relevant facts and framework.
The European Commission's guidance on handling requests distinguishes replies from the substantive treatment of different rights. A publisher can respond without agreeing to your preferred action. Conversely, a source change you discover does not necessarily explain why the correspondence was unanswered.
If uncertain, write down the known dates and ask the competent source to clarify rather than inventing a shorter deadline. A contractual update promised by your provider is another matter: it concerns the service agreement, not the directory's legal response framework. Keeping those timelines separate helps you ask the right organization the right question. It also prevents an administrative reminder from becoming an unsupported accusation about a legal obligation.
Prepare a short follow-up that advances the record
Use the existing reference and thread where appropriate. Identify the original date, exact page and requested action. State that you have not found a substantive answer or that a particular question remains unresolved. Ask for the status and the appropriate next step without rewriting the whole history.
Include only relevant information. If the first message lacked the URL, supply it. If no new evidence exists, do not attach a larger collection merely to make the follow-up appear more serious. A repeat identity document may create exposure without helping the recipient locate the request.
A fictional former director sent a correction request concerning one role label. After confirming delivery and checking for missed messages, the director follows up with the case reference, the affected URL and the same focused question. This is different from sending unrelated erasure demands through several addresses. The focused version preserves a usable record and makes the outstanding issue easier to identify.
Avoid several parallel follow-ups that omit earlier references. They can fragment the record and create ambiguity about whether a reply addresses the latest request or another version. If you must change channel because the original one failed, explain the reason and retain the link to the earlier attempt. Keep a copy of the reminder and note any acknowledgment separately from a substantive response or observed page change.
Organize what comes next
Maintain a chronology with evidence references: original request, delivery information, any clarification, follow-up and current observation of the page. Use a status such as “no substantive response located as of this check” rather than treating silence as approval, refusal or proof that the data was erased.
Verify the next route through the relevant authority for the country and issue. A Belgian directory case should not automatically follow a French complaint template. If a complaint or specialist review is appropriate, a concise record will help explain what was requested and which correspondence is missing. Do not assume that escalation guarantees the desired source change.
If paying someone to take over, ask what additional work the service will perform. It should review your existing record and define the follow-up rather than restart automatically. Agree a stopping point and final deliverable so the case does not remain indefinitely marked pending without a clear responsibility.
The directory-removal service explanation provides context for managed requests, subject to current availability and suitability. You can also continue directly where the route is clear. A useful next decision follows from the verified record: resolve a missing detail, wait within a justified framework, request a substantive answer or seek further guidance. The aim is disciplined progress on the specific unanswered request, not an increasing volume of messages disconnected from the facts.
Related reading: Correcting personal data on Companyweb: how to prepare your request; Lawyer or administrative assistance: who should help with your online data?.
