UDOCAT privacy notice
What Udo remembers
This notice describes authentication and website analytics on the custom-domain application. The public GitHub Pages fallback has no authentication and does not expose account features.
Authentication is enabled on the custom-domain application.
Website analytics
Google Analytics loads on reviewed public pages by default to measure visits and basic engagement.
Google receives public page views, a single 90% scroll event per page, outbound destination domains, and access to approved comic image files. Query strings, fragments, referring URLs, link text, wallet addresses, account actions, searches and form contents are excluded. Advertising, Google Signals, custom user IDs, cross-site identity, demographics, video and form tracking are disabled. Google may derive basic session statistics from these events.
Google receives connection information, including your IP address and browser information, when its tag loads and events are sent. Analytics uses cookies limited to this host for up to 180 days; Google’s configured event retention is 14 months. Browser privacy tools can block Google Analytics; blocking future collection does not erase events already received by Google. See Google’s privacy policy.
Wallet identity
On the custom-domain application, a successfully verified canonical TON wallet address becomes the UDOCAT account identifier. A wallet is not proof of one human. Wallet addresses are public on-chain identifiers, but their association with activity on UDOCAT is treated as user-associated application data.
TON Proof verifies control of the selected address. Authentication does not authorize transfers, payments, claims, or token movement and gives UDOCAT no transaction authority.
What the authentication system stores
- The canonical wallet address associated with the UDOCAT account.
- Challenge and session timestamps, lifecycle state, and purpose.
- The system keeps opaque digests instead of raw challenge, pre-authentication, session, or CSRF values.
- A minimized abuse-control client digest retained for a bounded period.
- Bounded authentication audit categories needed to investigate security and session actions.
What is not kept as normal authentication history
- Wallet private keys, seed phrases, or transaction-signing authority.
- Raw session cookies, raw challenges, or raw CSRF values.
- TON Proof signatures or wallet state-init payloads after verification.
- Full request headers or a long-term raw IP-address history.
- Email/password identity, KYC identity, or browser fingerprinting.
Current retention baseline
- Challenges
- About 24 hours after expiry or consumption.
- Revoked or expired session tombstones
- About 30 days after they become eligible for removal.
- Authentication audit events
- About 90 days.
- Minimized abuse-control data
- About 24 hours.
- Live sessions
- 30 days idle and 90 days absolute maximum.
Controls and failure behavior
“Log out here” revokes the current UDOCAT session. “Log out everywhere” revokes every active UDOCAT session for the verified wallet. Disconnecting TON Connect is separate and does not log out a server session.
If the authentication database or a required dependency is unavailable, authentication fails closed. The public factual site and read-only wallet balance remain available independently.
Deletion requests and contact
Use the verified private privacy contact to request deletion of the current authentication account data.