Legal template

Cookie Policy

A simple cookie template for DevFrame deployments, focused on Clerk sessions, preview-cookie fallback, local editor state, and future analytics disclosure.

DevFrame system map

The same App Router shell powers marketing, Studio, Builder, Dashboard, and public portfolio routes.

Runtime

Next.js App Router

Server components first

Output

/p/[slug]

Shareable portfolio routes

Data

Single record

Template swaps preserve content

Fallback

Demo mode

Works without full setup

Template notice

Review before production use

This cookie policy is general placeholder copy for DevFrame and should be reviewed before production or legal use.

It is not legal advice.

Update it for the cookies, analytics tools, domains, and third-party services in your deployment.

Essential

Authentication cookies

When Clerk is configured, session-related cookies may be used to keep users signed in and protect owner workflows.

Authentication cookies are controlled by the configured Clerk project.

Owner-only editing flows depend on reliable server-side session checks.

If Clerk is not configured, demo mode does not provide durable account sessions.

Preview

Draft preview cookie

When Supabase write access is unavailable, DevFrame can store a preview portfolio draft in a secure cookie.

`devframe-preview` keeps local or unconfigured environments usable.

Preview cookies are not a replacement for durable Supabase persistence.

Public API responses adjust cache headers when preview cookies are present.

Preferences

Interface preferences

DevFrame may use small local preferences for UI behavior, such as theme or editor draft state.

Studio uses local browser storage for guest draft continuity.

Theme behavior depends on the existing theme provider setup.

Saved Supabase records should take priority over stale local Studio draft state.

Analytics

Analytics and tracking

This template does not claim that analytics are enabled by default.

If you add analytics for portfolio views, document the provider and retention behavior.

Future roadmap work may add privacy-conscious portfolio analytics.

Update this policy before enabling additional tracking technologies.

Control

Managing cookies

Users can control cookies through their browser settings, but disabling essential cookies can break auth and preview workflows.

Clearing browser data may remove preview drafts and local Studio state.

Production deployments should describe any consent mechanism they actually provide.

Third-party providers may set their own cookies under their own policies.

This page is general placeholder legal copy. Review and adapt it before using DevFrame in production or presenting it as your final cookie policy.