SMTracker by B. Belicario

Privacy Policy

Last updated: September 18, 2026

What this policy covers

This policy explains how the SMTracker browser extension and its companion time-tracker dashboard handle information when you choose to use them.

Information the extension handles

For SM, after you give permission in the extension's on-page disclosure, SMTracker reads only the visible hourly-work data needed for the tracker, such as the displayed date, time, worked-hour value, and related hourly metrics. It may read the response that renders that hourly table so the same rows can be captured when the table is inside the SM page preview.

The visible SM worker or agent name may be included with an hourly row. If you link that name in the dashboard, SMTracker uses it only to associate rows with the correct SMTracker account; the SM and SMTracker login emails do not need to match. New accounts may also be asked to enter contract dates, schedule, target, cap, and pay settings used for the dashboard calculations.

For CB, SMTracker reads only the task ID visible on the CB compliance queue and the page or queue status needed to know when timing should pause and resume. It stores the current and last observed task ID, task timestamps, active elapsed time, completed-task count, hourly totals and AHT values, pause state, and queue-tab heartbeat state in Chrome's local extension storage.

The extension stores SM normalized hourly rows, a sync timestamp, and local connection/setup status. SM rows are kept in separate local buckets by detected worker identity, and rows are not sent to a dashboard when the detected identity does not match its linked identity. It does not read passwords, cookies, authentication tokens, general browsing history, private messages, or unrelated page content. CB tracking does not read or store the queue's usernames, private messages, or image content.

How the information is used

SM hourly rows are made available to the SMTracker dashboard so it can calculate total work hours, coverage, weekend adherence, contract progress, and pay estimates. The dashboard may request the stored rows when you press Refresh data or when its optional auto-refresh feature is enabled.

CB timing data is used only to display the compact tracker, calculate the current task AHT and current-hour average AHT, maintain hourly task records, and apply the queue pause/resume rules. When the queue closes, timing pauses; when the same task ID returns, the paused time is excluded. When a different task ID returns, the new task starts without recording the paused task as completed.

Dashboard and cloud synchronization

If you use the companion dashboard's sign-in and cloud-sync features, the dashboard may also process the email or username you enter, tracker settings, manual hour entries, contract settings, weekly metrics, and the captured SM hourly rows. This lets your tracker profile be restored across devices. CB task IDs, CB timing records, and CB hourly AHT records remain local to the extension and are not included in the dashboard's cloud synchronization. The extension itself does not collect passwords or session credentials.

To protect against accidental hourly-data loss, the dashboard creates recovery points before destructive hourly-data changes such as clearing, replacing, or restoring rows. A recovery point contains the same dashboard data already described above and is kept under the signed-in account; restoring a point changes hourly rows only. Cloud recovery points are limited to the most recent 30 points, and the browser also keeps a limited local copy for offline recovery.

Sharing and limited use

Captured SM rows are made available to the companion SMTracker dashboard. If you enable cloud sync, the dashboard stores the tracker profile with its hosting and database providers so that the service can operate. CB task IDs and timing records are not sent to the dashboard by the extension. We do not sell this information, use it for advertising, or use it for credit, insurance, employment, or unrelated profiling decisions.

SMTracker's use of information received from SM and CB pages and other user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Data is used only to provide the disclosed time-tracking features and is not transferred for unrelated purposes.

Storage, retention, and deletion

The browser copy of SM rows, connection status, CB timing records, and local recovery points remains in Chrome extension or browser storage until you clear the relevant data or remove the extension. CB timing records can also be reset from the tracker. If you use cloud synchronization, the dashboard profile and its limited recovery points remain available for the service to restore your tracker until they are deleted or expire under the recovery retention limit. To request deletion of cloud-synchronized tracker data and recovery points, email br.belicario@gmail.com.

Security

The dashboard is served over HTTPS, and network requests used for cloud synchronization are sent over HTTPS. No online service can guarantee absolute security, so please use the extension only on devices and accounts you control.

Changes and contact

If the data practices change, this page will be updated before the change is used in the product. Questions about this policy can be sent to br.belicario@gmail.com.