Privacy policy

TransferRank is currently operated by the TransferRank team. For privacy questions, account requests, or legal notices relating to this policy, contact heytransferrank@gmail.com.

This policy applies to the TransferRank website, application, authenticated product surfaces, community submission tooling, and related operational support flows. It covers information provided directly by users, information generated through product use, and technical data produced when pages and APIs are requested.

It does not govern third-party sites, social platforms, publishers, or video services linked from TransferRank. When you leave the product or authenticate through an external provider, the terms and privacy policies of that provider also apply.

• Identity and account data such as Clerk user identifiers, username, email address, authentication state, and basic public profile metadata required to operate the account.
• Preference and profile data such as favourite club selections, follows, onboarding choices, saved state, and any settings used to shape product output.
• Community activity data such as story submissions, moderation outcomes, ratings, reactions, and related anti-abuse metadata.
• Technical and diagnostics data such as browser type, device characteristics, page requests, approximate IP-derived region, error logs, request timing, and security signals.
• Support and communications data when you report bugs, request deletion, ask for help, or otherwise contact us through the product.

• To authenticate users, protect accounts, and maintain signed-in sessions.
• To personalise feeds, ranking context, follows, club-specific views, and onboarding-dependent surfaces.
• To store and process community submissions, associate them with the submitting account, and support moderation and audit review.
• To diagnose product issues, investigate suspicious activity, detect abuse, and improve availability, performance, and UX quality.
• To generate aggregate product insights about which flows succeed, fail, or are abandoned, without selling that information onward.
• To comply with legal obligations, enforce our terms, and respond to valid requests from regulators or law enforcement where required.

Depending on the jurisdiction that applies to you, we rely on a combination of contractual necessity, legitimate interests, compliance obligations, and consent where required. Legitimate interests include running the service securely, preventing abuse, understanding how the product performs, and moderating community features responsibly.

We disclose data only to providers that help operate the service, such as authentication, hosting, database, observability, analytics, and infrastructure vendors. Those providers process data on our behalf under their own contractual and operational controls.

• Clerk for authentication, session handling, and account identity services.
• Supabase for application data storage, row-level access control, and database-backed product features.
• Vercel for frontend hosting and delivery.
• Railway for backend API hosting and scheduled ingestion jobs.
• Model providers such as Google Gemini, Anthropic, and OpenAI where editorial, enrichment, or AI-assisted product functions are invoked.
• External football and media inputs such as API-Football and YouTube when those integrations are used to enrich product features.

Some of these providers may process limited request metadata, logs, or content fragments as part of operating the feature they supply.

If you submit a story link, request a new source domain, rate a source, or participate in similar community features, we store the submitted URL, your account identifier, timestamps, moderation state, and related review metadata. This is necessary to prevent spam, avoid duplicate submissions, and maintain an audit trail for moderation decisions.

Submitted links may include third-party URLs, including social posts, publisher articles, or video references. We store those links and related processing results as part of the submission record. Submission content may be reviewed by moderators or internal operators where moderation or debugging requires it.

We retain account and product data for as long as the account remains active and for a reasonable period afterward where needed for fraud prevention, moderation history, service continuity, legal compliance, tax records, or dispute handling.

Some data may be anonymised or aggregated once it is no longer necessary to keep it in identifiable form. Backups, security archives, and operational logs may persist for longer where standard infrastructure retention windows apply.

Support tickets, moderation notes, raw diagnostics, and deleted-account backups are kept only for as long as reasonably necessary for support, security, abuse prevention, legal compliance, or operational recovery.

TransferRank is operated through cloud services and infrastructure providers that may process data in multiple countries. By using the service, you understand that your information may be transferred to and processed in jurisdictions different from your own, subject to the safeguards offered by the relevant provider arrangements and applicable law.

• You can update account-facing profile details through the product where those controls are available.
• You can clear browser storage or revoke sessions through the authentication provider’s account controls.
• You can ask for account deletion, data export, or privacy-specific support through the help page.
• Where applicable law grants you additional rights, such as access, correction, objection, restriction, or erasure, we will review and respond in line with those obligations.

For privacy-specific requests, contact heytransferrank@gmail.com.

TransferRank is intended for a general football audience, but it is not directed at young children. If we become aware that personal data has been provided in a way that violates applicable age restrictions, we may remove the relevant account or information.

We may update this policy as the product evolves, especially when new account features, moderation systems, analytics tooling, or commercial surfaces are introduced. Material changes will be reflected on this page by updating the effective date and the policy text itself.