1. Who we are & how to contact us
This policy applies to the SnapSet workout logging app and this privacy webpage. “We”, “us” and “our” refer to the operator of SnapSet.
For privacy questions, access requests or account deletion, contact:
marcjanik.arkadiusz@gmail.com
2. Information we handle
- Account information: email address, Firebase user identifier, optional display name and sign-in provider information. Firebase handles authentication credentials. SnapSet does not store a separate plaintext password in workout files.
- Workout information: exercise names and identifiers, remembered aliases, workout days, reps, weights, timestamps and saved performance history. Device backups and exports can include this information.
- Voice input: microphone audio processed by Android's recognition service, and the resulting text used to interpret a workout set.
- Preferences and access: weight units, sound and vibration preferences, daily free-exercise usage and, when available, subscription entitlement information.
- Technical and support information: authentication and request metadata, service usage counters, error diagnostics, and information you choose to include when emailing us. Hosting and service providers may process IP addresses, device/browser information and security logs.
We use this information to provide your account and workout features, interpret voice input, enforce usage limits, secure the service, manage access and respond to support requests. Where applicable law requires a legal basis, these purposes may rely on providing the service you request, legitimate interests in security and operation, consent for optional features where required, or legal obligations.
3. Firebase Authentication, Cloud Firestore & Hosting
Firebase Authentication, provided by Google, manages account registration, sign-in, profile updates and account deletion. Depending on the sign-in methods available in your app version, you may use email/password or a supported social account such as Google or Facebook. Those providers also process information under their own policies.
Cloud Firestore stores backend AI usage counters associated with a hashed Firebase user identifier and aggregate service counters. Hashing does not make the account-linked record anonymous. In the current implementation, your full workout tables and history are stored on your device, not synchronised to Firestore.
Firebase Cloud Functions authenticates AI requests, applies service limits, forwards eligible text requests to OpenAI and processes account deletion. Firebase Hosting serves this public webpage without requiring a SnapSet account.
Read more about privacy and security in Firebase.
4. Android voice recognition
Voice logging requires your permission to use the microphone. SnapSet uses Android's default SpeechRecognizer service to convert speech into text. The recognition provider depends on your device and its configuration.
Recognition may involve sending audio to the provider's servers. SnapSet does not currently require offline or on-device recognition, so voice logging should not be treated as an offline-only feature. The recognition provider's processing and retention rules apply.
SnapSet does not create or retain audio recording files in its workout storage or upload audio to its own Firebase backend or OpenAI integration. The app uses the recognised text to extract exercise information. You can use manual entry instead, or revoke microphone permission in your device settings.
5. OpenAI text processing
SnapSet first attempts to interpret and match exercise text locally. Clear matches and local candidate choices do not require an OpenAI request. When the enabled AI feature needs additional help, SnapSet sends recognised text over HTTPS to our Firebase backend, which forwards it to the OpenAI API.
The request can contain the recognised sentence, a limited catalogue of exercise identifiers, names and aliases, and the identifiers of exercises on the selected workout day. The recognised sentence itself may include the reps and weight you spoke. The request does not include audio recordings or your complete numeric workout history. We do not deliberately add your account email address or password to the AI input. Anything you say can be part of the recognised text, so avoid including unrelated personal information. Your Firebase sign-in token is used by our backend to authenticate the request; it is not forwarded as part of the OpenAI text input.
Our OpenAI integration uses store: false. This does not guarantee zero retention: OpenAI may retain prompts, responses and related metadata in abuse-monitoring logs under its applicable policy, ordinarily for up to 30 days, with stated exceptions. API data is not used to train OpenAI models by default unless the API customer opts in.
Read OpenAI's API data controls. Provider-level retention settings are separate from deleting your SnapSet account.
6. Subscriptions & payments
SnapSet includes Free and Premium access logic. At the date of this policy, real store subscription purchases are not connected; the development-only test purchase does not charge money.
When subscriptions become available through Google Play or Apple's App Store, the store will process the payment and billing information under its policies. SnapSet will need purchase identifiers or tokens and verified subscription status to provide and restore Premium access. SnapSet does not collect or store your full payment-card details.
Deleting a SnapSet account does not automatically cancel a store subscription. Manage or cancel subscriptions through the store where you purchased them. We will update this policy when live billing and its related processing are introduced.
8. Storage, backups & retention
Your current workout database, history and device backup are kept in SnapSet's account-specific app storage. Preferences are kept on the device. Local data remains until you remove it, delete your account on that device or clear app storage; device backup and operating-system behaviour may affect copies. Local backups are not cloud workout synchronisation.
Firebase account information is retained while your account exists, subject to Google's service retention and backup policies. Backend usage records are maintained for service operation and the account-linked usage record is removed by SnapSet's account deletion flow. Aggregate counters that do not identify an individual account can remain.
Release app code does not deliberately log full voice transcripts. Unity Editor and Development Builds can log recognised text for diagnostics; such builds should not be used for sensitive voice input. The backend logs error categories rather than transcript contents. Service providers may retain separate operational and security logs.
Support emails are kept as needed to respond, resolve the request and meet applicable obligations. Exported or shared copies are controlled by you and the recipient. Service-provider backups, legally required records and security logs may have separate retention periods; deletion is not a promise that every provider copy disappears immediately.
9. Delete your account & associated data
In the app, open Settings → Delete Account, read the confirmation, type DELETE and confirm. You may need to sign out and sign in again first to verify that the request is recent.
The deletion flow removes your Firebase Authentication account and profile, your account-linked backend AI usage record, and the account's workouts, history, aliases, usage ledger and backups stored by SnapSet on that device. It also clears temporary Android export files. If device cleanup cannot finish, the app tells you how to clear its storage.
Without the app: email marcjanik.arkadiusz@gmail.com from your registered address with the subject “SnapSet account deletion request”. We verify account ownership before processing the request. Do not send your password. You can also use our public account deletion information page.
Deletion is permanent. It cannot recall files you exported or shared outside SnapSet, erase app data on other offline devices, cancel store subscriptions, or override third-party security-log and legally required retention. Remove those copies or contact the relevant provider where appropriate.
10. Your choices & privacy rights
You can edit workout information, update your account name, request a verified email change, export your workouts, revoke microphone permission and request account deletion. Manual workout entry remains available without microphone permission.
Depending on your location and applicable law, you may have rights to access, correct, delete or obtain a copy of personal information, restrict or object to certain processing, and withdraw consent where processing relies on consent. Contact us to exercise a right. We may need to verify your identity. You may also have the right to complain to your local data protection authority.
If you believe a child has provided personal information to SnapSet inappropriately, please contact us so we can investigate and address it.
11. Security & international processing
SnapSet uses HTTPS for its backend requests and Firebase authentication for protected operations. Workouts are stored within the app's device storage, but exported files are ordinary files and should be protected by you. No transmission or storage method can be guaranteed completely secure.
Firebase, Android recognition providers, OpenAI and app stores may process information in countries other than your own under their applicable terms and safeguards. The location of a SnapSet backend function does not mean every provider processes all information in that same country.
12. This webpage & policy updates
This privacy webpage requires no account or login and includes no analytics scripts, advertising, tracking pixels or external font requests. It does not set cookies itself. Firebase Hosting and network providers may still handle technical request information to deliver and secure the page. Following an external link takes you to another provider's website.
We may update this policy as SnapSet changes. The date at the top identifies the latest revision. Material changes will be communicated through the app or another appropriate channel where required.
Questions? Contact SnapSet about privacy.