Cookie Policy: Clear Terms for Our Digital Tools
At Diglino Studio, we build games that live in browsers. Like any professional toolkit, our games require a few small, persistent memory files—cookies—to function correctly, remember your preferences, and help us understand what works so we can build better experiences for you.
This policy isn't a legal abstraction. It's a technical specification for how our site stores data in your browser, what each cookie does, and how you can control it. We treat your data with the same precision we apply to our code.
Technical Context
Cookies are simple key-value pairs, not databases. They're designed for lightweight, client-side state management.
The Cookie Vocabulary
Plain-language definitions for our specific implementation.
Session Cookie
Lasts only while the browser is open. Essential for keeping you logged in during gameplay or preserving a level state between pages.
Persistent Cookie
Has an expiration date (up to 1 year). Used for remembering your accessibility settings or cookie consent choices across visits.
First-Party Cookie
Set by Diglino Studio directly (diglino.com). All our necessary operational cookies fall into this category.
Third-Party Cookie
Set by a different domain. We do not use these for analytics or advertising. Our games are self-contained experiences.
Cookie Implementation Matrix
A breakdown of the minimal set of cookies required to run our site and games. We don't use cookies for tracking or profiling.
diglino_session
Purpose: Maintains your authenticated session. Without it, you'd be logged out after every page load.
Data Stored: An anonymous session ID (random string).
Duration: Expires when the browser session ends.
pref_theme
Purpose: Remembers if you've chosen a light or dark theme for the studio site.
Data Stored: A simple string ("light" or "dark").
Duration: 1 year. You can clear it anytime in your browser settings.
cookie_consent
Purpose: Stores your consent choice (accept/reject) so we don't show you the banner on every visit.
Data Stored: Timestamp and your preference.
Duration: 6 months. We will re-prompt you after this period.
Technical Realities & Trade-offs
Building browser-based games requires precise client-side state management. Cookies are one of the few tools that work reliably across all browsers for this purpose, despite their age.
Trade-off: Simplicity vs. Precision
Using server-side sessions only is more secure but creates latency for users with unstable connections. We choose to handle non-sensitive state (like theme preference) with cookies to keep the game experience snappy, while all critical data (account info, purchase history) lives server-side.
"In our game engine, we use cookies solely for UX persistence. The actual game state is mirrored in localStorage for immediate response, then synced to the server when a connection is available."
— Lead Developer, Engine Team
You Are In Control
You can disable or delete cookies at any time through your browser settings. For our essential session cookies (like keeping you logged in), disabling them will mean you need to re-authenticate on each visit.
How to Manage Preferences
- Chrome: Settings > Privacy and security > Cookies and other site data
- Firefox: Options > Privacy & Security > Cookies and Site Data
- Safari: Preferences > Privacy > Manage Website Data
Questions About Our Data Practices?
We believe in transparent engineering. If you need clarification on how we handle data in our games or on our studio site, our technical team is here to answer.
Mon-Fri: 9:00-18:00 | ul. Nowy Świat 12, 00-001 Warszawa