Last updated: 2026-10-15
Pacexis engages the third-party services below to process user data on our behalf. Each is bound by a data processing agreement (DPA) and processes only the data described. We update this list when we add, remove, or replace a provider; the “last updated” date at the top reflects the most recent change.
Questions about our sub-processors or to request a copy of a DPA: [email protected].
Pacexis is operated by nunocaseiro. The services listed below are sub-processors acting on our instructions; we remain the controller of your data. Contact [email protected] for any request under the GDPR.
Purpose: Compute and database hosting (API, web, PostgreSQL)
Data shared: All Pacexis data
Purpose: DNS, TLS and CDN for pacexis.com; object storage (R2). R2 is planned to hold encrypted database backups — see below.
Data shared: Web and API traffic. R2 does not hold user data today. A planned change will store database backups there, encrypted by Pacexis before upload, in a bucket created with EU jurisdiction; we will update this entry when it takes effect.
Purpose: Transactional email delivery (data export ready, payment failed, trial ending, weekly summary)
Data shared: Email address, message content
Purpose: Sign in with Apple, push notifications (APNs)
Data shared: Apple ID, device token
Purpose: Sign in with Google, Google Calendar OAuth, Firebase Cloud Messaging (push notifications)
Data shared: Google account email, device token
Purpose: AI model for every AI feature: run insights, race briefing notes and recaps, weekly and monthly summaries, pain-pattern summaries, shoe suggestions and morning briefs (all only with your AI consent). Reading workout text, screenshots and calendar events you submit.
Data shared: With your AI consent: health and fitness data (run dates, distance, duration, pace, splits, heart rate, cadence, feel ratings and tags, race notes, pain logs, planned workouts, shoes, race goals, race-day weather), linked to your account by Pacexis; not your name or email. Always: the workout text, screenshot or calendar event you submit to be read. Requests Anthropic flags as abuse can be kept for up to 2 years; not used to train its models (commercial terms).
Purpose: Web subscription payments + Customer Portal
Data shared: Email, billing details, subscription state
Purpose: In-app subscription management (iOS + Android)
Data shared: Subscription state and purchase history from the App Store or Google Play, linked to your Pacexis account ID (an anonymous app user id before you sign in)
Purpose: Product analytics on the web and in the mobile apps (opt-in only, off by default)
Data shared: Product events (pages and screens used). Only after you opt in to analytics: the cookie banner on the web, the consent screen or Settings → Privacy in the apps.
Purpose: Analytics (opt-in only), mobile crash reporting (Crashlytics) and push delivery
Data shared: Analytics: app and web events, only after you opt in to analytics. Crashlytics: crash stack traces, device details and a hashed form of your account ID. Cloud Messaging: device token.
Purpose: Backend + frontend error tracking and performance traces
Data shared: Error reports and performance traces: stack traces and request metadata (method, URL path, status). The API and the web app remove cookies, auth headers, query values and the user agent before sending, and replace tokens in URL paths with a placeholder. Traces from the mobile apps are not yet scrubbed the same way and can include the user agent and tokens in URL paths.
Purpose: Infrastructure metrics and log aggregation
Data shared: Server metrics and structured server logs, kept for up to 14 days, with pseudonymous internal user IDs. IP addresses, cookies, auth headers and query strings are removed before sending, and tokens in URL paths are replaced with a placeholder.
Primary data storage (Postgres + object storage) sits in the EU. The AI processing does not: the Claude API can run on servers outside the EU, mainly in the US. Those transfers rely on the Standard Contractual Clauses (SCCs) in Anthropic's data processing terms. A small number of other US-based services are accessed under SCCs too. Anthropic receives your health and fitness data only with your AI consent. We don't send it your name or email address, unless you type them into a note, a shoe name or a workout title; see the privacy policy.
We give at least 30 days' notice before adding or replacing a sub-processor with material access to personal data. Notice goes to the email on file and is published here.