1. Who this policy covers
This extension and the connected platform are an independent personal project owned and operated by Muhammad Sabir. They are not affiliated with, endorsed by, or operated by MakeOpinion GmbH or the makeopinion.com website. References to third-party services describe technical integrations only.
This notice describes the Link Batch Opener browser extension, currently identified in Chrome as Link Batch Opener, provided for authorized project accounts by Muhammad Sabir. It covers extension features such as opening batches of links, working with supported administrative pages, quality checks, extraction helpers, text expansion, account access, and attendance actions available through the extension.
The operations dashboard and the optional World Clock companion have separate notices. Installing the main extension does not itself register a Chrome new-tab override. Access to individual tools depends on your account permissions and organization configuration.
2. Information the extension handles
| Category | Examples and use |
|---|---|
| Account and session information | Link Batch Opener Admin ID, name, role, permissions, session token, expiry information, and authentication status used to sign in and authorize tools. Passwords entered during sign-in are submitted to the authentication service for verification. |
| Installation and technical information | A generated installation identifier, extension version, request timestamps, and browser/session technical details used to distinguish installations and troubleshoot access. Login requests can result in the backend recording the connecting IP address and user-agent details. |
| Work inputs and supported-page data | Links you provide, selected URLs, supported-page content, identifiers, domain matches, extraction results, and quality-check inputs needed for the specific tool you use. Workflows that save or submit results send the relevant data to Link Batch Opener services. |
| Preferences and configuration | Tool settings, saved inputs, appearance choices, cached permissions, domain/keyword rules, and text-expander shortcuts. Some settings are local; configuration and shared shortcuts are retrieved from Link Batch Opener services. |
| Operational activity | Feature names, actions, timestamps, counts, result/status metadata, installation ID, and extension version. Backend event records associate activity with Admin ID and snapshots of name, team, and role. |
Only provide information you are authorized to process in Link Batch Opener workflows. Text entered into tools or saved shortcuts may contain additional personal information depending on what you choose to include.
3. Browser access, text expansion, and clipboard use
Browser tools can read tab URLs and relevant page content to open links, scan supported work pages, extract identifiers, or perform quality checks. A scan or extraction may inspect multiple tabs within the selected workflow. Opening a supplied URL also sends a normal browser request to that destination, whose own privacy practices apply.
The text-expander content script runs on HTTP and HTTPS pages and watches supported editable fields for configured shortcut triggers. It supports ordinary text inputs, text areas, and editable content; its input-type allowlist excludes password inputs. It is not intended as a general keystroke recording service.
When a shortcut is expanded, its usage event can include the shortcut ID, trigger, title, source of the expansion, and the website hostname where it was used. This hostname is browsing-related information associated with use of that feature. This notice does not claim the main extension never handles browsing data.
Clipboard access supports copy/paste tools and shortcut templates that request clipboard content. A clipboard variable reads clipboard text when that template needs it; inserted text is then handled by the destination page. Avoid putting credentials or unnecessary sensitive information in shortcuts or clipboard-based templates.
4. Why Chrome permissions are requested
| Permission | Purpose |
|---|---|
| tabs | Locate and operate tabs used by link-opening, scanning, extraction, and copy-tab tools. |
| storage | Save session state, preferences, cached configuration, working inputs, and companion pairing details. |
| alarms | Schedule batches and periodic configuration or access checks. |
| activeTab and scripting | Run supported helpers in the relevant browser tab and respond to requested page operations. |
| clipboardRead and clipboardWrite | Read or write text for clipboard tools and supported text-expander templates. |
| Site access and content scripts | Integrate with configured configured third-party CPX, MakeOpinion, and Prime work sites and the operations dashboard. Text-expander content scripts are declared on HTTP/HTTPS pages. |
| External extension messaging | Exchange World Clock pairing, account-access decisions, and companion feature events. |
Permission availability does not by itself mean every tool is enabled for every account. Account controls and the individual workflow determine what features are available.
5. Why information is used
- Authenticate your Link Batch Opener account and enforce tool permissions.
- Carry out requested browser operations and Link Batch Opener administrative workflows.
- Synchronize operational configuration and shared shortcut libraries.
- Record attendance actions where enabled.
- Measure feature adoption, diagnose failures, support users, and provide internal operational reporting.
- Pair the optional World Clock companion and verify its entitlement.
Operational usage records are associated with work accounts and are not represented as anonymous. Their visibility depends on reporting permissions.
6. Storage, recipients, and service providers
The extension uses Chrome local, session, and, where a feature uses it, synchronized extension storage. Local data belongs to the browser profile; session storage is temporary; synchronized data is handled according to your Chrome settings. Browser storage is not a substitute for keeping your device and profile secure.
Requests are sent to the Link Batch Opener backend at extlogin.space and to the configured work-service endpoints needed by the feature. The current backend uses Vercel hosting and Supabase database services. Authorized administrators and operational staff can access records made available to their roles. Providers process relevant information to deliver their services; their infrastructure and transfer arrangements are governed by the applicable service agreements.
The optional World Clock companion receives pairing/account identifiers and access decisions, not your Link Batch Opener password or main-extension session token. Opening the dashboard introduces the additional processing described in its own notice, including its AI feature if you use it.
7. Retention and deletion
Local preferences and working data can remain until changed, cleared, or removed with the extension/browser profile. Session tokens are subject to server expiry and revocation. Signing out does not necessarily remove every saved preference, shortcut cache, or prior operational record.
Server-side account, attendance, configuration, usage, and security records can remain after sign-out or uninstall. Retention depends on the record type, operational need, applicable obligations, and the organization’s retention arrangements. This notice does not promise automatic deletion after a fixed number of days. Request the applicable period or deletion review using the contact below. Backups may persist separately until their retention cycle ends.
8. Your controls
- Review or change extension/site permissions in Chrome’s extension settings.
- Use available settings to disable optional tools such as text expansion.
- Edit or remove saved shortcuts and tool inputs where your permissions allow.
- Sign out to stop authenticated account workflows; ask an administrator to revoke account access if needed.
- Disable or uninstall the extension to stop it running in that browser profile.
- Contact support about access, correction, export, or deletion of account-associated records.
Restricting required site access or disabling the extension can prevent related tools from functioning. Uninstalling does not erase data already submitted to Link Batch Opener or destination websites.
9. Data-use commitments
Extension data is used for the functions and related operational purposes described here. We do not sell extension personal data, use it for personalized advertising, or use it to determine creditworthiness or lending eligibility. Transfers must support the disclosed service or another permitted purpose, such as meeting a legal obligation.
Use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including its Limited Use requirements. This statement does not mean the extension requests access to Gmail, Google Drive, or other unrelated Google account content.
10. Security and access
The extension communicates with configured HTTPS services and uses authenticated requests for protected backend functions. Server permissions restrict account features and reporting. Keep your Link Batch Opener credentials private, lock shared devices, and sign out when you finish on a shared profile. No storage or transmission system can guarantee absolute security.
11. Questions, requests, and applicable rights
Contact Muhammad Sabir at Sabirqureshi104@gmail.com with the product name and enough information to locate the relevant account. Do not email passwords or session tokens. Identity and authority may need to be verified before records are disclosed or changed.
Depending on applicable law and your circumstances, you may have rights relating to access, correction, deletion, restriction, objection, portability, or a complaint to the relevant supervisory authority. Some requests may be limited by employment, contractual, security, recordkeeping, or legal obligations. Ask the organization for the lawful basis and retention arrangements applicable to your particular work records.
12. Updates and related notices
This notice is effective from 19 October 2026. Material changes to data handling should be reflected here and in the applicable Chrome Web Store disclosures. The policy should be read together with organization-specific notices for your account.
Related notices: operations dashboard privacy · World Clock privacy.