Countdown timer data paths

Where WordPress countdown timers send visitor data

Some countdown timers store the deadline in a cookie on your site. Clearing that cookie can reset the timer. Other timers load an outside countdown service. A timer that also logs the visitor IP on your WordPress server can still remember the visitor after cookies are cleared. This table describes the setups below; your settings can change where requests go.

Based on plugin documentation, not tests of your site. Your settings can change what loads. This is not legal advice or a compliance rating.

Scan your site for third-party requests

How we group countdown timers

We compare the countdown timer setups named below. A timer that stores the deadline in a cookie on your site is different from a timer that loads an outside countdown service. Clearing cookies can reset a local cookie timer. A timer that also logs the visitor IP on your WordPress server can still remember that visitor. We have not tested consent timing, cross-device matching, or how long countdown-service logs are kept.

Countdown timer plugins

No paid placement. Deadline stored on your site first, then outside countdown services, then plugins not yet reviewed. Names are alphabetical within each group.

PluginDocumented behaviorDocumented service domainsHow long data is keptBefore consentLinksSource
Evergreen Countdown Timer

This row covers Evergreen Countdown Timer when the deadline is stored in a cookie on your site. Clearing cookies can reset that timer. Cookie plus IP tracking is a different setup and is not this row. Consent timing is not tested here.

Deadline stored on your siteNo outside countdown service documented for this setup. Other page requests are not covered.Not assessedNot tested
  • None
HurryTimer

This row covers HurryTimer when the deadline is stored in a cookie on your site. Clearing cookies can reset that timer. IP-based tracking logs the visitor on your WordPress server and can still remember the visitor after cookies are cleared. Consent timing is not tested here.

Deadline stored on your siteNo outside countdown service documented for this setup. Other page requests are not covered.Not assessedNot tested
  • None
OptinMonster

This row covers OptinMonster when a campaign is published. The page loads an outside script from a.omappapi.com, including countdown campaigns. This is not a deadline stored only on your site. Consent timing is not tested here.

Outside countdown servicea.omappapi.comNot assessedNot tested
  • None
Deadline Funnel

We have not reviewed this plugin's countdown data path yet.

Not reviewedDocumentation not reviewed yet.Not assessedNot tested
  • None

What this table does and does not prove

This table describes the named countdown timer setups. It does not show what loads on your site. Where no outside countdown service is documented, that applies only to the setup described. Other page requests are not covered. Clearing cookies can reset a local cookie timer; an IP log on your WordPress server can still remember the visitor. Plugins marked Not reviewed have not been assessed. We have not tested consent timing, cross-device matching, or how long countdown-service logs are kept. The site scan linked below checks for third-party requests; it does not access your WordPress database.

Documentation snapshot: Oct 1, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-countdown-timer-privacy