Who develops DB Timer
DB Timer is developed by Donald W. Jordan under the WolfsRaven developer brand. Questions about this policy can be sent to support@wolfsraven.com .
Information you enter in the app
DB Timer processes the race and participant information that you enter or import. This may include names, registration identifiers, bib numbers, age, gender, race or heat assignments, participant status, start times, lap crossings, splits, and results.
The app also records correction and review information, including the operator name, reason, original entry, and later decision. Timing records contain technical evidence such as timestamps, device uptime, and process or boot identifiers to support elapsed-time calculation and recovery.
Local storage and use
Race information, timing events, backups, settings, and emergency-capture records are stored locally in the app’s storage. DB Timer uses them to time races, calculate splits and results, recover saved sessions, and maintain an audit history.
The current app has no developer-operated race-data server, automatic race-data upload, advertising SDK, or third-party analytics SDK. It does not require a DB Timer account. Device storage protection and any device-level backups depend on your Apple device and account settings.
Files you import, export, or share
You choose participant files to import and initiate exports, backups, and sharing. Exported files may contain participant information and timing history. If you save a file to iCloud Drive or another storage provider, or share it by email or another app, that service handles the file under its own policies.
The organizer controls which participant information is entered and which exports are shared. Review recipient and file contents before sharing race records.
Device diagnostics
The app reads battery and available storage information to show race-day warnings. It uses device uptime and clock evidence to calculate elapsed time and detect recovery issues. Diagnostic exports are initiated by you. Review any diagnostic file before sending it.
TestFlight, crash reports, and support
If you install DB Timer through TestFlight, Apple processes beta installation, usage, crash, and feedback information according to Apple’s TestFlight terms and privacy practices. The developer may receive crash information and feedback made available through Apple’s testing tools.
If you contact support or submit feedback, the developer receives the information you provide, including your email address, message, screenshots, and any attached files. This information is used to respond, investigate problems, and improve the app. Avoid sending participant records unless they are needed for the issue.
Retention and deletion
Race data remains in the app until you remove it or delete the app. Deleting a race may leave a previously created backup. Exported files, saved backups, and device backups may remain in the locations where they were saved and must be managed separately.
Support correspondence is kept as needed to resolve the request and retain relevant troubleshooting history. You can contact support to request deletion of correspondence you submitted, subject to legitimate retention needs.
This website
This website provides app information, help, and testing guidance. The supplied site has no account system, contact form, advertising, analytics script, or tracking cookies. Its fonts, scripts, logos, and app screenshots are served with the site. Gallery and FAQ interactions run in your browser.
The hosting provider may process standard request information, such as IP address, request time, browser details, and the pages or files requested, to deliver and protect the website. Links to Apple, the club website, and other external services are subject to those services’ policies.
Children and participant information
DB Timer is a tool for race organizers and volunteers. Organizers are responsible for handling participant information appropriately, including information about minors, and for using suitable permissions for imports and published results.
Changes to this policy
This policy will be updated when the app’s data practices change. The effective date above identifies the current version.