Privacy policy

Effective October 21, 2026

This notice describes information used by the Benton Technology website and our activity tracking, shoe mileage, and race technology projects. The information involved depends on the project and the features used. The portfolio pages do not accept activity uploads. A separate, owner-restricted Garmin connection page handles authorization for Benton Running Log.

Who we are

Benton Technology is operated by Jacob Benton in the United States. Benton Running Log is operated by Benton Racing LLC and is currently restricted to its owner; it is not an open, multi-user service. Our work includes independently developed running logs, connected shoe mileage tools, race timing software, and results websites.

Activity and running information

Our activity tracking tools may import records from a connected activity service, including Garmin, or use activity files and manually entered records. Information can include an activity identifier, activity type, date and time, distance, duration, pace, elevation, splits, location or route information, and notes. A running log may also include race names, finish times, and placements.

We use these records to maintain activity history, display individual runs, calculate mileage and other summaries, compare activity over time, and present running and race statistics. Activity identifiers help match imported records and prevent duplicate entries. Manually entered notes and corrections can supplement imported information.

Garmin data and authorization

Benton Running Log imports Garmin data only for accounts whose owner authorizes access. Garmin activity data can include account and activity identifiers, device information, activity dates and times, distance, duration, pace, lap splits, heart rate and other recorded activity measurements, GPS routes, and elevation. This information remains associated with the authorized individual; it is not collected solely as anonymous aggregate data.

We use Garmin data to maintain a private running history, display workout statistics and route maps, generate elevation profiles, compare training and race performances, calculate shoe mileage, add location and weather context, and answer user-requested running-log searches. We do not sell, rent, license, or provide Garmin data to data brokers or advertisers.

The Garmin developer connection uses Garmin's authorization and permissions screens. Garmin account passwords are entered with Garmin, not collected by our application. The authorization callback and server-side token exchange run on our DreamHost-hosted site behind Cloudflare. These providers therefore process connection requests, Garmin activity notifications, and transfers of original activity files, which can include GPS routes and other recorded measurements. DreamHost stores queued notifications and temporary original files in private server-side storage, alongside the developer app credentials and connection tokens, outside the public website directory. After the home importer confirms a completed import, the temporary DreamHost file is deleted; private delivery metadata may remain for duplicate prevention and diagnostics. Files awaiting a successful import remain queued for retry. Client secrets and access tokens are not displayed to website visitors or included in the public source code.

The existing Personal API connection is separate from the developer app connection. Starter developer access receives newly shared data after authorization and does not provide historical backfill. Previously imported activity history may remain in the private running log.

AI transparency: optional searches and summaries

The running log includes an optional AI Search feature using Anthropic's API. When you choose AI Search and submit a request, the application sends your question and database-schema context to Anthropic to interpret the request. Relevant query results, which may include Garmin activity information, identifiers, locations, performance statistics, or notes, may then be sent to Anthropic to prepare a response. The fields sent depend on the question and results; this is not a promise that every request excludes identifiable or sensitive activity information.

AI processing is for searches and summaries requested by the user. We do not use Garmin data or anything derived from it to train, fine-tune, evaluate, benchmark, or improve AI models, and do not authorize service providers to use that data for those purposes. Anthropic's commercial API does not use inputs or outputs for model training by default. We do not submit Garmin data as model-training material or feedback examples. AI responses can be inaccurate and should be checked against the underlying records.

Before using AI Search, review this disclosure and choose whether to send your request and relevant results to Anthropic. You can withdraw permission for future AI processing by stopping use of AI Search and contacting the operator directly through your existing private contact channel to request that the feature be disabled for your data. Ordinary running-log viewing and non-AI searches do not require sending query results to Anthropic. Withdrawal does not automatically recall information previously processed; requests concerning that information can also be made through the same contact.

Shoe mileage and connected devices

Shoe tracking projects associate activities with particular pairs of shoes. Information can include shoe names, shoe or storage-bin identifiers, shoe selections, mileage adjustments, and timestamps from shoe-bin opening and closing sensors. These events can help determine which shoes were used for an activity.

