Effective date: November 1, 2026
Controller: Li Shenghao (李晟豪), individual developer in China. Contact: racerecorder@163.com.
Race Recorder processes email address, account/user ID, device or installation ID, authentication tokens, precise and background location, speed, heading, track, lap, vehicle, challenge and leaderboard data, photos or other content you submit, subscription transaction identifiers, and product-operation analytics events generated by older versions. Camera video and microphone audio are stored locally unless you take a separate explicit upload action.
Data is used to provide recording, timing, analysis, authentication, cloud backup, community, moderation, subscriptions, security, troubleshooting, and service reliability. We do not use advertising SDKs or cross-app tracking.
Driving data is local by default. Explicit login, cloud backup, community publishing, room submission, or leaderboard submission sends the necessary data to Tencent Cloud services hosted in China. If you separately consent to distance verification, necessary coordinates and elapsed times are also sent to that service after a recording or challenge ends to verify driver growth, never per GPS point. Public standings participation is a separate choice and is off by default. You can disable verification or leave the standings at any time. Apple provides MapKit, WeatherKit, Sign in with Apple, and App Store payments under its own terms. Cross-border access may occur when you use cloud functions from another country or request support.
We retain local data until you delete it or uninstall the app. Cloud data is retained while your account or submitted content is active, until you delete it, request deletion, or retention is required for security, dispute handling, or law. The specific database backup deletion period is described below.
You can access and delete records in the app, withdraw optional permissions in iOS Settings, delete your account in the app, or contact us to request access, correction, deletion, restriction, or a copy of applicable personal data. We may verify identity before acting.
Do not submit another person's image, location, or content without authority. The service is not directed to children. Users below the applicable age must have guardian authorization. Material policy changes will be announced in the app or on the policy page.
Send diagnostic report (2026-10-22)
To help investigate a problem, you can send a diagnostic report to Race Recorder support (Li Shenghao) through Tencent Cloud in China. Sending is optional and requires your agreement for this report. There is no continuous automatic upload. Viewing the report performs normal login and service checks but does not submit the report. Cancelling does not affect recording or playback. A request already sent cannot be recalled by closing this page.
The report contains app/build and system versions, an unknown network-type field, a configuration fingerprint, and up to 300 structured events from the last 10 minutes (under 48 KiB): event times, counts, action/page/error codes, request/trace IDs, durations, retry flags and HTTP status. It excludes passwords, tokens, raw locations, full tracks, avatar URLs and request/response bodies. Authentication is sent separately; the server associates the report with your account and uses an IP-derived key for rate limiting. This is not anonymous. Authorized support personnel use it for troubleshooting. For access or deletion requests, email racerecorder@163.com with your RR report ID; identity verification may be required. The diagnostic retention policy is seven days for online reports and their ownership records, followed by hourly batch cleanup. After verifying ownership, support handles deletion requests at racerecorder@163.com and removes data that can be attributed to you. Limited anti-abuse records expire within two hours; a deletion fence can remain for seven days to prevent an old report from being resubmitted. Hourly expiry cleanup is enabled. Maintenance records distinguish completed, failed, and review-required work. Legacy reports may lack verifiable ownership. Tencent Cloud retains database backups for seven days. After an online document is deleted, historical database backups containing it are cleared within seven days at the latest, rather than immediately. This period applies only to database backups, not to object-storage backups such as photos and videos.
Account deletion removes public photos, track content, vehicle contributions, personal results and related copies uploaded by you. Independent contributions by other users remain; their association with a deleted event is marked as deleted. Verified data is removed in batches. Uncertain ownership requires human review and remains incomplete in the app; we do not guess ownership or report premature success. Available Apple credentials are revoked; legacy accounts without a revocable token receive instructions to revoke access in Apple account settings. Minimal deletion receipts and denial records prevent old sessions or delayed writes from restoring data. Database backups are retained for seven days. After an online document is deleted, related historical database backups are cleared within seven days at the latest, rather than immediately.
After your deletion request is accepted, we aim to delete the account and associated online data within 7 business days. This is a processing target, not a waiting period. Requests requiring human review remain incomplete; reaching the target date does not mark them complete. If processing exceeds this period, contact racerecorder@163.com with your deletion request reference. Completion is confirmed in the app.
Automatic usage analytics is paused in this version. Launch, login and feature actions no longer generate or upload analytics events or create an analytics installation identifier. Upgrading clears the local legacy analytics queue. The device identifier required for authentication and necessary local fault logs remain. Shared endpoints for older clients are not yet disabled; historical analytics remains covered by personal-data deletion and retention review. Sending a diagnostic report still requires separate consent for each report.
Community protection processes the reporting account ID, target event, report reason, handling status, receipt and block relationships for moderation and filtering public events, recommendations and leaderboards according to your choices. Report or block an uploader from event details; view receipts and unblock from Driver Center, or contact racerecorder@163.com. Management actions require server-verified privileges.
Sign in with Apple uses the existing authentication service to verify identity. The server encrypts revocable Apple credentials bound to the verified account for account security and revocation during deletion. They are excluded from diagnostic logs. Historical App Store purchase records remain; all previous subscriptions have been removed from sale and formerly member-only features are free.
Weather queries and diagnostic management
When the save-record screen requests weather, the query location and date are sent through Tencent Cloud to Apple WeatherKit; this does not require uploading the full recorded route. Known Apple weather includes the Apple Weather mark and legal attribution link. The diagnostic report screen also lets you request deletion of online reports whose ownership can be verified. Backup handling and data with unconfirmed ownership are described separately.
Driver growth and public standings: new XP, counted distance, challenge counts and new publication counts start at server activation; historical data is not imported. Only after your separate consent, necessary coordinates and elapsed times are sent at the end of a recording or challenge for verification, never per GPS point. Coordinates are processed in memory and discarded when the request ends. At most 20 pending activities are kept locally, isolated by account; withdrawing verification removes pending verification copies and preserves original recordings. Public participation is a separate choice, off by default; leaving preserves private growth. Public entries contain only avatar, nickname, level, XP, verified distance and new publication count. The server stops serving an entry immediately after leaving; already loaded pages expire within five minutes. History displays 90 days; totals and minimal deduplication and moderation reversal receipts remain until account deletion and are removed through the existing closure process. Driver reports and blocks use community protection.
P Room content protection: reports process the account, room or member identifiers, reason, receipt and status for the reporting user and authorized moderators. Moderators may inspect the reported room name, description, cover or avatar and restrict content. Blocking a host also leaves the room; a host blocking a member removes that membership. Other blocks hide that person’s displayed content. Leaving or blocking does not delete previously submitted results; account deletion clears them under the existing policy. Reports and blocks can be managed from Driver Center. Unblocking does not automatically restore membership.