Privacy Policy
ANSER CODING INC.
Last Updated: May 25, 2026
ANSER CODING INC. ("we," "us," or "our") operates the NexLink mobile application. This Privacy Policy describes how NexLink ("the App") collects, uses, and handles your data when you use our mobile application designed for industrial message management.
1. Data Collection
We collect information to provide a better experience and essential functionality for industrial operations, and this information is limited to use on the user's own devices. The types of data we collect include:
- User Identity Information: Your Google email address is collected via OAuth 2.0 to identify your account for cloud backup services.
- Industrial Message Data: We process proprietary message templates, printing parameters, and configuration files (e.g., text, binary formats) created by you or your organization.
- Technical Log Data: Local connection status and hardware monitoring data derived from your industrial equipment within the local network.
- Device Information: Basic hardware information required for the Qt framework to ensure compatibility with your Android device.
2. Permissions Justification
We only request permissions that are essential for the App to function as a professional industrial tool. The App requests only non-sensitive Google API scopes — it does not request any Restricted or full-access Drive scope.
A. Google Drive API (Non-Sensitive Scopes Only)
- Scopes Requested:
https://www.googleapis.com/auth/drive.file — read/write access strictly limited to files and folders the App itself creates, or that you explicitly open with the App. (Non-sensitive)https://www.googleapis.com/auth/drive.appdata — access to the App's private application-data folder, hidden from your Drive UI. (Non-sensitive)https://www.googleapis.com/auth/userinfo.email — read your email address for account identification. (Non-sensitive)
- Purpose: The App synchronizes factory message templates and configuration data between the mobile device and a dedicated App-created folder named ANSER_NexLink in your Google Drive. Both the upload (export) and the listing / download (import from that folder) operations are performed entirely under the
drive.file scope.
- Scope Is Narrow:
drive.file is enforced by Google to limit the App's access to files and folders the App itself created, or that you explicitly picked. The App creates and accesses only its dedicated sync folder ANSER_NexLink (or an optional user-specified folder name); it cannot see, modify, or delete personal files elsewhere in your Drive.
- No Restricted Scope: An earlier version of the App requested the Restricted
drive.readonly scope to enumerate the whole Drive. This has been removed. The App now relies solely on the non-sensitive scopes above, so it does not require Restricted-scope verification (CASA) or annual recertification.
- Session Management: Once you sign out of Google Drive within the App, all session tokens are cleared and Google is asked to revoke the App's grant. Re-authorizing the App is required for any subsequent access.
- Email Usage: Your email address is accessed solely to identify your account for secure data synchronization. It is not used for marketing or shared with third parties.
B. Importing Files via the Android System File Picker (Storage Access Framework)
- How It Works: To import files that were not created by the App (for example, templates a factory administrator prepared elsewhere), the App uses Android's Storage Access Framework — the operating system's built-in file picker. You explicitly select each file, including files stored in Google Drive or other cloud providers exposed by the system picker.
- Per-File Access Only: The Android operating system grants the App access to only the specific files you choose, as a temporary content URI. This is handled entirely by Android and does not use any Google Drive API scope, which is why the App no longer needs the broad
drive.readonly permission.
- Local Copy: A selected file is copied into the App's local storage for use with the connected printer; the original remains untouched in its source location.
C. Local Network and WebView (HTTP)
- Usage: The App connects to industrial equipment via local TCP/IP and HTTP.
- WebView: We use an integrated WebView to display the hardware's internal monitoring dashboard.
- File Transfer: We use TCP/IP for secure file transfer directly to industrial printing and machine control units.
- Security: This communication is strictly confined to the user's Local Area Network (LAN) and does not transmit data over the unencrypted public internet.
3. Google Limited Use Disclosure
The App's use and transfer to any other app of information received from Google APIs will adhere to the Google API Service User Data Policy, including the Limited Use requirements.
- We DO NOT sell your data to third parties.
- We DO NOT use your Google user data for advertising or marketing.
- We DO NOT store your Google Drive files on our own external servers. All processing is local on your device.
4. Information Sharing
We respect your privacy and do not share your industrial or personal data with third parties, except in the following limited circumstances:
- Service Providers: Sharing with Google Drive API solely to perform the synchronization services you have requested.
- Legal Requirements: If required to do so by law or in response to valid requests by public authorities.
- Consent: With your explicit consent to share data with other authorized industrial platforms within your organization.
5. Data Retention, Sharing, and Security
- No Server-Side Storage: We do not host your industrial messages or Google Drive data on our servers. All processing is local on your device.
- Data Security: We implement industry-standard security measures, including HTTPS encryption for all cloud communications and isolated local storage for sensitive configuration files.
6. Children's Privacy
Our Service does not address anyone generally under the age of 18. We do not knowingly collect personal information from children. If we discover such data, we will delete it immediately.
7. User Rights
You have the right to access, correct, or request the deletion of your data.
- Cloud Data: You can terminate our access by logging out within the App or revoking permissions in your Google Account Security Settings.
- Local Data: You can delete all locally stored message data by clearing the App cache or uninstalling the App.
8. Changes to Policy
We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.
9. Contact Information
If you have any questions or concerns regarding this Privacy Policy or our data practices, please contact us at:
Last Updated: May 25, 2026
ANSER CODING INC. ("we," "us," or "our") operates the NexLink mobile application. This Privacy Policy describes how NexLink ("the App") collects, uses, and handles your data when you use our mobile application designed for industrial message management.
1. Data Collection
We collect information to provide a better experience and essential functionality for industrial operations, and this information is limited to use on the user's own devices. The types of data we collect include:
- User Identity Information: Your Google email address is collected via OAuth 2.0 to identify your account for cloud backup services.
- Industrial Message Data: We process proprietary message templates, printing parameters, and configuration files (e.g., text, binary formats) created by you or your organization.
- Technical Log Data: Local connection status and hardware monitoring data derived from your industrial equipment within the local network.
- Device Information: Basic hardware information required for the Qt framework to ensure compatibility with your Android device.
2. Permissions Justification
We only request permissions that are essential for the App to function as a professional industrial tool.
A. Google Drive API (Non-Sensitive Scopes Only)
- Scopes Requested: https://www.googleapis.com/auth/drive.file (read/write access limited to files and folders the App itself creates or that you explicitly open — non-sensitive), https://www.googleapis.com/auth/drive.appdata (App private data folder hidden from your Drive UI — non-sensitive), and https://www.googleapis.com/auth/userinfo.email (account identification — non-sensitive). The App does NOT request any Restricted or full-access Drive scope.
- Purpose: The App synchronizes factory message templates and configuration data between the mobile device and a dedicated App-created folder named ANSER_NexLink in your Google Drive. Both the upload (export) and the listing / download (import from that folder) operations are performed entirely under the drive.file scope.
- Scope Is Narrow: drive.file is enforced by Google to limit the App's access to files and folders the App itself created or that you explicitly picked. The App creates and accesses only its dedicated sync folder ANSER_NexLink (or an optional user-specified folder name); it cannot see, modify, or delete personal files elsewhere in your Drive.
- No Restricted Scope: An earlier version of the App requested the Restricted drive.readonly scope to enumerate the whole Drive. This has been removed. The App now relies solely on the non-sensitive scopes above, so it does not require Restricted-scope verification (CASA) or annual recertification.
- Session Management: Once the user logs out of Google Drive within the App, all session tokens are cleared and Google is asked to revoke the App's grant. Re-authorizing the App is required for any subsequent access.
- Email Usage: Your email address is accessed solely to identify your account for secure data synchronization.
B. Importing Files via the Android System File Picker (Storage Access Framework)
- How It Works: To import files that were NOT created by the App (for example, templates a factory administrator prepared elsewhere), the App uses Android's Storage Access Framework — the operating system's built-in file picker. You explicitly select each file, including files stored in Google Drive or other cloud providers exposed by the system picker.
- Per-File Access Only: The Android operating system grants the App access to only the specific files you choose, as a temporary content URI. This is handled entirely by Android and does NOT use any Google Drive API scope, which is why the App no longer needs the broad drive.readonly permission. A selected file is copied into the App's local storage for use with the connected printer; the original remains untouched.
C. Local Network and WebView (HTTP)
- Usage: The App connects to industrial equipment via local TCP/IP and HTTP.
- WebView: We use an integrated WebView to display the hardware's internal monitoring dashboard.
- File Transfer: We use TCP/IP for secure file transfer directly to industrial printing and machine control units.
- Security: This communication is strictly confined to the user’s Local Area Network (LAN) and does not transmit data over the unencrypted public internet.
3. Google Limited Use Disclosure
The App’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Service User Data Policy, including the Limited Use requirements.
- We DO NOT sell your data to third parties.
- We DO NOT use your Google user data for advertising or marketing.
- We DO NOT store your Google Drive files on our own external servers. All processing is local on your device.
4. Information Sharing
We respect your privacy and do not share your industrial or personal data with third parties, except in the following limited circumstances:
- Service Providers: Sharing with Google Drive API solely to perform the synchronization services you have requested.
- Legal Requirements: If required to do so by law or in response to valid requests by public authorities.
- Consent: With your explicit consent to share data with other authorized industrial platforms within your organization.
5. Data Retention, Sharing, and Security
- No Server-Side Storage: We do not host your industrial messages or Google Drive data on our servers. All processing is local on your device.
- Data Security: We implement industry-standard security measures, including HTTPS encryption for all cloud communications and isolated local storage for sensitive configuration files.
6. Children's Privacy
Our Service does not address anyone generally under the age of 18. We do not knowingly collect personal information from children. If we discover such data, we will delete it immediately.
7. User Rights
You have the right to access, correct, or request the deletion of your data.
- Cloud Data: You can terminate our access by logging out within the App or revoking permissions in your Google Account Security Settings.
- Local Data: You can delete all locally stored message data by clearing the App cache or uninstalling the App.
8. Changes to Policy
We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.
9. Contact Information
If you have any questions or concerns regarding this Privacy Policy or our data practices, please contact us at: