Cookie Policy
What exactly are we storing when you build with Brandixo?
Short answer: preference data and analytics that make your workshop run faster, not personal tracking.
Long answer: Like any modern tool, Brandixo uses small text files—cookies—to remember your session, your workspace settings, and how you use the builder. We don't sell this data. We don't use it for ad networks. The 'long answer' is that we're optimizing for your performance as a game developer, not for third-party surveillance.
Core Principle
Every cookie we set has a single, stated purpose: to remove friction from your workflow. If a cookie's job isn't obvious from its name, we don't use it.
Cookie Breakdown
Scope: brandixo.spaceThese cookies keep you logged in to your project workspace. They expire when you close the browser (session cookies) or after 30 days of inactivity.
No persistent personal ID. Just a random session token.Remembers your panel layout, preferred build engine (Unity/Unreal toggle), and asset library filters. These persist for 90 days.
This is why your workspace looks the same every time.A single, anonymous analytics cookie. Helps us identify which API endpoints are slow on legacy Android devices, or if asset previews load too slowly on mobile data.
No IP addresses stored. No cross-site tracking.None. We do not embed Facebook Pixel, Google Analytics, or any ad network SDKs. Your cookie jar is empty of third-party cookies by default.
If you see something else, it's a bug. Report it.Realism Anchor: The Indie Dev
Scenario: You're debugging a Unity build export crash at 2 AM. Your session cookie saves your unsaved workspace. The analytics cookie notes a spike in export failures on iOS 17, prompting a patch.
Constraint: App Store Compliance
We avoid all cookie policies that could trigger an App Store rejection (e.g., mandatory 3rd-party tracking). Our policy aligns with strict platform guidelines.
Trade-off: Privacy vs. UX
We choose UX > Analytics. If a cookie hurts the experience, it gets removed. We sacrifice granular data for a faster, cleaner tool.
Your Control: Granular Consent
Required for core functionality: authentication, saving workspace state, and protecting against CSRF attacks. These cannot be disabled. If you block these, the site will not function.
Anonymous data on load times and error rates. Used only to prioritize performance fixes. We delete this data after 12 months. View our data retention policy.
Remember your UI layout, filter preferences, and visual settings. Disabling this will reset your workspace to default every session.
Want to change your mind?
You can adjust your cookie settings at any time. Changes apply immediately to new page loads.
Cookie Concepts: From Storage to Session
A visual guide to how data flows through our system.
auth_session
The key to your workshop. Not a user ID, just a temporary session token that expires.
workspace_layout
A map of your UI. Your window positions, panel states, and filter settings.
perf_pulse
A silent heartbeat. Logs API latency and error rates, but never links to your account.
csrf_token
A security proof. Proves your form submission came from the site, not a malicious script.
Swipe to explore concepts
Stay Informed
Get policy updates or product news. Unsubscribe anytime.