Sign in

BLINK · TRUST & COMMUNITY

Privacy Policy

What we collect, what becomes public, how information is used and how you can exercise your choices.

Effective and last updated:

1. Who this notice covers

This policy explains how the Blink operating team handles personal information through goblink.gg and its account, community, TiersGO, giveaway and support services. Contact the team through Help & requests; an account is not required. Third-party websites and game services have separate privacy practices.

We distinguish public contributions from private account and operational records below. Acknowledging this policy does not give blanket consent to optional tracking or unrelated marketing.

2. Information we handle

  • Account information: email address, public name, avatar, password hash, creation details, verification and reset tokens, sessions, account status, and records of agreement to a policy version and minimum-age confirmation. Registration does not ask for your full birth date.
  • Contributions and activity: posts, images, comments, replies, reactions, saved items, followed games, reports, notifications, experience events, TiersGO templates, rankings and saved versions. Giveaway records are described below.
  • Support and moderation: request type, subject, links, correspondence, status, account connection and staff responses; reports, decisions and restricted audit records. Avoid unnecessary sensitive information in messages.
  • Technical information: service requests can reveal your IP address, browser and device details, requested URL and time, and security or error information. Hosting infrastructure processes this to deliver and protect the site. The application also stores hashed rate-limit identifiers derived from information such as IP or email addresses. Hashing does not necessarily make information anonymous.

3. What other people can see

Your public name, avatar, level and contributions can appear to visitors, search engines, shared links, downloaded ranking images and creator leaderboards. Others can copy public content. A poster can reveal its author, ranking, date and engagement totals.

Email addresses, password hashes, session credentials, support correspondence and full prize codes are not displayed in public profiles or posts. Saved items and previous TiersGO versions are account features rather than public history pages. Aggregate reactions and ranking counts are public. Do not put private information in names, images or public contributions.

Authorized staff access information needed for account administration, moderation, support and giveaways. A private request link is an access credential: anyone with the full link can read and reply to that request. Do not share it publicly.

4. Why we use information

We use information to create and secure accounts, deliver contributions, provide rankings and saved items, send service notifications, run giveaways, handle requests, investigate abuse, maintain the site and comply with applicable obligations.

Where a legal basis is required, it depends on the purpose: performing our agreement for requested account and community functions; legitimate interests in operating and securing the service and resolving disputes, balanced against your rights; legal obligations; or consent where required for optional uses. You may object to legitimate-interest processing and withdraw consent for consent-based uses. Withdrawal does not affect earlier lawful processing.

Verification, reset and prize emails support requested services. Registration is not a promotional email subscription. We do not sell personal information or use account activity for third-party behavioral advertising in the current service. Material new uses or tracking features will require updated notice and any choices or consent required by law.

5. Cookies, local storage and embeds

  • The blink_reader cookie keeps you signed in for up to seven days. It is an HttpOnly session credential with browser security restrictions. Signing out invalidates that session. Verification and reset links expire after 30 minutes.
  • Search keeps up to six recent queries in browser local storage until cleared. Use the search history’s Clear control or remove site data. Queries also appear in requested URLs; they are not necessarily confined to the device.
  • The service worker stores an offline fallback page. Browser caching can retain site resources. Clearing site data removes local storage and caches, not your server account or public contributions.
  • Embedded videos load the provider’s player when you choose to play them. The provider can then receive technical information and apply its own storage rules. A privacy-enhanced player does not mean it receives no information. External links lead to services with their own policies.

6. TiersGO and automated features

TiersGO stores your current ranking, earlier saved versions and template images and labels. Current eligible rankings contribute to community statistics, and activity can affect creator positions and medals. Earlier saved versions are available through your account. Removing or hiding content can change totals.

Software orders feeds, calculates experience and rankings, applies rate limits, and checks giveaway eligibility and random selection. These features use activity and published rules rather than determining your legal status or creditworthiness. Ask for human review through Help & requests if an automated check affects you incorrectly.

7. Giveaway information

We record entries, rule acceptance, qualifying contributions, eligibility checks, draw outcomes, deadlines, prize assignments and redemption status. A protected identifier derived from email helps enforce entry limits within a campaign; it is pseudonymous, not necessarily anonymous.

