- Home/
- Cookie Policy
Cookie Policy
How MakeSKU uses cookies, local storage, and related browser technologies across its public pages and product workspaces.
Introduction
This Cookie Policy explains how MakeSKU may use cookies, local storage, session storage, and similar browser technologies. Read it with the Privacy Policy. MakeSKU includes browser-native deterministic editors and configuration-gated AI workspaces; browser storage supports both but does not itself activate an AI provider or authorize a credit charge.
What These Technologies Are
Cookies are small text records a website can ask a browser to store and return. Local and session storage keep site data on a device. Similar technologies can support sessions, remember settings, measure performance, correlate a protected request, or connect an embedded service. A technology can be set by MakeSKU or by a configured provider whose feature you use.
How MakeSKU Uses Browser Storage
The site may use these technologies for:
- Essential operation and security: routing requests, maintaining an enabled account session, protecting forms, preserving checkout state, and detecting abuse.
- Preferences: remembering language, light or dark theme, interface choices, and the optional-services preference.
- Deterministic workspace state: retaining selected controls, temporary preview state, crop settings, batch selection, and browser-generated previews during an editing session.
- AI workspace state: retaining non-sensitive interface choices such as model selection, output count, format, and storyboard order before a server submission.
- Performance and reliability: understanding load behavior and errors when an applicable service is configured and allowed.
- Analytics: measuring query-free page paths and coarse product steps when optional third-party services are allowed under the rules below.
- Support: loading a configured third-party support widget when allowed under those rules; the Contact page remains available without it.
- First-party Affiliate attribution: recording a valid aff or aff_id and validating it again during checkout. This track is independent of region, consent, and GPC, and those controls do not delete an existing track.
- Third-party referral integration: loading configured affiliate or referral scripts and sending outbound reports only when the optional-service rules allow.
Browser storage does not bypass AI readiness. If required server configuration is incomplete, the AI workspace remains unavailable, no provider submission occurs, and no credit is charged.
Necessary Technologies
Necessary technologies support page delivery, security, enabled account sessions, protected server requests, and checkout. Blocking them may prevent sign-in, submission, history, download, payment, or other account features from working. These technologies are not controlled by the floating consent card.
Preference Technologies
MakeSKU stores an explicit Allow all or Only essential choice as a versioned value in a first-party, server-readable cookie named optional_services_consent and mirrors the same value in local storage. The preference cookie lets the initial server response respect a returning visitor's choice; it does not itself load an optional service and lasts up to 180 days. Only values for the current disclosure version are accepted, so an older version becomes unknown and gated visitors are asked again. If cookie and local-storage values disagree, MakeSKU resolves the conflict to Only essential. A denial from the former MakeSKU analytics-only setting may migrate to this broader preference, but an old grant does not grant support or referral services.
Optional Analytics, Support, Referral, and Product Measurement
Configured optional services are split by location. For visitors in the EEA, the United Kingdom, Switzerland, or with a missing or unknown location result, they remain off until the visitor chooses Allow all on the non-modal floating consent card. For visitors elsewhere, they are allowed by regional default after MakeSKU checks GPC, and that default does not create a synthetic preference. A configured optional service can include site analytics, a support widget, a third-party affiliate or referral integration, and MakeSKU's privacy-limited product funnel measurement. Choosing Only essential or using the opt-out keeps them off in every region. This optional category does not include MakeSKU's first-party server attribution or first-party Affiliate track.
A configured cookieless Umami script may load independently of this choice with automatic tracking disabled. MakeSKU sends product analytics events through that integration only when the optional-services rules permit them.
MakeSKU records limited first-party server attribution in every region. Its separately signed, first-party browser artifacts use independent 30-day windows: the Marketing fallback follows the regional consent policy, while a valid aff or aff_id updates the first-party Affiliate track regardless of region, consent, or GPC. They contain only an anonymous identifier and approved attribution fields, never an uploaded image, prompt, file name, image URL, email address, or checkout session ID. Eligible attribution can be associated after sign-in or authenticated checkout; an invalid or unavailable handoff is ignored and never blocks either flow.
Global Privacy Control
In gated locations, the visitor's direct Allow all or Only essential choice controls optional services and GPC does not override it. GPC only blocks optional third-party services and outbound sharing in non-gated locations. It does not overwrite a saved preference or clear first-party Marketing or Affiliate attribution.
Third-Party Technologies
Configured authentication, payment, infrastructure, analytics, support, referral, storage, or AI providers may set or read their own technologies when the relevant feature is used, under their policies. Optional browser analytics, support, and third-party referral integrations remain blocked unless the gated-region choice, or the non-gated regional default and GPC rule, allows them. AI provider task identifiers and signed callbacks are server-side workflow data, not marketing cookies.
Local Files Are Not Cookies
A product image selected for browser editing or upload is not a cookie. Deterministic editor inputs are processed locally unless an explicit persistence step uploads an output. AI reference images are uploaded only after you submit a configured AI workflow. Temporary object URLs and Canvas previews may disappear when the page is refreshed or closed.
Managing Cookies and Storage
Most browsers let you view, delete, or block cookies and local storage. Clearing site data may sign you out, reset language or theme, remove workspace state, invalidate temporary previews, and remove an explicit optional-services choice. Gated visitors, and anyone who has made an explicit choice, can use Cookie settings in the shared footer or account sidebar to reopen the floating consent card. Do Not Sell or Share My Personal Information is available there in every region and applies the same Only essential opt-out, followed by a confirmation message. To remove a saved choice entirely, clear MakeSKU cookies or site data. GPC remains available independently.
Blocking necessary technologies can make account, generation, history, download, or checkout features unavailable, while public content pages should remain readable. Declining optional services does not disable MakeSKU's five core workflows.
Retention, Changes, and Contact
Session technologies may expire when the browser session ends. The optional-services preference is versioned, and its first-party cookie lasts up to 180 days unless you clear it sooner; values from an older disclosure version are no longer accepted. First-party Marketing and Affiliate browser artifacts use independent 30-day attribution windows. Only essential or withdrawal clears the Marketing browser fallback, while the Affiliate artifact is not cleared by region, consent, or GPC. Third-party providers set their own retention periods. This policy may change as site technology and connected services change; the current version and effective date will remain on this page. Questions can be sent through the MakeSKU contact page.