dataDex suspension — timeline

App: dataDex (com.talzz.datadex)

Status as of May 5, 2026 (Day 15 since suspension): suspended; the standard Google Play appeal is exhausted; AdMob first-line support is exhausted; the parallel Developer Support desk has closed. Two public escalations on Google's Help Communities have been escalated by a Product Expert each but remain pending team responses.

2026-04-20, 19:09 UTC — Suspension

Google Play suspends com.talzz.datadex under the App Promotion policy (deceptive ads).
Cited creative: PROMO_GRAPHIC-6445.png — "Tower Rush" / "PREMIO 1500 EUR + 250 FREE SPINS GIOCARE", an Italian-language casino interstitial.
Served programmatically through the publisher's single AdMob interstitial unit.
Not uploaded by the developer, not selected by the developer, not part of any Play Console asset.

2026-04-20 → 2026-04-26 — Standard Google Play appeal (case `2-1866000040535`, agent Ronan)

Apr 20, 23:58 UTC — appeal submitted; auto-acknowledgement.
Apr 21, 00:23 UTC — publisher submits detailed context including security audit ruling out account compromise across Play Console, Google Cloud / Firebase, and Google Ads.
Apr 21, 23:59 UTC — Template reply #1. App Promotion policy quote, "remove your ad campaign or promotion," "upload a new app under a new package name." First time the publisher learns the cited creative is an in-app ad, not a Console upload.
Apr 22, 01:11 UTC — publisher confirms the AdMob source and reports remediation (sensitive categories disabled, max ad rating set to T, ad unit disabled).
Apr 22, 22:04 UTC — Template reply #2. Verbatim repeat.
Apr 23, 11:24 UTC — publisher posts comprehensive reply with AdMob configuration screenshots, the systems-failure analysis, and reference to the parallel Developer Support ticket.
Apr 23, 22:59 UTC — Template reply #3. Verbatim repeat.
Apr 24, 12:28 UTC — publisher posts a final detailed message with five specific questions for a human reviewer.
Apr 26, 20:04 UTC — Template reply #4. Slight wording change ("I've already given you all the available information"); same App Promotion policy text. Standard Play appeal exhausted.

2026-04-23 → 2026-04-25 — Parallel Developer Support ticket (case `9-9277000041337`, agent Joseph)

Apr 23, 04:06 UTC — initial denial, redirect to the appeal thread.
Apr 23, 10:54 UTC — Joseph engages on the merits, summarizes the remediation correctly, recommends posting all evidence directly on the appeal thread.
Apr 24, 11:47 UTC — Joseph confirms in writing: "I have re-flagged the appeal case internally to ensure your latest documentation is visible for human review." Notes the repetitive template-response cycle in his internal notes. States all available Developer Support assistance has been provided.
Apr 25, 12:49 UTC — auto-survey closing the ticket. Joseph's desk closed per scope.

2026-04-22 onward — Google Play Developer Community escalation

Apr 22, 23:11 UTC — publisher posts: App suspended over AdMob-served casino ad. Stuck in template-reply loop, requesting escalation help, asking for escalation to a human Google reviewer.
Apr 22, 23:49 UTC — a Platinum Product Expert escalates the case.
Apr 26, 21:37 UTC — publisher asks for update.
Apr 26, 21:43 UTC — Product Expert: "I will let you know, if I get an update from the team."
May 1, 12:59 UTC — publisher checks in again, cross-references the new AdMob Help Community post.
As of 2026-05-05 — no further reply from the Product Expert or the team. Thirteen days since the escalation; ten days since the last Product Expert reply.

2026-04-27 → 2026-04-28 — AdMob support (case `4-3221000040899`, agent Qian)

Apr 27, 18:28 UTC — Brush-off #1. Reply opens with an apology that AdMob does not currently offer support in Hebrew. The publisher's submission was in English; only the locale-driven auto-acknowledgement was in Hebrew. Reply otherwise treats the case as a routine "Play app suspended; AdMob restriction is downstream" matter and does not engage with the classifier-failure question.
Apr 27, 19:28 UTC — publisher reframes: the Play suspension is the symptom; the issue is the AdMob-side classifier failure. Resends the full report, the eleven creative IDs, and the AdMob configuration evidence.
Apr 28, 05:35 UTC — Brush-off #2. "We are unable to perform cross-product transfers" — referring to a transfer the publisher did not request. Redirects to Play Console support.
Apr 28, 09:26 UTC — publisher clarifies that no transfer was ever requested; restates the three concrete asks (written confirmation that the eleven variants violated AdMob policy; AdMob-to-Play internal coordination; investigation of the broader pattern of casino creatives bypassing AdMob's classification).
Apr 28, 09:39 UTC — Brush-off #3. Same redirect to the Play Console team. AdMob support exhausted.

2026-04-29 onward — AdMob Help Community escalation

Apr 29, 23:47 UTC — publisher posts: Casino-ad scheme bypassed AdMob's classifier and was served in my now-suspended app. PE help needed, with the full evidence and the eleven documented creative IDs.
May 1, 12:06 UTC — a Diamond Product Expert engages, says they will escalate the case from the AdMob side.
May 1, 12:56 UTC — publisher thanks the Product Expert; cross-references the older Google Play Developer Community thread.
As of 2026-05-05 — no further reply on the thread. Four days since the Product Expert's engagement.

2026-05-05 — Day 15: current status

Standard Google Play appeal: exhausted (no engagement on the remediation evidence; case stuck in template-reply loop).
Google Play Developer Support: closed.
AdMob first-line support: exhausted.
Two public Help Community escalations now on record. Both have been escalated by a Product Expert. Both are pending team responses that have not arrived.
Internal redress paths exhausted; public escalation paths stalled.

Public evidence bundle (PDF report, 11 creative screenshots, AdMob configuration, full appeal threads): https://drive.google.com/drive/folders/1d6SdbJrHdGSe4IJHnEPesKDt_PcdWQDB