Counted Menu uses the information you provide to process your order, review restaurant data, prepare your menu economics analysis, and make the completed work available through your order-specific link.
PUBLIC NOTICEWHAT WE RECEIVE · HOW IT IS USED · RETENTION
01 INFORMATION AND USE
Information used to prepare your analysis.
A / ORDER AND INTAKE
Details you provide
The intake form collects a contact name, business name, email address, location count, POS system, sales period, currency, and notes.
These details identify the order, describe the analysis requested, and help review the supplied data.
B / RESTAURANT FILES
Source tables and notes
Customers may upload CSV or XLSX tables for POS sales, menu and pricing, ingredient costs, and optional recipe or portion information for the eligible menu represented in their files. PDF and image uploads are not supported.
Counted Menu uses these details and files to validate the intake, review item-name matches, calculate food cost, food-cost percentage, contribution margin, sales mix and menu classifications, complete quality checks, and prepare the workbook and summary.
↗Uploaded restaurant data is not sold.
02 PAYMENT INFORMATION
Checkout is handled through Stripe.
When Stripe-hosted Checkout is enabled, card information is entered with Stripe. The Counted Menu application does not store full card numbers. Its order record stores the amount, currency, payment status, customer email returned by Stripe, and Stripe reference identifiers used to confirm or refund payment.
03 FILES AND ACCESS
Private order files, prepared for this analysis.
Uploaded files and generated workbooks and summaries are stored in private per-order storage, separate from public offer and sample pages. Intake and delivery use order-specific links; anyone with a link may access that order's workflow, so keep it private.
Secure intake and delivery links expire after 30 days. A customer who still needs access may ask Counted Menu to review a renewal; an operator can send a replacement link only while the order's workflow remains available. For a delivered order, link expiration follows the latest successful delivery and does not extend beyond the 30-day retention cutoff. For a refund or cancellation before delivery, access expires 30 days after that event. Link expiration does not delete files; the separate purge process below controls live-storage deletion.
04 RETENTION AND DELETION
When files become eligible for removal.
Uploaded source files and generated delivery files become eligible for live-storage purge 30 days after the most recent successful delivery, including a corrected delivery if one is issued. Failed correction attempts do not restart this period. If an order is refunded or cancelled before any delivery, its files become eligible 30 days after that event. An active paid order without delivery, refund, or cancellation does not become eligible just because 30 days pass.
THE CURRENT PROCESS
Eligibility does not mean automatic deletion.
No scheduled purge runs. An operator reviews the eligibility report and triggers the protected purge for one order at a time.
WHAT A LIVE PURGE DOES
Files and intake details are removed.
A completed live purge removes the order's uploaded and delivery files, upload records, intake details, and intake access link. It retains the order reference and limited payment, refund, and operational audit records.
A live purge does not delete earlier backups. Private backups copy the database and storage as they exist and may retain customer information until they are rotated or deleted. The backup utility does not serve backup files through the customer application. File removal from live storage is not a certified secure erase.
Keep your own copy of anything you still need. The spreadsheet and summary delivered to you are yours to keep.
05 SERVICE PROVIDERS
Services supporting the current workflow.
PAYMENTS
Stripe
When checkout is enabled, Stripe-hosted Checkout handles payment-card entry. Counted Menu receives the payment confirmation details described above.
HOSTING
Render
Counted Menu currently uses Render to host the validation service and its application infrastructure. The current validation environment has infrastructure limitations that differ from a production configuration. Counted Menu does not represent the validation environment as permanent archival storage. A production configuration requires separately configured private persistent storage.
QUESTIONS ABOUT THIS NOTICE
Use the existing Contact page.
Questions about how your information is handled can be directed through the contact information provided by Counted Menu.