Privacy

Browsing and phone accounts

Fixtures, scores, probabilities and finished-match predictions can be browsed without an account. Register with your phone number and password, then request a code by SMS or WhatsApp to verify your registered number before member access. Phone changes also require verification. We store a normalized phone number, salted password hashes, verification and password-change times, login times, access periods, account status and owner support notes. Password recovery uses a code sent through your selected channel. Goal Hint stores keyed code hashes rather than plaintext codes. Generated personal slips are not stored. You can save up to ten filter presets. Published Best Slips retain their original selections and odds. The owner separately checks payments against the account number before approving access. Do not include unrelated personal information.

Logging in sets an essential, HttpOnly, SameSite=Lax member cookie; it is Secure on production HTTPS. The cookie holds a random session token; the database stores its hash and session times. Up to two authenticated sessions can stay active; a successful third login ends the oldest active session on the server. Logging in again from the same browser replaces its session token. Registering first grants a restricted verification session, and a verified password reset code grants a restricted password-change session lasting up to 15 minutes. Restricted sessions do not displace authenticated sessions. Completing account verification, password recovery or a password/phone change revokes prior sessions for security. The ordinary browser cookie lasts up to 400 days, while a session expires after 90 days without renewal through use. Logging out clears this browser session. Anonymous browsing sets no member cookie. Opening an invitation link sets a separate signed, HttpOnly referral cookie for up to 30 days. Registration records the inviter, verification/award times and a keyed digest of the number; the digest is retained after erasure or deletion to prevent repeat rewards, without retaining the number in referral storage. Inviters see reward status and dates, never the referred number. Browser storage or cookie restrictions can prevent access and referral attribution from working.

Payment reports and screenshots

A payment report stores your account number, payer number (your account number unless you enter another), receiving network, the transaction ID, the amount your browser read from your screenshot (a hint for review, not the amount charged), the selected plan with its price and duration snapshot as the amount, terms version, review status, and relevant times. We keep an owner action history and, for each access period, the hash of a random value that is never shown. Editable form fields are sent only when you submit; a tab-scoped draft of those fields stays in session storage until sent, logged out or removed by the browser. The draft excludes image bytes. A credit top-up is recorded the same way, with the amount you chose instead of a plan. Account credit keeps a ledger of each change (top-up, extra paid, plan bought, auto-renewal, reversal, correction or number change) with its amount, resulting balance, time and the payment or access period it names; the ledger holds no phone number, and its amounts stay for accounting if your personal data is erased.

A screenshot is optional for a payment report. When you choose one, your browser reads its text on your device to fill in the transaction ID, amount and network; only the ID and the amount it read are sent with your report, never the rest of the text. Your browser prepares a JPEG before upload. The screenshot, its hash and size are stored in the database and can be viewed only through authenticated owner tools. Approved and reversed screenshots are deleted by maintenance after the configured retention period, 90 days by default from the decision; rejected and superseded screenshots after 7 days. Pending screenshots remain until reviewed. Maintenance runs in batches, so expiry is not immediate deletion. Encrypted backups can retain earlier copies until the backup retention policy removes them.

When you request account verification or password recovery, Goal Hint sends your registered phone number and the message or code to YoolaSMS for delivery through the SMS or WhatsApp channel you select. Choosing WhatsApp confirms you want that code delivered on WhatsApp; this confirmation accompanies the provider request. Payment decisions, credit updates and auto-renewals also send an account-update SMS to your registered number, asking you to log in for details. Those messages contain no payment references, decisions, amounts, balances, plan names, expiry times or review reasons. Goal Hint removes closed account-update SMS delivery records, without the number or message text, through bounded maintenance after 7 days, or 30 days for failed or unconfirmed attempts. Open delivery intents are retained until processed. Separate payer numbers are not recipients. Payment approval opens access on your logged-in device even if the SMS fails. WhatsApp is provided by Meta and can process phone numbers and message content across borders under its own terms. YoolaSMS and the delivery services receive message content, including verification codes; their processing locations, retention and contractual safeguards still require confirmation. Calls and chats through the Call admin or WhatsApp admin links happen outside this site. External messages and screenshots can remain in WhatsApp, the owner’s phone, linked devices and their backups. Opening a prepared WhatsApp message may leave it in browser history.

