Privacy Policy
Last updated: October 16, 2026
Scan News is provided by NextMining ("we", "us"). This policy explains how we handle information when you use the app and your choices about that information. Available features and sign-in methods can differ by platform and app version.
1. Account and saved learning information
When you create an account or sign in, we process account information such as your name, email address, account identifier, authentication information, and any profile information you provide. Where Google sign-in is available, we receive the information needed for that sign-in from Google. New Facebook sign-in is no longer offered in the current release; information already associated with an existing account remains subject to this policy.
We store vocabulary and expressions you choose to save, associated learning information, bookmarks and their URLs/titles, and account settings so you can access and manage your saved data. An explicit save is separate from enabling automatic reading-history storage.
2. Optional reading history
Reading-history storage is off by default. If you sign in and enable it after viewing the in-app notice, qualifying pages you visit in the app can be saved to your account. This supports the reading-in-progress list, synchronization across your signed-in devices, and restoration of a saved scroll position where supported. Scroll position and elapsed time do not establish that you read or understood an article.
- Account ID; normalized page URL; page title; source domain and, when matched, a registered site ID.
- Visit identifiers, first and recent visit times, visit count, last and maximum scroll ratios, and active reading time.
- Counts of word lookups, distinct words looked up, and successful vocabulary saves, plus a reading-completed state you explicitly choose.
- The reading-history feature sends cumulative counts, not individual clicked-word text or a stream of every click and scroll event. Words or expressions you explicitly save are handled separately as vocabulary data.
3. Reading-history retention and controls
We retain reading-history visits for up to 90 days from the visit and keep up to 100 page entries per account. Older entries can be removed sooner when the page limit is reached. Expired visits are excluded from available history and removed through scheduled cleanup. The home screen may display a shorter time window; that display limit does not change server retention.
You can turn off new reading-history storage, delete an individual page, or delete all reading history through the in-app reading-history controls. Turning storage off does not itself delete existing records. Marking a page as read hides it from the reading-in-progress list but does not delete its stored history. Deleting your account also removes reading-history settings, page records, and visit records.
4. Technical information and analytics
We process device and connection information needed to operate the service, such as device identifiers, device/operating-system information, language settings, IP addresses, and request metadata. Operational logs help us investigate errors and protect the service. Avoid including passwords or other sensitive information in URLs or support messages.
Release builds use Google Firebase Analytics to understand app usage and improve the service. Our analytics events include screen names and events such as vocabulary or bookmark saves. We do not include page URLs, page titles, selected text, clicked words, email addresses, account IDs, or authentication tokens in those custom event parameters. This does not mean that Firebase collects no data: its SDK can collect app-instance identifiers, device information, and automatic usage events. Turning off reading history does not turn off this separate analytics collection.
5. How information is used and who processes it
We use account and learning information to authenticate users, provide and synchronize saved learning features, respond to support requests, and operate and protect Scan News. Analytics is used to understand usage and improve the app. The current reading-history feature is not a personalized recommendation service; adding a new use of this information requires review and an updated notice or consent where required.
Hosting and storage providers process information needed to run our backend, and Google processes analytics information through Firebase. Service providers may process information on servers outside your country. Google describes its practices at https://policies.google.com/privacy and Firebase describes service privacy at https://firebase.google.com/support/privacy. Information may also be disclosed when legally required.
6. External websites, search, dictionaries, and legacy media
When you open a third-party site or use a search or dictionary service in the app, that provider receives the information needed to handle the request, such as the requested URL or search/lookup text and connection information. These providers have their own privacy policies and may use cookies or similar technologies. The reading-history switch controls our account history feature; it does not prevent the website or dictionary provider from processing your request.
The current release does not offer the previous video/audio browsing features. Older versions with YouTube features use YouTube API Services and are subject to YouTube Terms of Service (https://www.youtube.com/t/terms) and Google Privacy Policy (https://policies.google.com/privacy).
7. Account and data deletion
You can delete your account in the app under Settings > Delete account. A successful in-app deletion removes the account, saved vocabulary, bookmarks, reading history and settings, device associations, and associated folder/channel/video lists from the active application database. Profile-image cleanup is handled separately and may be retried after the account database deletion. Deleted learning data cannot be restored through the app.
Purchase transaction records are retained separately after account deletion and are not removed by the account-deletion operation. We therefore do not promise that account deletion erases all transaction records. Contact us for questions about these retained records or to make a data request. Backup and operational-log handling are separate from deletion of active account records.
You can also request account and associated data deletion without opening the app: email nextmining@gmail.com with the subject "Scan News account deletion", your registered email address or username, and a clear deletion request. Do not send your password or login token. We may ask for information needed to verify account ownership before deleting data. We will respond and process verified requests in accordance with applicable law; any retained-data exception will be explained.
8. Security and your choices
We use authenticated account APIs and encrypted HTTPS connections for our backend. No system can guarantee absolute security. You can manage saved data and reading-history settings in the app or contact us about access, correction, deletion, or other privacy rights available to you under applicable law.
9. Changes to this policy
We will post updates on this page and update the revision date. For material changes, we will provide additional notice and obtain consent where required. Posting an updated policy does not, by itself, enable reading-history storage or replace any required consent.
Contact: nextmining@gmail.com