Practical Arabic.Back to the homepage
YOUR COURSE. YOUR CHOICE.

Privacy policy

How the app and this website handle information, and the choices available to you.

Effective 8 November 2026
Your learning progress stays on your device. Usage sharing is your choice.

The app has no course account or cloud progress sync. Optional Google Analytics for Firebase is off until you explicitly allow it in an eligible production mobile build. Stores and website hosting process information separately.

Who operates Practical Arabic

The app operator and privacy contact are:

Legal app operator
Marwan Farha

Hanna H. Farha is the author and rights owner of the course text and recordings. Course ownership is separate from responsibility for operating the app and handling privacy requests.

This policy covers the Practical Arabic mobile app and its website at practicalarabic.madebytwain.com. Apple, Google and other service providers have their own policies for the services they operate.

Learning information on your device

The app stores lesson progress, listening positions, Recall practice results, study mode, playback speed, translation visibility and audio-follow settings locally. It also stores your usage-sharing choice and information used to remember confirmed course access.

The app does not create a course account or upload your learning progress to a course cloud-sync service. Progress does not automatically transfer to another device. Uninstalling clears the app’s local progress; restoring a purchase restores access rather than that lost progress. Device backup or restoration features are governed separately by your platform settings.

The course text and recordings are bundled with the installed app for offline study. Playback does not record your voice or send your spoken practice to an app-operated service.

Purchases through Apple or Google

The full-course unlock is a one-time in-app purchase. The applicable store handles checkout and payment details. The app does not collect your payment-card details.

The app checks store-provided purchase and entitlement information to unlock the course, restore access and maintain an offline access cache. These checks can include product and transaction identifiers. A purchase or restoration needs a store connection; confirmed access can be used offline and refreshed when connectivity returns.

A limited set of purchase identifiers is stored on the device to avoid counting the same confirmed purchase repeatedly in custom analytics. Those identifiers are not sent as custom analytics parameters. Store reporting, receipts, refunds and any platform-managed purchase reporting remain subject to Apple’s or Google’s policies.

Optional Google Analytics for Firebase

Usage sharing helps us understand use of the course and improve the app. Collection is off by default and is enabled only after an explicit opt-in in an eligible production native build. You can decline, close the choice, or change it later in Privacy & usage. Course access, recordings, purchases and offline study do not depend on allowing analytics.

Information processed when sharing is enabled

  • App sessions, engagement and returning installations.
  • Lesson numbers and study modes: Listen, Explore and Recall.
  • Starts of a recording or phrase, lesson and Recall completions, and views of the full-course unlock screen.
  • Confirmed purchase activity, including the full-course product identifier.
  • Pseudonymous installation identifiers, app and device information, operating-system details, and approximate country or region as processed by the SDK.

The app’s custom events do not send names, email addresses, Recall answers, course recordings, voice recordings, payment-card details or store transaction IDs. The app does not assign an analytics user ID. This is not a claim that no information is collected: the Firebase SDK also processes identifiers and automatic app activity when collection is enabled.

Advertising identifiers and advertising personalization are disabled in this integration. No cross-company advertising tracking is implemented. The app uses Analytics; it does not add advertising or an advertising SDK.

Browser previews and TestFlight are excluded from normal production analytics by the app’s version and distribution-channel gates. Current Android beta version names are excluded as well. Deliberate development diagnostics are separate from normal production reporting.

Changing your usage-sharing choice

Open Privacy & usage in the app and choose Keep sharing off to disable sharing, or Allow usage sharing to enable it in an eligible build.

Eligible analytics events may be queued on the device while offline and uploaded when a connection returns. Disabling sharing stops collection and resets Firebase’s local analytics state. It does not erase information already received by Google, clear your lesson progress or remove your purchase access.

Uninstalling is not a request to delete data already processed by a provider. For help with a privacy request, use the contact below.

The website and support messages

The website is a static site hosted on Render and delivered through its content-delivery infrastructure. Loading it requires processing connection and request information, such as an IP address, requested URL and browser-supplied request details, to deliver the page and its assets. This is separate from optional analytics in the mobile app.

The website uses Google Tag Manager to load Google Analytics by default. Analytics measures page visits, traffic sources, engagement, scrolling and outbound links. It also records which App Store link was used and interactions with the website’s sample audio, walkthrough, recall demo and FAQs. Google processes analytics cookie identifiers, browser and device information, session information and approximate location. Advertising personalization is disabled. The website honors any analytics opt-out previously saved in your browser.

If you email support or the privacy contact, your message, sender address and any information you choose to include are used to respond and handle the request. Please do not send passwords, payment-card details or unrelated sensitive information.

Support contact: support@madebytwain.com.

Providers, stores and international processing

Google processes website usage information through Google Analytics and app usage information through Google Analytics for Firebase. Read Google’s Privacy Policy and how Google uses information from sites and apps that use its services for its practices and controls.

Store downloads, payments, refunds and platform diagnostic or usage reporting are separate from the app’s optional usage-sharing choice. They are governed by the applicable platform’s policies and your platform settings: Apple Privacy Policy and Google Privacy Policy. Render describes its processing in its Privacy Policy.

These providers may process information outside your country. Their policies describe their processing arrangements and protections. No claim is made here that every website request or analytics event is processed in a particular country.

Retention

Learning progress and settings remain in local app storage until they are cleared or the app is removed, subject to the device’s own backup and storage behavior. Purchase access can be checked again with the applicable store.

Analytics data already received by Google follows the Analytics retention and deletion controls that apply to the service. Turning sharing off does not itself delete that information.

Retention of analytics, correspondence and hosting records

Support correspondence is kept while responding to your request and for necessary support records or applicable legal obligations. You can request deletion through the privacy contact. Information already processed by Google Analytics or Render is also subject to the provider’s applicable retention and deletion controls; this policy does not promise a fixed provider retention period.

Contact the privacy contact for questions about information already processed or a deletion request. The app’s local controls and provider-held information have different deletion processes.

Children and families

The app does not ask learners to create an account or enter a date of birth. Usage sharing can be kept off. If you are a parent or guardian with a concern about information relating to a child, contact the privacy contact so the request can be considered.

Parents and guardians can also use the platform’s age-rating information and parental controls when choosing how the app is used.

Privacy questions and requests

You may contact the operator with questions or requests to access, correct or delete information handled in connection with the app or support. Applicable rights and the handling of a request depend on the information involved and the law that applies. Information held only on your device is not available to the operator through a course account or sync service.

Please describe your request and the relevant app or website interaction without sending passwords or payment-card details. Provider-held data may require the provider’s own controls or assistance; a request cannot be treated as a guarantee that every provider can identify or erase every record.

For help using the app, visit Support.

Changes to this policy

An approved update will identify its effective date and policy version on this page. The effective date and policy version identify the current policy. Material changes should be reflected here and, where relevant, in the app’s disclosures.