CG Templates1. Scope and current inventory
This draft covers cookies, local storage and similar technologies used by CG Templates. The inventory below is based on local source inspection, not a completed audit of a published site or all provider-injected technologies.
The existing email-link purchase portal uses the first-party __Host-cg_buyer cookie to authenticate purchase access for up to 24 hours. It is Secure and HttpOnly. The application also uses Supabase authentication storage, normally in local storage, and a session-brokering mechanism on Lovable previews.
[TBD: exact authentication storage keys, lifetimes and behavior for the future registered-buyer account flow; audit hosting, payment, font, diagnostics and embedded-demo technologies on the approved launch configuration. Link or cookie expiry is not a database deletion schedule.]
2. Planned analytics
Google Analytics is planned but is not added or configured by these draft pages. It may involve identifiers and information about pages, visits, traffic sources and device/browser context, depending on the settings ultimately selected.
[TBD: actual cookies and other identifiers, provider, purposes, events, retention and expiry, recipients, consent requirements and data-sharing settings. Do not substitute assumed default cookie lifetimes for a verified inventory.]
3. Possible advertising technologies
Personalized advertising and remarketing are under consideration. No partner, technology or activation date has been chosen in the owner intake.
[TBD: partner and technology inventory, purposes, expiry, regional permissions and opt-outs, and any applicable sale/sharing or targeted-advertising notice.]
4. Choices before activation
Proposed launch approach: keep optional analytics and advertising disabled until the relevant notice, permission and preference controls have been implemented and tested. Where consent is used, customers should be able to accept, reject and later change optional choices without treating purchase or registration as consent.
[TBD: implement the preference interface, withdrawal/rejection behavior, retention of choice records and applicable browser opt-out signals. There is no working cookie-preference control supplied by this draft. No new tracking script is installed by it.]
Browser controls can remove or block cookies and local storage; doing so may sign you out or affect purchase-access functions. Browser blocking alone does not replace the site's required choice and permission controls.