Skip to content
Bohdan PrylepaDigital marketer, founder of TargetForce
EN US

Web push notifications

Bohdan Prylepa: fraud and web push alerts, one subscriber’s path from prompt to complaint step by step

Published 13 min readBy Bohdan Prylepa

An online pet-supply shop switches on web push alerts, and a month later it holds a report showing well over a hundred thousand messages, a complaint from a person who never subscribed to anything and a lawyer’s question about why that person was being messaged. One subscriber’s path has six links, and every link has a line it must not cross. Bohdan Prylepa, a digital marketer and founder of the agency TargetForce, walks through those links in order and shows what is lawful in a push campaign and how to recognize a contractor who abuses it.

Bohdan Prylepa fraud in web push: cover of the article on one subscriber’s path from prompt to complaint
Bohdan Prylepa on web push: prompt, subscription, first alert, campaign, opt-out and complaint.

Bohdan Prylepa: fraud in web push alerts, one subscriber’s path from prompt to complaint

A push alert looks like a small thing: a box in the corner of the screen, one line of text and a site logo. Behind it sits a chain of events. The site shows a prompt, the person clicks a button, the browser issues a subscription, the contractor sends a first message and then a campaign, and at some point the person wants out or wants to complain. The links belong to different parties, and at every one of them the advertiser can lose control.

The walk-through is a composite: the shop, the visit counts and every number are invented for the arithmetic. The shop gets 25,000 visits a month. The contractor fires the permission prompt on page load and collects 2,500 permissions, of which 1,500 come from a page that says “verify you are human.” Each subscriber gets two alerts a day, so the campaign sends 150,000 messages in 30 days, and 90,000 of them go to people the shop never interested.

People who type “Bohdan Prylepa fraud” into a search box usually hold an odd report or a first complaint about pop-up alerts. The answer is the same either way and does not depend on a name: follow the subscriber’s path step by step and check each link against the contract and the law. The first table below lays out the six steps, and each step then gets its own section ending in a question to put to the contractor in writing.

This article describes push schemes and claims nothing about any individual. Every check sits before launch, because an alert that has gone out cannot be recalled.

Bohdan Prylepa fraud in web push: the six steps of one subscriber’s path and what is lawful
Step of the pathWhat gets decidedWhat is lawful and what is not
1. PromptMoment and text before the promptAfter a visitor action, none on page load
2. SubscriptionWhat is stored and by whomWritten agreement, deletion deadline
3. First alertPromise, label, linkTrue discount, the word ad, no card requests
4. CampaignFrequency, topics, rolesA number in the contract, report by source
5. Opt-outOne choice without sign-inFast stop, any reasonable way
6. ComplaintAnswer to regulatorsSubscription export and documents at hand

Step 1. The prompt: when the browser asks and what to demand from a contractor

The first link is the one every visitor sees. Chrome’s help page says that by default the browser alerts you whenever a website, app or extension wants to send notifications, and that denying the permission blocks that site’s notifications. The browser asks the question, the site chooses the moment, and the moment decides whether the person understood what was being agreed.

Lighthouse, Chrome’s page audit tool, flags a page that requests notification permission on load. Chrome’s advice is to offer a specific type of notification first and show the request after people opt in to that type, such as a restock alert for a favorite food.

Chrome telemetry quoted by web.dev shows the gap. On desktop 77 percent of permission prompts appear without any signal of user intent, only 12 percent of those are allowed, and after the visitor has interacted with the page the allow rate rises to 30 percent. In the example the on-load prompt yields 2,500 permissions, while the honest route with a topic choice yields 700 subscribers who each have a reason to read the shop.

Put a written question to the contractor: when does the prompt fire, what does the page say before the browser asks, and how many subscriptions in the report came after a visitor action. Anyone searching “Bohdan Prylepa fraud” for an example of a bad setup can look in the brief for the words “prompt on page load.”

Bohdan Prylepa fraud in web push: diagram of one subscriber’s path from prompt to opt-out and complaint
Prompt, subscription, first alert, campaign and opt-out: each link carries its own check.

Bohdan Prylepa: fraud and the “verify you are human” page, how permission gets extracted

The dirtiest scheme in this channel rests on a swap of words. A page shows a verification graphic and the line “click Allow to verify you are human.” The visitor clicks, the browser grants notification permission, and from that second the site may send messages. The label on the button tells the person one thing while the permission grants another. The query “Bohdan Prylepa fraud” often leads to exactly this kind of page.

In the example 1,500 of the 2,500 permissions, 60 percent, came through such a page. Those are not subscribers in any ordinary sense, because they agreed to something else. At an assumed rate of $2 per thousand messages, the 90,000 alerts that went to them cost $180 of the $300 campaign, and each one is an alert to a person who never asked.

