Trust & privacy

Privacy Policy

Updated November 11, 2026

Taste-AZ operates Hospitality Control, available through DineTraction.ai Control for authorized restaurant owners, managers and staff. DineTraction provides the supporting technology. This policy covers the hosted service, the iPhone and iPad app, capture tools, connected services and operational text-message alerts. The features and restaurant data available to you depend on your account permissions.

Miel de Agave Phoenix guest reservation texts

Taste-AZ Hospitality Control also provides DineTraction Voice for Miel de Agave Phoenix. The restaurant's current AI receptionist call number is (602) 334-4841. When reservation texting is enabled for that line, guests may request one SMS containing the restaurant's OpenTable reservation link. The requested text comes from the separate business SMS sender (602) 704-5154. This policy also covers requests through the existing receptionist flow at (602) 704-5154. We process the calling number, consent record, requested link and delivery status to fulfill the request. A call or a reservation-link request does not subscribe the guest to marketing.

The opening identifies the AI receptionist and says the conversation is transcribed and saved. The current receptionist's transcripts are retained in the platform; the voice provider may temporarily process audio to complete the conversation, but retained audio recording is off. In the existing receptionist flow at (602) 704-5154, that notice occurs before speech collection begins. Callers in that flow can press zero during the notice to request the team without AI transcription, or continue by speaking to the assistant. If the caller requests a person and the team is unavailable, a message is transcribed only after separate keypad permission. Authorized restaurant staff can review inquiries and messages. Calls with an available phone number are grouped into a restaurant contact record with call history, inquiry categories, a name when provided, and staff notes.

The phone disclosure identifies Miel de Agave Phoenix, explains the requested OpenTable link, and offers keypad 1 to agree or keypad 2 to continue without a text. For calls to (602) 334-4841, it also identifies (602) 704-5154 as the separate text sender. Only keypad 1 after the complete disclosure authorizes the requested text; spoken agreement, keypad 2, silence and caller ID do not. We retain the exact presented disclosure, affirmative keypad choice, calling number, request time and message delivery status for that request. These records do not establish permission for promotional messages.

This is not a marketing subscription. Frequency is one text per request, with a maximum of one requested reservation-link text per caller per restaurant per day. Message and data rates may apply. Mobile numbers and SMS consent are not sold or shared for third-party marketing. Communications and hosting providers process them only to operate the service. Reply STOP to opt out or HELP for help. For restaurant assistance or a privacy request, call Miel de Agave Phoenix at (480) 690-2872. See the reservation-text terms and exact English and Spanish consent scripts.

Information we collect

We may process names, business contact information, email addresses and mobile numbers; account identifiers, authentication details and restaurant assignments; point-of-sale activity such as checks, cash totals, discounts and voids; employee schedules, time entries, payroll and operational review records; identification documents, food-handler certificates, and tax forms including taxpayer identification numbers and signatures when submitted through employee tools; inventory counts, purchase invoices, vendor and connected accounting records; messages, notes and uploaded content; restaurant floor plans; and technical and audit logs needed to operate and secure the service. The information processed depends on the features your organization uses and your access permissions.

How we use information

We use this information to provide the portal, route real-time operational alerts and daily summaries, investigate unusual activity, maintain security, troubleshoot the service and comply with applicable legal obligations. SMS message frequency varies with restaurant activity. Message and data rates may apply.

DineTraction on iPhone and iPad

The app opens the hosted Control service and uses its existing sign-in and access controls. Session cookies and website storage may remain on your device to maintain sign-in, preferences and saved report views. Saved report views can include restaurant and employee information available to your account. They help redisplay previously fetched information; current access permissions are checked by the service. Downloads and exports may also be stored temporarily on your device and can be shared using the system share sheet.

App notifications

