1. Scope and operator
This service 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.
World Clock is an optional Chrome new-tab companion for authorized Link Batch Opener team accounts, operated by Muhammad Sabir. It replaces Chrome’s new-tab page with up to nine configurable clocks and connects to the separately installed Link Batch Opener extension to verify account access.
This policy covers the World Clock companion. The main Link Batch Opener extension and operations dashboard handle additional data under their separate notices. Installing World Clock does not itself grant a Link Batch Opener account or World Clock entitlement.
2. Information used by World Clock
| Data | Purpose and storage |
|---|---|
| Clock preferences | Selected time zones, user-defined clock labels, generated clock identifiers, 12/24-hour format, seconds display, theme, density, arrangement, text sizes, and toolbar visibility are stored using Chrome synchronized extension storage. |
| Pairing details | The paired Link Batch Opener extension identifier and Link Batch Opener Admin ID are saved in local extension storage to bind the companion to the connected account. A generated setup/pairing code can be stored locally before linking. |
| Access decisions | Short-lived allow/deny results, expiry values, and the associated account identifier are cached locally to reduce repeated access requests. |
| Feature interactions | Opening World Clock or its editor and supported clock/settings changes can send action names to the paired Link Batch Opener extension, which records permitted events in its backend usage system. |
Clock labels are free text. Do not include sensitive information in them. The browser’s configured time zone can be used to choose a default clock; World Clock does not request device GPS location.
3. Chrome storage and synchronization
Clock settings use Chrome’s synchronized extension storage. Depending on your Chrome sign-in and Sync configuration, Google can synchronize those preferences between browser profiles associated with your account. Actual synchronization availability, retention, and clearing controls depend on Chrome settings and Google’s service behavior.
Pairing and access-cache information use local extension storage rather than the clock-preference synchronization record. World Clock does not upload the complete clock configuration as part of its feature-interaction event. An initial migration can copy saved clock settings from the main Link Batch Opener extension into the companion if no companion configuration already exists.
4. Pairing and account verification
The companion exchanges messages with the installed Link Batch Opener extension. Pairing stores the sender extension’s identifier and the linked Link Batch Opener Admin ID. Store-based detection uses the permanent World Clock item ID configured in the main extension. Verified store proofs are bound to that ID; unpacked builds with a different ID cannot use the store connection flow.
The main extension checks account authentication and World Clock permission through the Link Batch Opener backend. The companion receives an access result and relevant account identifier. Link Batch Opener passwords and main-extension session tokens are not copied into World Clock.
The manifest allows external extension messages so pairing can work. Before accepting a peer, World Clock verifies a backend-signed proof tied to the sender extension ID and account. Proofs expire after one minute and are checked over HTTPS with the project backend; the backend checks current account access. A sender’s own claim of access is not sufficient. Proofs are temporary and do not contain your main-extension session token.
5. Interaction logging and who can see it
Permitted World Clock interactions can be forwarded through the paired main extension to the Link Batch Opener usage endpoint. The companion sends a feature action; the main extension adds the world_clock feature designation, companion source, installation identifier, and main-extension version.
The backend associates the event with the signed-in Admin ID and snapshots of the account’s name, team, and role, together with a timestamp and event metadata. Authorized administrators or staff with usage-report access can view individual and aggregated operational activity.
These records support feature usage reporting, troubleshooting, and operation of the service. They are account-associated, not anonymous. World Clock does not independently collect ordinary website history, page content, searches, or unrelated browsing URLs. This narrower statement does not describe the separate browser tools in the main Link Batch Opener extension.
6. Permissions and code execution
The companion requests Chrome’s storage permission to save preferences, pairing state, and temporary access decisions. The new-tab override registers the packaged World Clock page as Chrome’s new-tab destination. It does not request the broad tabs permission or access to general websites. Its host permission is limited to https://extlogin.space/*, used to verify signed pairing and access proofs directly with the project backend.
All executable companion JavaScript is included in its extension package. The companion does not download or execute remotely hosted application code. Extension messaging for account access and settings is not a transfer of executable code.
7. Recipients and service providers
Relevant information is handled by your Chrome profile and Google’s Chrome Sync service when synchronization is enabled, the paired Link Batch Opener extension, and the Link Batch Opener backend for access checks and operational event reporting. The current backend uses Vercel hosting and Supabase database services.
Authorized organization staff can access backend records according to their role. Provider processing and any international transfers follow the applicable service agreements and legal arrangements. Contact the organization for details relevant to your account; no specific hosting region is promised by this notice.
8. How long data remains
Clock settings remain until changed or removed through the editor, browser storage controls, or applicable Chrome Sync controls. Pairing details remain until reset, replaced, or cleared. Local access approval can be cached for up to five minutes; a denied check can be cached for approximately 30 seconds. Those intervals describe access decisions, not backend event retention.
Existing server-side usage, account, or security records can remain after you disconnect or uninstall. Backend retention is determined by the organization’s operational, security, and recordkeeping needs; this notice does not claim a fixed automatic deletion period. Ask support for the applicable schedule or deletion review. Backups may persist until their separate retention cycle ends.
9. Your settings, removal, and access revocation
- Edit or delete clocks and change presentation in the World Clock editor.
- Control synchronized preferences through your Chrome Sync settings.
- Use Disconnect / pair again on the setup/access screen when available to reset pairing. Pairing reset does not itself delete saved clocks or server usage history.
- Ask your administrator to review or revoke World Clock Companion Access.
- Disable or uninstall World Clock in
chrome://extensionsto stop its new-tab override.
Revocation or sign-out can take time to appear because of the short-lived access cache. A denied access check shows an unavailable/setup page. The new-tab override remains registered until you disable or remove the companion; revoking entitlement does not automatically restore Chrome’s previous new-tab page.
Uninstalling clears the extension’s active local installation data, but synchronized copies and backend records are governed by their own controls and retention. The separately installed main Link Batch Opener extension remains installed.
10. Purpose limitation and security
World Clock data is used to display and synchronize saved clocks, link access to an authorized Link Batch Opener account, and support the operational reporting described above. We do not sell World Clock personal information, use it for personalized advertising, or use it to determine creditworthiness or lending eligibility. Transfers must support disclosed functionality or another permitted purpose such as 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.
The companion separates local pairing state from synchronized clock preferences and delegates Link Batch Opener credential handling to the main extension. Relevant backend connections use HTTPS. Keep your browser profile and device secure; no system can guarantee absolute security.
11. Contact and privacy requests
Contact Muhammad Sabir at Sabirqureshi104@gmail.com. Identify World Clock and the account or issue involved. Do not send passwords, session tokens, or pairing codes in a privacy request. Support may need to verify your identity or authority before providing account-associated records.
Depending on applicable law, you may have rights to access, correction, deletion, restriction, objection, portability, or a complaint to a supervisory authority. Requests may be subject to security, employment, contractual, or legal recordkeeping requirements. Ask the organization for the lawful basis and retention details applicable to your account.
12. Policy updates and related services
Effective: 19 October 2026. Material changes should be reflected on this page and in the companion’s Chrome Web Store privacy disclosures. Additional organization-specific account notices may apply.
Link Batch Opener extension privacy · operations dashboard privacy.