Building a business
Why I Consider the Doppel and Cloudflare Takedown Process Abusive
A disputed phishing report disrupted my work at Bear Trail Works. Days after Doppel said it was working with Cloudflare toward reinstatement, I still have no substantive update, clear case owner, or restoration timeline.
I build software at Bear Trail Works. Over the past week, I have spent time disputing a phishing allegation, assembling evidence, and asking two companies who can actually resolve a restriction affecting my work.
The companies are Doppel and Cloudflare. The site is abogados.beartrailworks.com.
I consider the way this process has been handled abusive. A report can lead to a restriction with immediate consequences for a small business, while the person affected is left asking for evidence, an accountable reviewer, and a date when something will happen.
Here is what has happened in my case, and what I believe needs to change.
What happened
By October 5, I was disputing a report attributed to Doppel that alleged my site impersonated Morgan & Morgan, P.A. I contacted both Doppel and Cloudflare about the block and asked for human review, the specific content behind the allegation, screenshots, and the relevant URLs.
That day, I also submitted supporting material. It included locally reconstructed versions of earlier Nube Privada sign-in screens and notes about the available commit and deployment history. The inspected screens did not show Morgan & Morgan branding, an affiliation claim, or payment fields.
There is an important limitation here: those images were reconstructions. I could not establish an exact match to the historical deployment. I disclosed that limitation in the submission. The later Bóveda Legal branding was added after the report, so I did not present it as evidence of what was online when the report was made.
That is why I asked Doppel for its original capture, timestamp, exact URL, and supporting evidence. A meaningful review needs to compare the actual allegation with the relevant version of the site.
On October 6, Doppel replied: “We are working with Cloudflare to have your page reinstated.” They also said the hourly emails would not speed things up and asked for time to work through the process. I stopped the automated follow-ups to their team.
That response gave me a reason to expect progress. It did not confirm that the report had been withdrawn or that Cloudflare had approved restoration.
I followed up on October 7 and October 8, asking what remained pending, who was responsible, and when I could expect restoration or a substantive update. Cloudflare's October 8 response was an automated acknowledgement requesting a reference number and a summary. I supplied both.
On October 12, I followed up with both companies again. As of October 12, 2026, I have received no further substantive update since Doppel's October 6 message. I still do not have confirmation of a withdrawal or correction, a clear case owner, or a restoration timeline.
The scope also needs an answer
I separately reported a problem activating another subdomain under beartrailworks.com. My correspondence documented a Cloudflare Pages message saying that the hostname was part of a banned domain and could not be added.
I asked Cloudflare to explain the scope and basis of that restriction and whether it was connected to the disputed phishing report. The panel did not identify the originating report. I do not have confirmation that these two problems share the same cause.
That uncertainty matters. I need to know which properties are affected and what is required to restore normal operation. Without that information, even planning the next technical step becomes harder.
Why I call this abusive
The power imbalance is substantial. Doppel can submit a report. Cloudflare can enforce a restriction. I have to keep the business moving while trying to learn what evidence was used, where the review stands, and which team owns the next action.
I have already told both companies that the disruption affects my work and client access. For a small software business, time spent reconstructing deployments and chasing status is time taken away from building and supporting software. Uncertainty also makes it harder to give clients a useful answer.
Security reviews can take time. Mistakes can happen. But a process with this much practical power needs a correction path that the affected person can actually use. An acknowledgement and an open-ended request to wait leave too much of the burden on that person.
My criticism is about that process and its consequences. I cannot see either company's internal investigation. From my side, I have supplied material, explained its limitations, and repeatedly asked concrete questions. Those questions still need concrete answers.
What a fair process should provide
I am asking Doppel and Cloudflare for five things:
- The evidence behind the allegation. Identify the exact URL, capture time, and specific content considered impersonation.
- A responsible reviewer or team. Make it clear who owns the case and the next step between the two companies.
- The scope of the restriction. Explain what is affected, why, and whether the separate subdomain activation problem is related.
- A usable timeline. Give a realistic review or restoration estimate. If that is not possible, give a date for the next substantive update.
- A documented correction path. If the report cannot be substantiated, withdraw or correct it, communicate that to Cloudflare, and confirm what must happen for restoration.
These are basic expectations when a company's decision interrupts someone else's work. The ability to impose a restriction should come with responsibility for explaining it, reviewing it, and correcting it promptly when warranted.
Bear Trail Works should not have to keep asking who is responsible for the next step. Doppel and Cloudflare need to answer that question and bring this case to a clear resolution.