Runner’s Review — Privacy & Terms Annex
Aquaduct Data Strategies LLC — DBA: Runner’s Review Version: 1.1-draft Effective Date: March 21, 2026 Last Updated: 2026-03-21
This annex supplements the Aquaduct Data Strategies LLC master Terms of Service and Privacy Policy. It describes data practices specific to the Runner’s Review iOS application and associated backend services. In the event of conflict between this annex and the master documents, this annex controls for Runner’s Review.
App Store Connect URL:
https://legal.aquaductdata.com/annexes/runners-review
1. About Runner’s Review
Runner’s Review is a race discovery and review platform for runners, operated as a DBA of Aquaduct Data Strategies LLC. The application is distributed through the Apple App Store as an iOS application. Backend services are hosted on Google Cloud Platform.
2. Data We Collect
The following data types are collected by Runner’s Review. Data is collected only to the extent necessary to provide the features described.
2.1 Account and Identity Data
| Data Type | How Collected | Purpose |
|---|---|---|
| Apple ID (anonymized user identifier) | Sign in with Apple | Account creation and authentication |
| Email address | Sign in with Apple (if user elects to share) | Account communication, support |
| Display name / username | User-provided at registration | In-app display |
Note on Sign in with Apple: Apple’s Sign in with Apple may provide either the user’s real email address or a privacy-relay email address (Hide My Email), depending on the user’s choice. We accept and work with either.
2.2 User-Generated Content
| Data Type | How Collected | Purpose | Storage |
|---|---|---|---|
| Race reviews and ratings | User submitted in-app | Product functionality — community reviews | Google Cloud SQL |
| Photos and images | User uploaded in-app | Attached to race reviews | Google Cloud Storage (GCS) |
| App usage analytics | Automatically logged when analytics collection is permitted | App usage events (e.g., api_request, race_view, search_performed); collection is privacy-gated via is_analytics_collection_allowed() — only logged when the user has permitted analytics | Google Cloud SQL |
2.3 Precise Location Data
| Data Type | How Collected | Purpose | Retention |
|---|---|---|---|
| GPS coordinates (precise) | Device location services (when permission granted) | Proximity-based race search and discovery | Session only — not persistently stored |
Important: Runner’s Review requests location permission for the purpose of returning nearby race results relevant to the user’s current location. Location data is used in real time for search queries and is not stored to a database, logged to a user profile, or transmitted to third parties beyond the immediate GCP query processing. Users may deny location permission; search by city/zip code remains available without location access.
2.4 Apple HealthKit
Runner’s Review does not access Apple HealthKit data. The application does not request HealthKit permissions and does not read from or write to Apple Health. App usage analytics described in Section 2.2 are automatically logged app-interaction events and are not sourced from HealthKit or any health data source.
If HealthKit integration is added in a future version, this annex will be updated before the relevant App Store release, and users will be notified per the change notification procedure in the master Privacy Policy.
2.5 Technical and Security Data
| Data Type | How Collected | Purpose | Retention |
|---|---|---|---|
| Firebase App Check tokens | Automatically by Firebase SDK | Verify that requests originate from a genuine Runner’s Review app instance (anti-abuse) | Session/request scoped |
| Device type and OS version | App metadata | Compatibility diagnostics and crash reporting | 12 months |
| App version | App metadata | Feature rollout and support | 12 months |
| Error and crash logs | Automatically captured | Bug diagnosis and service improvement | 12 months |
3. Third-Party Service Providers
Runner’s Review uses the following third-party services. Each provider processes data only as necessary to deliver the described function.
| Provider | Service | Data Shared | Provider Privacy Policy |
|---|---|---|---|
| Google Cloud Platform — Cloud SQL | Relational database hosting | Account data, reviews, app usage analytics | Google Privacy Policy |
| Google Cloud Platform — Cloud Storage (GCS) | Photo and image storage | User-uploaded photos | Google Privacy Policy |
| Google Cloud Platform — Cloud Vision API | Image analysis for content review | User-uploaded photos (processed for content moderation) | Google Privacy Policy |
| Google Firebase — App Check | App integrity verification | App Check tokens, device signals (no personal data transmitted) | Google Privacy Policy |
| Apple Inc. — Sign in with Apple | Authentication | Apple ID, email (if shared by user) | Apple Privacy Policy |
| Apple Inc. — App Store / TestFlight | App distribution and beta testing | Standard App Store analytics (aggregate, per Apple’s policies) | Apple Privacy Policy |
Runner’s Review does not use:
- Advertising SDKs or ad networks
- Third-party analytics platforms (e.g., Firebase Analytics, Mixpanel, Amplitude)
- Social sharing SDKs beyond Sign in with Apple
- Location data aggregators or brokers
4. How We Use Your Data
We use the data described in Section 2 to:
- Authenticate and manage your account — Sign in with Apple handles authentication; we store the resulting user identifier to maintain your account
- Deliver core app functionality — Display race listings, store and retrieve your reviews and photos; log app usage analytics events when analytics collection is permitted
- Enable location-based search — Return nearby races relevant to your current location when location permission is granted
- Moderate content — Use Google Cloud Vision to review uploaded photos for compliance with our Terms of Service
- Ensure app security and integrity — Firebase App Check verifies that requests come from legitimate app instances
- Diagnose issues and improve the app — Crash logs, error reports, and usage data help us identify and fix bugs
We do not use Runner’s Review data to:
- Serve targeted advertising
- Build behavioral profiles for third-party marketing
- Store or share location data beyond real-time GCP query processing
5. Data Retention
| Data Type | Retention Period |
|---|---|
| Account data (active users) | Duration of account |
| Reviews | Duration of account; deleted on account deletion request |
| App usage analytics (activity_logs) | 12 months rolling; deleted on account deletion request |
| Photos (GCS) | Duration of account; deleted on account deletion request |
| Precise location data | Not stored — used in-memory for search query only |
| Firebase App Check tokens | Session/request scoped |
| Error and diagnostic logs | 12 months rolling |
To request deletion of your account and all associated data, contact strategies@aquaductdata.com with the subject “Account Deletion Request — Runner’s Review.”
6. Your Privacy Choices
| Choice | How to Exercise |
|---|---|
| Deny or revoke location access | iOS Settings → Privacy & Security → Location Services → Runner’s Review → set to “Never” |
| Delete uploaded photos | In-app photo management, or via account deletion request |
| Delete your account and all data | Email strategies@aquaductdata.com — subject: “Account Deletion Request — Runner’s Review” |
| Access a copy of your data | Email strategies@aquaductdata.com — subject: “Data Access Request — Runner’s Review” |
For full rights including California/CCPA rights, see the master Privacy Policy, Sections 9 and 10.
7. Children’s Privacy
Runner’s Review is not directed at children under 13. We do not knowingly collect personal information from users under 13. If you believe a child under 13 has registered, please contact strategies@aquaductdata.com.
8. Apple App Store Privacy Nutrition Label
The following reflects Runner’s Review’s Apple App Store privacy declarations. This annex serves as supporting documentation for those declarations.
| Category | Collected? | Linked to Identity? | Used for Tracking? |
|---|---|---|---|
| Contact Info (email) | Yes (if shared via Sign in with Apple) | Yes | No |
| Identifiers (User ID) | Yes | Yes | No |
| Photos or Videos | Yes (user-uploaded) | Yes | No |
| Location (Precise) | Yes (when granted) | No — session only, not stored | No |
| User Content (reviews) | Yes | Yes | No |
| App Usage Data (analytics events: race_view, search_performed, api_request) | Yes (when analytics permitted) | Yes | No |
| Crash Data | Yes | No | No |
| Health & Fitness | No | — | — |
| Purchases | No | — | — |
| Browsing History | No | — | — |
| Search History | Yes (search_performed events logged to activity_logs when analytics permitted) | Yes | No |
9. Governing Documents
This annex is to be read together with:
For general contact, support, or privacy requests, see Master Privacy Policy Section 15.
10. Version and Effective Date
| Attribute | Value |
|---|---|
| Version | 1.1-draft |
| Effective Date | March 21, 2026 |
| Last Updated | 2026-03-21 |
| Status | Draft — technical review complete; pending final approval |
Document History
| Date | Version | Changes | Author |
|---|---|---|---|
| 2026-03-21 | 1.0-draft | Initial draft | ADS Legal |
| 2026-03-21 | 1.1-draft | Technical review corrections: (1) removed shoe inventory — feature not in app; (2) rewrote activity_logs as app usage analytics (api_request, race_view, search_performed) with is_analytics_collection_allowed() privacy gate; (3) corrected Search History in Nutrition Label from No to Yes | ADS Legal |
This annex was prepared by Aquaduct Data Strategies LLC and has not been reviewed by a licensed attorney. Apple HealthKit data is explicitly not collected. Accuracy of all data types and third-party integrations should be confirmed before App Store Connect submission.