1. WHAT ARE COOKIES
Cookies are small data files deposited and stored on your computing terminal, workstation, or mobile device when accessing modern digital environments. In conjunction with standard HTTP cookies, ATELIER // ARCH utilizes related computational storage mechanisms including:
- Local Storage & Session Storage: Web storage mechanisms providing client-side key-value capabilities to retain UI state configurations and session resilience across browser refresh cycles without transmitting data in headers.
- Single-Pixel Tags & Beacons: Microscopic graphic scripts embedded in pages or operational emails designed to verify operational availability, technical rendering compatibility, and message transmission fidelity.
- Cryptographic Session Identifiers: Ephemeral tokens exchanged within secured header parameters to maintain encrypted state coordination between user workstations and distributed inference clusters.
Collectively, these mechanisms are referred to throughout this instrument as "Storage Technologies."
2. HOW WE USE COOKIES
ATELIER // ARCH enforces a rigorous principle of computational minimalism. We deploy storage technologies strictly for legitimate platform operations across three core systemic modules:
Layout coordinates, canvas render preferences, grid snap tolerances, and tool palette orientation.
Attribution telemetry for registered inbound partner referrals and suppressing redundant platform announcements.
Zero-trust authentication state, API nonce integrity, rate-limiting guards, and inference compute load balancing.
3. CATEGORIES OF COOKIES
The operational scope of storage elements is compartmentalized into four delineated legal taxonomies:
| CATEGORY | PURPOSE | OPTIONAL? | STATUS |
|---|---|---|---|
| Essential | Authentication, security, session continuity, CSRF defenses | NO (REQUIRED) | ALWAYS ACTIVE |
| Functional | Workspace layout persistence, currency, language, regional parameters | YES | CONFIGURABLE (ON) |
| Analytics | Aggregate diagnostic metrics, latency tracking, UI load optimization | YES | RESTRICTED (OFF) |
| Marketing | Campaign attribution, partner verification, frequency capping | YES | RESTRICTED (OFF) |
4. ESSENTIAL TECHNOLOGIES
Essential storage tokens are deployed under Article 6(1)(f) of the GDPR and equivalent international legal standards, representing the strict legitimate interest of providing reliable, safe software infrastructure.
Disabling these technologies through browser-level overrides will prevent authentication, disrupt cryptographic session handshakes, and render the ATELIER // ARCH workstation inoperative. Specific essential keys include:
5. FUNCTIONAL TECHNOLOGIES
Functional cookies ensure environmental continuity for professional workflows. They retain the user's designated monetary denomination (e.g., USD, EUR, GBP), studio layout configuration, expanded tool drawer state, and high-DPI viewport adjustments.
When toggled off, ATELIER // ARCH defaults to standard UTC timezone rendering, auto-detected system currency, and standard workspace docking configurations on every session load.
6. ANALYTICS
Diagnostic telemetry permits our computational engineering team to detect rendering bottlenecks, GPU compilation errors, and API latency trends across varying screen form-factors.
Third-party analytics agents are strictly blocked until affirmative consent is logged via the Cookie Preferences panel. In accordance with zero-trust design, telemetry data is pseudonymous, IP-masked at transmission ingress, and never combined with customer creation prompts or generative image outputs.
7. MARKETING TECHNOLOGIES
Marketing technologies are restricted to verifying campaign attribution for creator-partnership codes and limiting repeated institutional invitations.
Non-Participation Guarantee: ATELIER // ARCH does not participate in third-party cross-context behavioral ad networks, does not deploy data-broker tracking scripts, and does not sell or lease computational records or user metadata to any outside entity.
8. THIRD-PARTY TECHNOLOGIES
Certain structural sub-processors embed necessary computational storage tokens to process payments (e.g., PCI-DSS Level 1 compliant processors) and mitigate distributed denial-of-service incursions.
All integrated third parties operate under strict contractual Data Processing Agreements conforming to ISO/IEC 27001 and SOC 2 Type II certifications. For an exhaustive register of verified external data subprocessors, please inspect our companion documentation:
SEE PRIVACY POLICY arrow_forward9. COOKIE RETENTION
Storage elements possess explicit temporal boundaries:
- Session Cookies: Instantiated in volatile memory and terminated immediately upon browser termination or workspace sign-out.
- Persistent Cookies: Maintained on client hardware until their designated expiration date (typically ranging between 24 hours to a maximum statutory limit of 12 months) or manual cache purge.
10. MANAGING PREFERENCES
You maintain unalienable sovereignty over non-essential telemetry. You may revise, revoke, or re-enable permissions at any juncture by utilizing our on-page interactive control dashboard:
MANAGE COOKIE SETTINGS ↑11. BROWSER CONTROLS
Direct hardware controls can be executed through your local browser environment. Standard browsers allow you to review, inspect, reject, and delete existing storage records:
* Note: Universal third-party blocking will not disrupt essential ATELIER // ARCH authentication when operating within first-party domain contexts.
12. CHANGES TO POLICY
We reserve the prerogative to recalibrate this Cookie Policy in alignment with technical evolutions, product architecture updates, or revised statutory edicts. Material revisions will be broadcast through system notification alerts upon workstation initiation or via prominent banner notices 30 days prior to effectiveness.
13. CONTACT & INQUIRIES
For legal inquiries, Data Protection Officer communications, or full audit log verification, address our compliance desk: