QuotaSprintQuotaSprint private beta privacy notice — DRAFT FOR REVIEW
Version: 2026-10-private-beta-v1 | 19 October 2026
Operator: Simon Howe. Privacy and support contact: support@quotasprint.co.uk, or the private support inbox in the app. Postal/service address and the allocation of controller/processor responsibilities for business workspaces must be confirmed before an external pilot.
This private pilot uses fictional test data. Do not enter buyer names, customer identifiers, confidential receipts or sensitive personal information. Core account email/name, workspace membership, competition entries, approved sale quantities/values, scoring and audit history support the app. A verified account and the operator's beta invitation are needed for pilot enrolment. Not joining optional telemetry does not prevent access to your privacy rights or support.
Application data stays on the native Loneranger service. Firebase is used only for separately opted-in generic Android push delivery and device registration; it is not the application database. BarcodeNest receives a barcode only when the optional unknown-product lookup is used. Optional beta analytics and diagnostics remain on Loneranger; no Firebase Analytics or Crashlytics SDK is added.
Analytics and diagnostics are separate choices, off by default. Analytics contains only fixed app-event names. Diagnostics contains session start/end or framework/uncaught-error markers. Both contain a random session identifier, app version, platform and server time linked to your account. No stack traces, exception messages, screen text, URLs, customer details, sale content or advertising/device identifiers are sent. Missing session endings are reported as unknown, not assumed crash free. You may withdraw either choice; its earlier optional events are then deleted.
Your own account-data pages can be saved as JSON. They cover profile, beta preferences, memberships, own sales/ledger, feedback, telemetry and deletion status. Other people's data, session tokens and password hashes are excluded. Ask Simon Howe for review of any additional personal data held in shared audit records or backups; self-service export is not a claim that every possible access request is completed automatically.
Account closure requires password confirmation. It immediately disables sign-in, revokes sessions, push and paired displays, clears direct name/email and optional beta data. Current participant aliases become "Former participant". Shared immutable transaction/audit/final-result records may remain restricted and pseudonymous pending a recorded review; pseudonymisation is not full erasure. Business ownership and active organised competitions must be resolved before self-service closure. You can still request assistance without agreeing to telemetry.
Optional events expire after 30 days; resolved/dismissed in-app feedback after 90 days. Open support and retained closure history are reviewed by Simon Howe, with closure review due within 30 days. A backup is protected and used only for recovery; any valid erasure must be reapplied before a restored service is used. Backup/mailbox retention schedules and any case-specific legal basis for retained business records must be approved before an external pilot; no blanket indefinite retention or automatic legal exemption is asserted.
Proposed bases for review: core service delivery and proportionate security/record integrity; separate consent for optional telemetry. Business employee contexts require an appropriate controller agreement and lawful-basis assessment. Rights may include access, correction, objection, restriction, erasure and qualifying portability. Contact Simon Howe to exercise rights or raise a privacy concern. You can complain to the ICO. These drafts require human review and are not a declaration of legal clearance.