Full codes are stored encrypted and shown through the winning account. Authorized editors manage inventory and status. A winner’s redemption report and staff confirmation are distinct; Blink does not automatically verify activation with Steam or other platforms. Emails link to your account rather than include full codes.

Account deletion removes the direct account link from retained giveaway records but does not automatically erase draw, inventory or protected entry-limit records. These may be needed to prevent repeat claims, resolve disputes and meet legal obligations. Retention is assessed against campaign, dispute and legal needs; these records currently have no automatic expiry. You may request review or deletion where applicable.

We do not routinely give sponsors participant email lists. If a prize requires information sent to a fulfillment partner, the campaign must explain what is needed, who receives it and why before collection or disclosure.

8. Providers, disclosures and international processing

Cloudflare provides hosting, delivery, databases, media storage and security infrastructure. Resend processes email delivery for verification, password reset and prize notifications when used. They receive information necessary for those functions, such as request data or email recipients and content. Their own privacy notices also describe processing in their own capacity.

We may disclose information when reasonably necessary for valid legal process, safety, fraud prevention or legal claims. We assess requests for scope and validity. A rights complaint may need to be shared in substance with the affected person for a fair response, avoiding unnecessary personal disclosures.

If Blink is transferred or reorganized, information may be transferred with appropriate protection and notice where required. Providers operate internationally, so processing is not necessarily confined to your country. Where law requires cross-border safeguards, those requirements must be addressed for the relevant transfer. Contact us for information about your circumstances.

9. Retention, deletion and security

Account records are generally kept while active. Verification and reset tokens become unusable after 30 minutes; expired records are cleaned up during later token operations. Sessions expire after seven days and expired session records are cleaned up during sign-in operations. Rate limits stop applying at their configured reset time; expired records are cleaned up during token operations.

Account deletion removes live account records and associated contributions and interactions through deletion routines, including private ranking history, policy acceptance and the author’s live moderation-edit history. Media cleanup can run later. Independently retained support and giveaway records have different retention needs. Deletion does not instantly erase provider backups, security logs, search-engine caches or copies others saved; those follow their relevant retention or deletion process.

Private support cases are automatically removed 90 days after their last update when resolved, or after one year without activity, unless authorized staff record a specific legal or dispute preservation reason. Deleting an account removes the direct account link but not necessarily correspondence. Staff should periodically review preservation needs.

Other operational logs and legally retained records depend on purpose, sensitivity, security or dispute needs, legal obligations and provider arrangements. We do not promise a fixed period we cannot enforce. Request assessment of a particular record if you need more detail.

We use access restrictions, password hashing, session protection and encryption of prize codes. No online service is completely secure. Protect passwords and private request links and report suspected unauthorized access.

10. Your choices and privacy rights

Your profile provides supported controls for your public name, avatar, contributions and account deletion. Manage saved items and follow choices, clear local search history, and choose whether to load videos. Contact us about information you cannot change through those controls.

Depending on applicable law, rights may include access or a copy, correction, deletion, restriction, portability, objection to certain uses, withdrawing consent and complaining to a data protection authority. You do not need to create an account to make a request. We do not retaliate for exercising a protected right.

Select Privacy in Help & requests and explain what you need. We may verify your account connection or request clarification before disclosing or changing private information. Verification should be proportionate; do not send passwords or identity documents through the initial form. We will respond within applicable legal time limits and explain a refusal or extension where required.

11. Younger users

Accounts are for people aged 16 or older who meet any higher local minimum, with guardian permission where required below the local age of majority. Age confirmation is an assertion, not independent verification of every user’s age.

If a child below the minimum age has provided account information, contact us. Parents and guardians can use Help & requests without registering. We will investigate and take appropriate steps, including removing an ineligible account and addressing related information as required by law.

12. Changes and contacting us

We will update this page as practices change and give appropriate notice of material changes. The date above identifies the current version. Contact the Blink operating team through Help & requests. Save the private link supplied after submission and return to it for replies; the form does not automatically send email updates.