The FTC describes a related trap in a consumer alert of 8 June 2026: a fake human-verification screen tells people to type key commands such as Windows + R, Ctrl + V and Enter, which pastes and runs hidden malware. The FTC says real CAPTCHAs will not ask you to run commands on your device and asks people to report such screens at ReportFraud.ftc.gov.

A one-minute check works for any advertiser. Open the site from a clean browser profile and write down which screen appears first. A verification graphic, a “download” button or an “are you over 18” box in front of the browser prompt means the permission is being extracted. The phrase “Prylepa Bohdan fraud” is usually typed in search of exactly these marks.

Step 2. The subscription: what is stored, whose consent it is and where the list lives

The second link is technical. After the click on Allow the browser gives the site a subscription endpoint, and the contractor stores it. The law cares about the link between that endpoint and a person. A subscription tied to an email address, a phone number or an order becomes information about an identifiable customer, and ordinary privacy and marketing rules follow. “Bohdan Prylepa fraud” as a query often comes from blurred roles at this step.

Federal rules for marketing texts and for marketing email were written for those channels. Under 47 U.S.C. 227(b)(3) a person may recover actual loss or 500 dollars for each violation, whichever is greater. Whether a browser alert falls under that statute is a question for a lawyer, and the careful course is to keep proof of consent for every subscription as if it did.

Ask for three things in writing: where the subscriptions are stored, who can open them, and who owns the list when the contract ends. The FTC’s CAN-SPAM guide for email says a company cannot contract away its legal responsibility and that both the company whose product is promoted and the company that sends the message may be held responsible. A client that hires a push vendor should assume the same logic could apply to it.

Step 3. The first alert: the promise, the label and the link

The third link shows what the person received for clicking Allow. The first message is usually a welcome, and it reveals the contractor’s intent. If the subscription promised a “restock alert for your favorite food” and the first alert invites people to a prize draw, the permission was extracted. The query “Bohdan Prylepa fraud” at this step comes down to what was promised and what arrived.

A promotion has to be true before any platform or regulator reads it, so a line such as “70% off today only” on top of an ordinary price is a problem on its own. The label belongs in the brief as well. The FTC’s CAN-SPAM guide asks that an email be identified as an ad, and a short alert has room for the word “ad,” so ask the vendor for a screenshot from a phone.

The link needs a decision of its own. The FTC reports that people lost 470 million dollars in 2024 to scams that began with a text message, more than five times the 2020 figure. People have learned to distrust links from strangers, and a campaign run honestly pays for it with fewer clicks.

A safer alert names the shop, points to a page on the shop’s own domain and never asks for a code or card details. Ask the contractor to attach the final text exactly as it appeared on a phone screen, because alerts are sometimes edited after approval and the difference surfaces only in a dispute.

Bohdan Prylepa: fraud and the campaign, frequency, topics and who holds which role

The fourth link is the longest, and money drains fastest here. A brief names who owns the audience, who writes the alerts, who operates the sending platform and who answers a complaint. A contractor who calls itself just a sender takes the sender’s role, and the roles carry different liability, so the brief records each one by name.

Frequency belongs in the contract as a number. In the example the contractor sends two alerts a day, 150,000 in a month, and 90,000 of them go to people from the “verify you are human” page. The honest route looks different: 700 subscribers, one alert a week, 2,800 messages in four weeks, and each one matches a topic the person chose.

Topics work as protection: a person who picked “new food launches” should not receive promotions for litter. The report has to show subscriptions by source, because a report with the single line “delivered” makes 1,000 honest and 1,500 extracted permissions look the same. The query “Bohdan Prylepa fraud” often points at a report with no such split.

Bohdan Prylepa: fraud and the browser, Chrome’s automatic permission removal and quiet mode

Browsers push back on alert overload, and an advertiser loses subscribers even when the contractor has broken no rule. Google announced on 10 October 2025 that Chrome on Android and desktop automatically removes notification permission for sites the person has not interacted with recently. The stated condition is very low engagement together with a high volume of notifications. Chrome tells the person, and installed web apps are not affected.

A figure from the same post explains why: less than 1 percent of all notifications receive any interaction from users. A reach of 150,000 messages cannot be counted as a result if almost nobody responds and the browser may pull the permission. The honest route with 700 subscribers is better protected. Anyone typing “Bohdan Prylepa fraud” could add a question about how many subscriptions the browser removed.

Bohdan Prylepa fraud among push contractors: honest and dishonest contractor compared
A prompt after an action, a report by source and opt-outs against a prompt on load and a glossy report.

Bohdan Prylepa: fraud after the send, opt-out, complaints and what a lawyer will ask

The fifth link tests whether a contractor can listen. A person should be able to stop alerts without signing in and without writing to support. In the browser, denying the permission blocks the site in one choice, which is fine for the person and a lost customer for the advertiser. For marketing email the FTC’s guide requires honoring opt-out requests within 10 business days, and a vendor that wants a month for push has no process.