If you allow app notifications, we associate an Apple push token and a random app installation identifier with your signed-in account and restaurant permissions. A device credential stays in the app's protected Keychain; the server stores its hash to verify registration changes. We use Apple Push Notification service to send the notification type and a short preview of activity available to your account, together with a random notification identifier. Previews can include restaurant and employee names, message excerpts and relevant amounts. They may appear on your device's lock screen according to your notification preview settings. Opening a notification checks your current account access before showing details.

Notification registration and provider acceptance records help us operate and troubleshoot delivery. You can turn off app notifications in Settings → Notifications within Control, or change notification permission in your device settings. Signing out stops future sends for that signed-in session; a notice already accepted by Apple may still appear. App notifications are separate from SMS, email and WhatsApp preferences.

Camera, inventory and room capture

If you start a native inventory or room capture, the app requests camera access. Inventory capture can include up to four shelf photos, capture times, a selected restaurant identifier and, on supported LiDAR devices, a center-distance observation. Room capture uses Apple RoomPlan on a supported LiDAR device to create measurements and classifications of walls and furnishings. Capture processing occurs on the device. Native captures are not automatically uploaded to DineTraction or OpenAI.

When you choose to share a capture, the app creates a JSON file and opens the system share sheet. Copies you save to Files, cloud storage or another app are handled by the destination you choose. Importing a room file into Control creates a local preview and floor-plan draft; the raw room capture file is not uploaded by that import. If you review and save the floor plan, the resulting layout geometry is stored with the restaurant in Control.

When you choose Analyze shelf in Control, the selected photos, shelf or zone label, authorized product catalog and any supplied capture/depth metadata are sent through our server to OpenAI to create inventory suggestions. Photos are resized and image metadata is removed before sending them to OpenAI. The analysis request does not save the source shelf photos in our inventory database. Suggestions require your review; applying them creates a draft count, and saving the count is a separate action.

You can decline camera access and use manual inventory counts or the floor-plan editor. You can change camera permission in device settings. Closing an unshared capture discards its active photos or measurements. Shared file copies remain wherever you saved them until you or the destination service removes them.

AI features and submitted information

When you ask Ratatouille AI a question, we send the question, recent conversation, relevant reports within your authorized restaurant scope and any relevant approved business memory to OpenAI to generate an answer. Depending on the question and your access, those reports may include employee, operational or financial information. Feedback can save the question, answer, correction and source context in Control; authorized owners or administrators can also choose to save approved business memory. Other requested AI features may send the selected documents, photos, text or authorized report context needed for that feature, such as invoice extraction, business planning, website drafts or social drafts. Review outputs before using or publishing them.

OpenAI also processes information under its applicable API data policies and the service configuration, including applicable provider retention rules. You can choose manual workflows where available instead of submitting information for AI processing.

Before app-initiated AI processing, choose whether to allow the named provider in AI sharing settings. OpenAI and Retell have separate choices. You can decline or withdraw permission and continue using available manual tools. Automatic restaurant processing requires separate authorization from an authorized organization administrator. Withdrawing an app permission stops future app-initiated requests; it does not erase information already received by a provider. Existing restaurant phone lines route calls directly through the configured voice provider and must be stopped or rerouted in that provider's controls.

Microphone and receptionist tests

If you choose Start browser test in the receptionist workspace and grant microphone access, your voice is transmitted to Retell to run the conversation. The voice provider may temporarily process audio to complete the call. Retained audio recording is disabled in the configured test flow; transcripts, summaries, call status, duration and related metadata are saved in Control for your authorized restaurant team. The microphone starts only when you start a test, and you can stop the test or revoke microphone permission. Guest phone calls and reservation texts are described separately above.

QuickBooks Online connection

When an authorized owner connects QuickBooks Online, authorization happens through Intuit. We retrieve company identity, reports, accounts, vendors, transactions and location or class information used by enabled accounting features. Authorized users may also approve supported accounting actions, such as updating a permitted register purchase or creating a bill from a reviewed invoice and attaching its document. These actions send the approved data to QuickBooks. We do not receive your QuickBooks password. Authorization tokens are encrypted at rest and may be revoked by disconnecting the company from the QuickBooks connections page. Disconnecting does not undo transactions already sent to QuickBooks or remove records retained in Control.

