An address remaining online after an Insee request does not identify the cause by itself. The request may still be pending, the remaining page may draw on another source, or you may be looking at an old document or search excerpt. Compare the actual decision with the exact publication before repeating the procedure or paying someone to restart it.
Check what Insee actually processed
Find the original request, acknowledgement and any later confirmation. Record the business identifier, requested change and date. An acknowledgement shows receipt; it does not necessarily establish that the intended status is in effect. Keep these stages separate in your notes.
Read the terminology in current guidance. Insee describes changes between full and partial dissemination in its personal-data dissemination information. Older discussions using “non-diffusion” can lead readers to expect complete disappearance. Use the current scope rather than treating an informal label as a promise.
Check whether the confirmation concerns the correct entity and establishment. If you operate more than one activity or have changed arrangements, a record linked to one identifier should not be assumed to cover every page associated with your name. Where the confirmation is unclear, seek clarification through the official service.
Fictional example: Anaïs receives an automated receipt and immediately searches for her address. The directory is unchanged. Before alleging a failure to update, she needs to establish whether the administrative change has actually been processed. Her receipt and the live status answer different questions.
Do not submit a contradictory new request just to test the system. Preserve what you have and verify the intended status. Repeated changes can make your own timeline harder to understand and do not establish which downstream publication remains unresolved.
Identify the publication that remains
Open the exact URL. Classify it as a live profile, a historical document, another official publication or a search result. Copy the destination address into your inventory. If a result leads to a PDF, record the PDF separately from its parent page.
Compare the content with the information covered by your original request. The remaining address might be presented as a company's registered office rather than a person's residence. It might also be an older address in an incorporation document. These differences matter before attributing the publication to an unchanged Sirene field.
Read the surrounding label and dates. A page can contain accurate historical information next to an inaccurate current panel. The presence of the address somewhere on the site does not tell you which component needs analysis. Record the precise field or document page.
Search excerpts need a source check too. If Google shows the address but the destination no longer does, note the discrepancy. Do not send the publisher a screenshot claiming the current page contains information you have not found there. Explain both observations accurately.
Keep your check bounded and reproducible: URL, date, visible field and relevant source comparison. A new general search can help locate copies, but a case built only on “it still comes up” is difficult for either a publisher or an adviser to investigate.
Compare the sources behind the remaining data
Look at the directory's source explanation, then compare the particular item. Do not assume that a site naming Insee relies only on Insee. Pappers, for example, identifies several public sources in its FAQ. An attached document may follow a different path from a summary field.
Create a table with four columns: remaining URL, information shown, likely or confirmed source, and what your Insee confirmation covers. Where you lack evidence, write “not established.” This distinguishes a suspected propagation problem from a publication outside the change you completed.
Check current official information where available, without downloading unnecessary personal data. If the relevant source already reflects the change while the directory does not, preserve that comparison. If the source still displays the item, the next question may concern scope or a different original record.
Avoid imposing a universal refresh period. A directory may publish general update information, but that is not proof that every field and historical attachment changes on that schedule. Ask about the specific discrepancy rather than promising yourself that all copies must vanish by a particular date.
The source-mapping guide explains how to separate actors. Your purpose here is narrower: establish whether the remaining item is connected to the completed request and what evidence would help the next recipient assess that connection.
Report the discrepancy to the appropriate recipient
If the remaining page is on Pappers and the relevant Insee step has been processed, its FAQ identifies a complaint route for that situation. Use the current route reached from the official site. For another directory, verify its own privacy or correction instructions rather than assuming Pappers' route applies.
Include the URL, field, relevant identifier and concise account of the completed step. State what is still visible and why you believe it relates to that change. Attach only the confirmation or extract necessary to establish the point through the verified channel.
If the item comes from a different official source or a document, ask about that publication specifically. “Insee approved my request” may be useful context, but it does not substitute for explaining why a different record needs assessment. Do not assert that every organisation is bound to delete the same material without checking the applicable scope.
Keep the requested action focused. You might ask for a source check, correction of a field or examination of a remaining address. A complaint combining company financial history, personal address exposure and all Google results can obscure the issue you have already documented.
If a reply identifies a new dependency, add it to the timeline. It may explain why the first request did not resolve the publication. Understanding that dependency is more useful than sending the same letter repeatedly to organisations that control different parts of the data chain.
Preserve replies and verify again
Store the full response, date and reference. Classify it accurately: confirmation, request for evidence, referral to another source or refusal with reasons. Do not reduce every response short of deletion to “nothing happened”; a source explanation can materially change the next step.
Return to the original URL after a reported change. Compare the same field and attachment. Record a dated observation rather than assuming a message saying “updated” covers every component. Check the original search context separately where search visibility was part of the concern.
Use a simple closeout note: what Insee processed, which pages were checked, what changed and what remains. This note is useful if you later delegate the remaining work. It also prevents a new provider from charging to repeat steps that have already been completed.
If the situation involves a disputed interpretation of the official procedure, seek clarification or specialist advice rather than relying on an old forum template. If it is mainly several remaining copies, a targeted directory-assistance scope may be appropriate, subject to the offer available.
You do not need to solve the whole internet before recognising progress. A completed source change and an unresolved document are distinct results. Keeping them distinct lets you choose the next action on evidence, preserve control of the case and avoid mistaking a narrower procedure for universal deletion.
Keep the wording of the Insee confirmation alongside your inventory instead of paraphrasing it from memory. A phrase such as “my details are private now” may imply more than the document says. When asking another organisation to investigate, quote only the short relevant scope and provide the reference through its verified channel. If your interpretation changes after clarification, update the case summary so later requests remain accurate. This avoids building a chain of complaints on an assumption that nobody has checked against the original administrative response.
Related reading: Sirene dissemination status: what changes and what to check next; A free request solved only part of the problem: should you delegate the rest?.