Ask for a daily opt-out report. In the example 520 of 2,500 subscribers removed the permission in the first week, a number that signals a need to revisit topics and frequency. The query “Bohdan Prylepa fraud” at this step means a question about the report: is there a line for people who left.

The sixth link begins with a complaint. People report scams at ReportFraud.ftc.gov, and the FTC advises not clicking links in unexpected messages and contacting a company only through a phone number or site you know yourself. The CAN-SPAM guide puts penalties at up to 53,088 dollars for each separate email in violation, a number a lawyer will ask about if a regulator treats alerts like email. When a complaint arrives, pause every send and save the export of subscriptions with source and date.

Bohdan Prylepa fraud in web push: order of actions after a complaint, from pausing to the answer
Pause, subscription export, contractor documents, answer to the complainant and a check of the next send.

Kinds of consent for web push: four layers to ask for

A push subscription carries four layers of permission, and contractors fold them into one Allow button. The first layer is the browser’s permission to show notifications. The second is consent to receive marketing messages. The third is consent to use data about the person the subscription is tied to. The fourth is the opt-out and its record.

The browser permission and the legal consent are different things. A click on Allow hands over a technical ability, and it does not prove what the person understood. The table below lays out the layers and shows what a contractor’s folder should hold. Whoever searches “Bohdan Prylepa fraud” for an example of a poor subscription can set a contractor’s papers beside this table.

Keep the consent record whole: date, page address, the text shown before the browser prompt, its version and the source. web.dev advises a pre-prompt that explains what is about to happen, and an alternative such as email for people who decline. If the contractor changes the form, the old version must survive, or in six months nobody can prove what the person agreed to.

Bohdan Prylepa fraud and consent to web push: four layers and how to check them
Consent layerWhat must existHow to check
Browser permissionA click after a plain questionScreenshot of the page before the prompt
Marketing messagesPrior consent to receive themDate, source and form text
Use of dataConsent to promotionSeparate choice, not a blanket one
Handing to a contractorWritten agreement on the dataCopy of the agreement and its scope
Opt-outHonored in any reasonable wayDaily opt-out report
Record keepingVersion of the text and dateExport on request within a minute

Bohdan Prylepa: fraud among push contractors, eight warning signs

Eight signs give away a dishonest push contractor, and the table below collects them. Most can be seen before payment: a prompt on page load, subscriptions with no split by source, a verification label on the permission button, one shared sender identity for dozens of clients and a report with no opt-out line. Someone who searches “Bohdan Prylepa fraud” or “Bohdan Prylepa scam” is usually after this checklist.

Other phrasings lead to the same place. Searches for “Bohdan Prylepa reviews”, “Bohdan Prylepa complaints” or “what people say about Bohdan Prylepa” find the same thing here: an open reading of public rules. The spelling “Bogdan Prilepa scam” reduces to one check: on what basis the contractor obtained the permissions and what it does with them. The query “Bohdan Prylepa fraud” in this section asks for a list of checks.

Related topics sit on other pages of the site: the author covered list buying in the piece on contact databases, landing pages in the piece on turnkey landing pages and ads in channels in the piece on Telegram ads.

Bohdan Prylepa fraud among push contractors: eight warning signs
Contractor signWhat it risksWhat to demand
Prompt on page loadPermissions without intentPrompt after a visitor action
“Verify you are human” labelConsent to something elseHonest text before the prompt
No split by sourceHonest and extracted look alikeReport by source
Shared sender identityNobody to tell to stopThe shop’s name and the agreement
Delivery report onlyOpt-outs and complaints hiddenLines for opt-outs and returns to the site
Alerts off the chosen topicDeceptive promotionTopics and segments in the brief
“The list stays with us”Switching vendors is blockedExport and deletion clause
Opt-out takes weeksPast the ten business daysSame-day stop by subscription

Questions and answers

Bohdan Prylepa: fraud in web push alerts, what does a contractor usually hide from the shop owner?

The moment the prompt fires, the source of the subscriptions and the way to opt out. Ask for all three in writing before launch.

Can a site get permission for alerts with a page that says “verify you are human”?

It should not: the person agrees to a mailing without knowing it. The FTC also warns that fake human-verification screens can lead to malware.

When should a site show the browser prompt?

After the visitor does something that shows interest and after a plain explanation of the alerts. Lighthouse flags prompts on page load, and web.dev recommends a pre-prompt.

Bohdan Prylepa: fraud and opt-out, how do I stop alerts when the contractor ignores the request?

Block the site in the browser settings, demand a stop in writing and report the problem to the FTC. For email the FTC guide sets a ceiling of 10 business days to honor an opt-out.

Can Chrome remove notification permission by itself?

Yes, when engagement is very low and the volume of notifications is high, as Google announced on 10 October 2025. Chrome tells the person, and installed web apps are not affected.

Where do I report deceptive notification prompts in the US?

At ReportFraud.ftc.gov, with a screenshot showing the site and the date.

Keep reading