Privacy at Puzziva
Puzziva stores the account details you provide, your game sessions and results, friendships, messages, activity interactions, and notification preferences to operate the service.
Guest play and cookies
A necessary HTTP-only cookie identifies guest game sessions. Signing in uses a necessary authentication cookie. A separate security cookie protects forms. This browser may store guest progress and your theme preference. Authentication tokens are never stored in browser local storage.
Website analytics
The production website uses Google Analytics to understand visits and page usage. It shares an Analytics property with Tetana; reports can be separated by website hostname. Google Analytics may use analytics cookies. We do not send account identifiers, email addresses, messages, or game answers as custom analytics data. Analytics is not loaded for visits starting on email-verification or password-reset links.
What other players can see
You control profile visibility, activity sharing, friend requests, and presence in account settings. Activities can be public, friends-only, or private. Public profiles may appear on leaderboards. Messages are available to conversation participants; authorized moderators can review content that is reported.
Retention and removal
Guest game sessions expire from storage after 30 days of inactivity. Notifications are removed after 90 days. Account emails are cleared after delivery and sent-email records are removed after seven days. Reviewed reports are retained for up to 90 days. Registered game history and messages are retained while your account exists, unless removed through account deletion or moderation.
Your controls
You can update your information, block players, hide your activities, change notifications, or delete your account from Account settings. Deletion removes your profile, friendships, game history, activities, and messages you sent. Shared rooms can remain for other participants without your membership or results.
Before public launch
This notice describes the current implementation. The service operator must provide its legal identity, privacy contact, applicable rights process, hosting details, and backup retention policy before accepting public registrations.