Visitor reporting and privacy
Support, seller compliance, and safety records
Coded in GT LLC stores support requests and replies, reporter contact details and evidence, moderation and appeal decisions, protected-file access audit records, seller business details, and versioned policy acceptance records to operate support, prevent abuse, enforce policies, and meet legal obligations. These records are separate from visitor analytics, are not publicly displayed, and are available only to authorized participants and staff. Relevant allegations may be shared with an affected seller for review. Records are kept while needed for the request, enforcement, dispute, or legal administration; legal holds can require longer retention. Do not send passwords, card data, or unnecessary sensitive information. Contact support@usagita.com for questions or privacy requests. Private case links grant access to the case and should not be shared.
Usagita keeps internal visitor reports to understand traffic, referral websites and popular public pages. This reporting does not load Google Analytics or other third-party tracking scripts and does not show a consent prompt.
What we record
We record approved page paths without query strings or fragments, referral website hostnames without paths, broad device categories, and visit times. Cart and checkout activity uses fixed page labels without order identifiers. Authentication callbacks, account details, messages, downloads, seller-management and admin pages are excluded. No search text, form inputs, passwords, payment details, raw IP addresses or full browser user-agent strings enter these visitor reports.
Visitors and visits
This reporting does not set cookies, use local or session storage, or fingerprint browsers. An anonymous visit uses a temporary random identifier held only in the loaded page’s memory. It cannot recognize an anonymous person returning later. If you are already signed in, we use your existing sign-in session to derive a separate pseudonymous reporting key. This allows new and returning signed-in visitor counts without storing your name, email address or account ID in the visitor report.
Retention and browser preferences
Visitor events are kept for up to 90 days. Pseudonymous signed-in visitor history expires after 365 days of inactivity. Cleanup runs in bounded batches as new events arrive, so physical deletion can lag; expired events are excluded from reports. Reporting respects Do Not Track and Global Privacy Control browser signals. Bot filtering and browser preferences mean these counts are approximate.
Operational records needed for accounts, payments, downloads and security are separate from these visitor reports. For questions, contact Usagita.
Find it. Make it. Keep it.