Is Scheduled Analytics safe?
Scheduled Analytics reads your LinkedIn 'li_at' session cookie and sends it to app.scheduled.so, where it is stored to act on your account.
When you open a LinkedIn tab or use the extension popup, the background service worker calls chrome.cookies.get to read your LinkedIn 'li_at' session cookie and POSTs its raw value as a 'token' to https://app.scheduled.so/api/providers/linkedin/upsert. The extension first resolves your account by sending its stored extension key to /api/extension/synchronize. Because the li_at cookie is the credential that authenticates your LinkedIn session, the server holds enough to act on your LinkedIn account on your behalf.
Who publishes itScheduledFor EURL - no other listings under this identity
ScheduledFor EURL - no other listings under this identity
What this publisher told the store about itself, and the other listings that told it the same thing.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
What it can do
Permissions this extension asks for, as declared in version 1.3.0. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Read and change your data on app.scheduled.so
https://app.scheduled.so/*
Read and change your data on www.linkedin.com
https://www.linkedin.com/*
Store data in your browser
storage
Read and change cookies, including the ones that keep you signed in
cookies
Act on the current tab, but only after you click the extension
activeTab
Where it sends data
Destinations our analysis observed Scheduled Analytics contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- app.scheduled.so
Scheduled Analytics sends data to app.scheduled.so. No other extension we have analyzed sends data here.