Privacy Policy
Impact Tracker · Last updated September 16, 2026
This policy describes how Ringrust AB handles information in Impact Tracker. The app supports reviewing training videos, recording training information, profiles, coaching and communication between users. The sections below explain how information is handled when you use these features.
Contact
For privacy questions, requests to access or correct your information, or help deleting your account or data, email ringrustfeedback@gmail.com. You can request deletion without reinstalling the app. See Delete your Impact Tracker account and data for instructions.
Account and profile information
An account is required to use the app. Account information includes your email address, authentication information, an account identifier, a username and a display name. Firebase Authentication provides sign-in and account security. If you sign in with Google, Google and Firebase process the information needed to authenticate your account.
You may add profile and cover images and details such as your date of birth, gender, height, reach, weight class, sport, experience, club, country, city and social links. Profile information is stored using Firebase, and profile images use Firebase Storage. These details support your sporting profile and the app’s social and coaching features. Country and city are optional details that you enter yourself; they are separate from location inferred by Analytics.
Visibility controls affect what other users see; they do not mean that all information is stored only on your phone. Other signed-in users can find accounts through the app’s user search. Your username and display name can be included in search and profile information.
Training records and video review
Training and review information can include session titles and dates, participants, rounds, manually marked punches, scores, timestamps, annotations and notes. While you are signed in, review metadata can synchronise automatically with Firebase, including video filenames and local file paths. Calendar entries can also synchronise, including titles, times, notes, statistics and participants. This supports saving your records, restoring supported metadata and providing coaching and analysis features.
Imported and recorded review videos, their audio and local thumbnails are stored on your phone. Automatic review-metadata synchronisation does not upload the video files themselves. Keep important original videos separately: synchronised metadata cannot restore a missing local video.
Profiles, coaching, messages and sharing
Profile visibility, coach relationships, result visibility and accepted sharing requests control access to supported profile and analysis features. Profile fields are public by default unless you change their visibility. Following another account does not require that account to approve the follower. A followers-only profile is therefore not a closed group of individually approved people.
Profile-image links already obtained by others are not protected by the followers-only setting. Do not use profile or cover images for sensitive material. Messages and their sender identifiers, timestamps and read status are stored in Firebase and made available to the participants in the conversation.
When you choose to export or share files, recipients can receive independent copies. Removing access inside the app does not recall those copies. Only use and share recordings and information that you are entitled to use, and inform other people who appear in your recordings.
Diagnostics and analytics
In Android version 1.0.0 (build 12), Google Analytics for Firebase collection is disabled, including Analytics collection of the Android advertising identifier. This version does not send app-use events to Google Analytics or use Analytics to derive an approximate location. This Android change does not change the collection settings in earlier builds or in the iOS app, and it does not delete information collected previously.
Firebase Crashlytics remains enabled to help identify crashes and reliability problems. Crashlytics and its installation and session components can automatically process installation identifiers, device and operating-system information, crash and diagnostic information, and session activity such as when the app is brought to the foreground. The app does not offer a switch for this automatic diagnostic collection. Disabling Google Analytics does not disable these separate services.
Earlier development builds and the iOS app may use Google Analytics for Firebase to measure app use, including app-instance identifiers, app-use events and device information. Where Analytics is enabled, it can derive an approximate location from the network address; earlier Android development builds may also process the Android advertising identifier when available under the device’s settings. Google processes information through these services; further information is available in Firebase’s privacy information and Google’s Privacy Policy.
At the time of this update, the Analytics “Google products & services” data-sharing setting and Google signals are turned off, and no Google Ads account is linked to the Analytics property. Contributions to modeling and business insights remain enabled; Google describes this use as combining data in aggregated, de-identified form so that individual users cannot be identified. Access for Analytics technical support is also enabled. These settings concern Analytics data where collected, including retained information from earlier collection. See Google’s explanation of Analytics data-sharing settings.
Feedback and support
When you send feedback, the app submits your subject and message to its Cloudflare feedback service. The service uses your signed-in account to include your account identifier, email address and name, together with the message’s language, platform and submission time, in an email to the support mailbox. Your email address can be used to reply. Network and account information is used to limit abusive requests. The service records delivery or error status. Opening the feedback form does not send your message.
Do not include passwords, verification codes or unnecessary sensitive information in feedback. Previously submitted feedback is not automatically deleted by the app’s account-deletion function; contact us if your request should also cover that feedback.
Permissions and service providers
Camera, microphone and media permissions support recording, choosing files and saving exports. Notifications support app reminders. You can manage permissions in Android settings; denying a relevant permission can prevent that feature from working.
Google Firebase provides authentication, databases, profile-image storage and backend functions, as well as analytics and crash services. Cloudflare provides the feedback service and website infrastructure. Information is transmitted to these providers to operate the relevant features. Social and instructional links can open external services, whose privacy practices apply when you use them.
Storage, retention and deletion
Local files and cloud records are separate. Signing out does not delete your account or local videos. In the app, go to Settings → Account → Delete account, confirm your sign-in again, and confirm deletion. The app waits for the server’s result before reporting that deletion is complete. If the app reports an error, contact us rather than assuming that deletion is complete.
Successful account deletion removes your sign-in account, cloud profile and username entry, profile images, owned cloud review and coaching-analysis records, calendar records, conversations and messages, and supported account relationships.
Service-provider deletion also includes processing of retained copies. Firebase states that authentication information is removed from its live and backup systems within 180 days after deletion of the associated user is initiated. See Firebase’s data-processing and retention information.
A server record of the deletion remains, including the account identifier, status, timestamps and technical cleanup results, so that the outcome can be checked and failed cleanup can be investigated. Previously sent feedback remains in the support mailbox and is not removed by the account-deletion function. Analytics, crash and other operational records are handled separately from the account’s cloud records. Contact us if your request should also cover these records or feedback that identifies you.
For previously collected Analytics data and data from app versions where Analytics remains enabled, Google Analytics retention is configured to 2 months for event data and 14 months for user data. New activity restarts the user-level retention period. These settings apply to detailed data covered by Analytics retention controls; standard aggregated reports are not subject to these periods. Eligible expired data is removed in Google’s monthly deletion process. See Google Analytics data retention.
Firebase Crashlytics keeps crash details and associated identifiers for 90 days before starting removal from its live and backup systems. This is the start of the removal process, rather than a guarantee that every retained copy is gone on day 90. See Firebase’s Crashlytics retention information.
Google Cloud operational logs in the project’s default log bucket are retained for 30 days. Its separate required audit-log bucket has a fixed retention period of 400 days. These are separate from your account’s training records.
We archive feedback emails and technical account-deletion status records indefinitely, with no fixed automatic deletion date. To request deletion of archived information that identifies you, send a separate request to ringrustfeedback@gmail.com and specify the feedback or deletion record concerned. These archived records are separate from the Google Cloud operational and audit logs described above.
Other users’ training records are preserved. Links to the deleted account are removed where supported, but historical participant names can remain in their material. Local videos and review files on your phone, exports in your media library and copies held by other people are separate and are not recalled by account deletion.
See Delete your Impact Tracker account and data to request deletion without the app or to request removal of particular information.
Changes to this policy
This policy may be updated when the app or its data practices change. The update date will be shown at the top of this page.