Staging Working Draft Legal Review Pending

This Privacy Notice is a preliminary working draft describing actual BiteShark staging data flows and highlighting open privacy-engineering and legal tasks. It is not a finalized privacy policy or compliance certification.

Operator Identity [LEGAL OPERATOR NAME], doing business as BiteShark
Version & Last Updated Version 0.1-draft · November 19, 2026
Responsible Internal Owner Operator (Admin: Top), Engineering & Privacy Counsel
Review Status Legal review pending · No effective date

2. Privacy Notice (Preliminary Working Draft)

2.1 Data Controller / Operator

BiteShark is operated by [LEGAL OPERATOR NAME], doing business as BiteShark. Official postal and privacy-request contact addresses remain to be confirmed before public launch.

2.2 Categories of Information Processed Today

Feature / Surface Data Processed in Current Application Current Retention / Storage Behavior
Account Registration & Sign-In Normalized email address, opaque account ID, single-use OTP HMAC challenges, SHA-256 hashed session token, minimized/pseudonymous truncated SHA-256 IP and user-agent digests for rate-limiting and session security (not treated as anonymous), and derived 14+ age-eligibility metadata. OTP challenges and rate-limit buckets are purged after 24 hours (during rate-limit writes and periodic worker cleanup); revoked/expired sessions are purged after 7 days; account rows persist until disabled/deleted (automated self-service deletion not yet built).
Date of Birth (14+ Check) Self-reported Month, Day, and Year submitted over HTTPS during account creation or one-time existing-account check. No identity documents are collected. Raw date of birth is never stored. Only age_eligibility_status (eligible_14_plus or not_assessed), policy version, assessment timestamp, and self-reported basis are saved. Rejected under-14 signups create zero accounts, zero OTP challenges, and zero marketing records. If a pre-existing account reports under-14 on its one-time check, the account is disabled and sessions are revoked immediately; existing non-auth historical records are preserved pending legal review of retention/deletion handling.
Abuse Cooldown on Rejected Signup HttpOnly cookie __Host-bs_age_gate=1 (constant value 1; 15-minute max-age) and a minimized, pseudonymous truncated SHA-256 IP rate-limit bucket (age_ineligible_ip) to deter automated birth-date fishing. Cookie expires in 15 minutes; pseudonymous IP rate-limit bucket is purged after 24 hours (never treated as blanket anonymous data). Stores zero DOB and zero email address.
Location & Nearby Discovery Optional browser geolocation coordinates sent to /api/trucks/nearby when you tap “Near me” to compute distance to Sonoma County listings. Processed transiently in memory to calculate distances; customer geolocation coordinates are not written to user profiles or sold.
Favorites & Dish Notebook Saved truck IDs (stored in PostgreSQL when signed in and cached in browser localStorage); personal dish notebook notes/photos. Dish notebook notes and photos stay locally in your browser’s localStorage and are not uploaded to BiteShark servers.
Event / Catering Booking Inquiries Requester user ID/email, target vendor ID, requested event date, guest count, package interest, and optional note shared with the selected vendor. Stored in bookings for requester and vendor tracking; formal archival/deletion schedule is pending legal review.
Digital Pickup Pagers & Web Push Order ticket label/number, opaque status token, optional web-push endpoint and P-256DH/auth keys when subscribed. Pager tickets expire automatically; web-push delivery is currently disabled on staging (PUSH_PROVIDER_MODE=disabled).
Community Reviews, Reports & Support / Feedback Tickets Display name/nickname, star rating, comment text, moderation history, abuse reports, and private support/feedback tickets (ticket number BS-…, category, subject/description, immutable reporter urgency, sharing scope personal vs vendor_service, separated public replies vs internal staff notes, and optional user-reviewable sanitized context such as correlation ID corr_…, release SHA, and coarse device/browser/viewport category — never raw user-agent strings). Moderation preserves original submitted text internally for audit/appeals; support tickets and append-only ticket events/notes are retained separately from short-lived diagnostic event samples so diagnostic cleanup never erases user support conversations; formal retention/archiving schedule pending counsel review.
Vendor Onboarding Applications & Proof Business contact details, permit/license summary, ownership statement, and optional PNG/JPEG/WebP/PDF ownership proof (up to 512 KiB per file, max 3 files). Uploaded onboarding evidence records carry a 90-day retention_expires_at timestamp and scrub raw file bytes upon deletion.
First-Party Operational Diagnostics Sanitized error codes, allowlisted route templates, component/feature identifiers, correlation IDs (corr_…), server release SHA, browser bundle version, and rate-limiting truncated SHA-256 IP buckets when unexpected operational errors occur. Never stores request/response bodies, emails, full URLs/query strings/fragments, cookies, OTPs, raw DOBs, precise coordinates, tokens, or uploaded files. Stored in first-party PostgreSQL only (zero third-party monitoring SDKs). Representative event samples default to 14-day retention, resolved incident groups to 30 days, and open groups to 60 days via scheduled worker cleanup; append-only operator triage notes persist separately for operational auditability.

2.3 Proposed Age Policy (14+) & Youth Privacy

Under the operator’s proposed account policy (awaiting legal approval), users aged 13 and younger cannot create accounts; minimum account age is 14. BiteShark does not knowingly create accounts for children aged 13 or younger, does not run behavioral advertising, and does not sell or share personal information for cross-context behavioral advertising.

Important limitation: Self-reported date of birth is not verified age, and restricting account signup to 14+ does not by itself resolve all legal questions regarding teen users (ages 14–17), EU/UK digital-consent rules, or unauthenticated public browsing and anonymous pickup pager use. Those items remain explicitly open for legal review.

2.4 Third-Party Service Providers & Data Sharing

2.5 Current Limitations on Privacy Rights & Account Deletion

Signed-in users can currently open a private support ticket in the app (Profile → Support & issues), and administrators can disable accounts and revoke active sessions. However, automated self-service account deletion, data export, and formal privacy-request (DSAR) workflows are not yet implemented or verified and must be completed before public launch.

[UNRESOLVED — CONFIRMATION REQUIRED] Open Privacy & Compliance Tasks

  • Confirmed operator identity & privacy contact inbox: Replace [LEGAL OPERATOR NAME] and publish a monitored privacy request contact method and postal address.
  • Account deletion & DSAR procedure: Build and verify user-initiated account deletion and data-access/correction workflows, including rules for records retained for security, fraud prevention, or legal obligations.
  • Retention schedule & disabled-account record handling: Finalize exact retention periods for bookings, community posts, support issues, onboarding applications, backups, and append-only audit logs — including how historical records tied to a pre-existing account disabled after an under-14 assessment should be retained, anonymized, or deleted under counsel guidance.
  • Jurisdictional notices (California CCPA/CPRA, CalOPPA, CA AADC, state privacy laws, EU/UK GDPR): Determine applicability based on confirmed launch jurisdictions and operator thresholds, and add required statutory disclosures.
  • Public browsing & anonymous pager review: Confirm with counsel whether unauthenticated map browsing or pickup pager status checks require additional youth-privacy safeguards.