Live presence — current feature
The owner’s operational monitor shows your current page category, active status and coarse browser/device category. A signed-in visit also identifies your existing account name, email and account status; a guest visit uses a temporary identifier. The monitor does not collect full URLs, form contents, IP addresses or page history. Live visits expire after 90 seconds without an update, though existing encrypted backup copies may contain a short-lived snapshot.
Visitor totals separately use a first-party counting cookie lasting up to one year. The counter stores a pseudonymous browser hash without account details, page history, IPs or device information. Hashes are retained for all-time distinct-browser counts; dated counting memberships cover the current and previous Lagos calendar month. Clearing cookies or using another browser may count as another visitor. You can block the counting cookie to be excluded from totals.
The monitor respects browser Do Not Track and Global Privacy Control signals. Its privacy notice is available at the bottom of each page. The monitor is hosted within Oddriva and sends no data to third-party analytics or advertising services.
Version 0.4 · 2026-09-28
1. Who is responsible
ODDRIVA LTD, Nigeria, is responsible for the purposes and means of processing personal information through Oddriva. Send questions, requests or complaints to info@oddriva.app, using the subject “Privacy”.
This notice covers visitors, account holders, analysts and authorised operators. Research accounts require email confirmation and manual account approval before posting Drops. These are access controls, not legal-identity checks. No phone or third-party identity-verification service forms part of the workflow. Cash rewards and payouts are not active under the research-account terms.
2. Information we handle
| Category | Information and context |
|---|---|
| Account and agreement | Name, email, confirmation status, account identifiers, display timezone and restrictions. Public registration records the accepted terms version, document fingerprints, acceptance time and adult declaration; the declaration does not independently verify age. |
| Authentication and security | Protected password hash, session identifiers and expiry, IP address, browser or device information, verification and recovery records, multi-factor enrolment information and security events. |
| Account review | Your request and message, any support request reference, reviewer, decision, reason and timestamps. Requests and decisions form review and audit records. |
| Football research | Event, market, selection, observed odds, source, rationale, bookmaker booking reference, submission time, screenshots and review decisions. |
| Screenshot records | Processed image, sanitised filename, size, content hash and link to the Drop. |
| Support and administration | Messages, case history, relevant account references, review notes, role assignments and audit records. |
| Optional payout preferences | A TRON receiving address you choose to save, receiving-instruction acknowledgement, change time and security-hold state. Saving it neither proves ownership nor initiates payment. |
| Future rewards and payments | Only if an active programme permits them: qualifying company activity, reconciliation, NGN statements, accepted USDT quotes, withdrawal approvals, transaction references and confirmation evidence. |
Information comes from you, your use of the service and authorised reviewers. We do not request phone verification, identity documents, biometrics or bank details through the current account-review flow. We never need wallet private keys or recovery phrases. Historical restricted review records, if any, do not mean a former verification service remains active.
Share only what is needed. Remove unrelated names, balances, account details, notifications and other people’s information from screenshots and messages.
3. Screenshots and private research
Authenticated server uploads are decoded and re-encoded into a standard image format. This removes embedded metadata, including EXIF, from the stored image. It does not remove personal details visible in the image itself. A content hash is retained for integrity; the upload flow does not retain the original as a separate attachment.
Server screenshots belong to private research records and use access-controlled routes. Relevant authorised reviewers can inspect them, with privileged access recorded. Other analysts cannot access your private screenshots or support cases through the service. A screenshot is user-supplied material, not independently verified evidence of a ticket or payment.
4. Purposes and lawful grounds
We identify an applicable lawful ground for each purpose rather than treating website use as consent to everything.
| Purpose | Applicable ground |
|---|---|
| Provide a requested account, agreed research participation and support | Necessary steps requested before an agreement, or performance of that agreement, where applicable. |
| Secure accounts, investigate abuse, enforce access controls and maintain decision history | Legitimate interests in a secure and accountable service, subject to necessity, proportionality and your rights. |
| Meet a specific applicable recordkeeping or disclosure duty | The identified legal obligation, not a general justification for extra collection. |
| Establish, exercise or defend a legal claim | The applicable lawful ground, with use and retention limited to necessity. |
| Optional future marketing or another consent-based feature | A separate, specific choice that can be withdrawn. Accepting account terms does not activate it. |
Required information may be necessary for the function you request. Optional information should not be required for unrelated access. Email confirmation demonstrates mailbox control; account approval does not turn a declaration into verified identity or wallet ownership. Materially different processing needs its own assessment, safeguards and appropriate notice before introduction.
5. Providers and other recipients
Internal access is limited by responsibilities such as support, research review, finance, security and audit. Role controls, privileged multi-factor checks and audit records support those limits. Analyst approval does not remove administrator MFA requirements.
Hostinger provides the virtual-server infrastructure and processes stored service data and technical information needed to operate it. Hostinger SMTP handles transactional email, including confirmation, recovery and invitations, using the recipient address, message and relevant delivery metadata. Sending-server acceptance does not prove inbox delivery.
Sportmonks supplies server-side football fixture lookups. The adapter sends a fixture identifier using the company’s provider account; it does not send an analyst’s name, email or screenshots for that lookup. Fixture data is not identity verification or bookmaker execution. No external identity-verification or bank-payout provider is part of the current workflow.
Authorised operators may use football analysis for company decisions described in the account terms. No bookmaker is represented as an active execution partner, and the platform does not place a ticket on your behalf. Limited information may be disclosed to professional advisers or competent authorities where necessary and supported by an applicable lawful ground; this is not unrestricted access to our records. We do not sell personal information or use the current application for targeted advertising.
If manual USDT rewards open, the company’s external sending-wallet service may process receiving addresses and transfer details. The relevant service and arrangements will be disclosed before that function is offered. Oddriva does not offer custody of analysts’ tokens or a wallet-signing integration.
An actual TRON transfer makes addresses, amount, hash and timing public. Others may link these to wider transaction history; account closure cannot erase the blockchain. Do not add names, emails or support messages to public transaction fields. Oddriva remains responsible for the private address-to-account links and personal information it controls.
6. Hosting and international transfers
Hosting, email routing or provider support can involve processing outside Nigeria. Future public-blockchain records can be viewed and replicated globally. We do not claim that all data stays in Nigeria or identify an unverified physical hosting location.
Where an international transfer occurs, we must establish the applicable transfer ground and safeguards and provide information required by law. You may ask about relevant recipients and safeguards, subject to legitimate security and confidentiality limits. A foreign location does not remove applicable privacy rights.
7. Cookies and the local demo
Necessary session and security cookies maintain sign-in and protect account actions. Blocking them may sign you out or prevent protected functions. The current application does not include advertising pixels or third-party behavioural analytics. Non-essential tracking would need appropriate notice and choices before introduction.
The demo stores its submissions, support cases and preferences in browser local storage, and screenshot files in that browser’s IndexedDB. That flow does not submit local records to the production research database. Loading the website still produces ordinary server connection information.
Do not put confidential or real financial information in the demo. Others using your browser profile may see its records. Use Reset demo records in demo Settings, or clear this site’s browser data, to remove them. This does not delete a separate production account or server support record. The server metadata-removal process does not apply to an original screenshot merely saved in the demo.
8. Security
The deployment uses HTTPS for transport, password hashing, protected multi-factor credentials, role permissions and audit records. Private data is not deliberately placed in a public offline cache.
The backup process encrypts database exports before writing backup files. This does not mean the live database or disk is encrypted at rest; we make no such claim. Access controls, key protection and recovery procedures remain necessary. No system can promise that every incident is impossible.
Report suspected unauthorised access or a privacy incident to info@oddriva.app. We will assess it, act to contain it and provide legally required notices. Do not include passwords, authentication secrets or unnecessary personal information.
9. Retention and deletion
We keep information for its stated purpose, considering account status, unresolved support or disputes, security needs and applicable duties. We do not promise fixed periods or automatic deletion on a timetable that has not been adopted.
Research and decisions may be needed to explain a review. Limited agreement, audit or future accounting records may remain necessary after closure. That does not justify keeping every screenshot or message indefinitely. If a record cannot yet be deleted, we will explain the applicable reason and limit further use where appropriate.
Deletion or anonymisation must account for lawful preservation requirements, others’ rights and the integrity of necessary records. Removed data may remain in a protected backup until that backup expires; restoration procedures must respect applicable deletion requests. We cannot alter independently maintained blockchain records, but remain responsible for personal information we control.
10. Rights and choices
Depending on applicable law and circumstances, you may request information about processing, access, correction, erasure, restriction, portability or objection, or withdraw consent where processing relies on it. Withdrawal does not invalidate lawful earlier processing. You may also raise concerns about solely automated decisions where the law provides protection.
Email info@oddriva.app; no particular form is required. We may seek proportionate information to establish that a request concerns your data, but will not routinely ask for a complete identity document by email. We will respond within applicable legal time limits and explain any lawful limitation, refusal or extension and the challenge route. Account closure and deletion are related but distinct requests.
You may complain to the Nigeria Data Protection Commission through its official website without giving up another available remedy or accepting our internal decision.
11. Automated rules and human decisions
The application applies rules to submission quotas, timing, input formats, authentication and access restrictions. These can reject invalid submissions or prevent unavailable actions. The account terms explain the main research limits.
Email confirmation demonstrates mailbox control. A human reviewer separately approves or rejects posting access and records a reason. The system does not automatically place bookmaker tickets or send payouts. A future withdrawal would still require separate administrator approval after quote acceptance and review of transfer evidence; an entered hash alone would not prove payment.
Contact support to challenge incorrect information, an access decision or a calculation and request appropriate human review. A score or short run of results does not by itself prove identity, eligibility, profitability or misconduct.
12. Adults and changes
Oddriva is intended for adults aged at least 18 who meet any higher applicable age requirement. It has no parental-consent route for underage participation. If we learn an account is ineligible by age, we will assess the report, restrict access as appropriate and handle its information lawfully.
We will date adopted versions and explain material changes before new processing where required. Updating a notice does not replace necessary consent or another legal requirement. Contact ODDRIVA LTD at info@oddriva.app about your information or the version that applies.