Retopos
Provider platform
Privacy
Effective date: April 20, 2026. This page explains what Retopos collects, why it is collected, and how venue data is handled across the public website, provider backend, and cashier application.
When a customer registers a Retopos product, we collect the name, email address, company or venue name, phone number when supplied, registered product, billing or reference details, venue record, and issued activation key metadata.
Retopos stores venue IDs, public venue codes, activation keys, device bindings, delivery-provider credentials, and provider event history to provision, secure, and support each venue.
The cashier app is designed to work locally after activation. Operational venue data such as menu, tables, bills, and reports can continue functioning on the venue device even when internet access is unavailable.
When a venue connects delivery services such as Uber Eats or PickMe Eats, Retopos stores the necessary provider configuration, callback payloads, and normalized order records so the correct venue can receive incoming orders.
Retopos uses collected data to provision accounts, issue activation keys, manage venue registrations, support delivery integrations, provide customer and admin dashboards, investigate failures, and maintain licensing and device-lock rules.
Retopos shares data only with service providers required to operate the system, such as payment processors, email delivery services, and delivery integration providers connected by the venue. We do not sell venue or customer data.
Sensitive configuration such as provider tokens and credentials is stored in the hosted backend for integration purposes. Device-lock and activation records are retained to enforce one-device licensing until released by an administrator or replaced under support workflow.
For privacy-related questions, support requests, or deletion requests, contact Retopos support at support@retopos.com.