How We Use Attribution Data

GameAccount.us uses first-party attribution so we can understand which educational channels (for example WhatsApp, SMS, or social entry links) lead visitors to open the chatbot.

• localStorage stores durable anonymous first- and last-touch fields
• sessionStorage stores the current tab’s session source
• There is no first-party attribution cookie
• Browser storage may be unavailable, blocked, or cleared by you

We may generate anonymous visitor_id and attribution_session_id values. These are not passwords and are not used alone as proof of identity.

Channel fields such as source, medium, campaign, landing page, and referrer may be linked to a chat session together with operational funnel events (for example chat started or handoff). Attribution records are not intended to contain names, emails, phones, payment data, passwords, or chat-message bodies. Information you type into chat is separate conversation content.

Google Analytics 4 and Meta Pixel are not currently enabled. Qualified-lead and conversion-completed catalog events remain disabled.

Browser durable attribution may persist up to 400 days (client-side intent). Server attribution and funnel records do not carry a public automatic-deletion promise until a tested purge mechanism exists. Records are retained only as reasonably necessary for support operations, security, reporting, dispute handling, and applicable legal requirements. Deletion requests are reviewed individually.

See the Privacy Policy and Cookie & Browser Storage Policy. Privacy questions: privacy@gameaccount.us.