Cookie policy
The checker keeps results in current-page memory. Google AdSense may use advertising cookies and similar technologies; security logs and counters are handled separately.
What this page covers
This page lists every cookie and every piece of browser storage SassaCheck uses, who else is involved in serving the site, and how to block any of it.
It covers sassacheck.org.za and the status check that runs at our Johannesburg-hosted Google Cloud Run API. It does not cover srd.sassa.gov.za, or any other site we link to.
SassaCheck is an independent service. We are not SASSA and not a government website. We cannot approve, decline or change any grant.
The three categories at a glance
SassaCheck uses Google AdSense to display advertising. Google and its advertising partners may use cookies or similar technologies and process IP addresses, browser/device information and ad interactions for advertising, measurement and fraud prevention. We do not send status-form ID numbers, cellphone numbers or results to AdSense. We do not use a separate Google Analytics tag.
| Category | What it is for | Current use |
|---|---|---|
| Current-page memory | Displays the status result while the page is open; not a cookie or persistent storage | Yes |
| Analytics | Counting visits so we know which explanations people need | No |
| Advertising | Google AdSense advertising and ad measurement | Yes; cookie use depends on Google settings and applicable consent choices |
Google AdSense may use advertising cookies and similar technologies. You can manage cookies in your browser and advertising preferences through Google My Ad Center.
Strictly necessary
The form holds the result in the current page memory. It does not write the result to cookies, local storage or session storage. Reloading or closing the page clears that page state; browser history, autofill and device behaviour remain under your control.
What it holds
The status word SASSA returned, such as Pending or Approved, and the time of the check. We do not save raw ID numbers, cellphone numbers or status results in our application database. Keyed security hashes, request counters and operational logs are retained separately; see our data-handling explanation.
Why it is there
So the result stays on your screen while you read what it means. It stays in your browser and is not sent anywhere else.
How long it stays
Until you close the tab. Closing the tab clears it, and so does clearing your browsing data.
What it is not
It is not a cookie, it is not a profile of you, and it is not used to recognise you on a later visit.
What the check keeps on our side
Our server keeps two things during a check, and neither one is a cookie.
| What | Why | How long |
|---|---|---|
| Keyed, one-way hashes of the IP address and applicant ID, with request counters | Rate limiting, so nobody can use this tool to guess other people's ID numbers | Counters expire after 10 minutes; Firestore TTL deletion happens asynchronously after expiry. |
| Operational hosting logs, including connection metadata and IP addresses | Security and uptime | 30 days for the default operational log bucket |
| Administrative audit logs (Google Cloud) | Records of administrative actions, separate from status-result storage | 400 days in the required audit-log bucket |
The home-page checker processes your ID number and cellphone number through our server to retrieve your result from SASSA. It does not save the raw ID, phone number or result in its application database. Separate security counters and hosting logs are retained as described in our privacy policy.
Analytics
SassaCheck uses Google AdSense to display advertising. Google and its advertising partners may use cookies or similar technologies and process IP addresses, browser/device information and ad interactions for advertising, measurement and fraud prevention. We do not send status-form ID numbers, cellphone numbers or results to AdSense. We do not use a separate Google Analytics tag.
Google Cloud request and error logs can include IP address, request URL, time, status, latency and user agent. Our application does not log request bodies or status results. The default operational log bucket retains records for 30 days; separate administrative audit logs have a 400-day retention period.
If we add analytics later, we will name the provider, say what it collects and how long it keeps it, and ask for your consent before it loads. That change will appear on this page first.
Advertising
SassaCheck uses Google AdSense to display advertising. Google and its advertising partners may use cookies or similar technologies and process IP addresses, browser/device information and ad interactions for advertising, measurement and fraud prevention. We do not send status-form ID numbers, cellphone numbers or results to AdSense. We do not use a separate Google Analytics tag.
A link is not a cookie. Some pages link to srd.sassa.gov.za or to SASSA's contact details. Clicking one takes you to another site that we do not control.
Learn how Google uses information and manage advertising choices: Google partner-site data use · Google My Ad Center
Who else is involved
Google provides Firebase Hosting and the Cloud Run status-check service. DNS and any proxy service are separate; see the POPIA page for provider details.
| Party | What it does | What it sees |
|---|---|---|
| Firebase Hosting (Google) | Delivers the page files to your browser | The page request and your IP address, which any web host receives |
| Our status check server, our Johannesburg-hosted Google Cloud Run API | Passes your ID number and cellphone number to SASSA's public status service and returns the answer | Keyed, one-way hashes of the IP address and applicant ID, with request counters. Counters expire after 10 minutes; Firestore TTL deletion happens asynchronously after expiry. Google Cloud request and error logs can include IP address, request URL, time, status, latency and user agent. Our application does not log request bodies or status results. The default operational log bucket retains records for 30 days; separate administrative audit logs have a 400-day retention period. |
SassaCheck uses Google AdSense to display advertising. Google and its advertising partners may use cookies or similar technologies and process IP addresses, browser/device information and ad interactions for advertising, measurement and fraud prevention. We do not send status-form ID numbers, cellphone numbers or results to AdSense. We do not use a separate Google Analytics tag.
Email is not covered by this page. Our privacy policy explains what happens to a message you send us.
How to block or delete cookies
You can block or delete cookies and site storage in your browser settings, and every major browser gives you the option.
Look for the section called Privacy, Cookies, Site data or Storage. In most browsers it sits under Settings, then Privacy and security. Menu names differ between versions, so search your browser settings for the word cookie if you cannot find it.
- Chrome and Edge: open Settings, then Privacy and security, then the cookies or site permissions section. You can block all cookies, or allow sassacheck.org.za as an exception.
- Safari on iPhone and iPad: open the Settings app, then Safari, then Advanced, then Website Data. You can delete data for sassacheck.org.za there.
- Firefox: open Settings, then Privacy and Security, then Cookies and Site Data. You can manage exceptions for a single site.
- Android: open Chrome, tap the three-dot menu, then Settings, then Site settings.
What happens if you block everything
The pages still load, but the status check may not work with some settings.
- Reading pages: works. Articles, status meanings, payment dates and contact pages need no storage at all.
- The form holds the result in the current page memory. It does not write the result to cookies, local storage or session storage. Reloading or closing the page clears that page state; browser history, autofill and device behaviour remain under your control.
- With storage blocked: the result may not appear, or it may disappear as soon as it arrives.
- Strict tracking protection: some browsers block storage for every site by default. You can allow sassacheck.org.za for one check, then remove the exception.
If the check does not work with your settings, you can still check your status without us. The next section shows you how.
You can check without us
You can run the same check at srd.sassa.gov.za without using SassaCheck at all.
You need your ID number and the cellphone number you used when you applied. That site is run by SASSA and we have no control over it.
Open srd.sassa.gov.za/sc19/status ↗ (opens in a new tab). We cannot see what you do there.
Changes to this page
If we change what this site stores, we will update this page before the change goes live and change the review date at the bottom.
We will not add a new cookie, a new tracker or a new company and leave this page as it is. Any new category will be named here, with the company involved and how long it keeps data.
Who runs this site and how to contact us
SassaCheck is an independent SRD status checker, and it is not SASSA and not a government website.
Operator, registration and Information Officer details are available on request. Contact us at hello@sassacheck.org.za.
We are not affiliated with SASSA, the Department of Social Development or the South African government. We cannot approve, decline, suspend or change any grant, and we cannot change your banking details.
Questions about this page go to hello@sassacheck.org.za. We reply within 2 business days, Monday to Friday, during business hours (confirm availability before calling).
For more on who we are and why our domain contains "sassa", see who runs this site.
Questions people ask
SassaCheck uses Google AdSense to display advertising. Google and its advertising partners may use cookies or similar technologies and process IP addresses, browser/device information and ad interactions for advertising, measurement and fraud prevention. We do not send status-form ID numbers, cellphone numbers or results to AdSense. We do not use a separate Google Analytics tag.
Does SassaCheck use cookies?
The form holds the result in the current page memory. It does not write the result to cookies, local storage or session storage. Reloading or closing the page clears that page state; browser history, autofill and device behaviour remain under your control.
Can I use the status check with cookies blocked?
The form holds the result in the current page memory. It does not write the result to cookies, local storage or session storage. Reloading or closing the page clears that page state; browser history, autofill and device behaviour remain under your control.
Do you sell my data?
SassaCheck uses Google AdSense to display advertising. Google and its advertising partners may use cookies or similar technologies and process IP addresses, browser/device information and ad interactions for advertising, measurement and fraud prevention. We do not send status-form ID numbers, cellphone numbers or results to AdSense. We do not use a separate Google Analytics tag.
Do you track me across other websites?
SassaCheck uses Google AdSense to display advertising. Google and its advertising partners may use cookies or similar technologies and process IP addresses, browser/device information and ad interactions for advertising, measurement and fraud prevention. We do not send status-form ID numbers, cellphone numbers or results to AdSense. We do not use a separate Google Analytics tag.
What happens if you add analytics later?
We will name the provider, say what it collects and how long it keeps it, and ask for your consent before it loads.
Sources
The facts on this page come from two places: SASSA's own status service, and Google's Firebase Hosting documentation.
- SASSA, SRD status service. srd.sassa.gov.za/sc19/status ↗, checked 29 October 2026. The service the check passes your details to, and the alternative we link to above.
- Google, Firebase Hosting documentation. firebase.google.com/docs/hosting ↗, checked 29 October 2026. How the pages are delivered to your browser.
If either link stops working, tell us at hello@sassacheck.org.za and we will fix it.
Last reviewed: 29 October 2026
Your ID number and cellphone number are sent over HTTPS through our server to SASSA to retrieve your status. Our checker does not save the raw ID number, cellphone number or result in its application database, and its application logging code does not record those values. The result is held in the current page memory, without saving it to cookies, localStorage or sessionStorage. For rate limiting, keyed hashes of your IP address and applicant ID are stored with request counters; their expiry is set to 10 minutes after an allowed request, and Firestore deletes expired records asynchronously. Google Cloud request logs can contain your IP address and connection metadata: the default operational log bucket retains records for 30 days, while the separate administrative audit log bucket retains records for 400 days. These audit logs are administrative records, not a 400-day database of status results. Google AdSense may use cookies and process IP, device and ad-interaction data; our code does not send status-form details or results to AdSense. We do not use a separate Google Analytics tag. See our Privacy Policy for details.
See the SASSA contacts page for current official guidance.