Effective date: July 20, 2026
Last updated: July 20, 2026

NGRecipe respects your privacy and is committed to handling information responsibly and transparently.

This Privacy Policy explains how the Android application NGDialogue: Speak English, package name com.ngrecipe.ngdialogue, accesses, uses, processes, stores, and shares information.

1. Developer information

Application: NGDialogue: Speak English
Tagline: Your Live Speaking Companion
Developer: NGRecipe
Lead Developer and Product Architect: Md Chhafrul Alam Khan
Company website: NGRecipe.com
Developer website: MdChhafrulAlamKhan.com
Privacy and support contact: support@ngrecipe.com

For information handled directly by NGRecipe, NGRecipe is responsible for the practices described in this Privacy Policy. Third-party services used by the application process information according to their own terms and privacy policies.

2. Scope of this policy

This Privacy Policy applies to the NGDialogue Android application and its related speaking-practice, speech-recognition, text-to-speech, advertising, sharing, saved-content, recent-activity, recommendation, and settings features.

It does not govern independent websites, applications, speech providers, advertising providers, email providers, social networks, app stores, or other third-party services that users choose to open or use.

3. Information processed by the application

NGDialogue does not require users to create an account, register, log in, or provide a name, postal address, telephone number, or payment information.

Depending on the features used, the application may process the following information.

3.1 Microphone audio and speech recognition

When a user chooses to speak, enables hands-free conversation, or uses voice search, NGDialogue requests permission to access the device microphone.

Microphone audio is used to:

• recognise spoken English;
• display the learner’s spoken response as text;
• continue a selected conversation;
• support hands-free speaking practice;
• search for relevant speaking situations.

NGDialogue does not intentionally store voice recordings on NGRecipe servers, does not use voice recordings for advertising, and does not send voice recordings to AdMob.

Speech recognition is performed using the speech-recognition service configured on the user’s Android device. Depending on the device, operating system, selected service, language support, and service settings, microphone audio may be processed on the device or transmitted to the speech-recognition provider’s servers. Android states that implementations of its speech-recognition API may stream audio to remote servers.

Users can deny or revoke microphone permission and continue using typed responses, visible authored responses, suggested replies, and other non-voice features.

3.2 Recognised and typed text

Recognised speech may be converted into text and displayed during the conversation. Typed responses, selected suggested replies, search terms, and conversation text may also be processed locally to provide the requested feature.

NGRecipe does not intentionally upload startup voice-search transcripts or ordinary conversation transcripts to an NGRecipe server.

Session text may remain visible while the conversation is active or while the application retains that screen. Locally saved items or recent activity may remain on the device until removed, application storage is cleared, or the application is uninstalled.

3.3 Text-to-speech information

NGDialogue uses the text-to-speech engine configured on the device to speak authored dialogue, suggested responses, welcome messages, recovery prompts, and other learning content.

Text-to-speech processing may occur on the device or through the selected text-to-speech provider. The provider’s own privacy practices apply to any processing performed by that provider.

3.4 Approximate location

NGDialogue does not request precise GPS location for its speaking-practice functionality.

The Google Mobile Ads SDK may receive the device’s Internet Protocol address. Google states that the IP address may be used to estimate the device’s general or approximate location.

NGDialogue does not use AdMob information to determine the user’s precise physical location.

3.5 App interactions

Google advertising services may process interaction information such as:

• application launches;
• taps;
• ad impressions;
• ad interactions;
• video views;
• related product-interaction information.

Google states that its Mobile Ads SDK automatically collects and shares user-product interaction information for advertising, analytics, and fraud-prevention purposes.

3.6 Diagnostic information

Google advertising services may process diagnostic or performance-related information, including information concerning:

• application or SDK launch time;
• responsiveness or hang rate;
• SDK performance;
• energy usage;
• technical ad-delivery errors.

This information may be used for analytics, advertising operations, service reliability, security, and fraud prevention.

NGDialogue does not currently use a separate NGRecipe crash-reporting server.

3.7 Device and other identifiers

The Google Mobile Ads SDK may process identifiers such as:

• the Android advertising ID;
• App Set ID;
• device-related identifiers;
• where applicable, identifiers associated with accounts signed into the device.

These identifiers may be used for advertising, analytics, frequency control, measurement, security, and fraud prevention.

Users may be able to reset or delete the Android advertising ID through their device settings. Availability and wording depend on the Android version and device manufacturer.

3.8 Locally stored information

NGDialogue may store information locally on the user’s device, including:

• application settings;
• microphone and hands-free preferences;
• startup voice-search preferences;
• saved speaking situations;
• recent situations;
• learning or completion status;
• accessibility preferences;
• advertisement cooldown information;
• rewarded ad-free time;
• consent status and privacy-message status;
• recommendation history;
• dismissed recommendations;
• “Not interested” preferences;
• locally generated audit or safety state;
• other information needed to preserve the user experience.

This local information is not automatically uploaded to an NGRecipe server.

