Trust, moderation, and privacy

Open debate.
Clear boundaries.

The site is designed to host serious disagreement without publishing abuse, confidential material, or unreviewed allegations. These standards apply to the project and every reader contribution.

01

Disagreement is welcome

Criticize the rules, assumptions, evidence, tradeoffs, or conclusions as directly as you like. Contributions do not have to agree with the proposal.

02

People are not targets

No harassment, demeaning language, threats, personal attacks, doxxing, impersonation, or discrimination. Argue with the idea—not the person.

03

Claims need support

Do not submit knowingly false claims, rumors presented as fact, unsupported accusations, or confidential information you are not authorized to disclose.

04

Accountable writing

Everything is public to read. Signed-in members may publish at a thoughtful pace; private account identifiers support moderation without appearing beside public writing.

05

Conflicts should be visible

Readers are encouraged to describe relevant employment, institutional, commercial, conference, media, or advocacy connections in the optional affiliation field.

06

Corrections stay transparent

Material corrections to the proposal will be dated and explained. Reader contributions may be corrected, updated, or removed upon a verified request.

07

Automated gates reduce abuse

Before publication, common profanity, slurs, public contact details, repeated-character spam, and excessive links are screened automatically. Filters can miss context or make mistakes, so every public item retains a report route and a private account connection.

08

Reports remain private

Every published thread and reply includes a private reporting path. Identify the item and concern; the owner may hide it while reviewing safety, rights, privacy, or accuracy issues.

Reader privacy

What the site collects—and why.

Joining a discussion requires a Better College Football account and a fan profile. Accounts use a verified email address or username and password; Google sign-in may also be offered as a convenience. The site stores the contributor’s identity-provider account identifier, sign-in email address, chosen public name, optional favorite team or affiliation, selected perspective, optional phone number, consent record, submission text, moderation status, and timestamps. Phone is not required for sign-in or posting.

Email addresses, phone numbers, consent records, and account identifiers are never displayed publicly. When a thread or reply passes automated safety checks, the site displays only the chosen public name, optional team or affiliation, perspective, topic, headline, contribution, and publication date. A member may instead publish as Anonymous fan; the private account connection remains available for safety enforcement but the public name, fandom, Creator role, and profile link are removed.

Non-anonymous contributors receive a public member page reached from their byline. It shows only their public name, optional fandom, perspective, and approved contributions they have chosen to list. Members can hide or restore each eligible contribution from My profile. Anonymous posts never appear on a public member page.

A signed-in member may give one thumbs-up or thumbs-down to each public thread or reply. The site stores the item, private account identifier, reaction, and timestamps needed to enforce one vote per account; only aggregate totals are public. A vote can be switched or removed by pressing the selected control again.

Members who hold a public role—such as a coach, athlete, athletic staff member, researcher, or established media professional—may privately request verification. Submitted evidence is visible only to the owner. A Verified badge means the owner manually reviewed evidence connecting the member to the claimed identity or role; it is not an endorsement, guarantee of expertise, or institutional affiliation. The Creator badge separately identifies the site owner.

Private account data is used only for account integrity, moderation, correction or removal requests, and essential community notices. It is not sold or used for advertising. Private contact messages separately store the name, email, optional organization, subject, message, category, status, and timestamps needed to respond. The optional update list stores an email address, consent record, status, and timestamps. To request correction, removal, unsubscribe, or access to information you submitted, use the private contact form. Requests remain private.

Community profile contact data is retained while the profile or its moderation record remains active. A saved blank phone field removes an existing phone value. A verified deletion request will remove or de-identify private profile data unless temporary retention is necessary for security, dispute resolution, or a legal obligation.

Account authentication and recovery are handled by Clerk rather than a home-grown password database. Google processes information only when a visitor chooses Google sign-in. The public proposal does not require an account.

The site is hosted through ChatGPT Sites on Cloudflare infrastructure. OpenAI and Cloudflare process requests as infrastructure providers, and Clerk processes account, session, and recovery data. Google processes sign-in information only when a visitor chooses Google sign-in. Like other secure web hosts, those providers may process network and device information needed to deliver, protect, authenticate, and troubleshoot the service; the project does not receive that infrastructure data as an advertising profile and does not sell it. OpenAI’s Privacy Policy, ChatGPT Sites Terms, and, where applicable, the Sites Data Processing Addendum apply alongside Clerk’s, Cloudflare’s, and Google’s published terms.

