Privacy policy

How the quicknades app handles your data

This policy covers the quicknades mobile app, including account-linked features, feedback, analytics, crash reporting, purchases, and data deletion.

Last updated:

Overview

What this policy covers

quicknades is a Counter-Strike 2 companion app. Most features work without an account, but account-linked features such as preferences, favorites, tracked feedback, and purchases require sign-in.

Collection

What quicknades collects

Account and authentication data

If you sign in, quicknades relies on Firebase Authentication and stores the app user identifier, sign-in provider metadata, and related account-linked data needed for login, account recovery, favorites, preferences, feedback history, and account deletion.

Preferences and app activity

If you use account-linked features, quicknades stores favorites, lineup settings, ratings, and related preferences. The app also records aggregated map and lineup interaction metrics to understand feature usage.

Product analytics (Wiredash product-usage events, aggregated map and lineup interaction metrics) are separate from account features and are not used for advertising tracking.

Feedback and optional diagnostics

If you submit feedback, quicknades stores the text, replies, and any diagnostics you attach (app version, device details, submission context). Enabling feedback tracking links feedback to your account so you can review it later.

Diagnostics can include a device identifier. When sent with account-linked feedback, it is associated with that thread. When diagnostics are disabled, the device identifier is removed.

Tip purchase data

If you make an in-app tip purchase, quicknades stores the identifiers and verification data needed while the purchase is in progress. Once finalized, the account-linked purchase data is removed immediately. Apple App Store and Google Play handle the payment itself.

Device and local storage data

quicknades stores data locally so the app can work offline or recover gracefully. This includes queued offline changes, protected sensitive queue data, local caches, and temporary feedback drafts.

Use

How quicknades uses data

  • To sign you in and keep account-linked features working.
  • To save your favorites, preferences, filters, ratings, and other app state tied to your account.
  • To receive feedback, attach optional diagnostics you choose to send, and continue feedback conversations when tracking is enabled.
  • To verify, reconcile, and finalize in-app tip purchases.
  • To diagnose crashes and support requests.

Analytics

Analytics and crash reporting

  • quicknades uses Wiredash for product analytics and aggregated map and lineup interaction metrics.
  • Crash reporting is enabled on Android and iOS to help diagnose failures. Reports can include stack traces and device or session context. quicknades does not intentionally set a Crashlytics user ID.

App Store privacy

How this maps to App Store privacy labels

quicknades treats the actual app implementation as the source of truth for Apple App Store privacy labels:

  • Account user IDs, account-linked feedback, and in-progress tip purchase verification data can be linked to your account and are used for app functionality.
  • Product interaction and usage analytics are used to understand app usage, not for tracking.
  • Crash data is used to diagnose and fix failures, not for advertising or tracking.
  • Device identifiers may be used by analytics or diagnostics systems, and optional feedback diagnostics can be linked to a feedback thread when you submit account-linked feedback.

Services

Third-party services

quicknades relies on a small number of external services to operate core parts of the app:

  • Firebase Authentication: identity provider used for account sign-in.
  • Wiredash: analytics and feedback provider used for product analytics and in-app feedback tooling.
  • Firebase Crashlytics: crash reporting provider used to diagnose app failures on Android and iOS.
  • Apple App Store and Google Play: payment platforms used for in-app tips and purchase verification.

Retention

Retention

quicknades keeps account-linked data for as long as it is needed to provide the feature. Different categories have different retention periods depending on what the app needs them for.

  • Saved settings, favorites, ratings, and related account data remain until you change or delete them.
  • Feedback may remain in de-identified form after account deletion. Account links and device identifiers attached to that feedback are removed.
  • Wiredash analytics data is currently retained for 7 days.
  • Crash reports are retained for 90 days.
  • Tip purchase data is kept only while a purchase is still in progress and is removed immediately once that purchase reaches its final state.
  • Local caches, queued changes, and sign-in state on the device are cleared as part of sign-out and account-deletion cleanup.

Deletion

Deleting account-linked data

quicknades currently supports full account deletion only. Use the self-service deletion page for full details on what gets deleted, retained, or de-identified.

Choices

Your choices

  • You can use many quicknades features without signing in.
  • You can choose whether to attach optional diagnostics when you submit feedback.
  • If you are signed in, you can enable or disable account-linked feedback tracking preferences.

Children

Age guidance

quicknades itself is a companion app and does not contain the game. The app can be used more broadly, but it is built around Counter-Strike 2, which may be age-rated differently depending on the country.

Updates

Changes and contact

quicknades may update this policy when the product or its data handling changes. The public page will show a new effective date.

Operator: Till Schickle. Privacy and support contact: [email protected].

You can use this address for privacy questions or if you need help with account deletion.