Skip to content
Back to Pizza Ops Hub

Privacy policy

Pizza Ops Hub privacy policy

This policy explains how Pizza Ops Hub uses information for account access, store operations, its ChatGPT integration and support.

Published by Matthew Travis. Updated November 1, 2026.

What Pizza Ops Hub collects

Hub stores account and access-request information, store assignments, approved permissions and the information saved through its operational workflows. Depending on the tools used, this includes sales forecasts and uploaded actuals; staff names, availability and schedules; checklist responses; food, Coke and prep information; partner contacts; invoices and customer-order details; and calendar activities.

How information is used

Information is used to provide account access, calculate plans, save requested changes, support store operations and respond to support requests. Connection records and technical diagnostics support authorisation, reliable retries, troubleshooting and security checks.

Using ChatGPT

When you connect your account, Hub uses your current store access and the tool permissions you approve to determine what you can read or change. ChatGPT sends tool requests and any requested changes to Hub. Hub returns the authorised information and operation results to ChatGPT. Information shared with ChatGPT is also handled under the terms and settings for your ChatGPT account.

Service providers and integrations

Hub uses Vercel for hosting, Supabase for account and operational data, and Trigger.dev for background planning and integration jobs. Supported schedule changes can update saved posts and files in the Slack channels configured for your store. These providers process the information needed for their respective services.

Support email is forwarded through Cloudflare Email Routing to a Gmail inbox managed by the publisher. Include only what is needed to explain your request; do not email passwords, access tokens or payment-card details.

Connection and security records

Hub stores connection grants, refresh-token hashes, token-family history and operation metadata. Integration audit events record identifiers, tool names, outcomes and timing rather than tool inputs or returned business records. Technical diagnostics can include request and session identifiers, relevant account and store identifiers, routes, errors, timing and outcomes. Logging filters redact credentials and common personal-data fields.

How long information is kept

Saved business records and support emails are kept until manually deleted. They are not automatically deleted when you stop using Hub or disconnect ChatGPT. Consumed refresh-token hashes and token-family history are retained for replay detection after a connection expires or is revoked; they have no scheduled automatic deletion.

Access tokens expire after five minutes. Connections expire after 30 days without a successful refresh and have no absolute expiry. They can be revoked sooner following a security or permission change. These access limits do not set the retention period for saved records.

Technical logs and backup copies follow the retention settings of the services that hold them. Deleting a saved record does not immediately remove copies in backups or information already shared with ChatGPT or Slack. Those copies are subject to the relevant service's retention settings and controls.

Your choices and privacy requests

You can disconnect ChatGPT to revoke its Hub connection. Disconnecting does not undo saved changes, delete business records or remove retained security history. Use the available Hub controls within your permissions to correct or delete records, or contact the publisher about access, correction, retention or deletion.

Send support and privacy requests to support@pizzaopshub.com.