screener.in
screener.in was loaded in a real browser as a visitor from India and checked against the parts of the DPDP Act that can be seen from outside a site. Everything below is an observation about what loaded, not a finding about how screener.in handles data internally.
“Could not check” means exactly that — the signal was not readable from outside, often because the page was served differently to an automated visitor. It is not a gap, and it does not count against the score.
Want to exercise your own rights at screener.in?
We found where to ask — how to file an access, correction or erasure request.
This is your site?
The detail behind each line — what actually loaded, when, and what it exposes you to — is on the full report you can run yourself. To be removed from this index, email support@askmeidentity.com and we will drop it — no questions, and nothing further needed from you. How the crawler behaves is documented at /bot.
These observations were recorded automatically on the date shown and may be out of date. A site can change the day after we look. We are not affiliated with screener.in, we did not contact them, and nothing here is a legal conclusion about whether they comply with the DPDP Act — only a record of what a visitor could see.