Serviio privacy policy
Scope
This policy describes pickup ordering and phone verification. Contact info@serviio.ai with privacy questions. Version 2026-10-18-launch-2.
Phone verification and connection
Serviio stores your normalized phone number, a keyed identifier and a random private customer ID. 39 Miles transports verification texts. Codes expire after five minutes and are stored only as keyed hashes. Codes and connection credentials belong on the secure sign-in screen, never in ChatGPT messages. Verification is for customer access, not consent to marketing.
Information from ChatGPT
ChatGPT may share relevant chat content with Serviio when you use the app. Serviio uses its own authorized connection token to identify your private profile. This phone connection does not supply your OpenAI account ID or ChatGPT password. Serviio does not request your full ChatGPT conversation history.
Order and support records
Serviio stores reviewed dishes, options, quantities, prices, restaurant, customer owner, timestamps and submission state. A real pickup submission shares the pickup name, verified phone and order with the restaurant through 39 Miles. Support records include requests, status, customer explanations and restricted operator evidence. The dedicated reviewer account uses synthetic order and support records without restaurant dispatch.
Providers and purposes
Google Cloud hosts Serviio and its private application database. 39 Miles provides SMS, POS integration and hosted checkout through the restaurant’s configured Stripe or Antom provider. Card details are entered in the provider’s secure embedded form on Serviio checkout or on the provider’s page. Serviio stores order and payment references, checkout links, amount, currency, expiry, payment status and check timestamps, not full card numbers or security codes. ChatGPT receives customer-facing order and payment information needed for the requested action. Raw POS records and POS identifier mappings stay on Serviio’s backend. OpenAI processes conversations under its own policies.
Backups
The app-only backup policy is a daily private Google Cloud backup, scheduled for deletion after 90 days. Cloud deletion processing can take additional time. Deletion from the active app database does not immediately remove data in retained backups. Any recovery must honor later customer-deletion records before customer access resumes.
Access, deletion and retention
Contact info@serviio.ai to request access, correction or deletion. Serviio verifies ownership before acting. Unresolved orders or support matters may need to be settled before associated records can be deleted. Code or token expiry does not itself delete all stored records. Completed pickup orders and closed support cases are scheduled for deletion from the active database by the daily cleanup after 90 days from verified completion or closure. If a related support case closes later, the order stays until that later retention deadline. Unresolved orders and open cases stay until settled. A POS acknowledgement alone does not establish completion. Phone and private profile mappings remain for the returning-customer connection until a verified deletion request is completed. Minimal security deletion markers and operator audit are retained to enforce deletion and prevent unsafe retries; they do not contain the original order or support content.
Returning customers
Reconnect using the same verified phone when required. An order reference alone does not provide access. Historical guest sessions are separate and are not claimed automatically by matching a phone number. Changing phones does not automatically transfer old order history.
Online payment through 39 Miles
Enter card details only on the secure provider checkout. Serviio stores the order and payment status. If status cannot be verified, keep the existing order reference and contact support before paying or ordering again.