SessionSlice for Android
Privacy Policy
Effective date: September 17, 2026
Who we are
SessionSlice is developed and published by Igor Bobritskiy ("SessionSlice", "we", "us", or "our"). This policy explains how the SessionSlice Android application accesses, uses, stores, and shares information.
Privacy contact: igor.bobritskii.rs@gmail.com
Summary
- Your session audio, Session names, Slice names, Marks, and audio metadata are stored on your device or in a folder you select. SessionSlice does not upload this content to our servers.
- SessionSlice uses Firebase services for account-based trial and entitlement synchronization, product analytics, and crash diagnostics when Firebase is configured in the installed build.
- Google Play processes purchases for the lifetime unlock. We do not receive or store your payment-card details.
- SessionSlice does not contain third-party advertising and does not sell personal information.
Information the app accesses or processes
Microphone and session audio
SessionSlice requests microphone permission so it can monitor sound levels, record rehearsal audio, and detect playing ranges. While recording, Android may show a foreground-service notification and microphone indicator. Audio is written as a continuous WAV master. Session and Slice metadata is stored in a JSON sidecar. Derived WAV or M4A exports are created only when you request them.
We do not transmit audio recordings, filenames, Session names, Slice names, Marks, search text, or file paths to Firebase Analytics, Crashlytics, our servers, or advertising services.
Files and storage
Recordings and related files are stored in app-specific device storage, on a writable SD card when selected, or in a folder you choose through Android's system folder picker. Folder access is limited to locations you explicitly authorize. Temporary capture and export files may be created in the app cache and are removed after successful processing or during cleanup.
Google sign-in and Firebase Authentication
For paid/trial builds, SessionSlice may ask you to choose a Google account to establish and restore trial or lifetime-unlock access. Google Identity Services provides an identity token to Firebase Authentication. Firebase may process your Google account identifier and basic account information, such as your email address and display name, under Google's terms and privacy policy. SessionSlice uses the resulting Firebase user identifier to locate your entitlement record; it does not use your Google account to read Gmail, Drive, contacts, or unrelated account data.
Trial and entitlement information
SessionSlice stores trial start time, last-known app time, entitlement user identifier, last synchronization time, and lifetime-unlock status locally. In Firebase Firestore, the app stores a record keyed by the Firebase user identifier containing trial start and end timestamps, account-record creation and synchronization timestamps, and lifetime-unlock status and time. This information is used to provide the trial, reduce clock manipulation, and restore access across installations.
Product analytics
When Firebase is configured, Firebase Analytics receives product-usage events such as recording start and stop, recording duration, Slice and Mark counts, threshold mode and value, Session or timeline opening, editing actions, screen and control interactions, scroll-depth categories, export format, quality and duration, and trial, paywall, and purchase-funnel events. These events contain enum, count, duration, or numeric product metadata rather than user-entered content or audio.
Firebase Analytics may also process app-instance identifiers, device and operating-system information, approximate location derived from IP address, and other technical information collected by the Firebase SDK. We use this information to understand aggregate app usage and improve SessionSlice.
Crash and diagnostic information
When Firebase is configured, Firebase Crashlytics may receive crash reports, stack traces, app and operating-system versions, device information, and technical diagnostics. SessionSlice adds limited diagnostic context such as the current screen, whether recording or export was active, a broad Session-duration category, Slice and Mark counts, export format and quality, and failure area. Crash reports do not intentionally include audio, filenames, file paths, Session or Slice names, search text, or purchase tokens.
Purchases and payments
SessionSlice uses Google Play Billing for the one-time lifetime_unlock product. Google Play processes the transaction and payment information. The app receives product details, price, purchase status, and a purchase token needed to verify and acknowledge the purchase through Google Play. SessionSlice stores a local purchased-status flag and may synchronize lifetime-unlock status to the Firebase entitlement record. We do not receive or store your full card or bank details.
Device backup
Android backup or device-transfer features may back up eligible app preferences and local app data according to your device and Google account settings. Files saved in a user-selected folder or removable storage remain under your control and may be handled separately by your device, storage provider, or backup software.
How we use information
- Provide microphone recording, automatic Slice detection, playback, editing, and export.
- Save your settings and maintain trial or purchased access.
- Restore entitlements after reinstalling or changing devices.
- Measure feature reliability and aggregate product usage.
- Diagnose crashes, failed exports, storage errors, and billing problems.
- Prevent abuse of trial and purchase functionality and comply with legal obligations.
Sharing and service providers
We do not sell your personal information. Information is shared only as needed with service providers supporting app functionality:
- Google Play: app distribution, licensing, billing, purchase restoration, and Play-provided diagnostics.
- Google Identity and Firebase Authentication: optional account sign-in and identity verification.
- Firebase Firestore: trial and lifetime-unlock entitlement synchronization.
- Firebase Analytics: product-usage measurement.
- Firebase Crashlytics: crash and reliability diagnostics.
Google processes information under its own terms and privacy policies. Information may also be disclosed when required by law, to protect users or the service, or as part of a business transfer subject to appropriate safeguards.
Retention and deletion
Recordings and metadata remain on your device or selected storage until you delete them in SessionSlice, delete them through your file manager, clear app storage, or uninstall the app. Files placed in user-selected folders or removable storage may remain after uninstalling.
Local settings, trial state, and purchased-status cache remain until app data is cleared or the app is uninstalled, subject to Android backup and restore. Firebase entitlement records are retained while needed to provide trial and purchased access and maintain transaction-related records. Analytics and crash information is retained according to the configured Firebase retention controls and Google's applicable service policies.
You may request deletion of your Firebase Authentication account and associated entitlement record by contacting us at the privacy contact above. We may retain limited records when legally required or necessary to prevent fraud, resolve disputes, and enforce agreements.
Your choices
- You may deny microphone permission, but recording and sound-level monitoring will not work.
- You choose whether to sign in with Google when account-based entitlement setup is required.
- You can delete Sessions and exports from the app or the storage location you selected.
- You can clear local application data through Android settings.
- You can manage Google account, Play purchase, advertising, analytics, and backup settings through Google and Android controls where available.
Security
We use Android app-private storage where applicable, system-mediated folder access, HTTPS connections provided by Google and Firebase SDKs, and access controls for cloud entitlement data. No method of storage or transmission is completely secure, and we cannot guarantee absolute security.
Children's privacy
SessionSlice is a general-audience music utility and is not directed specifically to children. We do not knowingly use the app to collect personal information from children in violation of applicable law. A parent or guardian who believes a child has provided personal information may contact us to request deletion.
International processing
Google and Firebase may process information on servers located outside your country. Where required, service providers use contractual and legal safeguards for international transfers.
Changes to this policy
We may update this policy when SessionSlice features, service providers, or legal requirements change. The updated policy will be posted at this URL with a revised effective date.
Contact
Developer: Igor Bobritskiy
Email: igor.bobritskii.rs@gmail.com