Food guide and review shortcuts
Food profiles contain public menu information, business links and concise summaries of cited reviews. We do not publish diner contact details. Search and filters work in your browser. Profile-correction emails and photo permissions may be retained so we can verify and maintain a listing. We use our existing Google Analytics integration to measure restaurant-profile views and clicks for menus, directions, websites and social links. We also record a simple AI-referral event when a visit arrives from a recognized service such as ChatGPT, Perplexity, Claude, Copilot or Gemini; it contains the referring service and landing-page path, not a prompt or conversation. These events contain business and branch identifiers, not customer identities or precise visitor locations. Clicks and copied codes are interest signals, not proof of a physical visit. Any future owner-reported offer redemptions should be aggregate counts, not customer records. No new auction payment is required to browse or appear in the food guide. The transaction and profile-tool sections below describe the previous service and retained historical records, not new food-guide purchases.
PRIVACY NOTICE
HOW WE HANDLE INFORMATION.
DFW discovery guide
Business profiles use public information, source links and owner-submitted corrections. Contact emails may be retained to answer requests and verify changes. Search and filter controls operate in your browser. Bookings and orders happen on third-party business sites. Do not send medical information to 42 SPOTS. The guide is complimentary at launch; the transaction sections below describe retained records and tools from the previous auction service.
Information you submit
We store company or product name, destination URL, pitch, selected board, bid amount, contact email, acceptance of terms, moderation decisions, rights confirmations, and payment-state identifiers. If you use profile enhancement tools, we also store the profile fields, screenshots, images, filenames, media properties, upload status, and review decisions you submit. Stripe collects payment and billing details on its hosted page; 42 SPOTS does not receive full card numbers.
What becomes public
A captured sponsor receives a minimal continuing company directory page containing its approved name, destination, and pitch. Additional approved profile fields and sanitized image derivatives may become public. The badge is Sponsored only during a fresh verified active placement and otherwise is Curated. We do not publish bid amount, rank, contact email, payment identifiers, settlement state, or sponsorship history on the company page. Rejected, losing, missed, and capture-failed submissions remain non-public.
Operational data
Our hosting and security providers may process request metadata such as IP address, device and browser information, timestamps, and abuse signals. We use Google Analytics and Microsoft Clarity to understand aggregate site use and interaction patterns; those providers may process device and browser information, page activity, session interactions, and cookies or similar identifiers under their own policies. 42 SPOTS does not currently operate or publish its own sponsored-click counter.
Why we use it
We use data to operate auctions, verify authorization, moderate content, settle winners, release losing holds, deliver placements, create and maintain eligible company pages, process profile enhancements, prevent abuse, respond to reports, maintain records, and meet legal or financial obligations. Profile and asset review is separate from payment ranking and settlement.
Providers and disclosure
Stripe processes payments. Cloudflare and Sites provide hosting, security, database, and object storage services, including storage of uploaded assets and sanitized derivatives. We share only what those services need to perform their role, or what law, fraud prevention, disputes, and safety require. We do not sell personal information as a data broker.
Retention
Bid and payment records are retained as needed for settlement, disputes, accounting, fraud prevention, and legal obligations. Approved captured-sponsor directory content may remain public until corrected or removed. Staged, rejected, superseded, and orphaned uploads may be deleted on a shorter operational schedule; moderation evidence and reports may be retained to enforce policy. Removing public content does not require deletion of transaction, security, or legal records that we still need.
Your choices
You may request a correction, removal, or privacy review through the Report page. Some transaction and abuse-prevention records must remain even after public content is removed.
Contact
Privacy and data-handling questions may be sent to info@redct.ai.