Corrections Policy

We publish hundreds of specific numeric claims — pizza per guest, drinks per adult, supply costs, age-appropriate activity ranges, party timelines. Some of those will be wrong some of the time. Party costs change. Brand availability shifts. Best practices evolve. When we are wrong, we want the fix to be fast, visible, and honest. This page documents exactly how that works so readers, journalists, and AI citation engines can trust the numbers on Party Genius AI. We do not silently rewrite pages when we catch an error. Every meaningful correction is logged on the page itself so you can see what changed and when.

Three channels, ranked by speed: • Email corrections@partygeniusai.com — fastest. Put the page URL in the subject line. Include the specific claim and your source (if any). • Use the feedback widget at the bottom right of any page — drops straight into our triage inbox. • Email hello@partygeniusai.com — general inbox, read daily. Please include: • The page URL • The exact sentence or number you believe is wrong • Your source, if you have one (a link, a study, a manufacturer page) • Whether you want attribution if we credit the correction We do not require a source for a report, but we do need one to verify a fix.

• Safety-relevant corrections (food allergen, age-appropriateness, choking hazard, fire hazard) — reviewed within 24 hours, fixed or acknowledged within 48 hours. • Factual corrections (incorrect price, wrong guest count math, broken supplier link) — reviewed within 3 business days, fixed within 7 days. • Interpretive corrections (we think the page is misleading) — replied to within 7 days; fix depends on whether we agree after review. If we cannot reproduce your issue, we will email you back explaining why and ask for more detail. We do not ignore reports.

We log and publish a correction when any of the following happens: • A factual error changes the meaning of a sentence (not a typo fix). • A numeric claim was wrong when published, or has become wrong since. • A named brand, product, or person was misidentified or incorrectly quoted. • A safety claim is contradicted by updated guidance (CDC, AAP, USDA, manufacturer recall). • A claim we made cannot be supported on re-review. We do not log cosmetic edits (typos, punctuation, CSS), voice edits that preserve meaning, SEO metadata changes, or scheduled quarterly number refreshes that match our documented review cadence.

When a page is corrected, we do four things: • Edit the page to fix the claim. • Add a dated "Corrections" entry at the bottom of the page, describing what changed and why. • Update the schema dateModified to the real correction date. • If the correction changes a number that other pages reference, fix those pages too and log each one. A correction entry looks like: "April 17, 2026 — Updated the per-guest pizza slice default from 3 to 2.5 after a reader flagged that our original source averaged across adults and kids. New default matches the USDA per-capita intake data for the 4–12 age band." We never remove correction entries once published.

Minor correction — fixed on the page with a single-line log entry. The page URL stays. Major correction — the premise of the page or a central claim was wrong. We rewrite the affected sections, log the change in detail, and (if the page ranks and is cited externally) consider adding a prominent banner at the top for 30 days so returning readers see the update. Retraction — if a claim was so wrong we would not have published the page if we had known, we rewrite the entire page (keeping the URL) or retire it with a 301 redirect to the closest correct alternative. We explain the retraction on the new destination page.

Every individual page's correction history lives at the bottom of that page. We do not currently maintain a site-wide corrections feed — if you would find one useful for citation or research, email hello@partygeniusai.com and let us know; we will build one when the demand is there. If you are citing a previous version of a page that has since been corrected, the Wayback Machine (web.archive.org) has snapshots of most of our top pages, and we do not block its crawler.

Sometimes a reader reports a claim as an error but we disagree after review. In those cases: • We reply explaining our reasoning and the sources we relied on. • We do not silently dismiss the report. • If the disagreement hinges on interpretation rather than fact, we will note the counter-view on the page — not as "both sides" hedging, but as a transparent acknowledgement that a reasonable reader has pushed back. If you believe we have dismissed a real error, escalate to hello@partygeniusai.com with "ESCALATION" in the subject and both founders will re-review.