Skip to content
PorchOps
Legal

Cookie Policy.

last updated · version 1.1

Every cookie and tracker porchops.com sets or loads, in one place: what it is for, how long it lasts, whether it is in use today, and how to say no. The tables below are rendered from the same list our code reads, so this page and the site cannot quietly disagree. Right now 2 of 7 vendors are running and 5 are listed ahead of use; a vendor is switched on only after this page already says what it does, which is why some rows below read "not switched on" and say what would switch them on. The 3 cookies we set ourselves are in the same tables, each under the category it belongs to.

This page is the operative statement of our cookie practices. Section 15 of the Privacy Policy summarizes it; for cookies, where the two differ, this page controls.

Section 2

Strictly necessary.

Needed for the site to keep your choices. Cannot be refused, because refusing them is itself a choice we have to remember.

ProviderPurposeCookies and lifetimeStatus
TermlyRemembers the choices you make in the cookie banner, the version of this policy you saw and the region we detected, so we can honor your choice on your next visit and prove we did.Neither lifetime rolls forward. The 180 days run from the day you answered, not from your most recent visit, so a stored answer expires into a fresh question rather than lasting for ever. Consent records are kept for at least 18 months.
  • pco_consent180 days from the day you answered, and it does not restart on later visits, so the window ends and we ask again · set by porchops.com
  • pco_regimeYour browser session · set by porchops.com
Not switched on

The two cookies above are ours and are set as soon as there is something to remember: pco_regime on the first request, pco_consent when you answer the banner. Termly's own cookie is not listed yet because the account is not bought and its banner is not running; it is added to this table before that banner is switched on.

Section 3

Analytics.

Tell us which pages people read and which lead to a signup. Off by default in the opt-in regions; elsewhere you can opt out, and a Global Privacy Control signal counts as an opt-out.

ProviderPurposeCookies and lifetimeStatus
PorchOpsRemembers which campaign or link brought you here, so a later signup can be credited to it. Carries no name, no email and no account.The 30 days run from your first visit and do not roll forward on later ones. It holds the campaign parameters that were in the address bar you arrived on, the site you came from, and the first page you landed on.
  • pco_attr30 days from your first visit, measured from that first visit and not restarted by later ones · set by porchops.com
In use

Written only if you allow analytics cookies. Refuse them and it is never set; withdraw and it is deleted.

Plausible AnalyticsCounts page views, referrers and approximate location in aggregate, so we know which pages people read.Sets no cookie and no persistent identifier. Processed in the European Union. If you withdraw analytics consent we do write two flags into your browser's local storage, plausible_ignore and pco_plausible_ignore, which exist to keep Plausible quiet on later pages; they identify nobody and are the record of your refusal, not of you.No cookie, no persistent identifier.In use
PostHogRecognizes repeat visits as the same visitor so we can see which pages lead to a signup. Not used for advertising and not shared with advertisers.Session replay is switched off in our code. A Global Privacy Control signal stops the script loading at all, so no cookie is set.
  • ph_<project>_posthog (plus a copy in browser storage)1 year (posthog-js default) · set by porchops.com
In use
HubSpotRecognizes a returning visitor and, if you sign up, ties the pages you visited on porchops.com to your contact record, so we can follow up and build advertising audiences.Filed under analytics because that is the consent our code actually asks for, and the page has to match the gate. It is not the whole story, so here is the rest: HubSpot also feeds advertising audiences, and that half is governed separately by your advertising choice, which we pass to HubSpot. Allow analytics and refuse advertising and you get a tracker that counts page views and does not build an audience from you. HubSpot's own cookie banner is switched off; ours is the one that decides.
  • hubspotutk6 months · set by porchops.com
  • __hstc6 months · set by porchops.com
  • __hssc30 minutes · set by porchops.com
  • __hssrcthe browser session · set by porchops.com
Not switched on

The loader ships, and it runs only once a HubSpot account id is configured for the site. Until then nothing is requested and none of these cookies is set.

Section 4

Advertising and CRM.

Measure ads and build audiences so we can show ads to people who visited. Off until you consent in the opt-in regions; elsewhere you can opt out, and a Global Privacy Control signal counts as an opt-out.

ProviderPurposeCookies and lifetimeStatus
Google (Ads, via Google Tag Manager)Measures which ads brought you here and lets us show ads to people who visited porchops.com, on Google's network.Google Consent Mode v2 in Basic mode: in the opt-in regions the tag does not load until you consent, and sends nothing if you refuse.
  • _gcl_au3 months · set by porchops.com
  • IDE13 months · set by the vendor
Not switched on

Carried by a Google Tag Manager container. The container loader ships, and it runs only once a container id is configured for the site. Until then no tag loads and none of these cookies is set.

Meta (Facebook, Instagram)Measures ad results and lets us show ads to people who visited porchops.com, on Meta's platforms.Never loaded on a page with embedded video. Limited Data Use is on for every visitor from the United States. In the opt-in regions the pixel is not loaded until you consent.
  • _fbp3 months · set by porchops.com
  • _fbc3 months · set by porchops.com
  • fr3 months · set by the vendor
Not switched on

Carried by the same Google Tag Manager container, so it runs only once a container id is configured for the site and the pixel is added to it. Until then none of these cookies is set.

LinkedInMeasures ad results and lets us show ads to people who visited porchops.com, on LinkedIn.LinkedIn offers no consent API, so the tag is blocked outright until you consent rather than loaded and told to stay quiet.
  • li_sugr3 months · set by the vendor
  • bcookie1 year · set by the vendor
  • UserMatchHistory1 month · set by the vendor
  • lidc1 day · set by the vendor
Not switched on

Carried by the same Google Tag Manager container as the two rows above, so it runs once a container id is configured for the site and the tag is added to it. Until then none of these cookies is set.

Section 5

Your privacy choices.

We do not sell personal information for money. When advertising cookies are set, the information they carry is "shared" for cross-context behavioral advertising as California law defines it, and you have the right to opt out of that at any time. This section is the opt-out.

  • Send a Global Privacy Control signal. Turn it on in your browser or install a browser extension that sends it. We honor it everywhere, as an opt-out of sale and sharing, and in the opt-in regions as a refusal of analytics cookies too. Nothing loads; no cookie is set. This is the fastest way and it needs no account.
  • Use the control in the footer. "Your Privacy Choices", at the bottom of every page, reopens the preference center where you can change any category. Withdrawing is the same single click as giving, which is the standard the law sets and a fair one.
  • Refuse cookies in your browser. Blocking or clearing cookies for porchops.com removes every entry above except the strictly necessary ones.
  • Email us. [email protected] with "opt out" in the subject. You may use an authorized agent; we will ask for enough to verify the request. We respond within the time the law gives us, usually 15 business days for an opt-out.

Opting out never costs you anything on porchops.com: the same pages, the same prices, the same product.

Section 6

What we never do.

  • Record a replay of your visit. Our analytics vendor supports it and it is switched off in our code.
  • Load the Meta pixel on any page with embedded video.
  • Identify you by name from your IP address or device. We do not use visitor de-anonymization services.
  • Fingerprint your device beyond what security requires.
  • Set an analytics or advertising cookie in an opt-in region before you have said yes, or anywhere after you have said no.
Section 7

Changes to this page.

When a tracker is added or switched on, this page changes first, in the same change that adds the code. The date and version at the top move with it. Material changes to how we use cookies are also announced as described in Section 16 of the Privacy Policy.

last updated · version 1.1