Why Not? Italian Food
Privacy Policy
Last updated: October 26, 2026
1. Restaurant Ordering Experience
This website is presented under the Why Not? Italian Food brand. Ordering and customer data are collected and used by Why Not? Italian Food to receive, prepare, fulfill, and support guest orders.
Why Not? Italian Food may work with payment, ordering, delivery, analytics, and communications service providers to operate this site and support guest requests.
2. Data We Collect for Orders
- Name, phone number, email, and order details
- Delivery address when delivery is offered
- Operational events needed to process, fulfill, and support orders
- Pseudonymous ordering-funnel and upsell-rail signals keyed by a random browser identifier, including cart and checkout stages and up to 48 server-verified menu item, recommendation set, and modal or cart surface interactions
3. How Data Is Used
- To transmit and fulfill your order with Why Not? Italian Food
- To send order updates, receipts, and support communications
- To prevent fraud, resolve disputes, and improve reliability
- To produce directional conversion analytics about the upsell rail
4. Service Providers and Restaurant Operations
Service providers may process order details, payment status, notifications, technical logs, and support information on behalf of Why Not? Italian Food. Why Not? Italian Food remains responsible for menu accuracy, preparation, fulfillment, and direct restaurant operations.
Google Ordering Referrals
Where enabled, a Google ordering link saves a signed referral receipt in first-party browser storage for 30 days. A new Google referral replaces it; direct visits do not extend it. It may attribute repeat orders and orders at another restaurant on the same origin. Independent domains do not share browser storage.
After successful checkout, Google receives only the referral token, the conversion partner identifier and whether the branch changed. No customer contact details, address, cart, prices or payment data are sent. Server tokens are erased after delivery ends or its 24-hour deadline; uncompleted attribution expires with the referral or cancellation. Outcome records without tokens are retained for 30 days, then removed by scheduled cleanup. Required consent must be obtained before enabling capture; capture remains disabled where that consent is unavailable.
5. Upsell Attribution and Retention
Only a session that touched the upsell rail and later converted may be linked to the resulting order for directional conversion analytics. Sessions without upsell-rail activity are not linked to an order for this purpose. The attribution record does not include customer name, contact details, delivery address, order notes, payment information, prices, or full cart contents.
A converted session's attribution summary may be displayed within existing internal order notifications used by operations staff; these signals never trigger, gate, or delay any notification. They are not used for pricing, tax, payment, fulfillment, fraud decisions, merchant reporting, ranking, or checkout correctness. Raw records are kept for approximately 30 days and are deleted after 30 days during the next scheduled cleanup interval, so deletion may take up to 31 days total.