Privacy Policy

1. Who is responsible

Predixn is operated by ID GROUP LTD, a private company limited by shares registered in England and Wales under company number 16722536. ID GROUP LTD decides why and how your personal data is processed, and is the controller for it.

You can write to us about privacy at privacy@playpredixn.com, or use the privacy request form, which returns a reference number you can quote. Both reach the same place.

We have not appointed a data protection officer, and privacy@playpredixn.com is not one — it is a role address for privacy correspondence. Privacy requests reach the same small team that builds the product.

RelatedMake a privacy request

2. The short version

• We ask for an email address and a password. Everything else is generated by playing.
• We never store your password. We store a one-way hash of it and cannot reverse it.
• There are no analytics tools, no advertising trackers, no tag manager, no pixels and no session recording anywhere in this product.
• Exactly one cookie exists, and it is the one that keeps you signed in.
• We do not sell personal data, and we do not share it for advertising.
• Some things you do are public by design: your username, your display name, leaderboard positions, and community activity.

RelatedCookie Policy

3. Account data

To hold an account you give us an email address, a username, and a password. The email address is used to sign you in, to reset your password, and to reach you about your account. It is stored on your account record and is never shown on a public profile.

Your password is never stored. What we store is a bcrypt hash, which is a one-way transformation — we cannot read your password from it, which is also why we cannot tell it to you if you forget it.

Your account record also carries a display name, your role, and your account status, which is what allows us to suspend an account that breaks the rules.

If you sign in through Telegram, we store the link between your Predixn account and your Telegram identity. That link is only ever visible to you. Unlinking removes it.

4. Sessions and sign-in security

When you sign in we create a session. The session token is 256 bits of randomness sent to your browser in a cookie; only its SHA-256 hash is kept on our side, so a copy of our database does not yield a working session.

Sessions expire after 30 days. They are deleted when you sign out, when you reset your password, and when you unlink Telegram.

When someone asks to reset a password, we record the request: a hashed token, when it expires, whether it was used, the IP address the request came from, and the browser user agent string. The IP address and user agent are kept because a password-reset flow is the part of any product most worth attacking, and without them an attack is invisible.

One consequence worth naming: a used reset record is marked as used rather than deleted, so the IP address and user agent on it are kept rather than erased.

5. What you create by playing

Playing generates data, and it is the substance of the product rather than a by-product of it:

• Predictions, the tokens committed to them, and how each was graded.
• Your token wallet and its transaction history.
• Your rating, division, season history and achievements.
• Duels and rivalries, including who you played and how it ended.
• Follows, public moments and activity events shown in the community feed.
• Notifications sent to you and your notification preferences.
• Your acceptance of the age and terms notice.
• Your chosen interface language, when you are signed in.

None of this is inferred about you. It is a record of things you did in the product.

6. What other people can see

Some of the above is public because the game would not work otherwise. Your username, display name, rating, leaderboard position, achievements, public moments and community activity can be seen by other players and by anyone visiting a public profile.

Your email address, your account status, your wallet, your notification settings and your individual prediction detail are private to you. Administrators can see them where they need to in order to operate the service.

7. Advertising data

Predixn shows advertising, and — only if you have agreed to it in Privacy choices — we record when an advertisement is displayed and when one is pressed. If you have not answered, or you turn it off later, the advertisements still appear and neither is recorded.

A record holds the placement it appeared in, the page it appeared on, the interface language the campaign was selected for, and your account id if you were signed in at the time. If you are signed out there is nothing on the record that identifies you: we do not generate a visitor identifier, we do not store anything on your device for this, and we do not work out where you are.

This exists so we can report on placements and pay for the product. It is not used to build a profile of you, it is not shared with an advertiser at the level of an individual, and it is not combined with any third-party dataset — there is no third-party advertising technology in this product at all.

We do not currently delete these records on a schedule, and we would rather say so than state a period we do not apply.

RelatedAdvertising PolicyWhat consent covers

8. When you contact us

A message sent through any of our contact forms is stored as a support record: the category you chose, your email address, your name if you gave one, the subject, the message, and whatever category-specific fields the form asked for. We add a reference number and, where relevant, your account id if you were signed in.

We use it to answer you and to keep a record of what was asked and what we did. Every status change an operator makes is recorded against the record.

Please do not put a password, a session token, a reset link, or payment details into a contact form. No route we operate ever needs one, and anything you send is stored.

RelatedAll contact routes

9. Logs

Our servers write operational logs: a random correlation id per request, the route path, the outcome, and sanitized error information. Log output passes through a single redaction layer that strips both known secret values and secret-shaped strings.

Two things in logs are worth naming rather than glossing over. If an email fails to send during a password reset, we log the account id as a handle so it can be investigated — that is personal data in a log line. And a request rejected for coming from an untrusted origin has that origin recorded, stripped of control characters and truncated.

IP addresses are used in memory for rate limiting, bucketed by network rather than kept per request, and are not written to the log line.

