Effective and last updated: November 6, 2026. Applies to version 1.0, the read-only Hazlnut for ChatGPT integration.
Hazlnut LLC operates this integration for authorized Hazlnut merchants. This notice explains the integration’s collection, use, sharing, retention, and controls. It supplements the Hazlnut Privacy Policy, which also applies to the underlying Hazlnut account, restaurant services, and website. OpenAI operates ChatGPT separately.
What version 1 does
Version 1 has five tools: get_profile, list_locations, list_orders, search_customers, and get_menu_items. They read existing information. They do not change hours or item availability, create or send rewards, award points, place orders, process payments or refunds, send customer messages, or create CSV exports.
Information collected and returned by each tool
When ChatGPT calls a tool, Hazlnut receives the tool name, its structured inputs, and the authorization needed to check access. Those inputs are derived from your request in ChatGPT; they can themselves contain personal information. The integration does not need your entire ChatGPT conversation to perform these calls.
- Connected merchant profile (
get_profile): uses your connection, with no merchant selector, to return the connected business name or nickname and an opaque profile reference. - Locations (
list_locations): accepts page size and pagination references and returns permitted location names, opaque location references, timezones, and currencies. - Orders (
list_orders): accepts selected location references, dates or times, order statuses, an optional order reference or ticket number, and pagination inputs. Results can include order references and ticket numbers, location, status, creation and scheduled times, order type, item names and variants, quantities, historical prices, subtotals, taxes, discounts, fees, tips, totals, and currency. Results cover the authorized locations and requested window; they are not an unrestricted business-wide sales report. - Customer lookup (
search_customers): accepts one customer reference, name, email address, or telephone number, together with selected locations and a date window. Hazlnut may process an exact, unmasked email address or telephone number that you supply as the search input. Results contain an opaque customer reference, display name, masked email or telephone details when available, and activity from qualifying closed orders in the authorized locations and window, including counts, first and last order dates, and order totals. Version 1 does not authorize business-wide loyalty balances or loyalty changes. - Menu lookup (
get_menu_items): accepts a location, an optional item reference or text search, stock filter, and pagination inputs. Results can include opaque item and parent-item references, item and category names, variants, prices and price levels, currency, publication status, and stored stock or availability information. Stored availability is not a guarantee that an item can currently be purchased in the storefront.
Responses also include relevant filters, date windows and timezones, pagination or coverage information, and warnings or errors. Internal database identifiers are replaced with opaque references in tool results; internal stock fingerprints are not returned. Masking returned customer contacts does not remove an email address or phone number you typed into ChatGPT or supplied as a lookup input.
Account linking, connection, and technical information
You sign in on Hazlnut’s sign-in page, not by giving ChatGPT your Hazlnut password. Hazlnut processes the sign-in and uses your identity, merchant role, selected permissions, and selected locations to establish the connection. The connection uses OAuth authorization codes and access and refresh tokens. Hazlnut stores authorization and consent records, grant status and expiry, selected scopes and locations, protected token state, and revocation history. ChatGPT receives the authorization tokens needed to use the approved connection; your Hazlnut password is not returned in tool results.
Hazlnut also processes technical and security information associated with requests and sign-in, such as IP address, browser or client information, timestamps, request or correlation references, tool or authorization actions, outcomes, error codes, and consent or policy revisions. Sign-in uses a short-lived browser-binding cookie. Audit records use a pseudonymous actor reference; they are not a copy of the full ChatGPT conversation.
Why we use this information
We use tool inputs and existing Hazlnut records to find and return the information you request. We use account, consent, location, and token records to link accounts, enforce your current permissions and location restrictions on each request, maintain or end authorized access, and prevent unauthorized use. Technical records and audit events support security, abuse prevention, troubleshooting, service operation, and investigation of access or consent issues. Support information you send us is used to respond to your inquiry.
The connector retrieves records for these functions; it does not send retrieved merchant or customer records to a separate model-training service. Hazlnut does not share or sell personal information provided to us for another company’s marketing use. OpenAI’s processing of information received in ChatGPT is governed separately, as explained below.
Who receives information
- OpenAI / ChatGPT: receives tool results and error responses for your approved requests. Your prompts and any lookup information you enter are also processed in ChatGPT. Returned information can appear in the conversation and be accessible to people with whom you share it. See OpenAI’s Privacy Policy and your ChatGPT account or workspace settings for OpenAI’s retention, model-improvement settings, and controls.
- Hazlnut and the connected merchant: Hazlnut’s services process the request against the merchant’s existing records. Authorized Hazlnut staff may access information as needed for support, security, and operation. Authorized merchant administrators can manage connections and view available connection activity in Treehouse.
- Service providers: hosting, storage, delivery, security, and application providers process information for the assigned service. These include Amazon Web Services for the integration’s backend, database, and operational logs, and Vercel for the Treehouse web interface. Website analytics are described below. These providers do not receive authority to operate your merchant account independently.
- Legal and business disclosures: information may be disclosed where required by law, to protect rights and security, or in connection with a business transfer, as described in the Hazlnut Privacy Policy.
Hazlnut’s integration infrastructure is hosted in the United States. Using ChatGPT and the hosting providers may involve processing outside your country.
How long information is retained
Retention differs by record type; disconnecting is not an instruction to erase every related record.
- Existing merchant, order, customer, and menu records: remain in the underlying Hazlnut service under the merchant’s account and applicable service and legal obligations. This read-only connector does not create a separate permanent archive of the returned order or customer pages. Source records are retained to provide the merchant service, maintain transaction and business records, and meet legal, accounting, dispute, and security needs. Their retention is not tied to the OAuth token lifetime; contact us about the applicable account or deletion request.
- Authorization state: access tokens last up to 10 minutes and refresh-token families have an absolute lifetime of up to 30 days. Temporary sign-in and OAuth records expire according to their function; expired state is scheduled for cleanup, generally after a further one-day recovery or security window. Refresh-family state is scheduled for cleanup one day after the family’s expiry. Token expiry limits access and is distinct from deletion of connection history.
- Connection history: terminated grant and related consent history is scheduled for cleanup 90 days after revocation or expiry. Active connection records remain while needed to provide the approved connection.
- Integration audit events: are scheduled for cleanup 180 days after the event. The production integration’s OAuth, MCP, and cleanup service logs have a configured 30-day retention period. Other website, infrastructure-security, support, and account records are retained for the operational, security, contractual, or legal purposes described in the Hazlnut Privacy Policy, rather than being deleted when a token expires.
- Cleanup, backups, and exceptions: scheduled deletion occurs through periodic cleanup and is not instantaneous at expiry. Backup copies follow the underlying backup lifecycle. Records needed for a legal obligation, dispute, or security investigation may be retained for that purpose; expired credentials do not regain access because a record remains.
- ChatGPT: conversation and tool-result copies held by OpenAI follow OpenAI’s policies and your ChatGPT settings, independently of Hazlnut’s cleanup.
Your choices and privacy requests
You choose the requested permissions and locations on Hazlnut’s consent screen. Version 1 requests only profile:read, locations:read, orders:read, customers:read, and menu:read. Your current merchant role and business or location policy can further restrict access. Locations added later require new approval; refreshing a token does not silently add permissions.
You can revoke the connection in Treehouse’s Connected Apps and remove it in ChatGPT’s connection settings. Reauthorization is needed to establish access again. Revocation ends future authorized use; it does not delete source business records, retained security or consent history, or information already returned to ChatGPT. Use ChatGPT’s controls to manage or delete conversations and to review its data settings.
To request access, correction, or deletion of personal information held by Hazlnut, or to ask about retention, contact info@hazlnut.com. Identify the merchant or account and the nature of the request; do not send passwords or payment-card details. We verify identity and authority before acting. For customer records controlled by a restaurant, contact that merchant as well; we can help route the request. Applicable legal or recordkeeping requirements may limit deletion. Rights depend on your jurisdiction, as explained in the Hazlnut Privacy Policy.
Website cookies and analytics
The public Hazlnut for ChatGPT pages use Google Analytics for website traffic measurement. This can process page paths, approximate location derived from IP address, device or browser information, referrer origin, and analytics identifiers or cookies. The page script removes query strings and fragments from the page address it sends to analytics, strips referrer paths, and disables advertising-personalization signals. It does not send merchant tool results or customer search inputs to website analytics. Browser cookie controls, available Hazlnut measurement choices, and analytics blocking can limit this tracking. Other Hazlnut website practices are covered by the main Hazlnut Privacy Policy.
Contact and changes
For privacy questions or integration help, contact Hazlnut LLC at info@hazlnut.com or through our contact page. We will update this notice and its effective date if the integration’s data practices change. This notice describes the read-only version 1 release; it does not authorize additional capabilities.
