A Google Play data safety review that feels slow is usually still within the normal window rather than stuck. When you submit or change your Data safety declaration, Google reviews it, commonly taking up to about a week and sometimes one to two weeks for apps subject to an expanded review. While it is pending, the associated update is held from going live, but your currently-published version stays available to users, so the app is not down. The important thing not to do is cancel and resubmit repeatedly, since that can restart the review. Check the Publishing overview page in Play Console for the status, and contact Google Play developer support only if it is stuck well beyond the usual window.
Short answer
A pending data safety review is normally a waiting game, not a problem to fix. Per Google's Data safety guidance, your declaration is reviewed and typically appears on your listing within about seven days, though an expanded review can take one to two weeks. It holds the pending update until it clears, while your live version stays available. Do not cancel and resubmit, since that can restart the review, and use the Publishing overview page to see the status. If it is stuck well past the normal window, contact Google Play developer support. There is no fixed guaranteed time, so judge against these ranges.
What the data safety review is
The data safety review is Google checking the Data safety declaration you provide about what data your app collects and shares. Whenever you submit a new declaration or change an existing one, that declaration is reviewed, and because a data safety change is tied to a release, the review happens as part of processing that update. So a data safety review taking time is really your update waiting on the review of the declaration attached to it.
This matters because it frames the wait correctly. The review is not a separate queue you can jump; it is part of the normal release review, and the data safety portion is one thing Google verifies before the update goes live. Understanding that the declaration and the update move together explains why a slow data safety review holds your update, and it points you at checking your submission status rather than at re-editing the form, which is covered below.
How long it normally takes
There is no fixed, guaranteed time for a data safety review, but the practical window is up to about a week for most apps. Google indicates a submitted data safety declaration typically appears on your listing within roughly seven days, and many reviews complete faster than that. So a data safety review that has been pending for a few days is well within normal, and waiting is the right response rather than intervening.
Some apps take longer because they are subject to an expanded review, which can extend the time to one or two weeks, and occasionally longer in exceptional cases. This is more likely for apps handling sensitive data or flagged for closer scrutiny. So the realistic expectation is up to a week for a routine review and up to one to two weeks when an expanded review applies, with anything inside those ranges being normal rather than a sign that something is wrong.
Does it stop production updates?
Yes, in the sense that the specific update tied to the pending review does not go live until the review clears, so a data safety review in progress holds that release. If you submitted an app update along with a data safety change, the update waits on the review, and users do not receive the new version until it is approved. So a slow data safety review does delay a production update you are trying to ship.
But it does not take your app down. Your currently-published version remains live and available to users throughout, because only the pending change is under review, not your existing listing. And if you use managed publishing, an approved change still will not go live until you choose to publish it from the Publishing overview page, which gives you control over the exact timing once the review passes. So the accurate picture is that the pending update is held, while your live app keeps running.
Normal versus abnormal waiting
Judging whether to wait or act comes down to comparing the elapsed time to the normal ranges. A data safety review pending for a few days, or up to about a week, is normal, and up to one to two weeks is normal for an app under an expanded review, so within those windows the right move is simply to wait. Google does not promise a specific completion time, so treat these as expectations rather than deadlines.
It becomes worth investigating when the review has been pending well beyond these ranges, for example clearly past two weeks with no movement, especially if you have not received any request for more information. At that point the delay is outside the typical pattern, and after confirming the status on the Publishing overview page, contacting support becomes reasonable. So the rule is to wait through the normal window and treat only a clearly overdue review as something to escalate.
Does resubmitting reset the review?
This is the key mistake to avoid: canceling your submission and resubmitting, or repeatedly editing and re-sending the form, can restart the review rather than speed it up. Each resubmission can put you back at the start of the queue, so an impatient re-send often makes the wait longer, not shorter. The review is already in progress, and it does not go faster because you resubmit.
So resist the urge to resubmit while a data safety review is pending within the normal window. Instead, leave the submission in place and monitor its status, because the review will complete on its own. Only make a change if Google actually asks you for one or if you discover your declaration was wrong, in which case correcting it is warranted despite the reset, since an accurate declaration matters more than speed. Otherwise, patience is faster than resubmitting.
Status at a glance
Matching how long it has been pending to whether that is expected tells you what to do. The table below maps it.
| Time pending | Normal? | What to do |
|---|---|---|
| A few days | Normal | Wait; this is routine |
| Up to about a week | Normal | Wait; check Publishing overview |
| One to two weeks (expanded review) | Normal for some apps | Wait; monitor status |
| Clearly past two weeks, no movement | Investigate | Confirm status, then contact support |
| Google requested information | Action needed | Respond promptly to unblock it |
Read the last two rows as your action triggers, since everything above them is a normal wait rather than a problem.
How to check status and escalate
The first step when a data safety review feels slow is to confirm where it actually stands, using the Publishing overview page in Play Console, which shows whether your submission is still pending review. This tells you the review is genuinely in progress rather than stalled on something you missed, and it is where an approved change appears for you to publish if you use managed publishing.
If the review is clearly overdue against the normal ranges, escalate by contacting Google Play developer support through the Help Center, where you can reach support for publishing issues. Have your app details and the pending submission ready so you can describe exactly what is waiting and for how long. So the order is to check the Publishing overview first, respond to any request for information, and only then open a support contact for a review that is genuinely stuck beyond the usual window.
What to check
Working through these steps tells you whether to wait or act. The checklist below covers them.
| Step | Action | Done? |
|---|---|---|
| Check the status | Open the Publishing overview page | [ ] |
| Compare to the window | A week is normal; up to two for expanded | [ ] |
| Do not resubmit | Leave the submission in place | [ ] |
| Respond to requests | Answer any Google request quickly | [ ] |
| Confirm your live app | Your published version stays available | [ ] |
| Escalate if overdue | Contact developer support past the window | [ ] |
The step teams skip most is checking the Publishing overview page, since it confirms the review is in progress and prevents an unnecessary resubmission that would restart the clock.
Where a scan fits
A data safety review is a Play Console timing matter, so a security tool does not speed it up, but the wait is a natural time to make sure the app whose data practices you declared is actually secure.
A scanner like PTKD.com analyzes your Android build and reports what data-related behavior and third-party code it contains, alongside security issues such as exposed keys and over-broad permissions, by severity and mapped to OWASP MASVS. To be clear about the boundary: PTKD does not review your data safety form or influence its timing, which are Google's. It helps you confirm that what your app does with data matches what you declared, so the review time doubles as a check that your declaration and your app agree.
What to take away
- A data safety review commonly takes up to about a week, and one to two weeks for apps under an expanded review, so a few days pending is normal.
- It holds the pending update from going live until it clears, but your currently-published version stays available to users, so the app is not down.
- Do not cancel and resubmit while it is within the normal window, since resubmitting can restart the review and lengthen the wait.
- Check the Publishing overview page for the status, respond promptly to any request for information, and use managed publishing to control go-live once approved.
- Escalate to Google Play developer support only if the review is clearly past two weeks with no movement, and use a tool like PTKD.com to verify the build during the wait.
