CHAIN LINK 3
Support the channel

Privacy

Last updated .

Chain Link 3 is a fan site for Yu-Gi-Oh! tournament coverage. This page explains in plain words what the site keeps, where it goes and how to ask us to remove something. It describes what the site's code does today. Questions go to contact@chainlink3.com.

The short version

Visiting the site

Cloudflare Pages hosts this site. Cloudflare sees your IP address and basic browser details when it serves a request. Application records for submissions, bug reports, removal requests and sync do not store raw IP addresses or user agents. This says nothing about the contents or retention of Cloudflare edge logs.

The standings, bug-report and removal forms, the Points page and the Live API use a one-way code made from your address (a SHA-256 hash) for abuse limits in server memory. It can still link requests from the same address; it is not a guarantee of anonymity. Sync uses a separate secret key, described below.

Our code keeps no request logs. Cloudflare Pages shows the logs of our server code only live, while someone is watching; they are not stored (checked 2026-10-29). Cloudflare runs and protects its network with request data under its own privacy policy: https://www.cloudflare.com/privacypolicy/

Cookies and storage in your browser

Public application code sets no visitor cookies. The calculator uses browser storage on this device (localStorage) for saved decks, journal entries, preferences and sync settings. This is separate from analytics. Tool assets can also be cached by a small background program (a service worker) for offline use.

The private operator desk uses Cloudflare Access sign-in cookies and a secure sign-in safety cookie (a CSRF cookie) to protect operator actions. These are separate from public calculator storage and cookie-free Web Analytics.

We checked our Cloudflare settings on 2026-10-29: Bot Fight Mode is off, the bot check uses no pre-clearance cookie, and our public pages send no cookies. So no Cloudflare security cookie is set on public pages today. Before we turn on a feature that sets one (for example __cf_bm or cf_clearance), we will name it on this page.

Visit counts

We count daily tool opens, preset opens, completed odds calculations and points searches, and nothing in these counts identifies a person.

Cloudflare Web Analytics is on. It adds a small script from static.cloudflareinsights.com that reports to cloudflareinsights.com. It uses no cookies. It reports summary visits and page views. Cloudflare adds the script through the dashboard setting.

An optional operator health report can send summary visit, page-view, new-code and saved-deck counts to Telegram. Those counts do not contain names, sync codes or addresses; running that report is a separate operator setting.

Video pictures and links to other sites

Our pages show pictures of YouTube videos. The pictures are copies served from chainlink3.com, so opening one of our pages sends nothing to YouTube.

We do not put YouTube players inside our pages. Clicking a video link still opens YouTube, and links to other sites, such as Facebook or YGOPRODeck, open those sites. Their own privacy terms apply there. We ask your browser not to tell those sites which of our pages you were on.

No accounts, no ads

The site has no visitor accounts, no sign-in and no ads. Our pages allow no ad scripts.

Tools and deck sync

The deck tools save profiles in browser storage on this device (localStorage): deck names, card counts and categories, calculation settings, side plans and match journal entries. A journal entry contains date, matchup, going first or second and result; it may also contain event, note, dice result, game stage, side plan and whether the hand was unplayable. Treat free text as private notes. Saved profiles, including their journals, are sent to the server only if you use sync.

Sync is optional. Creating a new sync code requires the bot check. You can also connect with an existing code. The browser keeps the secret code and version numbers used to track changes. Anyone with the code can read or change the collection; there is no account, email or recovery. Do not email your sync code or put it in a bug report.

Cloudflare D1 stores a one-way code made from it (a SHA-256 hash), not the secret sync code itself. Requests carry the secret code to find that hash. The database stores profile names and saved deck data (including journals, stored as JSON text), versions, creation and last-use dates, update times, hourly and daily counters, bytes per code and a shared content-byte counter.

To limit new codes, we keep a scrambled code of your address that needs our secret key to check (HMAC-SHA-256). The database keeps the number of codes created and the hour, not the raw address.

Limits: 5 new codes per address per UTC hour (80 new codes globally per UTC day); 50 saved profiles per code; 60 changes per code per UTC hour and 80 changes per UTC day. Each code can hold 1 MiB (about 1 MB) of saved profile data. A shared 400 MiB storage cap and a shared daily limit on database writes can pause saves sooner. If sync fails, your local deck stays on this device; check the sync message before relying on another device.

How to delete a synced deck

  1. Open the calculator where sync is on.
  2. Choose the deck in Saved profiles.
  3. Press Delete, then Confirm delete, and check that the sync operation succeeds.

A successful synced delete removes the remote profile contents, including its journal, but leaves a deletion marker (a tombstone) with the name, version and deletion time to reject stale writes. It is not a promise to erase other devices or exported backups. Stop syncing removes the code from this browser; it keeps local decks and the remote collection. Clearing site data removes local storage and cached assets, not remote data or exported files.

There is no whole-collection deletion button or endpoint. Automatic cleanup prunes expired creation-client rows when a new code is created, tombstones after 30 days, inactive codes and their profiles after 90 days of non-use, and daily quota rows after 90 days in bounded batches on later sync writes; otherwise you can delete your own decks as described above. Ask contact@chainlink3.com about options without sending the code; do not assume support can identify or erase a collection.

