Skip to main content
StatStoat
Sign inCreate account
HELP CENTER

Set up authorized activity tracking with clear boundaries.

Learn how the StatStoat account, local desktop runtime, presence history, comparisons, alerts, and exports work together—without sending contact timelines to the website.

ProductCurrent StatStoat web and desktop release

First-time setup

Create a web account

Continue with Google when available, or register with your email address, a unique passphrase, and an optional display name. The account protects browser access; it does not upload your desktop history.

Open the desktop application

Live monitoring requires StatStoat’s Electron runtime. Follow the desktop setup guide if you have authorized source access; a browser-only dashboard correctly reports that the privileged bridge is unavailable.

Sign in to WhatsApp Web locally

Use your own session and wait until WhatsApp Web has completed loading before starting the monitoring engine.

Select an authorized scope

Add or select only contacts you are allowed to monitor. Real empty states remain empty until your runtime observes activity.

Desktop setup

StatStoat does not currently advertise a public packaged desktop download. Authorized collaborators with a checked-out copy of the project can build and verify the Electron application locally:

cd "Desktop App/Source Code"
npm ci
npm run verify
npm run pack

The build requires Node.js 22 and a supported desktop operating system. Run the generated application only on a device and WhatsApp account you control, and keep the repository and build artifacts private if your access is restricted.

Web account and dashboard

Sign-in loops

Confirm cookies are allowed for statstoat.com, use the canonical HTTPS domain, and try signing out before signing in again.

Session unavailable

Use “Try again” once. If verification still fails, return to sign-in; an expired or revoked session cannot be restored locally.

Desktop unavailable in browser

This is expected. The public website and browser dashboard never receive the Electron preload bridge.

Only your real activity

StatStoat does not seed people, sessions, or logs. Add contacts through your own runtime before expecting history.

Live monitoring

If the monitoring engine does not become ready, work through these checks in order:

  1. Confirm you are using the desktop application rather than a regular browser tab.
  2. Confirm WhatsApp Web is signed in and the chat list has finished loading.
  3. Open Diagnostics and review the reported runtime, bridge, and WhatsApp state.
  4. Stop and restart the engine once after WhatsApp Web is ready.
  5. Check whether an upstream WhatsApp Web interface change has been reported through your authorized project channel.

Supported meaning: StatStoat reports the states its current adapter can observe. It does not infer typing, message content, or communication between contacts.

History, comparisons, and exports

History looks empty

Check the selected contact and time range, then confirm the desktop engine actually observed a state transition.

Comparison has no result

Both selected contacts need independently observed sessions inside the chosen range. Overlap is context, not proof of contact.

Export button is disabled

Choose a range containing history first. Exports reflect the current filter rather than inventing missing records.

Moving to another device

Account sign-in does not synchronize local timelines. Export what you need before clearing application data or changing machines.

Notifications and integrations

  • Desktop alerts: allow notifications in both StatStoat and your operating-system settings.
  • Sound or speech: confirm the device is not muted and that the selected output is available.
  • HTTPS webhooks: use a destination you control, test with non-sensitive data, and do not put credentials in the URL.
  • notify.run: treat it as an optional external service and review the destination before sending contact-related alerts.

Prepare a useful support report

Capture the StatStoat version, operating system, affected screen, exact action, expected result, actual result, and redacted diagnostic message. Explain whether the problem occurs in a normal browser or the desktop app.

No public support channel is currently advertised. Authorized repository collaborators can use the project’s private issue tracker. For a security flaw, follow the security reporting instructions and never publish sensitive details.

Redact before posting: passwords, cookies, tokens, phone numbers, contact names, timeline exports, QR codes, and screenshots of private chats.