Verification request records contain the registered phone number, purpose, selected channel, keyed code hash, attempt count and request, send and use times. Codes expire after 24 hours or successful use, and a newer request invalidates the previous code. Consumed and failed request records remain until their original 24-hour expiry to enforce request limits, then maintenance removes expired records; expiry is not immediate deletion. Expired member sessions are also removed by maintenance. Keyed-hash throttle records are removed after their request window and any lock have ended plus one day; legacy records can take longer. Accounts without a password, payment report or access period are removed after 30 days without logging in. Payment metadata, payer numbers, access periods and owner audit rows currently have no automatic deletion period: the lawful retention schedule and backup handling still require owner approval.

Numbers, sessions and payment reports support the access you request; security throttles protect the service using keyed hashes of connection information rather than raw IP addresses. These purposes do not establish an approved lawful basis. The operator must confirm the applicable lawful bases, data-protection registration position, cross-border safeguards and breach procedure before paid access opens.

Page requests and server logs

Delivering a page or a stored-data update exposes connection information, such as your IP address, request time, requested address and browser headers, to the serving infrastructure. This information can be used to deliver and protect the service. Anonymous access does not make network requests unidentifiable.

The application does not implement a visitor activity-log database. The operator reports that the database is hosted on a Namecheap server. Hosting, network or security services may keep request and error logs, including URL query text. Server location, log contents, access rules and retention still need confirmation; this summary cannot promise that no logs exist or give a deletion period.

Search, filters and public endpoint protection

Match searches, dates, league, market and pagination choices appear in page or API URLs and are sent to Goal Hint to read stored football data. URLs can remain in browser history, bookmarks, copied links and infrastructure logs. Avoid putting personal or sensitive information in search text.

Search protection uses one shared request count and window start in the database, not a per-person profile. That counter stores no IP address, cookie, visitor token or search text. A later search replaces an expired counting window; this is not a visitor log-retention policy.

Visible match pages periodically request stored updates and pause background polling when hidden. These requests use the same public endpoints. Browsing, searching and refreshing do not send your search text to football, research or AI providers or start prediction jobs.

Browser storage and navigation

Loaded matches and request state also live in page memory. Blocking browser storage leaves ordinary page links and stored-data reads usable, but saved preferences and Back-position restoration may be lost. The privacy page itself does not write these preferences or navigation records.

Analytics, cookies and advertising

Goal Hint uses its own first-party analytics only if you allow it in the consent banner. Until you choose, and if you decline, the analytics system records nothing about your visit. Browsers that send a Global Privacy Control or Do Not Track signal are treated as having declined. There are no advertising tags, tracking pixels, third-party analytics services or analytics cookies, and advertising and affiliate promotions remain disabled.

With your consent, local storage keeps your choice plus a random visitor identifier and visit identifier, session storage briefly keeps the current page view's identifier so an automatic reload is not counted twice, and your browser sends page addresses without query strings or fragments, page titles, time spent on each page, the labels of links and buttons you click, match searches, the referring website's domain and any campaign tags in the link you followed. The server keeps a keyed hash of the visitor identifier, browser and operating system families, device type, screen-width band, language and an approximate country and city derived from your browser's time zone.

Analytics never stores your IP address, full browser identification string, typed form input or the raw identifiers. Account and payment forms are excluded from click capture. Product events carry names only, with no phone, password, transaction ID, amount or screenshot. Search text and click labels are lower-cased, shortened and stripped of anything resembling an email address or phone number. Visits from automated browsers and from Goal Hint’s administrators are excluded.

Only the operator can view the statistics, through a password-protected dashboard; they are used to understand and improve the service and are not sold or shared. Raw analytics records are deleted automatically after the configured retention period, thirteen months by default. You can change your choice below at any time; withdrawing consent deletes the identifiers from this browser immediately.

