ADCsites Restaurant DemoSafe simulation — no real payments or messages

Sample / Demo Privacy Policy

How a real restaurant could explain data use

Effective for demonstration: September 7, 2026. This structure is illustrative and requires client-specific legal review before production.

01

Information a production site may collect

Order and catering forms may include name, email, phone, address, order details, gift-card recipient data, rewards activity and messages. A production policy must list only the information the restaurant actually collects.

02

Payments and delivery providers

Payment credentials should be handled by an approved provider such as Square or Stripe, and delivery information may be shared with an approved delivery provider only as needed. Their own terms and privacy notices may apply.

03

Use, retention and security

A real policy should explain operational use, support, fraud prevention, legal obligations, retention periods and reasonable safeguards. No website can promise absolute security.

04

Privacy rights and California readiness

Depending on the restaurant and applicable law, guests may have rights to know, correct, delete or limit certain uses of information. California-specific notices and do-not-sell/share choices should be added only when legally applicable to that client.

05

Children, updates and contact

A production policy should address minors where relevant, explain material updates and identify a verified privacy contact. Demo submissions here are not transmitted externally.