Favorites and History Guide
Client-Side Storage Overview
SlotScars operates as a non-commercial reference directory and does not provide registration, member dashboards, or persistent cloud user accounts. When you bookmark titles or review your recently viewed games, your selections are kept strictly on your local device.
This mechanism relies on standard web browser localStorage rather than complex local databases like IndexedDB or central profile databases. Your preferred interface language from our eight supported locales (English, Simplified Chinese, Indonesian, Thai, Vietnamese, Brazilian Portuguese, Filipino, and Hindi) is also recorded using this same client-side method.
How Selected Game Lists Are Processed
Because SlotScars uses server-rendered templates to provide swift loading and accurate metadata, your browser transmits the raw numeric or alphanumeric IDs of your saved titles to our application programming interface during browsing. This lookup enables the server to return enriched summaries, visual badges, and technical parameters.
This technical exchange is purely transactional. The server processes these item identifiers momentarily to compile the requested page layout and does not attach them to a persistent server-side account or long-term behavioral profile. We do not claim complete absence of network transmission, as standard HTTP request metadata is processed during page delivery.
Managing and Resetting Your Stored Preferences
Because your favorites and history reside exclusively within your individual browser instance, there is no cross-device synchronization. If you transition between a desktop workstation and a smartphone, your saved collection will not follow you.
You can purge your saved titles at any time by clearing your browser cache, wiping local storage cookies and site data, or engaging private browsing modes. Once wiped, this information cannot be restored by our support personnel since no secondary backups exist on our servers.
Third-Party Cookies and External Metadata
Our own storage policies strictly govern the catalog interface, navigation bars, and local bookmark toggles. However, once you choose to launch an external demo from a game detail page, the game frame connects directly to third-party game providers.
Those independent game studios may execute their own temporary scripts, store operational cookies, or evaluate network latency according to their respective terms. We suggest inspecting your browser permission settings if you wish to regulate how external providers handle client-side cache.