Our Cookie Policy is a transparency tool, not a compliance wall.
We believe you should know exactly what data helps our Bogotá studio craft better web experiences. This document explains what our site stores in your browser, why it matters for performance, and how you can control it. No tracking tricks, no hidden payloads—just the essentials for a functional studio presence.
"Data should serve design, not drive it. We use cookies to understand technical constraints—never to profile people."
What We Store & Why
Essential Operation Cookies
RequiredThese cookies are strictly necessary for site functionality. They handle session management, form submissions, and security tokens. No personal data is stored; these are temporary identifiers that expire when you close your browser or after 24 hours.
- _px_session: Maintains your contact form progress
- _px_csrf: Protects against cross-site requests
Performance & Analytics
OptionalWe use anonymized analytics to understand which portfolio projects attract technical inquiries versus creative briefs. This helps us balance our studio portfolio between e-commerce builds and brand-focused web experiences. All data is aggregated; no individual profiling occurs.
Embedded Content
ExternalPages with Google Maps or video embeds may set cookies directly from those third-party services. We do not control these cookies. Please review Google's privacy policy for details on their data practices when viewing our studio location.
Our Decision Lens: How We Choose to Track
- • Form recovery (prevents losing work)
- • Security (blocks spam submissions)
- • Performance (caches heavy assets)
- • Granular user journeys
- • Retargeting capabilities
- • Persistent cross-session tracking
We intentionally avoid behavioral advertising. Our goal is to answer your email, not sell you a pixel.
How We Think About Browser Storage
In our Bogotá studio, we treat cookies like the tools on our workbench: they should only exist if they serve a clear purpose. Modern web development has normalized invasive tracking, but we design our systems to function with minimal data persistence.
This approach impacts our workflow. When building e-commerce platforms or portfolio sites for clients, we often recommend server-side session handling over client-side cookies where possible. It's more secure, respects user privacy, and avoids the "cookie banner fatigue" that degrades user experience.
Real Constraint: Legal Compliance
Under Colombian law, informed consent is required for non-essential cookies. We design our forms and validation logic to capture consent granularly, ensuring our clients' sites remain compliant without breaking user flow.
By being transparent about our own practices, we hope to set a standard for the projects we deliver. Every pixlixa build includes a privacy-first approach to data collection, because trust is harder to earn than traffic.
Questions to Ask Any Studio About Data
Before signing a contract, verify their approach aligns with your risk tolerance.
If You Can't Explain It, Don't Set It.
The best cookie policy is one your studio team can defend in a client meeting. We build assuming every cookie we set will be audited by a skeptical user. That discipline improves our code and earns trust. You should expect the same from any partner.
Questions about our policy?
Reach our team directly. We respond within 24 hours during business days.