What SnapLotto is built to do
SnapLotto brings South African lottery results, draw information, ticket scanning and clearly labelled predictions into a mobile-first website and Android app. The service is intended for adults who already hold a lottery ticket or want to follow published draw information. Practical pages should help a user complete a real task without requiring a wager or purchase through SnapLotto.
SnapLotto does not sell lottery tickets, accept bets, operate a draw or pay prizes. It is not the South African National Lottery operator and does not imply operator endorsement. The original ticket, official published record and operator claim process remain decisive. These boundaries are repeated where a user could otherwise mistake an informational result for a claim decision.
Separate facts, tools and predictions
Published draw numbers, dates and payout tables are factual records tied to a source and draw identity. Ticket scans are tool outputs created by reading a user's image and comparing extracted details with those records. Guidance articles explain how the process works. Each category has different limits and should not be presented as though it carries the same certainty.
Predictions are informational experiments about future random events. They are stored before the relevant draw and can be evaluated afterwards, but they cannot guarantee a win or improve the mathematical odds of one purchased line. A prediction score is not a probability of winning a jackpot. SnapLotto keeps scheduled predictions separate from user-generated number sets and from confirmed results.
How public guidance is reviewed
SnapLotto writes its guides for the questions users face while reading a ticket, taking a photograph, selecting a draw or interpreting a pending result. Product instructions are checked against the current website and Android workflow. Statements about supported games and results are checked against the data structure and published operator information used by the service.
A guide displays a review date so readers can judge how current it is. Material game changes, product changes or corrections require another review. The content avoids claiming that an automated check is final and avoids invented payout information when a source is incomplete. Older game names may appear only when they are necessary to explain a historical ticket or archived result.
Corrections, privacy and user reports
Readers can report a factual or product discrepancy through the SnapLotto contact page, support email or published WhatsApp channel. A useful correction includes the page, game, draw number and disputed field. SnapLotto reviews the stored value and underlying public source, updates confirmed errors and rechecks affected ticket results when required.
Users should not send passwords, banking PINs, one-time codes or unrestricted images of potentially winning tickets. Support requests are handled according to the published privacy notice. Analytics choices are provided separately from essential site operation, and private account, admin and processing pages are excluded from search indexing and advertising eligibility.
How commercial content is kept independent
Advertising and sponsorship can support the cost of hosting, data collection, ticket recognition and user support. Commercial material must be identifiable and must not be placed where it can be confused with a scan status, navigation action, winning number or prize instruction. SnapLotto does not accept payment to change an official result record or the measured history of a prediction.
Google-served advertising is limited to reviewed long-form guide pages with substantial publisher content. It is not loaded on result lists, prediction tools, scanner workflows, login pages, error pages or other screens whose primary purpose is navigation or an action. Editorial usefulness is assessed independently of whether a topic could attract an ad, and an advertiser does not receive approval rights over a guide.
Practical checklist
- Treat operator results as facts and prediction outputs as experiments.
- Keep ticket scans subject to review against the physical ticket.
- Display current review dates on long-form guidance.
- Correct confirmed factual errors and recheck affected outcomes.
- Protect ticket images and never request banking credentials.
- Keep advertising separate from results, tools and editorial decisions.