What We Can and Cannot Do
This page exists for one thing: corrections. If something here is wrong, out of date, or stated more confidently than the evidence supports, we want to know, and we will fix it or explain why we are not fixing it.
Being equally clear about the rest saves people a wasted week.
| Request | Can we help? | Where to go instead |
|---|---|---|
| A factual error, a dead link, or instructions that no longer match the product | Yes. This is what the contact address is for. | Email us with the passage and the source you checked. |
| "What does this company know about me?" | No. We have no access to anyone's data and no way to obtain it. | Send a data access request to the company's privacy or DPO address. See exercising your data rights. |
| "Send a deletion or opt-out request for me." | No. A request has to come from you, or from an authorised agent you have formally appointed. | The company's privacy contact, or a central platform such as California's DROP where it applies. |
| "Is this tracker or this app spying on me?" | No. We cannot analyse your device, your traffic or a specific app build. | Work through app permissions and how tracking works, then take the specific case to a specialist organisation. |
| "Review my privacy setup and tell me what to fix." | No. We cannot assess accounts, devices or networks we cannot see. | Follow the order of work on the home page; it is short and complete. |
| "Act for me in a dispute" / "complain to the regulator for me" | No. We have no standing to act for anyone, in any jurisdiction. | The supervisory authority for your country, named in the data rights guide. Complaints are usually free to file. |
| "Rewrite this article for my site" / "add my link" | No. We do not accept guest posts, sponsored placements or paid links. | Nothing to offer here, and that will not change. |
If you are in immediate danger, contact your local emergency services or a specialist support organisation before writing to anyone about settings. If someone is using your data to locate, monitor or harass you, general guidance is not enough, and a reply from this site will not arrive fast enough to matter.
If a message claims to come from this site, treat it as phishing. We will never ask for a password, a one-time code, a payment, or remote access to your device, and we will never ask you to confirm account details by replying. We do not run support over chat, SMS or direct message. Anything claiming otherwise is not from us.
Report a Correction
A specific report is fixed fastest. "Some of this is wrong" takes longer, because we have to find the claim before we can check it.
What to include
- Which page and which passage. Quote the sentence or name the heading.
- What you believe is wrong. "This menu was renamed in the current version", "the deadline in my jurisdiction is different", "this describes a mechanism that has been deprecated".
- The source you are relying on. A link to the regulation, the authority's guidance, the standard or the vendor's own documentation. If you are reporting from first-hand experience rather than a document, say so - that is still useful.
What happens next
- We read it and check the point against a primary source ourselves.
- If it is right, we correct the page and, where the substance changed, record what was wrong, what it now says and the date of the change.
- If it is not right, we reply explaining why we are leaving it as it stands, with the source we checked.
- If we cannot verify it either way, we say so, and where it matters we mark the passage as uncertain rather than leaving it looking settled.
Typographical fixes and wording changes that do not alter meaning are made without a note. Everything substantive is recorded.
How This Site Is Researched and Written
Every factual claim here is meant to be traceable to a source a reader can open and check themselves.
What counts as a source here
- Law and regulatory guidance — the text of the applicable statute or regulation, and guidance published by the authority that enforces it.
- Standards bodies — the organisations that define how cookies, storage, identifiers and encryption actually behave, rather than how a vendor describes them.
- Browser and platform documentation — the vendor's own current help pages and release notes, because only the vendor tracks its own changes.
- Independent organisations with published methodology, where a measurement or a category of technique needs a source.
Rules we hold ourselves to
- We do not quote a statistic without naming the report and its year.
- We do not state a settings path unless the vendor's documentation still shows it.
- We do not present a product as the answer. Where a category of tool helps, we describe the category and what to look for in it.
- We do not write in the voice of expertise we do not have, and legal questions are pointed at lawyers or regulators rather than answered here.
- We name the limits of every control we recommend, in the same section as the recommendation.
- We do not use fear as a sales tool, and we have nothing to sell.
Review cycle
Every page carries the same last-reviewed date and links the sources it was checked against. That date means a person re-opened those sources and confirmed the guidance still matched them — not that a file was touched.
We deliberately do not state a fixed calendar interval, because a static site cannot enforce one and such a claim quietly becomes false the moment it lapses. What we do state is the trigger: a page is re-checked when a source it cites actually changes — a law is amended, a regulator revises its guidance, a browser changes a setting, a linked page moves — and in any case at least once a year, so that nothing is left unexamined through neglect.
If the date on a page looks old, treat that as useful information rather than as a defect: it tells you the page is due for its next pass, and every claim on it links the primary source so you can check the current position yourself.
Independence
There is no advertising, sponsorship, affiliate link, paid placement or product for sale anywhere on this site, and no data is collected from readers. If that ever changes, it will be disclosed here before it appears anywhere else. See the about section on the home page for the full statement of who is accountable for this site.
Reusing This Material
You are welcome to quote, summarise, translate or teach from these pages, which is largely the point of publishing them. Two conditions, both about accuracy:
- Do not attribute a claim to us that we did not make. If you shorten something, keep the hedge. Where we said a mechanism only partly helps, a summary that says it works is wrong in a way that will mislead your readers.
- Link to the primary source, not only to us. The regulations, authority pages and vendor documentation are what stay accurate. We are a summary, and summaries rot.
If you translate a page, tell us, mainly so we can warn you when the original changes. That is a courtesy rather than a permission requirement.
Contact
Corrections, factual disputes, reports of dead or hijacked links, and notices that a described setting has moved all go to the author of this site, Edi Rahmadani, who is also the person who wrote and self-reviewed every page here. There is no support desk, no team and no ticket queue behind this address — which is precisely why we would rather tell you what we cannot do than let you wait for an answer that is not coming.
What makes a report easy to act on
- Which page and which passage. Quote the sentence or name the heading.
- What you believe is wrong. "This menu was renamed in the current version", "the deadline in my jurisdiction is different", "this describes a mechanism that has been deprecated".
- The source you are relying on. A link to the regulation, the authority's guidance, the standard or the vendor's own documentation. If you are reporting from first-hand experience rather than a document, say so — that is still useful.
If you are reporting a problem with this site itself — a link that now leads somewhere harmful, or content that could mislead a reader — please say so in the subject line so it is read first. A privacy site that sends readers somewhere unsafe is worse than no site at all.
And to repeat the standing warning, on a site about data protection: we will never ask for a password, a one-time code, a payment or remote access to your device, and we will never ask you to confirm personal details by replying to a message. Any message claiming to come from this site and asking for any of that is not from us.
Sources checked for this page
- UK ICO - your data matters, and how to raise a concern
- European Data Protection Board - national supervisory authority contacts
- California Privacy Protection Agency - DROP
- Indonesia - Law No. 27 of 2022 on Personal Data Protection
- EFF Surveillance Self-Defense - practical guides and specialist referrals
About RAJA89
RAJA89 is an independent educational project written by one person. It is not a company, an agency or a managed editorial team, and it does not pretend to be one. Edi Rahmadani writes these pages, checks them against the primary sources cited on each one, and answers corrections sent to the address on the support page.
RAJA89 is the name the site publishes under; the name above is the person accountable for what it says. Nothing here is generated and published unread: a claim either traces to a source you can open yourself, or it is marked as the author's own judgement.
How this site is funded
It is not. There is no advertising, no sponsorship, no affiliate link, no paid placement and no product for sale anywhere on this site. No company pays to be mentioned, and no page carries a commission-bearing link. Hosting is paid for out of the author's own pocket, which is the whole of the commercial relationship. If that ever changes, the change will be disclosed on this page before it appears anywhere else.
How to read this site
- Primary sources only. Where a claim can be checked, it links to the standards body, regulator or vendor documentation that supports it — not to another summary of it.
- Limits are stated. Where a control fails, or a setting only partly helps, the page says so in the same breath as the advice.
- Country-specific answers are labelled. Reporting routes, consumer protections and privacy law differ by country, so a passage that applies in only one is marked as such.
- No fear as a sales tool. Scaring a reader into a purchase is the behaviour this site exists to argue against.
Editorial standards we hold ourselves to
- We do not quote a statistic without naming the report and its year.
- We do not name a step-by-step settings path unless the vendor's own documentation still shows it.
- We do not present a product as the answer. Where a category of tool helps, we describe the category and what to look for in it.
- We do not write in the voice of expertise we do not have. When a question needs a lawyer, a doctor or a regulator, the page says so and stops.
- We do not silently rewrite a substantive claim. Material corrections are recorded with a dated note on the page, as described on the support page.
Dates, and what they mean
The date below is the last time these pages were re-checked against the sources they cite. It is a record of what happened, not a schedule: no page here states a calendar interval for review, because a static site cannot enforce one. Pages are re-checked when something they describe actually changes — a vendor renames a setting, a standard is revised, a regulation is amended, a link breaks — and at least once a year regardless, so that nothing is left unexamined through neglect.
The date moves only when a person has re-opened the cited sources and confirmed the text still matches them. It is not the date a file was last saved. Where a passage has been left standing but is no longer certain, it is marked as uncertain rather than quietly carried forward.
If the date below looks old, that is information, not a fault. It means the pages are due for their next pass. Everything on them links its primary source precisely so you can check the current position yourself rather than relying on our copy of it.
Who is accountable for this page
| Published by | RAJA89, an independent educational project written and paid for by Edi Rahmadani |
|---|---|
| Written by | Edi Rahmadani — an independent writer, publishing under the RAJA89 name. No employer, qualification or years of experience is claimed here, because this site asserts only what can be checked. |
| Reviewed by | Edi Rahmadani. This site has no separate reviewer, and we do not name one to look better. Every page is self-reviewed against the sources it cites, and that is exactly what the review record below means. |
| Corrections | Send a correction — specific reports are checked against a primary source and fixed or answered |
| First published | 2026-10-08 |
| Last reviewed | 2026-10-08 — every page on this site carries the same review date, and each one links the sources it was checked against |
Contact
Corrections, factual disputes, reports of a link that now leads somewhere harmful, and notices that a described setting has moved are all welcome at the address below. Edi Rahmadani reads them.
We will never ask you for a password, a one-time code, a recovery code or remote access to your device, and we will never ask you to confirm account details by replying to a message. Any message claiming to come from this site and asking for any of that is not from us.
Scope and limitations
Read this before acting on anything here.
- This is general education, not advice for your situation. It explains how data collection and privacy controls generally work, and which rights a reader may have. It is not legal advice and reading it creates no professional relationship. It is not an assessment of your situation: we do not know your accounts, devices, employer policies or past breaches. And it is not anonymity — reducing a footprint lowers how much is collected and how easily it is linked to you, and it cannot erase what has already been gathered or sold.
- We cannot see your accounts or your devices. We cannot tell you whether a particular message you received is genuine, whether an account has been compromised, or what an organisation holds about you.
- We cannot act on your behalf. We cannot contact a platform, bank, regulator or data protection authority for you, and we cannot investigate anyone. Requests like that have to go to the provider directly.
- Menus move. Settings are renamed, moved and reset by updates. A click path that was accurate on the review date may look different in your version. Treat every step here as a description of what to look for rather than a guarantee of what you will see.
- We can be wrong. Errors get through. If you find one, the support page explains what happens next.