Cookie Policy

In the signed-in private application, a session cookie is set by Better Auth. It keeps you signed in, protects your account and is required for the application to work. It is HttpOnly and SameSite=Lax. The secure flag is enabled in production. The marketing-only site has no sign-in area, so it should not set that session cookie.

The site uses browser local storage for interface preferences and, in the private application, to resume an interrupted onboarding draft. The theme preference is stored under the theme key by Next Themes. Onboarding draft keys begin wepostsocials:onboarding and are cleared when the form is completed. Local storage is not sent with every request.

The theme preference is a functional preference, not a strictly necessary authentication cookie. The current build stores it automatically and does not show a consent banner for it. The owner must decide whether to treat it as strictly necessary for the requested interface preference or add consent before it is stored.

The onboarding draft is used to resume a form the signed-in user has already started. It may contain business/profile information and is cleared on completion. An abandoned draft may remain in that browser until the user clears site data or starts the flow again. It is not used for analytics or advertising. The final production behaviour must be confirmed before launch.

OWNER INPUT REQUIRED — decide the consent treatment for theme and onboarding local storage, or remove the persistence.

No advertising cookies, cross-site tracking pixels, third-party analytics or session-replay scripts are active in the audited code. The codebase contains no analytics tracker and no consent-gated tag. This does not by itself justify claiming that every item in local storage is strictly necessary; see the functional-storage section above.

OWNER INPUT REQUIRED — confirm the final production stack does not add analytics, error replay or marketing tags before launch.

Before adding any non-essential cookie or tracker we will add a consent mechanism that blocks it until you accept, provide an equally clear reject option, remember your choice, and allow you to change it later. This policy will be updated at the same time.

You can delete or block cookies in your browser. Blocking the session cookie prevents sign-in. Browser controls vary; use your browser's privacy settings for the exact steps.