We combine activity distance with shoe assignments to calculate cumulative mileage for each pair. Totals may appear in a web dashboard or on connected displays. Corrections and manual selections help keep those totals accurate.

Location and weather context

Location and activity dates or times may be used to add a place name or weather conditions to a running record. This context can include temperature, humidity, and dew point, helping explain conditions during an activity.

Where those features are enabled, the tools may send coordinates to OpenStreetMap Nominatim for a place-name lookup, coordinates and an activity date to Visual Crossing for weather information, or a time window to WeatherFlow to retrieve weather-station observations. These requests disclose the lookup information to the corresponding provider; enriching a running record does not require sending that provider the entire running history or shoe log.

Browser maps and software delivery

When a running-log map is displayed, OpenStreetMap tile servers receive requests identifying the map areas being viewed, together with ordinary browser request information. Those tile coordinates can reveal an approximate geographic area. The route itself is drawn by the browser from the private running-log data. jsDelivr and unpkg supply charting and mapping libraries and receive ordinary asset-request metadata, such as IP address and requested library URL; our application does not intentionally upload activity records to those CDN services.

Race timing and results

Race projects may use participant rosters, bib and chip identifiers, finish times, placements, and finish-line images or video to identify finishers, review timing evidence, correct results, and publish event results. Event-specific publication practices are separate from an individual's activity history and shoe mileage records.

Storage and service providers

Activity and shoe records are processed by our project software and may be stored in databases, activity files, and local or network storage. Connected sensors and displays exchange the information needed for their function, such as bin events and mileage totals. The current personal shoe-tracking implementation uses owner-controlled servers, PostgreSQL, network storage, and Raspberry Pi displays.

DreamHost hosts this company website, and Cloudflare provides its delivery and security layer. They may process standard web request information, including IP address, requested page, browser information, response status, and access time, to deliver and protect the site. The company pages do not include an advertising tracker or a separate analytics script.

Garmin provides the authorized activity service; Anthropic processes optional AI requests and their selected results; OpenStreetMap Nominatim processes geocoding coordinates; Visual Crossing processes coordinates and dates for weather lookup; WeatherFlow processes station identifiers and requested observation time windows. The Pushover notification service processes activity notifications where enabled, including the run date/time, distance, duration, elevation gain, weather context, and notification destination identifiers. These are supporting processors or integration providers, not purchasers of our activity data. A list of all enabled providers for the current owner-operated running-log flow is given in this policy; changes to that flow will be reflected here.

External activity, mapping, weather, and event services have their own privacy practices. Links from this website lead to sites with their own notices. Information may also be disclosed when required by law or to protect the security of our systems.

Retention and privacy choices

Activity histories and shoe mileage records support comparisons and cumulative totals over time, so they may remain in project storage across multiple activities and seasons. Corrections, reimports, and backups can affect which copies remain. Retention depends on the project and storage configuration; this notice does not promise automatic deletion after a fixed period. Hosting logs are subject to the hosting and security providers' retention practices.

Access, correction, export, deletion, and withdrawal

The current service is owner-operated. To request access to your information, correct a record, obtain an export of your running-log records or available original activity files, request deletion, or withdraw consent to a specific use, contact the operator directly through your existing private contact channel and identify Benton Running Log. The operator will verify the requester's identity before disclosing or changing private data. The running log also supports record corrections and deletion, and the shoe tracker supports shoe selections and mileage adjustments.

You can revoke the developer app's future Garmin access using the disconnect control on the owner connection page or Garmin Connect's account permissions. The Personal API key can be revoked separately in Garmin Connect. Disconnecting does not itself delete previously imported running history; request deletion separately if desired. Withdrawing AI permission is separate from disconnecting Garmin, because stored history can still be present in the running log.

For deletion requests, we remove the applicable records and activity files from active project storage, subject to information we must retain for legal or security reasons. Backup copies may remain until replaced or removed under the storage system's backup practices; retained copies must not be restored for normal use without honoring the deletion request. No automatic fixed deletion schedule is currently configured for the owner-operated archive. We will explain the available deletion scope and any retention limits when handling a request.

Updates

We will update this page when the practices described here change. The effective date identifies the latest revision.