Ask to be removed

The removal form stores these fields in Cloudflare R2 for private manual review:

Removal requests are kept until handled. On the first Monday of each month, the operator deletes handled requests and their optional emails, including exported copies. The name stays on the do-not-name list so it is not published again. This cleanup is manual.

Requests are stored separately in removals/ and are never deleted by the submissions cleanup. Closing the beta leaves the removal form open. Nothing is removed automatically.

Report a bug

The bug form stores these fields in Cloudflare R2 under bug-reports/:

No attachments or automatic browser or session details are added to the stored report. The separate bot check reads browser signals, as explained below. Consent is required. Only the team can read reports; nothing is emailed or published automatically. Do not include private information or sync codes.

We delete bug reports within 90 days after receipt.

The same 90-day limit applies to downloaded review copies. Older reports/ records keep their existing storage rule.

Send standings

The standings form accepts pasted text, a JPG, PNG or WebP photo up to 5 MB, or both. PDF uploads are not accepted. Submit only evidence you may share. These fields go to Cloudflare R2 under submissions/:

Photos are kept as sent, including any location or camera data saved in the file (metadata). Remove it first if you do not want us to have it. Consent and bot-check fields are checked but are not stored in the submission record.

Nothing is published automatically. The private operator desk can read and export the evidence; local review copies are described below. Contact details stay private.

We keep standings text and photos until the end of the 2027 North America WCQ and delete them by 2027-08-31 at the latest. We will update this date when Konami announces the WCQ date.

To request earlier deletion, email contact@chainlink3.com with the event and receipt date, without resending sensitive evidence. The operator handles these requests manually for stored text, photos and local review copies; the desk has no delete button.

Private review and approved public results

Private review can keep local exports, photos, contact details, raw evidence, transcription, reviewer identity, corroboration references and verdicts, verification decisions, correction history, evidence hashes and a local approval signature. A hash is a fingerprint used to match records and detect changes; it is not proof that a result is true. The reviewer must check the evidence.

The reviewed-results candidate contains only these public fields, subject to a separate release review and name opt-outs:

Raw evidence, photos, contact details, private review references and signatures are excluded from that public candidate. Approval creates a candidate; it does not automatically publish it. Public results are not covered by the raw-submission cleanup and remain until corrected or removed.

Local review exports and ledgers have no automatic cleanup and are not covered by Cloudflare storage rules. The operator deletes local raw standings evidence and photos by the same WCQ deadline, no later than 2027-08-31, updated when Konami announces the date. The private review ledger retains reviewed text, including contact details, and correction history for later fixes; it has no automatic deletion.

The bot check (Cloudflare Turnstile)

Four actions require Cloudflare Turnstile: Send standings, Ask to be removed, Report a bug and creating a new sync code. The forms load the check from challenges.cloudflare.com when configured; the calculator loads it when you choose to create a code. Reading or saving with an existing code does not require this check.

Cloudflare Turnstile runs in your browser and sends browser and device signals and your IP address to Cloudflare. Our application records do not keep the raw address or browser details.

For each verification, the server sends the check token and your IP address, when supplied by Cloudflare, to Cloudflare. The token is held briefly in server memory to reject simultaneous replays, not saved in application records. The server refuses the action if bot configuration is missing or verification is unavailable or invalid. The check does not verify that submitted evidence is true.

The bot check is Cloudflare Turnstile in Managed mode. It runs for 4 actions only: sending standings (submit), asking for removal (remove), reporting a bug (bug-report) and creating a sync code (sync_new). Our server accepts a check only for chainlink3.com and only for its own action. Turnstile reads signals such as your IP address, browser user agent and connection (TLS) details to tell people from bots; see Cloudflare's Turnstile Privacy Addendum: https://www.cloudflare.com/turnstile-privacy-policy/ Cloudflare controls what its own service collects and how long it keeps it.

The private operator desk

The site has a private desk where the operator reads standings submissions and manages match footage. It is not public. Our code refuses every request to it unless Cloudflare Access confirms the visitor signed in with one of the operator's own email addresses, and it refuses everyone if that setup is missing. Search engines are asked to stay out of it.

How to ask not to be named

If you are a player and you do not want your name on Chain Link 3, email contact@chainlink3.com. Tell us the name as it shows on the site and, if you can, a page where you saw it.

We add the name to our opt-out list. When we next rebuild the site:

We handle removal requests within 7 days on this site only. The operator publishes the updated site and refreshes the points estimates as part of the removal.

What this does not change:

Using this site

Chain Link 3 is an independent fan project and is not affiliated with or endorsed by Konami or tournament organizers. Points and calculator outputs are unofficial estimates. Coverage can be incomplete and estimates depend on the data entered. For a correction, email contact@chainlink3.com; for a name removal, use Ask to be removed. Submit only evidence you may share.

Before public intake launches

The operator approved this privacy notice on 2026-10-29 after reviewing the checked Cloudflare facts. The generated forms are enabled. Approval here does not open public intake; the release gates and service settings below still need separate confirmation.