Users can generally remove locally stored data by using relevant in-app controls, clearing the application’s storage through Android settings, or uninstalling the application.

4. Information NGDialogue does not access

The current application does not intentionally access or collect:

• contacts;
• SMS messages;
• call logs;
• precise GPS location;
• calendar information;
• personal photos or videos;
• financial or payment information;
• health or fitness records;
• installed-app inventory;
• biometric information;
• government identification;
• passwords or account credentials.

NGDialogue does not automatically send invitations, emails, SMS messages, or social-media messages to a user’s contacts.

5. Advertising

NGDialogue is supported by Google AdMob advertising.

Depending on availability, eligibility, consent, region, application state, and configuration, advertisements may include:

• anchored adaptive banners;
• inline adaptive banners;
• medium rectangle banners;
• native advertisements;
• interstitial advertisements;
• rewarded advertisements;
• rewarded interstitial advertisements;
• app-open advertisements.

Advertising is designed not to interrupt active speaking, microphone capture, speech recognition, hands-free recovery, emergency communication practice, permission explanations, or other sensitive tasks.

Rewarded formats are voluntary. A reward is provided only when the advertising SDK confirms that the user earned it.

Advertising data

Google states that its Mobile Ads SDK automatically collects and shares:

• IP addresses;
• product interactions;
• diagnostic information;
• device or account identifiers;

for advertising, analytics, and fraud-prevention purposes. Google also states that this information is encrypted in transit using Transport Layer Security.

Advertisements may be personalised or non-personalised depending on:

• the user’s region;
• applicable law;
• consent choices;
• device settings;
• advertising-ID availability;
• age or eligibility signals where applicable;
• Google’s policies and technical requirements.

NGRecipe does not independently sell personal information for monetary payment.

6. Consent and privacy choices

NGDialogue uses Google’s User Messaging Platform where required to request and manage advertising-related privacy choices.

The application may:

• request updated consent information;
• show a privacy or consent message where required;
• determine whether advertising may be requested;
• provide a Privacy Options entry point where required;
• allow users to review or modify applicable consent choices.

Google documents that UMP is designed to manage privacy choices and that some privacy messages require an entry point through which users can modify their choices.

Consent choices do not necessarily prevent all limited, contextual, security-related, fraud-prevention, or legally permitted processing.

Users can also manage relevant permissions and privacy controls through Android settings and Google account or advertising settings.

7. Developer-app recommendations

NGDialogue may display clearly labelled recommendations for other applications from NGRecipe.

These recommendations are separate from AdMob advertisements.

The recommendation system may use local contextual information, such as the current application section and locally stored recommendation preferences, to determine relevant recommendations.

NGDialogue does not:

• scan the user’s installed applications;
• access contacts for recommendations;
• send promotional invitations automatically;
• send cross-application promotional notifications;
• automatically open Google Play;
• force users to install another application.

Opening a recommended application listing is voluntary. When a user opens Google Play or another external destination, that service’s privacy policy applies.

8. Sharing

Sharing is initiated only by the user.

When the user chooses Share, NGDialogue may generate or prepare:

• invitation text;
• the selected speaking-situation context;
• completion or achievement information;
• a branded image;
• application-identification information;
• relevant hashtags.

The content is passed to Android’s system share interface. NGDialogue does not choose the recipient and does not automatically send the content.

Once the user selects another application, service, or recipient, the chosen service’s privacy practices apply.

Users should review shared content before sending it and avoid including personal or sensitive information unnecessarily.

9. External links

NGDialogue may provide voluntary links to:

• Google Play;
• NGRecipe websites;
• the developer website;
• developer social profiles;
• support email;
• other published applications;
• privacy or support resources.

External websites and services operate independently. NGRecipe is not responsible for their content, security, availability, or privacy practices.

10. Permissions

Microphone permission

Microphone permission is requested only when needed for speech recognition, voice search, hands-free conversation, or another clearly described voice feature.

Before requesting microphone access, the application should explain why access is needed. Users can decline the permission and continue using non-voice features.

Internet access

Internet access may be used for:

• loading advertisements;
• displaying consent messages;
• network-based speech recognition where used by the configured service;
• network-based text-to-speech where used by the configured engine;
• opening external links;
• sending a user-initiated support email;
• other user-requested online functions.

Notifications

The current application does not use notification permission to advertise other NGRecipe applications.

Any future speaking-practice reminder feature must provide a clear user benefit, be optional, respect user settings, and be reflected in an updated Privacy Policy and Data Safety declaration before release.

11. Purposes of processing

Information may be processed for the following purposes:

• providing speaking, typing, listening, and search functionality;
• converting speech to text;
• generating spoken output;
• preserving application preferences;
• maintaining saved and recent content;
• displaying and measuring advertisements;
• preventing fraudulent or invalid advertising activity;
• protecting users, the application, and advertising systems;
• diagnosing technical problems;
• maintaining service reliability;
• complying with legal and regulatory obligations;
• responding to user-initiated support enquiries.