An authorized restaurant owner or administrator can connect Facebook Pages, linked Instagram professional accounts, or TikTok accounts in Posts when the provider has enabled access for our app. Authorization happens on the provider's website; we do not receive your social account password. We store account identifiers, display names, encrypted authorization tokens, restaurant assignments, post drafts, uploaded photos or videos, publication approvals and provider status information to provide this feature. Uploaded media stays in private storage while drafting. When you approve publication, we send the selected caption and media to the selected provider; Meta may retrieve the approved photo through a temporary media link.

When you request an AI draft, your restaurant name, notes and selected photo may be processed through OpenAI to create an editable caption. Video files are not sent to OpenAI by this drafting feature. You review the content before publication. Approved Facebook and Instagram schedules can be submitted after the selected time; TikTok publication requires a separate immediate confirmation and privacy selection.

In Posts, choose Disconnect on the connected social account to remove its saved authorization tokens and stop pending schedules for that connection. You can also revoke the app in the social provider's account settings. To request deletion of saved social connection records, drafts or uploaded media, contact your restaurant's DineTraction account administrator and identify the restaurant and connected account. Disconnecting or deleting data here does not delete posts already submitted to a social platform; manage those posts directly with the provider. A publication already in progress may finish.

Mobile information and sharing

We do not sell personal information. Mobile information will not be shared with third parties or affiliates for marketing or promotional purposes. Text-messaging originator opt-in data and consent will not be shared with any third parties, except service providers that deliver the requested messages or as required by law.

We may use operational vendors, including communications, hosting, security and data providers such as Intuit, only to deliver and protect the service. They may process information solely for those contracted purposes.

Retention and security

We retain information only as long as reasonably necessary for operational review, security, legal compliance and the purposes described above. We use access controls, encryption and other safeguards designed to protect the information we process.

Our retention policy sets a four-year default for necessary payroll and tax evidence, 12 months for ordinary messages and 90 days for security logs. A documented legal obligation or hold can require a different period. Personal information that is not required for those purposes is removed earlier when your account is deleted. These periods do not authorize keeping unrelated personal content.

Delete your personal account

Sign in and choose Delete my account from account settings. You can submit the request even if you are the only owner of a restaurant. We complete deletion of your personal login and nonrequired active personal information within seven calendar days. The request receipt shows its deadline and status. You can cancel while the request is pending; cancellation ends when processing begins. Restaurant workspaces and necessary business records are preserved for authorized people. Removing your personal account does not delete the restaurant.

The database currently has a seven-day daily-backup recovery window, verified October 19, 2026. Database backups do not contain uploaded Storage objects. Restricted encrypted backup copies can remain until their verified rotation schedule expires. This exception does not extend the deadline for active personal-data deletion, and deleted information must be removed again before a restored system is reopened. Other processors can retain restricted records under their applicable retention rules; we verify and document the relevant handling for each deletion. Exported device or cloud copies remain under the control of the destination you chose.

Your SMS choices

Authorized recipients may reply STOP to end messages or HELP for assistance. Opting out stops SMS alerts but does not prevent an authorized manager from using the portal. For additional help, contact your restaurant's Taste-AZ Hospitality Control administrator.

Privacy questions and data requests

Contact martin@dinetraction.ai with privacy questions or requests concerning your personal information. Include the account email and restaurant involved so the request can be routed appropriately. Do not send passwords or verification codes. Your restaurant's authorized administrator manages access to its business records. Disconnecting a provider, signing out or removing the app does not by itself delete information already stored by the hosted service or a provider. Device and cloud copies you exported must be managed where you saved them.

Policy changes

We may update this policy as the service changes. The effective date above identifies the latest revision.