10. Why we are allowed to process this

We process your personal data on the following bases:

• To provide the service you asked for — your account, your predictions, your rating, your duels. This is performance of the agreement between us.
• To keep the service safe and working — rate limiting, abuse handling, security logging, moderation. This is our legitimate interest in operating a product that is not overrun.
• To fund a free product — showing advertising. That is our legitimate interest in keeping Predixn free to play.
• Measuring that an advertisement was shown or pressed is a separate thing and rests on a separate basis: your consent, given in Privacy choices and taken back in the same place. We do not treat it as a legitimate interest, because it is the kind of processing you are entitled to refuse without losing anything.
• To answer you when you get in touch — handling your support, privacy, abuse or security message.
• To meet legal obligations where one applies to us.

11. Who else is involved

We currently use these necessary external service providers, and no others:

• Cloudflare — our domain name service and the network your request reaches before it reaches us. It answers the lookup that turns playpredixn.com into an address, terminates the encrypted connection, and absorbs denial-of-service and other hostile traffic before it can reach the application. Doing that means handling the request itself: the address you connect from, the page you asked for, your browser user agent string, and the response we sent back. From that traffic it produces counts we can see in its own dashboard — how many requests arrived, from where, how many it turned away. It also keeps temporary copies of files that are the same for everybody — scripts, stylesheets, images — close to you, so they load faster. Predixn itself does not run there: the application and your account data are on Render, described next.
• Render — our hosting provider, and where the application and the database actually run. They run in Render’s Frankfurt region, and Render’s own edge is in turn fronted by a content delivery network of theirs, which happens also to be Cloudflare under an arrangement of Render’s rather than ours, so request metadata passes through that too in transit.
• API-Football — our sports data provider. The traffic is outbound only. Nothing about you is sent to them.
• Our email relay — used to send password-reset messages and contact acknowledgements. It receives the recipient address and the message.

There is no analytics provider, no advertising network integration, no error-reporting service and no customer-messaging tool in the product itself. We do not add Cloudflare Web Analytics, and there is no Cloudflare script, beacon, pixel or tag manager on any Predixn page — nothing measures you in your browser. What Cloudflare reports to us comes from requests passing through its network on their way to us, not from anything running on your device.

12. Where your data is

The application and its database run in Frankfurt, in the European Union, and that is not changed by anything else on this page. Cloudflare, our email relay and our sports data provider each operate their own infrastructure, which may be outside the UK and the EEA. Cloudflare in particular answers from whichever of its locations is closest to you, so your request may be handled outside Europe on its way to an application that is not.

If you would like to know what safeguards apply to a particular transfer, ask us through the privacy route and we will tell you what we have.

13. How long we keep things

With two exceptions, nothing is deleted on a schedule.

Sessions expire after 30 days and expired ones are removed. Password-reset tokens expire after 30 minutes. Everything else — your account, your predictions, your rating, advertising interaction records, activity events, notifications and support records — is kept while your account exists.

We would rather tell you that than quote a retention period we do not actually apply. If that changes, this section changes with it.

14. Your rights and how to use them

Depending on where you live, you may have the right to ask for a copy of your personal data, to have it corrected, to have it deleted, to object to or restrict certain processing, and to complain to a supervisory authority. In the UK that authority is the Information Commissioner’s Office.

Use the privacy request form or write to privacy@playpredixn.com, whichever suits you. What happens next is a person reading it either way. There is no automated export in this product and there is no self-service account deletion — we are telling you that in advance so you know what to expect.

Where we rely on your consent — the optional device storage and the advertising measurement described in the Cookie Policy — you can take it back whenever you like, from Privacy choices in the footer of any page. It takes effect at once, it does not require you to contact us, sign in or clear your browser, and it does not make what was already done under that consent unlawful.

Before we act on a request that would disclose or destroy data, we will verify that the request comes from the account holder. The form itself will never confirm whether an email address has an account; that answer only comes after verification, and only to you.

We do not state a fixed response time. A person handles each request and we will answer as quickly as we reasonably can, rather than promise a deadline we cannot guarantee.

RelatedMake a privacy requestCookie Policy

15. How we protect it

Passwords are hashed with bcrypt. Session tokens are stored only as hashes. Traffic is encrypted in transit. The API accepts JSON and nothing else, rejects unsafe requests from untrusted origins, applies per-caller rate limits, and routes every unexpected error through one boundary that logs a redacted line and returns an opaque incident id.

None of that is a guarantee. No online service can promise it will not be breached, and we are not going to be the one that does.

RelatedReport a security issue

16. Children

Predixn is for adults aged 18 and over. We do not knowingly process the personal data of a child. If you believe a child holds an account, tell us and we will close it.

RelatedReport a concern

17. Changes to this policy

When this policy changes materially we will make the change visible in the product rather than only editing this page. The date at the top of the page tells you which version you are reading.