KickPick.club
Privacy policy
Updated 21 July 2026
This notice explains how Poggers Oy processes personal data when you use KickPick.club, including private friend-group drafts and site-wide season competitions. It covers the free public launch; payment and optional AI features are not active.
Controller
The controller is Poggers Oy (Business ID 3171525-2), Tohtorinpolku 3, 33720 Tampere, Finland. Poggers Oy has not appointed a separate data protection officer. Privacy and support requests can be sent to [email protected].
Data we process and where it comes from
We receive data directly from you and your browser, from Google when you choose Google Sign-In, and from other members through shared group actions. API-Football supplies factual match data, not personal data. KickPick.club processes:
- Account and profile data: Google’s stable account identifier and Google-verified email address, the KickPick.club nickname you choose when you register, the illustrated avatar you select, your Finnish/English language and sign-in timestamps. We ask Google only for the “openid” and “email” permissions, so we never receive your real name or your Google profile picture, and we never receive your Google password.
- Your nickname and its reservation: your nickname is the only name anyone sees in KickPick.club, and it must be unique across the whole service. To make that possible we store a normalised form of it in a reservation record together with your internal member ID. A nickname is permanent — it cannot be changed after you register. Deleting your account is the only way to stop using it, and doing so releases it for someone else to claim.
- Group and game data: member and commissioner roles, group names, creator member-removal choices, group-scoped rejoin blocks, current lobby presence, matchday settings, immutable draft actions, card ownership, scores, settlement evidence and recap output. Nicknames, avatars, current presence and game activity are visible to the other members of the same group. If the group chooses deferred missed turns, current absence may also let later turns skip without another wait until a live connection registers return. Presence itself and the stored block list are not added to the permanent game history or shown publicly.
- Site-wide competition data: registration, your nickname and illustrated avatar, independently selected fixture and round-wide cards, save times, scores, settlement evidence and leaderboard totals. Anyone who opens the competition can see participant nicknames, illustrated avatars, points and the opaque internal participant reference used to retrieve that avatar; it is not a Google identifier or session credential. Registered participants can see each selection group only after its server-owned deadline: fixture kickoff for fixture cards and first kickoff for round-wide cards. Email addresses and Google identifiers are not shown there.
- Security and device data: an opaque session cookie; keyed hashes of session, invite and public-share tokens; IP address, user-agent and request metadata in access/security logs; and short-lived realtime connection identifiers.
- Optional notification data: the browser push endpoint and encryption keys. A turn notification contains the group name and a first-party group link in an encrypted Web Push payload.
- Strictly bounded product analytics: internal member/group identifiers, event type, timestamp, group size and turn duration. The schema rejects names, email addresses, Google identifiers, tokens and free-form text.
Purposes and legal bases
Google account data is required to create and maintain an account. If you do not provide it, you can view the public pages but cannot create or join a group or play in a site-wide competition. We do not ask for precise location, contacts, payment details or an advertising profile, and we do not use personal data for marketing or track you across other sites.
- Contract: account, group, site-competition entry, scoring, recap and sharing data are necessary to provide the service and perform the terms. The draft-start service email is necessary for the asynchronous private group to proceed and is not marketing.
- Legitimate interests: limited product analytics, access/security logging, service protection, abuse prevention and support are necessary for Poggers Oy’s interests in operating, securing and improving the service. We minimize the fields and retention and balance those interests against your rights. You may object as described below.
- Consent: browser turn notifications are optional. You can withdraw consent at any time by disabling notifications; this does not affect processing before withdrawal.
- Legal obligation: a specific record is restricted and retained only when applicable law requires it.
Cookies and browser storage
KickPick.club uses first-party storage needed to provide the requested service: the HttpOnly, Secure and SameSite=Lax session cookie expires after at most 30 days; session storage holds the one-time OAuth state and PKCE verifier only while you sign in; local storage remembers the language until you change or clear it; and the service worker caches versioned application files for offline/reliable use. KickPick.club does not use advertising or third-party analytics cookies and does not load Google scripts on its pages. Google may read or set its own cookies after you activate sign-in and the browser is redirected to Google; Google processes those under its own terms as the identity provider.
Recipients and service providers
We disclose only the data needed for each function. Authorized Poggers Oy personnel may access data when required for support, security, incident response or legal obligations. The active external recipients are:
- Amazon Web Services (processor) — hosting, database, queues, logs, content delivery and transactional email. Primary application data is held in the EU (Ireland). A draft-start email contains the destination address, group name and the first player’s nickname.
- Cloudflare (processor) — DNS, TLS termination, content delivery, firewall and rate limiting. It processes IP addresses and HTTP/network metadata at its global edge.
- Google (independent identity provider) — renders the sign-in control and supplies the Google account identifier and your verified email address after your sign-in choice. It supplies nothing else: we do not request the permission that would give us your name or profile picture.
- Your browser’s push service, such as Apple, Google or Mozilla — routes encrypted notifications when you enable them. The provider sees the push endpoint and delivery metadata but cannot read the encrypted payload in transit.
- Other players, public site-competition visitors and public-share visitors — nicknames, avatars, current lobby presence and group activity are disclosed inside a private group; site-competition nicknames, illustrated avatars and points are visible to anyone, while locked entries remain visible only to registered participants; avatars are not included in public recaps, and a recap is public only when a member deliberately creates and distributes a share link.
Inactive and data-free providers
API-Football and The Odds API supply football facts; KickPick.club sends them no personal data. OpenAI recap generation and Stripe billing are disabled for the free launch, so they do not receive data. They cannot be enabled until the processing register, contracts, transfer assessment, retention and this notice are reviewed and updated.
International transfers
Primary application storage is configured in AWS’s Ireland region. Cloudflare’s global network, Google, browser push providers and provider support/sub-processors may process data outside the EU/EEA. Where GDPR requires a transfer mechanism, transfers rely as applicable on a European Commission adequacy decision or the Commission’s Standard Contractual Clauses together with an assessment of supplementary safeguards. You may request more information or a copy of the applicable safeguards from [email protected].
Retention and deletion
You can delete your account from the profile page or ask for help at [email protected]. Deletion removes every private group the account created, for all of its members. In a private group created by someone else, your membership is depersonalised in place instead: your nickname is replaced by a neutral placeholder, your internal member ID is removed from that row, and your remaining draft turns are skipped, while the picks, scores and settlement evidence that form the group’s shared ledger are retained without identifying you. If that group is still a lobby with no draft, nothing has been recorded yet and your membership is removed outright. The confirmation explains this before deletion. In a site-wide competition, deletion removes only your registration, entries, scores and settlement records, not other players’ history.
- Sessions expire after 30 days, and signing out deletes the server-side session immediately.
- Account, profile, group/game, delivery-marker and related product-analytics data remain while the account is active. If you do not sign in for 13 consecutive calendar months, an hourly process deletes the account and the same related data. A successful sign-in restarts the period.
- Site competition registration, entries, scores and settlement evidence remain while your account is active. Self-service or inactivity deletion removes your rows and decrements the participant count; other participants’ rows remain.
- A permanent lobby rejoin block stores only the group ID, your internal member ID and the block timestamp. It remains until that group is deleted or your account is deleted; it is used only to reject another invite redemption for that lobby.
- Poggers Oy’s AWS access, security and application logs, including IP addresses and pseudonymous internal identifiers, are retained for at most 90 days in production. Providers may retain their own narrowly scoped security records for the periods stated in the applicable processing agreement.
- An address added to the AWS SES account-level bounce/complaint suppression list is retained for at most 90 days. KickPick.club requests deletion of the current address sooner when the account is deleted.
- Push subscriptions remain until you disable notifications, the browser reports that the subscription has expired, or the account is deleted. A queued push payload expires after one hour.
- Public recap links and their frozen snapshots expire after 30 days. Realtime tickets expire after 60 seconds and connection records after at most three hours.
- Self-service and inactivity deletion remove sessions, profile and Google account data, your nickname reservation, your avatar selection, push subscriptions, memberships, lobby rejoin blocks, the groups the account created, invitations, drafts, site competition registrations and entries, published cards, email delivery markers, picks, scores, recaps, related analytics events and active public recap links. Releasing the reservation returns your nickname to the pool, so another player can later choose it. In a group created by someone else, the drafts, published cards, picks, scores and settlement evidence are retained without your nickname or member ID, and the group’s recaps and public recap links are still deleted.
- Deleted active database data can remain only in encrypted disaster-recovery backups until the backup retention period ends, currently no more than 35 days. Backups are not used for ordinary product access and deleted data is not intentionally restored to active use.
- Where applicable law requires specific records to be retained, those records may be restricted and kept only for that legal purpose. KickPick.club does not currently collect payment records during the free launch.
Shared recap links
Sharing a recap is an explicit action that creates a public link. The page shows the group name, recap text, nicknames, ranks and points — nothing else — and expires after 30 days. Anyone with the link can open it, so share it as you would any public page.
Automated processing
Private-group draft order and card ownership, site-entry locking, scoring and settlement are decided by deterministic application rules from validated match data. The inactivity process automatically deletes accounts after 13 months, but KickPick.club does not make decisions based solely on automated processing that produce legal or similarly significant effects, and it does not profile players for advertising. AI never decides game results.
Your rights
Where GDPR applies, you may request access, correction, deletion, restriction and portability of your data; object to legitimate-interest processing; and withdraw notification consent. Email [email protected]. We may verify your identity and normally respond within one month; requests are normally free. You may complain to the Finnish Data Protection Ombudsman (tietosuoja.fi) or your local EEA supervisory authority.
One correction we cannot make is your nickname. It is chosen by you, it is unique across the service, and it is permanent by design — there is no way to change it, in the app or through support. If you no longer want the nickname you chose, delete your account; that releases it and you can register again with a different one. Your avatar and language can be changed at any time from your profile.
Age limit
KickPick.club is intended for adults. Because the game is built on betting-style mechanics — prediction cards priced from bookmaker odds — we set an 18-year age boundary even though no real money, deposit, withdrawal or cash prize is involved. The service is not for people under 18 and does not knowingly collect their data. If you believe an under-18 person has created an account, contact us so we can investigate and delete it.
Changes to this notice
If this notice changes in a way that matters, the change is announced in the app before it takes effect. This page always shows the current version.
Privacy and support contact: [email protected]
Play KickPick.club