Privacy notice

The service may process information supplied during account, restaurant, and team setup, including:

• account identity and contact details, email verification and sign-in records;
• restaurant name, location, timezone, team membership, role, and access state;
• submitted menus, catalog records, source material, ingredients, allergen context, pairing drafts, review notes, and published learning revisions;
• plan, licensed-learner count, quote, promotion-validation, subscription, payment-status, and provider transaction identifiers; and
• security, reliability, support, and bounded product-event records needed to protect and operate the service.

The exact fields collected in production and whether optional analytics are enabled must be checked against the deployed service before launch.

This information supports identity verification, restaurant setup, access permissions, menu and learning workflows, expert review and publication, pricing confirmation, subscription administration, service messages, support, fraud and abuse prevention, and operational reliability.

Menu and source content may be sent to configured AI providers to generate drafts for restaurant review. Draft output is not automatically expert-approved or published. The final notice must name or otherwise identify the deployed providers as required and confirm their contract, location, retention, and model-training terms; this draft makes no no-training or fixed-retention promise.

Payment and transaction information submitted during checkout is processed by Stripe. Stripe handles that information under its own privacy policy. Always Upsell receives the identifiers and status information needed to reconcile an authoritative quote and subscription.

Resend is used to deliver account and service email and may process recipient, message, delivery, and related technical information for that purpose. See Resend's privacy policy.

Configured infrastructure, support, security, and AI service providers may process information only as needed for their deployed functions. The production processor inventory and applicable disclosures remain launch review items.

A fixed retention schedule has not been approved. The final schedule should distinguish active account and restaurant records, published and historical revisions, billing and transaction records, security logs, support records, and backups, while accounting for operational and legal requirements. It must also state when deletion is unavailable or delayed.

Account holders may propose an access, correction, or deletion request by writing to support@alwaysupsell.com. Requests may require identity and authority verification and will be handled under the final policy and applicable law. This proposed mailbox must be verified as operational before launch.

The service uses role and lifecycle controls intended to limit access and protect account, restaurant, and billing workflows. No technical system can guarantee absolute security. Suspected account misuse or privacy concerns should be reported promptly to the proposed support address.

Material changes to an approved notice should receive a new revision date and any notice required by the final policy or applicable law. The owner must add the responsible legal entity and a working privacy contact before this draft becomes customer-facing policy.