Speedway public policy
Privacy Policy
This Privacy Policy explains how Speedway collects, uses, protects, shares, retains and deletes information across Speedway Go, Crew, Central, CrewHQ, delivery, tracking, payments, support, Google services and future payroll-related services.
Updated 29 September 2026
Public URL — Speedway.Global
Hong Kong S.A.R. · Global operations
Who operates Speedway
Speedway Global Operations Infrastructure Limited (Business Registration No. 81104297) is the legal entity operating Speedway services and is referred to in this policy as “Speedway”. Its registered office is Unit 2904-05, 29/F, Universal Trade Centre, 3 Arbuthnot Road, Central, Hong Kong S.A.R. Bestway and RaffsSync are trading names of Speedway. Privacy enquiries can be sent to [email protected] or [email protected].
Information we collect
- Account profile details such as name, phone number, email address, login identifiers, language preferences and support history.
- Go customer activity such as saved addresses, delivery notes, orders, bookings, baskets, payment status, refunds, disputes and support requests.
- Crew and driver activity such as assigned work, availability, route status, task events, delivery proof, attendance readiness and operational updates.
- Central and business activity such as business profile, staff roles, catalogues, orders, Cashier, production, service, customer display and back-of-house workflow events, settlement records and reporting data.
- CrewHQ workforce data such as staff profiles, roles, shifts, attendance events, approvals, 2FA status, device signals, telemetry, geo-location and biometric-style verification status where enabled.
- Payroll-ready and future payroll add-on records such as approved attendance, payee details, pay rates, deductions, reimbursements, payroll exports and employee self-service records where enabled by agreement.
- Technical and security information such as device type, browser, app version, IP address, diagnostics, logs, fraud-prevention signals and security events.
How we use information
- To provide and improve Speedway Go, Crew, Central, CrewHQ and related operational services.
- To process orders, bookings, deliveries, payments, settlements, refunds, disputes and support cases.
- To support fast, reliable and secure Speedway experiences across modern devices.
- To enable workforce visibility, attendance, telemetry, location-aware workflows, 2FA and verification features where configured.
- To prepare payroll-ready records, reports, exports and future payroll add-on workflows where enabled by the customer.
- To protect users, businesses, crews, drivers and Speedway from fraud, abuse, security incidents, service misuse and operational risk.
- To comply with applicable legal, accounting, tax, safety, payment, audit and regulatory requirements.
Location, telemetry and verification data
Speedway uses location, telemetry, device and verification signals to support delivery, dispatch, attendance, field visibility, fraud prevention, safety and service quality. Workforce monitoring, biometric-style verification, 2FA, geo-location and telemetry features are enabled according to customer configuration, staff notices, consent or lawful basis, operating policies and written agreements.
Google account connections and Google API data
Speedway lets authorised users connect Google services to their Speedway account or business. These connections are optional and are used only to provide the Speedway features the user or business chooses to enable. Speedway requests only the Google OAuth permissions needed for the connected feature.
- Google Sign-In and account identity: where Google Sign-In is offered, Speedway may receive the Google account identifier and basic profile information authorised by the user, such as name, email address and profile image, to sign the user in and link the correct Speedway account.
- Google Business Profile: for a merchant-owned connection, Speedway may access business account and location identifiers and merchant-controlled profile information such as business name, address, coordinates, phone number, website, categories, opening hours, attributes, profile text, media metadata, reviews, replies and verification or location status needed for the selected business features. Current Google Business Profile connections may request the
https://www.googleapis.com/auth/business.manage scope.
- Google Ads: for a merchant-owned connection, Speedway may access Google Ads customer and account identifiers, account hierarchy, campaign and advertising metadata, performance metrics and reporting data needed for reporting, analysis and merchant-requested advertising workflows. Current Google Ads connections may request the
https://www.googleapis.com/auth/adwords scope. Campaign changes are not made merely because an account is connected; any write capability must be separately enabled and authorised.
- Maps, Places and routing: Speedway may use Google mapping and place services to support address entry, maps, routing, venue discovery and location-aware features. The data used depends on the feature and the permissions granted by the user or business.
Speedway uses Google data only to provide or improve user-facing features the user or authorised merchant has chosen to enable, including authentication, linking the correct merchant-owned Google account, mapping Google locations to Speedway venues, displaying or reconciling authorised business information, reporting and operational context, reputation and discovery tools, and merchant-requested Google Ads management or reporting. Connected Google data is scoped to the authorised Speedway account or merchant and is not made available to unrelated merchants.
How Speedway accesses, uses, stores and shares Google user data
- Access: Speedway accesses only the Google account data covered by the OAuth permissions shown to and approved by the user for the connected feature. Speedway does not request Google permissions merely for possible future use.
- Use: Google user data is used only to provide or improve the user-facing Speedway feature for which access was granted, such as sign-in, Google Business Profile connection, venue/profile reconciliation, review and reputation workflows, or merchant-requested Google Ads reporting and management.
- Storage: OAuth credentials are stored in protected server-side credential systems. Speedway may retain linked account identifiers, authorised business data, reporting snapshots and audit evidence only where needed to operate the connected feature, maintain security and auditability, resolve support or disputes, or meet legal obligations.
- Sharing and transfer: Speedway does not sell Google user data or disclose it to unrelated merchants, data brokers or information resellers. Transfers are limited to service providers required to deliver the user-facing feature, security or abuse investigation, legal compliance, or another transfer expressly permitted by the Google API Services User Data Policy.
- Retention and deletion: Users can disconnect the Google connection in Speedway, revoke Speedway from their Google account, or request deletion through [email protected] or [email protected]. Google user data that is no longer required for the connected feature is deleted or de-identified unless a limited record must be retained for legal, financial, security, audit or dispute purposes.
How Speedway stores and protects Google data
Google OAuth access and refresh credentials are kept in Speedway's protected server-side credential systems, encrypted at rest in Speedway's secret store, protected in transit using HTTPS/TLS, and are not intentionally exposed in client-side application responses. Where Google issues expiring access credentials, Speedway may use the authorised refresh credential to obtain a replacement access credential while the connection remains active. Speedway keeps connected account identifiers, authorised business data, reporting snapshots and audit evidence only for as long as needed to provide the connected feature, maintain security and auditability, resolve support or disputes, or meet applicable legal requirements.
Users and authorised business administrators can stop future Google API access by disconnecting the Google connection in Speedway where that control is available, by revoking Speedway in their Google account or Google business account settings, or by contacting Speedway Support. A deletion request can also be made through [email protected]. Some minimal audit, financial, security or dispute records may be retained where Speedway has a legitimate or legal obligation to keep them.
Google API Services User Data Policy and Limited Use
Speedway's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Speedway does not sell Google user data, disclose it to data brokers or information resellers, use it to build advertising audiences or serve targeted advertising, user advertisements, personalised advertising, retargeted advertising or interest-based advertising, use it to determine creditworthiness or lending eligibility, create unrelated databases or profiles from Google user data, or use Google user data obtained through Google APIs to develop, improve or train general-purpose or non-personalised AI or machine-learning models. Speedway does not use Google Workspace API data, if a Workspace integration is enabled in future, to develop, improve or train general-purpose or non-personalised AI or machine-learning models. Speedway does not use one merchant's connected Google data to benefit an unrelated merchant. Human access to Google user data is limited to user-authorised support, security or abuse investigation, legal compliance, or other cases permitted by Google's policy.
Sharing and service providers
Speedway shares information only where needed to operate, secure, support or improve the service, or where required by law or written agreement. This can include payment providers, hosting providers, communications providers, mapping services, analytics, support tools, accounting/payroll integrations, fraud-prevention services, banks, regulators, professional advisers and authorised customer administrators.
Security
Speedway uses technical, organisational and operational safeguards designed to protect personal data and business data. These safeguards include secure access controls, role-aware permissions, encrypted transport, monitoring, logging, account protection, operational reviews and controlled access to production systems.
Retention and deletion
Speedway keeps information for as long as needed to provide services, support users, operate the business, meet legal/accounting/tax requirements, prevent fraud, resolve disputes, enforce agreements and maintain safety and security. Users and authorised business contacts can request account deletion or privacy support by contacting [email protected] or [email protected]. Some records remain retained where required for legal, security, accounting, payroll, dispute, audit or fraud-prevention purposes.
Your choices and rights
Users can contact Speedway to request access, correction, deletion, restriction or privacy support for personal data connected to Speedway services. Business and workforce records may also be subject to employer, customer, accounting, payroll, legal, safety or contractual retention requirements. Speedway will review requests according to the applicable service role, identity verification, customer agreement and legal requirements.
International operations and infrastructure
Speedway is incorporated in Hong Kong S.A.R. and operates services across multiple markets, including Indonesia. Speedway services may use RaffsSync Core, a Speedway trading and technology name, together with trusted service providers. Data may be processed, stored or supported from locations outside the user’s city or country where needed to operate secure, reliable and scalable services. Speedway applies operational safeguards and provider controls appropriate to the service and agreement.
Updates to this policy
Speedway updates this Privacy Policy as the platform, workforce services, integrations, legal requirements and operating model evolve. If Speedway materially changes how it accesses, uses, stores, shares or transfers Google user data, Speedway will update this policy and provide an appropriate in-product notice before or when the change takes effect. The latest version is published at Speedway.Global/privacy.