SOCIALSCOPE
Opening your workspace…
Opening your workspace…
OBSERVE. ANALYZE. UNDERSTAND.
SocialScope helps you understand public online activity without pretending to unlock private information.
We believe useful analytics should be inspectable. You can see where a result came from, when it was retrieved, how it was calculated, and what it cannot tell you.
SocialScope requests public data through supported APIs. A username is not consent to access an inbox, a private account or a device.
Sample data is fictional and explicitly labeled. Unavailable providers never silently fall back to simulated results.
The import analyzer works on this device. No passwords, OTP codes, session cookies or recovery codes are collected.
SocialScope stores a stable sign-in identifier, display name, preferences, personal watchlists, report snapshots, alert rules and recent searches when history is enabled. Email may be supplied by your sign-in provider for display but is not written to the SocialScope users table. Public entity metrics, snapshots and health checks are shared within an installation. No third-party advertising or behavioral tracking is included.
When maintenance runs, searches older than 30 days and public snapshots older than 90 days are deleted. You can clear personal history, download your workspace data or delete your workspace from Settings. Identity-provider sessions and hosting access are managed by their providers. Operational logs contain error codes and route names, not credentials or import contents.
Manage your dataUse SocialScope only for data you are permitted to access and analyze, and comply with each provider’s terms. Public does not mean unrestricted reuse. You are responsible for having permission to process an uploaded export.
Trend scores are descriptive statistics of observed data, not predictions, investment advice or claims about individuals. Availability, API quotas and API fields can change. Uptime and performance benchmarks are not guaranteed. This first release has not undergone an independent security audit.
Self-hosters are responsible for their own credentials, privacy notices, data-retention practices, access policies and backups. The source code is provided under the MIT License without warranty.
No. Entering a username does not bypass privacy controls. Live private-account connections are unavailable in this release.
GitHub and Hacker News have public adapters. YouTube, Reddit and X require configured approved API access. The capability registry lists exact implemented features.
Required credentials or approval may be missing, the service may have failed, or the requested capability is not implemented. The interface explains which condition applies.
Yes: provider results come from real requests, metrics use deterministic calculations, and demonstration data is labeled at every view.
Yes. The source includes a Next.js/PostgreSQL deployment path and a Cloudflare Worker/D1 path. Follow the README and deployment guide.
Saved searches are scoped to your authenticated account. You can disable or delete them in Settings. Public provider responses may be cached for the installation.
Only records actually present in your own export can be counted. SocialScope does not recover missing content.
A public API search does not require access to the target’s account. Underlying providers may log requests; no zero-trace promise is made.