Microphone audio is not used by NGRecipe for advertising or marketing.

12. Legal bases where applicable

Depending on the user’s location and applicable law, processing may rely on one or more of the following:

• the user’s consent;
• the user’s affirmative permission;
• performance of a user-requested service;
• legitimate interests in operating, securing, maintaining, and supporting the application;
• fraud prevention and security;
• compliance with legal obligations.

Where consent is required, users may withdraw or modify that consent through the available privacy controls. Withdrawal does not affect processing that was lawful before withdrawal.

13. Data sharing

Information may be processed by or transferred to the following categories of recipients when necessary:

• Google Mobile Ads and AdMob;
• Google User Messaging Platform;
• the speech-recognition service selected or configured on the device;
• the text-to-speech engine selected or configured on the device;
• Google Play and Android system services;
• applications selected by the user through the Android share interface;
• email, browser, social, or external services opened by the user;
• service providers required to maintain security or comply with law.

NGRecipe does not share microphone audio with AdMob for advertising.

NGRecipe may disclose information when reasonably necessary to comply with law, legal process, valid governmental requests, enforce applicable terms, investigate fraud, or protect users and legal rights.

14. International processing

Third-party service providers may process information in countries other than the user’s country of residence.

Privacy, data-protection, and government-access laws may differ between countries. Third-party providers are responsible for the legal safeguards applicable to processing performed through their services.

15. Data retention

NGDialogue follows these general retention principles:

• microphone audio is not intentionally retained by NGRecipe;
• startup voice-search transcripts are not intentionally stored on NGRecipe servers;
• active-session information is retained only as needed to provide the current experience unless a local feature stores it;
• saved items, recent activity, settings, recommendation preferences, consent status, and other application data may remain locally until deleted, cleared, reset, or removed by uninstalling the application;
• support emails may be retained for as long as reasonably necessary to respond, maintain records, resolve disputes, prevent abuse, or comply with law;
• information processed by Google or another third-party provider is retained according to that provider’s policies and legal obligations.

Because NGDialogue does not provide user accounts and does not maintain an NGRecipe server-side speaking profile, there is normally no central NGDialogue account record to delete.

16. Deleting local information

Users can remove locally stored NGDialogue information by:

• removing saved items where an in-app control is available;
• clearing recent or recommendation history where an in-app control is available;
• resetting relevant settings;
• opening Android application settings and clearing NGDialogue storage;
• uninstalling NGDialogue.

Clearing storage or uninstalling may permanently remove locally stored preferences, saved content, recent activity, progress, consent-state references, and other local application data.

NGRecipe cannot directly delete information independently controlled by Google, a speech provider, a text-to-speech provider, a social network, an email provider, or another third-party service.

Privacy questions may be sent to support@ngrecipe.com.

17. Data security

NGRecipe uses reasonable technical and organisational measures appropriate to the application and the information involved.

Network transmissions used by integrated services are expected to use secure transport protections. Google states that data collected by its Mobile Ads SDK is encrypted in transit using TLS.

No electronic storage, device, network, or transmission method can be guaranteed to be completely secure. Users should protect their devices, use current operating-system security updates, and avoid sharing sensitive information unnecessarily.

18. User rights

Depending on the user’s country or region, privacy laws may provide rights to:

• receive information about data processing;
• access personal information;
• correct inaccurate information;
• request deletion where applicable;
• restrict or object to processing;
• withdraw consent;
• opt out of certain targeted advertising;
• lodge a complaint with an appropriate data-protection authority.

Because NGDialogue does not maintain user accounts or an NGRecipe server-side speaking profile, NGRecipe may hold little or no information that can be linked back to a particular application user.

Users may manage:

• microphone permission through Android settings;
• local information by clearing application storage;
• Android advertising-ID controls through device settings;
• applicable advertising consent through the application’s Privacy Options controls;
• third-party data through the relevant third party’s own account or privacy controls.

19. Adults-only target audience

NGDialogue is currently designed and published for users aged 18 years and over.

The application is not directed to children. NGRecipe does not knowingly seek personal information from children through NGDialogue.

If NGRecipe learns that personal information belonging to a child has been provided directly to NGRecipe, reasonable steps will be taken to address or remove information under NGRecipe’s control, subject to applicable law.

Parents or guardians with privacy concerns may contact support@ngrecipe.com.

20. Changes to this Privacy Policy

This Privacy Policy may be updated when:

• application functionality changes;
• advertising or consent systems change;
• speech services or other SDKs change;
• legal or regulatory requirements change;
• data practices change;
• a new platform version is released.

The “Last updated” date will be revised when this policy changes. Where appropriate, material changes may also be communicated within the application or through the official website.

Users should review this policy periodically.

21. Contact

For privacy questions concerning NGDialogue, contact:

NGRecipe
Lead Developer and Product Architect: Md Chhafrul Alam Khan
Email: support@ngrecipe.com
Company website: NGRecipe.com
Developer website: MdChhafrulAlamKhan.com