Privacy
This page describes how Atview (this website, atview.net) collects and uses information when you browse, sign in, or publish through the service. If you use the AT Protocol, your personal data store (PDS) and public records remain governed by your host and the network; here we focus on what this app processes on its own infrastructure.
Usage and analytics
We use Vercel Web Analytics to understand aggregate traffic and performance (for example, page views and Core Web Vitals). It is designed to avoid using cookies for visitors who are not logged in. See Vercel's analytics privacy policy for details on what they process.
Accounts and sign-in
When you log in, we use the AT Protocol OAuth flow (via atproto) with your chosen identity provider. We do not receive your account password from that provider. Tokens and OAuth session data needed to keep you signed in are stored on the server , not in browser local storage. OAuth authorization state used during login expires after a few minutes; active sessions are kept for up to about thirty days, in line with the session cookie lifetime.
Cookies
If you sign in, we set a first-party cookie named atview_sid that holds an opaque session identifier. It is httpOnly (not readable by page scripts), SameSite=Lax, and it is only sent over HTTPS. It is used to associate your browser with the server-side session so we can restore your AT Protocol session. When you log out, we revoke the OAuth session where possible and remove this cookie.
Public content and the network
Posts and profile data you publish through AT Protocol are public by design on the network. Anyone can read them with compatible software. This site may fetch and display that public information; it does not change who can see it on atproto.
Changes and contact
We may update this page as the product changes. The date at the bottom reflects the last substantive update. For questions or requests related to this policy, you can open a discussion on the atview.net GitHub repository.
Last updated: April 6, 2026