pace.guard
Sign in

We've got your back

Support.

Need a hand, want to leave, or just want to see exactly what we have on you? Everything you can ask of us lives on this page.

Last updated · May 20, 2026

What we actually store about you

No marketing pitch — this is the full inventory of everything PaceGuard puts in its database when you use the watch app and the dashboard. If it isn't on this list, we don't have it.

Identity

Google account

  • Google subject ID (the stable sub)
  • E-mail address
  • Display name (first + last)

From Google Sign-In so we know which account a fix belongs to.

Trails

Location fixes

  • Latitude, longitude, altitude, accuracy
  • Timestamp (UTC)
  • Optional heart rate (bpm)
  • Session ID grouping fixes into one trail

So we can draw your route on the map.

Device

Watch metadata

  • Device model (e.g. Pixel Watch 2)
  • Random device + session identifiers
  • Heartbeat "ping" frames (no coordinates)

So the dashboard knows whether your watch is currently online.

SOS

SOS signals

  • SOS flag
  • Last known position at the moment SOS was raised

So your contacts can see where you triggered SOS from.

Billing

Subscription state

  • Google Play purchase token (server-side only)
  • Current entitlement (plan, expiry)
  • Real-Time Developer Notification events from Play

So premium features unlock for the right account. We never see your card number — Google handles payment.

Ops

Operational logs

  • Request counts, error traces, latency
  • Source IP (rotated after 30 days)

So we can keep the service up and fix bugs.

Not stored: contacts, photos, microphone audio, on-watch activity outside PaceGuard, anything while the app is closed, or any data sold to a third party. Ever.

What is encrypted, and where

Where the data livesProtection
On your watch — auth tokens, queued fixes waiting to syncAndroid EncryptedSharedPreferences using AES-256-GCM, backed by the device's hardware-backed keystore.
In transit — watch ⇄ backend ⇄ dashboardTLS 1.2+ with modern ciphers. HTTP is redirected to HTTPS at the edge.
Session JWT in your browserStored in localStorage for this origin only. Signed (HS256) on the server, ~24h TTL.
Database — fixes, sessions, identities, billingPostgreSQL inside the EEA, with disk-level encryption at rest provided by the hosting provider. Daily encrypted off-site backups.
Google Play purchase tokensStored server-side only; never exposed to the dashboard or watch UI.
Map tiles via MapboxMapbox sees the bounding box you're viewing — never your identity, your account, or your full route.

Delete my account

You can close your account at any time. We don't put it behind a survey, a phone call, or a retention offer.

Self-serve

Delete it yourself

The fastest way is to do it yourself, on the account deletion page. Sign in, confirm twice, and it's done: your watches sign out and you leave every family straight away, and your account — every fix, trail, SOS event, device record and subscription reference — is erased within 30 days. You can cancel from that same page any time before the deadline.

Delete my account →
Prefer email?

Or ask us to delete it for you

If you've lost access to the account and can't sign in, drop us a line and we'll wipe, within 30 days:

  • Your Google identity (sub, e-mail, name)
  • Every location fix and heart-rate sample, across every device
  • Every session, SOS event and device record
  • Subscription history and Play purchase tokens (anonymized for legal/tax retention where required)
  • Operational logs referencing your account
Email a deletion request

We confirm by reply within 30 days, as required by the GDPR.

Want to clean up first, without deleting the account?

From the dashboard you can already:

  • Delete individual location fixes
  • Delete an entire session (trail)
  • Wipe a device's entire history
  • Export your data as JSON or GPX before deleting it

Get support

PaceGuard is a small operation — there's no chatbot, no ticket queue, just a human reading your message. We answer within two working days.

Your message goes directly to the PaceGuard team. You can also email support@paceguard.io.

Other ways to reach us

For more on the legal basis and retention rules, see the privacy policy.