Remote images and external websites

Approved API-Sports team and league badges are resized and cached on Goal Hint's server. Your browser requests those versions from Goal Hint; the provider receives a server request when an image is fetched or refreshed. Other approved remote images are requested directly by your browser, and that host receives your IP address and browser/request information. Direct image requests suppress the referring page address, but this does not hide your IP address from the host.

Optimized badges are cached on the hosting server and refreshed on demand; older release files may remain until deployment cleanup. Direct remote hosts apply their own logging, retention and cookie practices, subject to your browser settings. Original Goal Hint branding and fonts are served with the site. Following a source or provider link visits that external service under its own data-handling rules.

Football sources and stored reports

Match information and supported fallback predictions come from stored API-Football data; analysis can include attributed football reporting when permitted. These records can include information about players and other people mentioned in the sources. They are distinct from visitor accounts or browsing profiles. Source attribution appears on the relevant match page.

Source permissions control permitted use and display. Retention and deletion arrangements for provider data, reporting, evidence, immutable forecasts, corrections and backups still require confirmation. A permission deadline or cache expiry does not establish that every stored copy has been deleted.

Shared caches and retention limits

The server can cache shared football responses under keys derived from the request filters, rather than a visitor identifier. Keys are hashes, but cached pagination links can contain your search text and filters. Hashing a key neither removes that text from the response nor guarantees anonymity. Account notifications store event references and read/dismiss state on the server for up to 90 days; older entries are removed on a later account refresh or maintenance run. Notification content and unread counts are not saved in browser storage.

Current responses can be reused for up to 5 seconds and immutable revision payloads for up to 6 hours, subject to earlier invalidation and source permissions. These are reuse limits. Expired entries are removed by a separate maintenance pass; expiry is not a promise of deletion at that instant. Audit and invalidation records have separate unresolved retention requirements.

Your browser choices and privacy requests

You can clear this site’s local and session storage and cookies through your browser’s site-data controls and manage images or third-party cookies in browser settings. Clear browser history or bookmarks separately to remove saved URLs. Clearing browser data does not erase server records or external messages. Ask the owner to erase your account: this clears its phone and support notes, relevant payer numbers and screenshots and logs out its devices; retained transaction amounts and IDs, access history and audit metadata remain pending an approved legal retention policy. Existing backups require separate handling.

Wilson Wasswa handles privacy requests through the email on the Contact page, including requests about access, correction or deletion. Applicable rights, any required legal basis or transfer safeguards and complaint routes still need review before release. This page does not claim a legal exemption or promise a response deadline.

If you email Goal Hint, Gmail (Google) handles your sender address, message and any attachments so Wilson Wasswa can review and respond. The website itself has no contact form or email-sending system.

The operator has adopted an email retention policy starting Sunday, November 1, 2026. Routine support and correction correspondence will be kept for up to six months after resolution. Only a minimal record of privacy requests will be kept for up to twelve months after closure. Unnecessary identity documents will be deleted promptly.

Relevant information may be kept longer for a documented dispute or legal obligation, with each exception reviewed every ninety days. These periods apply to correspondence under the operator's control, including sent replies and saved attachments. Google processes email through Gmail under its own policies.

What must be confirmed before release

Final notice publication requires the following decisions and evidence. Until they are recorded and reviewed, this page remains a factual prelaunch summary and public release is blocked.

• Actual request, security and error-log contents, access, recipients and retention.

• Actual hosting configuration, processing locations, contractual responsibilities and any required transfer safeguards.

• Permission-compatible retention and reuse of football and reporting sources.

• Verified deletion, audit and backup retention arrangements, including implementation of the adopted correspondence policy.

• Approved lawful handling and retention of payment metadata, payer numbers, screenshots and owner audit records, including backup copies.

• The refund, reversal, extension and outage-compensation policy and associated consumer disclosures.

• The applicable lawful bases, PDPO registration position, hosting country, YoolaSMS and SMS/WhatsApp delivery processing and retention, WhatsApp/Meta and other cross-border safeguards, erasure and breach procedures.