ArterialPulse
Sign in →

ArterialPulse · Legal

Privacy Policy

Effective date: 2026-04-26 · Last updated: 2026-08-12

1. Who this applies to

ArterialPulse is a business-to-business tool used by transportation engineers and consultants to perform arterial corridor travel-time studies. The mobile app is installed by a field engineer; the data flows to that engineer’s organization’s private portal account. ArterialPulse is not directed at consumers.

This policy applies to the ArterialPulse iOS app (com.rhythmengineering.arterial-pulse), the ArterialPulse Android app (com.rhythmengineering.arterialpulse), and the ArterialPulse portal at pulse.rhythmtraffic.com.

2. What we collect

2.1 From the mobile app (during a recording session)

  • Precise location (GPS): latitude, longitude, speed, accuracy, timestamp, and the source (PHONE_GPS / OBD_II / EXTERNAL_GPS) — sampled while a corridor recording is in progress.
  • Run metadata: corridor name, direction, start/end times, signal-passage events, study type (BEFORE / AFTER), time-period bucket, weather notes.
  • Device identifiers (optional): if a paired Bluetooth OBD-II adapter or external GPS is used, the adapter’s identifier is stored locally so the app can reconnect.

We do not collect:

  • Your contacts, photos, microphone, camera, calendar, health data, or web-browsing history.
  • Background location outside an active recording session.
  • Advertising identifiers (IDFA, IDFV).
  • Device fingerprints used for cross-app tracking.

2.2 From the portal (when the engineer signs in)

  • Account credentials: email, hashed password, name, organization.
  • Sync events: timestamps and counts of records pushed/pulled, for audit.
  • Administrative audit events: acting username, action, affected resource identifiers and names, related metadata, and timestamp. These records are visible only to the organization administrator for that organization.
  • Session cookies (ap_session, httpOnly, 12-hour TTL).
  • Interface preferences stored in your browser’s local storage (not cookies, never sent to us): whether you dismissed the onboarding checklist, whether you ticked “app installed”, and whether a study’s settings panel was left open.
  • Bot protection. The sign-in, sign-up and password-reset pages load Cloudflare Turnstile, which may store a short-lived challenge token in your browser. Security only — it is not used to profile or track you.
  • Map tiles. Corridor maps inside the portal load imagery from OpenStreetMap, so your IP address is visible to that service when a map is drawn. No study data is sent with the request.

Full detail, including how to block any of it, is in our Cookie Policy.

2.3 From your customer’s organization

The portal multi-tenants by organization_id. All study data is scoped to the organization that created it. An organization administrator may add additional users and view all data within that organization.

3. How we use it

  • Service operation: computing corridor travel-time, delay, fuel, emissions, reliability metrics, and economic-impact figures.
  • Reporting: generating before/after PDF and CSV reports for the engineer and their organization.
  • Account management: authenticating users, scoping data access, billing.
  • Fraud prevention: rate-limiting and anomaly detection on sync events.

We do not use your data for advertising, profile-building, or sale to third parties.

4. How we share it

  • Within your organization: other authorized portal users in the same organization can access study data they are permissioned for.
  • With service providers: infrastructure (hosting, email delivery, payment processing). Currently: Hostinger (VPS), Cloudflare (CDN/edge), Stripe (billing), GoHighLevel (CRM), the email provider for transactional mail.
  • For legal compliance: if compelled by valid legal process. We will notify the affected organization administrator unless prohibited.
  • Never: to advertisers, data brokers, or analytics resellers.

5. How we store and protect it

  • Cloud storage: PostgreSQL on a single private VPS. Study data is stored only there; Cloudflare’s network sits in front of it and terminates TLS at the edge location nearest you, but does not store your study data. Connections to the portal use TLS 1.2+.
  • Local storage: the mobile app holds an offline-first SQLite database on the device. Soft deletes are used so engineers can recover accidentally removed runs from the same device until a sync purge confirms upload.
  • Passwords are bcrypt-hashed; sessions are signed JWTs in httpOnly cookies.
  • Background location is not used unless an active recording session is in progress. On iOS the blue location indicator in the status bar reflects this; on Android a persistent “ArterialPulse — recording” notification is shown for the whole run. Both disappear the moment you stop data collection.

6. How long we keep it

  • Active accounts: indefinitely, while the organization’s subscription is active.
  • Cancelled accounts: the organization administrator may export and then delete data at any time. We retain a minimum-necessary record for legal/billing and security purposes (synchronization history, administrative audit logs, and invoices) for the applicable retention period.
  • Mobile-only data: runs that have not yet been pushed remain on the device until the user purges them. The “Purge synced data” tool in Settings hard-deletes runs already confirmed uploaded.

7. Your rights

  • Access: you can export all your data from the portal as JSON or CSV at any time.
  • Correction: you can edit run metadata (name, time period, weather) directly in the portal.
  • Deletion: organization administrators can delete projects, corridors, studies, runs, and users. Soft-deleted items are recoverable for 30 days, then hard-deleted.
  • Deleting your account: ArterialPulse accounts are provisioned by your organization’s administrator, not self-registered in the mobile app. To have your account and its associated personal data deleted, ask your organization administrator — who can remove you from the Admin screen in the portal — or request it directly from us at pulse.rhythmtraffic.com/contact or [email protected]. We action verified requests within 30 days. Study data belonging to the organization is retained or deleted at the administrator’s direction.
  • Portability: the export format is open (JSON and CSV) — there is no proprietary lock-in.
  • EU/UK users: GDPR rights of access, rectification, erasure, and portability are honored. Contact [email protected] for assistance.
  • California users: CCPA rights of access, deletion, and “do not sell” are honored. We do not sell personal information.

8. Children

ArterialPulse is for licensed transportation professionals. We do not knowingly collect data from children under 13.

9. Changes

We will publish a new “Last updated” date at the top of this page when this policy changes. Material changes will be notified to organization administrators by email.

10. Contact

Data controller: Rhythm Engineering

Email (privacy and general support): [email protected]

See also our Terms of Service.