Privacy Policy — 2plot.ai

Effective July 3, 2026. Last updated August 19, 2026. What the 2plot network's account hub collects, why, and who it is shared with. What you do inside a network app is covered by that app's own policy.

Who this covers

This policy covers two things: the 2plot.ai application (this website), and the shared 2plot network account that 2plot.ai provides — one sign-in used across the network's apps: 2plot.xyz, 2plot.media, 2plot.dev and its per-package documentation sites, cast.2plot.net, pip-install-python.com, ai-agent.buzz, and piratesbargain.com. What you do INSIDE a network app is covered by that app's own privacy policy; this page covers your account and your visits to 2plot.ai.

What we collect on 2plot.ai

• Visit analytics: when you load a page our server records the page path, a timestamp, your IP address, your browser's user-agent string, the referring page (if your browser sends one), the URL's query string (including which network app sent you here to sign in), and — for public IPs — a coarse city/country location derived from the IP. We use this to understand traffic across the network and improve it.
• Visit history: the analytics above are grouped per visitor (IP address + browser) into a profile — pages visited, first and last seen, and whether the visitor was signed in — used for traffic insight and abuse prevention. Profiles are derived from the visit log; we don't enrich them from any outside source.
• Account data (optional): if you sign in via Clerk (Google, Discord, GitHub or similar), we receive your display name, email address, and avatar URL from the provider. We use them to recognize your account across the 2plot network.
• Your account stays here: creating an account no longer sends your details to any other app in the network. 2plot.ai is the network's account hub, and account data is held here. If you go on to use a network app, what happens there is covered by that app's own policy.

What the network's apps report back to the hub

• Health checks: 2plot.ai probes each app's uptime and response time. Nothing about you.
• Traffic rollups: apps report periodic totals — visit and crawler counts, visitor and session counts, the most-requested pages, and a coarse country breakdown. These are counts about the app, not records about individuals.
• Sign-in attribution: when you sign in on one of the network's apps, that app tells the hub which app it happened on, along with a ONE-WAY HASH of your email address rather than the address itself. The hub uses it only to count distinct signers per app; it cannot be reversed to your email, and we do not attempt to.
• Live presence: apps report how many people are on them right now, and may include a short list of those people so the network board can show where everyone is. An app never sends your email address for this. It sends the same ONE-WAY HASH of it used for sign-in attribution, plus a coarse city/country and the page being read; because 2plot.ai issues the accounts, it can match that hash to your name on its own side. A hash it doesn't recognise stays anonymous. All of it is held only in memory, capped per report, and expires within minutes if the app stops reporting — it is a picture of right now, and nothing keeps it.
• Crawler and machine-surface analytics: we count how often automated clients fetch our machine-readable documents (llms.txt, robots.txt, sitemaps) and how many distinct crawlers we see. This is about software, not people.

What we don't do

• We don't sell your data, run third-party advertising, or use tracking pixels.
• We don't store card numbers or other payment credentials. 2plot.ai is free to use; where the network sells anything, payment is handled by the app making the sale and its payment processor, never by this hub.
• We don't use your data to train AI models, and the hub makes no AI calls of its own.

Cookies

Signing in sets authentication/session cookies (managed by Clerk and a signed session cookie of ours) so you stay logged in across the network. Without an account, the site works without identifying cookies.

Third-party services

• Clerk (authentication) — processes your sign-in with the OAuth provider you choose, for 2plot.ai and every network app that uses the shared account.
• Network apps — receive nothing about you at signup. If you visit one and use it, that app is its own data controller under its own privacy policy.
• Render (hosting) — our servers and database run on Render's infrastructure in the United States.

Security

Visitors that probe the Service (for example, requesting known exploit paths) may have their IP address blocked from the Service; we retain the blocked IP, the probed path, and the user-agent for as long as the block stands.

Retention and deletion

• Detailed visit records — including IP addresses — live on the server's temporary storage, which has no permanent disk attached. They are erased every time we deploy an update, which in practice is often. We keep no long-term archive of them.
• The operational log behind the network's monitoring is trimmed on a daily schedule, keeping roughly the last two weeks.
• What persists longer is aggregate: the periodic totals described above, which are counts rather than records about individuals.
• Account data persists until you delete your account or ask us to remove it. Email us and we'll delete the data we hold about you.

Children

The Service is not directed at children under 13 and we don't knowingly collect their personal information.

Changes

We may update this policy; material changes will be reflected by the dates above.

Contact

Privacy questions or deletion requests: [email protected]

Related

• Terms of Service: https://2plot.ai/terms
• Refund & Return Policy: https://2plot.ai/refunds
• How the shared account works: https://2plot.ai/docs/network-auth