StackAttack

iPhone · Privacy & support · Updated 23 October 2026

English Dictation Offline

This page covers the native iOS app com.stackattack.audiodictation, provided by Othmane BLIAL under the StackAttack product brand. It is separate from the Android version and its billing services.

Support

For help with lessons, playback, saved practice, or purchase restoration, email othmanovich.apps@gmail.com and mention “English Dictation Offline — iOS”. Do not send your Apple password, payment-card details, or private answers.

The app requires iOS 17 or later. Included lessons and sentence recordings work locally. Purchases and restoration need an internet connection and the Apple Account used for the purchase.

1. Practice information on your device

The app stores your local profile name, settings, saved lessons, unfinished answers, completed attempts, timing, accuracy, and daily practice allowance in its app sandbox. These records are used to resume exercises and show your history and progress. There is no app account, developer-operated login server, or advertising SDK. Your practice answers and local profile name are not passed to the purchase service.

The 934 included lessons and 5,001 sentence recordings are bundled with the app. Playback uses Apple audio frameworks. A system English speech voice can be used for individual words or as a fallback; downloading an additional system voice is managed by iOS.

2. Optional purchases through Apple

Three completed practices per local day are included. An optional non-consumable Lifetime purchase unlocks unlimited practice. Apple processes payment, purchase history, and restoration. The app uses Apple StoreKit and RevenueCat to load the localized offer, validate transactions, restore purchases, and determine Lifetime access, including purchase status and revocations.

RevenueCat receives an automatically generated anonymous app user identifier, purchase/receipt information, entitlement status, and technical store/app information needed to provide billing and purchase-history analytics. We do not supply your local name, email address, practice answers, or local usage counters as RevenueCat customer attributes. We do not use advertising identifiers or advertising tracking. We do not receive your full payment-card details or Apple password. See RevenueCat’s privacy policy and Apple’s privacy policy. Google Play Billing is not used on iOS.

3. Local counters, permissions, and sharing

Optional local usage counters record action totals such as visits and completed practice. They do not contain your profile name or answers and are not sent automatically. In Profile → Usage data you can turn them off, export them, or clear them.

The app does not request camera, microphone, contacts, photo-library, or location permission for its core practice flow. If you choose Share, iOS passes the result card, result text, or exported counters to the destination you select. Copies you share are then governed by that destination.

4. Retention, deletion, and iOS backups

Completed attempts remain until you reset progress or remove app data. Resetting progress keeps your saved lessons, profile, unfinished practice, purchases, and daily allowance. Clearing usage counters only affects those counters. Deleting the app removes its local sandbox; offloading the app may retain its documents and data.

Depending on your device settings, iOS or your computer may include app data in a system backup. The app does not provide its own cloud synchronization. Manage backups in Apple’s settings and remove separately any copies you exported or shared.

Deleting local history does not delete Apple’s or RevenueCat’s purchase records. Contact us about purchase information under our control; legal, fraud-prevention, and store retention requirements may apply. Lifetime access may be restored with the Apple Account used to purchase it, subject to Apple’s store services and purchase status.

5. Privacy questions and changes

Contact othmanovich.apps@gmail.com for privacy questions about information under our control. This policy describes the current native iOS implementation. We will update it if accounts, remote analytics, cloud features, or other data handling are added.