Do not submit sensitive personal data, private records, confidential communications, or material you lack the right to publish. Interactive features are not directed to children under 13.

Community safety

Prevent, review, report, respond.

Community is public to read. Signed-in members may publish up to two threads or replies every 24 hours with a 15-minute pause. Posts publish when automated safety checks pass; access never implies endorsement of any view. Exact duplicate posts are blocked.

Firsthand fan memories follow a different editorial path. A signed-in member with a public name and fandom may submit a short memory to a Saturday story, but it remains private until the owner approves it. If approved, only the memory, public name, fandom, and month of publication appear. The private account connection, email, consent record, and review status remain available for moderation and removal requests.

The owner may hide material after a report or direct review when it violates these standards or creates a credible safety, privacy, or rights concern. Use Community safety report for harassment, threats, hate, impersonation, exposed personal information, spam, or other concerns. Do not use this website as an emergency service. If someone appears to be in immediate danger, contact local emergency services or the appropriate crisis resource.

Anonymous measurement

Useful numbers without surveillance.

The site asks before enabling first-party audience measurement. If allowed, it creates random identifiers in your browser and stores public page areas, random browser/session identifiers, referring site’s hostname when available, and timestamp. With this version’s permission, it also stores allowlisted X/Instagram source, post/bio campaign and version tags, plus proposal-open, reading-signal, bracket-use and rankings-use events. A reading signal means at least 20 visible seconds with scrolling, not proof that a reader finished or agreed with the proposal. It does not store a signed-in account identifier with analytics events, and it does not intentionally store an IP address, arbitrary query strings, full referrer URL, fingerprint, advertising identifier, or browsing activity outside this site.

The private owner dashboard reports aggregates such as estimated consenting visitors, sessions, popular pages, referring hosts, and voluntary topic interests. These records are not joined to community profiles or sign-in accounts. Owner, sign-in, account-creation and private-contribution routes are excluded. Do Not Track and Global Privacy Control disable audience measurement. Earlier consent is requested again for this expanded scope. The private publisher receives aggregates only; it never receives visitor or session identifiers. Instagram bio attribution is shared, not tied to a specific carousel. Untagged visits cannot be assigned to a social post. Records are automatically removed after approximately thirteen months, and no third-party analytics or advertising scripts are installed.

Choosing community priorities and voting on creator prompts are separate voluntary actions. One browser can signal up to three distinct priorities. Creator-question voting requires sign-in and stores one current choice per question against the private account identifier. A member may replace that choice, while signed-out visitors can read the questions and public totals but cannot vote. Public totals are directional feedback, not representative polling, and neither the account identifier nor browser identifier is displayed publicly.

Your browser’s current setting: not chosen. Do Not Track and Global Privacy Control take precedence.

Production reliability

Detect failures without collecting the story around them.

The site records coarse browser failures needed to find broken public pages: script, rejected-promise, or resource failure; a broad technical category; the pathname without its query string; a one-way hash of a temporary browser-session identifier; and time. It never sends the error message, stack, form contents, account identifier, email, IP address, or full referrer to the project’s reliability table.

A browser session sends no more than six events and the server accepts no more than twelve in 24 hours for the same temporary session. Records expire after 30 days. These operational signals are separate from optional audience analytics and are used only to reproduce and repair faults.

Disclosures

Authorship, assistance, affiliation, and marks.

The policy positions and editorial judgments belong to Alec Levine. AI assisted with research, drafting, editing, modeling, document production, and website development. Reader contributions are their authors’ opinions. Creator and Verified badges describe account roles or completed identity checks; they do not imply approval of a contribution. The project is independent and is not endorsed by or affiliated with the NCAA, CFP, Ohio State, any conference, institution, athlete, bowl operator, broadcaster, poll organization, or media-rights holder.

Institutional names and marks are used only to identify teams, sources, venues, and examples. They remain the property of their respective owners. Proposed schedules, bowl assignments, simulations, rankings displays, financial ranges, and policy outcomes are illustrative unless a cited source identifies them as official.