Logsheet Quick Entry Privacy Policy

Summary

Logsheet Quick Entry does not collect, sell, or transmit your data to the developer or to any third party. There is no analytics, no telemetry, and no server operated by the developer. Everything the extension stores stays in your own browser profile on your own computer. The only site it ever contacts is https://www.trajecsys.com, the logsheet service you already have an account with.

Data the extension handles

Consistent with the Chrome Web Store disclosures for this item, the extension handles two categories of data, both locally:

Authentication information — optional, off by default

You may choose to store your Trajecsys username and password so the extension can sign you back in when the site times out mid-shift. This is disabled by default. When enabled, the credentials are written to chrome.storage.local on your own machine and are sent only to Trajecsys's own sign-in endpoint — the same request your browser makes when you log in manually. They are never sent to the developer or anyone else. Unticking the option in Settings clears them.

If you leave this off, entries you create while signed out are queued locally and submitted once you sign in yourself, so nothing is lost.

Website content — your own logsheet data

To do its job the extension reads, from your own account:

• the lists of sites, major studies, skills, participation levels, supervisors and pathologies used to configure the entry panel
• your own submitted logsheet entries, read back for the weekly completeness audit

It writes only the logsheet entries you explicitly create.

Stored locally

In chrome.storage.local, readable only by this extension in your browser profile:

• your program configuration (chosen site and major study, and the lists above)
• a local history of entries you submitted, used for the on-screen daily and weekly counts and the participation-level mix
• entries queued while your session was expired, kept until they send
• preferences: expected studies per clinic day, clinic days, deadline, target participation mix, and any custom finding text you add
• your credentials, only if you opted in as described above

Data the extension does not touch

No health records or patient data are read. Logsheet entries describe procedure types and clinical findings you record about your own training, and patient keys are non-identifying sequence numbers you assign. The extension does not access financial information, personal communications, location, browsing history, or activity on any site other than trajecsys.com.

Permissions

• storage — keep the configuration, queue and history described above
• alarms — schedule the weekly completeness check
• notifications — show the result of that check
• sidePanel — provide the entry panel, which is the whole interface
• tabs, scripting — locate your open Trajecsys tab and run the extension's bundled script there, so requests carry your existing session. A request from the extension's own origin would be rejected by the site.
• host permission for https://www.trajecsys.com/* — the only site contacted

No remote code is used. All scripts ship inside the extension package.

Retention and deletion

All data is local. Uninstalling the extension deletes it. Settings also provides "Export history", "Clear queued drafts" and "Reset program setup" so you can review or remove it at any time.

Not affiliated

This extension is an independent tool and is not affiliated with, endorsed by, or sponsored by Trajecsys.

Contact

Questions about this policy: use the support contact listed on the extension's Chrome Web Store page.