Paced
Privacy PolicyTerms of ServiceCookie PolicyAcceptable UseDPASubprocessorsSecurity & Trust
Back to app
Privacy PolicyTerms of ServiceCookie PolicyAcceptable UseDPASubprocessorsSecurity & Trust

Documents

Privacy PolicyTerms of ServiceCookie PolicyAcceptable UseDPASubprocessorsSecurity & Trust

Subprocessors

Effective: 3 June 2026 Last updated: 3 June 2026

Overview

Paced uses a small number of third-party services ("subprocessors") to deliver the platform. This page lists each subprocessor, their role, and the location where they process data.

We review our subprocessors regularly and update this page when changes are made. If you do not agree with our use of a subprocessor, you can stop using Paced and delete your account and data at any time from your account settings.

Current subprocessors

SubprocessorPurposeData processedProcessing locationTransfer mechanism
Google Firebase / Google Cloud
(Google LLC)
Authentication and database (Cloud Firestore) for account and ride dataAccount email, authentication data, and the ride data you log (distance, duration, elevation, route name, ride type, notes)United States (primary), EU/UK regional options availableGoogle Cloud DPA with SCCs
Vercel Inc.Serverless compute and hosting for the Paced applicationRequest headers, IP addresses (transient), application code executionUnited States and edge locations globallyVercel DPA with SCCs

Services not considered subprocessors

The following services are used by Paced but do not process personal data on your behalf in their capacity as our subprocessors:

  • Google Fonts — font delivery via CDN. Requests are made from users' browsers directly to Google's CDN. Paced does not pass personal data to Google for this purpose.
  • Font Awesome — icon font delivery. Same as above.

Notification of changes

We will update this page at least 30 days before adding a new subprocessor that processes personal data. If you do not agree with a change, you can delete your account and data at any time from your account settings.