Cookie Policy

Last updated: August 25, 2026

Prodmake LLC operates prodmake.com. Self-hosted analytics is cookieless. On paid campaign entry pages, Meta advertising cookies may be set only after you explicitly allow advertising measurement.

Browser storage used by Prodmake

  • Theme preference. Remembers whether you selected light or dark mode.
  • Campaign attribution. Remembers the first and latest campaign parameters so a submitted application or brief can be attributed to its source.
  • Application and brief drafts. Keeps unfinished answers in session storage so an interruption does not erase your work.
  • Advertising choice. Remembers whether you allowed or declined Meta campaign measurement.

You can clear this information through your browser settings. Clearing it may reset the theme or remove an unfinished brief, but does not prevent you from using the site.

Cookieless analytics

Prodmake uses a self-hosted Rybbit instance to measure page visits and anonymous actions such as opening or submitting a product application or brief. Rybbit does not set analytics cookies. It may process the page, referrer, browser and device information, approximate location derived from the IP address, and a rotating anonymous identifier derived from the IP address and user agent.

Session replay is disabled. Prodmake does not send names, email addresses, product application or brief answers, or other free-form form contents to Rybbit.

Optional Meta campaign measurement

On paid campaign landing pages, the central application quiz, and their linked brief flow, Prodmake asks before loading the Meta Pixel. If you allow it, Meta may set _fbp and _fbc cookies and receive page-view and submitted-application events. The browser and server versions of the application event share an event ID to prevent duplicate counting.

Meta is not loaded on the general website or direct brief visits. If you decline, the campaign flow still works and no event is sent to Meta.

Forms and delivery

Product application and brief endpoints may use server-side rate limiting and duplicate detection. Delivery providers process submitted information only to route it for human review.

Your choices

You can clear local or session storage and enable your browser’s Do Not Track setting. You can also withdraw a previous Meta choice below or contact [email protected] with a privacy request.