01
Controller and scope
METRIKA processes the data needed to operate this product and its public surfaces.
Who is responsible
METRIKA is the commercial name of the service acting as controller for the processing described here. Contact us at info@metrika.tips or through Contact. Applicable contractual identification is also provided during payment and in billing documents.
What this covers
This policy covers www.metrika.tips, the dashboard, PWA, public profiles and links, community, Support, METRIKA Intelligence, Vision, Discovery, and related communications. Third-party sites and services have their own policies.
How we decide
We apply data minimisation, purpose limitation, security, transparency, and user control. We do not ask for bookmaker passwords or full card details. A feature should not request data it does not need.
02
Data we process
The categories depend on the features you choose to use.
Account and profile
We process account identifiers, email, name, username, avatar, language, country, time zone, currency, profile type, preferences, plan, and verification status. Authentication handles credentials; METRIKA does not need your password in readable form.
Bets and content
This includes bankrolls, bets, selections, odds, stakes, results, notes, ticket screenshots, metrics, imports, Intelligence and Support conversations, posts, messages, reactions, profiles, and links you create. Some fields can reveal financial habits; choose carefully what you share.
Usage, device, and security
We may process IP address, browser, operating system, device identifiers, cookies, session events, feature usage, errors, telemetry, notification consent, and anti-fraud signals. Fingerprint helps prevent abuse and multiple-account promotion fraud, but failure alone does not block access.
Plans, Tokens, and payments
We retain plan, status, periods, amount, currency, payment references, pack purchases, and Token ledger movements. MONEI processes the payment method; METRIKA does not store your full card number or security code.
03
Purposes and legal bases
Each use must have a defined purpose and valid legal basis.
Performing the contract
We use data to create and maintain accounts, record bets, calculate metrics, manage bankrolls, sync preferences, run Vision and Intelligence, enable Discovery, process payments, answer Support, and display content you choose to publish. Contract performance is the main basis.
Security and integrity
We prevent fraud, promotion abuse, unauthorised access, spam, and attacks; preserve verified-history integrity; and diagnose incidents. We rely on legal obligations and our legitimate interest in protecting users and the platform, balanced against your rights.
Improvement and measurement
We analyse performance, errors, cost, and feature usage to improve quality, capacity, and experience. Where possible we use aggregated or pseudonymised data. We do not use your private history for third-party advertising.
Communications
We send transactional messages about account, security, payments, Support, and material changes. Marketing and push notifications depend on consent or preferences and can be disabled, except strictly necessary notices.
04
Intelligence, Vision, and automation
We explain what enters processing and what control stays with you.
Submitted content and context
To respond, Intelligence may use your message, files, language, time zone, plan, bankrolls, and relevant performance data alongside available sports information. Vision processes a ticket screenshot to extract a draft. Context is limited to what the requested task needs.
AI and data providers
We may send strictly necessary content to model, search, and sports-data providers acting as processors or service sources. We apply contracts, access controls, and transfer safeguards where required. Avoid including unnecessary sensitive data in messages or images.
No automated legal decisions
Analysis, extraction, and suggestions do not make decisions with legal or similarly significant effects about you. You review before saving a bet or confirming a result. Fraud signals may trigger additional checks, but material measures can be reviewed.
05
Profiles, community, and visibility
Private stays private until you choose a publishing surface.
Public profiles and links
If you enable a public profile, bankroll, or link, selected fields and statistics appear according to its settings. Visits may generate technical audience metrics. Check the public view before sharing; others may copy what you publish.
Forum, messages, and directory
Posts, reactions, and directory profile elements are visible according to the surface. Direct messages are shown to participants and may be reported or reviewed where needed for safety and moderation. Do not publish another person’s data without a valid basis.
Visibility controls
You can change visibility, withdraw links, edit permitted fields, and leave public surfaces. Some verified records may retain integrity or limited audit history to prevent manipulation, always subject to your rights and the disclosed purposes.
06
Cookies, device, and notifications
Technical tools maintain sessions, preferences, and security.
Cookies and local storage
Essential cookies maintain authentication, security, language, and operation. The browser may also store preferences and PWA state. Blocking essential items can prevent sign-in or product use. Non-essential controls follow the available settings.
Device intelligence
Fingerprint and signed cookies create signals to protect accounts, limit abuse, and detect multiple accounts. We may store a pseudonymous identifier, confidence data, and access events. We do not use the signal to infer civil identity or sell advertising profiles.
Push and permissions
Web notifications start only after your permission. We store the endpoint and technical keys required to send them. You can withdraw permission in settings or the browser, and we remove subscriptions that are no longer valid.
07
Providers, transfers, and disclosure
We share only what is needed to operate or meet an obligation.
Provider categories
We use infrastructure and database, authentication, payment such as MONEI, email, support, analytics, device security, storage, AI, search, and sports-data providers. They work under contract with access limited to their role.
International transfers
Some providers may process data outside your country or the European Economic Area. Where required, we rely on adequacy decisions, Standard Contractual Clauses, or other recognised safeguards and assess transfer information and risk.
Legal duties and corporate events
We may disclose data when required by a competent authority, to defend rights, or to protect people and systems. A corporate reorganisation would transfer data only with confidentiality, notice, and continuity of protection obligations.
08
Security, retention, and deletion
We protect data for as long as needed, not forever by default.
Protective measures
We use encryption in transit, access controls, per-user isolation, event logging, backups, privilege reviews, and incident processes. No system is infallible. If a breach creates relevant risk, we will act and notify as required by law.
Purpose-based periods
We retain account content while active; payment and obligation records for legal periods; Support, security, and audit data proportionately; and backups until rotation. We then delete, anonymise, or restrict data as appropriate.
Account deletion
You can request or run deletion from the product. The process removes the account and linked data except records we must retain or keep anonymised for security, legal duties, or claims. Content already copied by third parties is outside our control.
09
Your rights and how to use them
Data protection provides concrete controls, not just information.
Access, correction, and control
Depending on applicable law, you may request access, rectification, erasure, restriction, objection, and portability; withdraw consent prospectively; and ask about automated processing. Some rights are subject to legal limits.
Submitting a request
Email info@metrika.tips or use Contact and identify the right you wish to exercise. We may request proportionate verification to protect the account. We will respond within the legal period and explain any refusal or extension.
Complaint and authority
If you believe we have not resolved your request, you may complain to the Spanish Data Protection Agency or the supervisory authority of your habitual residence, and use any other remedy available under law.
Want to exercise a right or understand a processing activity?
Write from the email linked to your account. We will perform proportionate identity checks and respond within the applicable legal period.