Cookie Policy
Last updated: May 17, 2026
This Cookie Policy explains the cookies and browser local-storage entries that SimpleCronTab sets, either directly or through third parties. It complements the Privacy Policy, which describes the overall information we process and why. Cookies are small text files that a website asks your browser to store on your device. They let the site recognise you on return visits, coordinate ad serving, or remember a preference such as your colour theme.
We use cookies sparingly. The Service does not have user accounts, does not sell first-party data, and does not run remarketing campaigns against you elsewhere on the web. The cookies that do appear are there to make the visual builder, the analytics, and the advertising that supports the Service work correctly.
Cookies in use
The table below lists every cookie or local-storage entry you are likely to encounter while using the Service, the party that sets it, its purpose, and how long it persists.
| Name | Set by | Purpose | Expiry |
|---|---|---|---|
_ga | Third-party (Google) | Google Analytics 4 client identifier. Distinguishes anonymous visitors so repeat visits aggregate into a single profile in our analytics dashboard. | 2 years |
_ga_<container-id> | Third-party (Google) | Google Analytics 4 session state. Tracks session timing so a page view is not counted twice if you bounce between tabs. | 2 years |
__gads | Third-party (Google) | Google AdSense ad identifier. Used for frequency capping (so you do not see the same ad ten times in a row) and basic ad measurement. | 13 months |
__gpi | Third-party (Google) | Google Publisher identifier. Companion to __gads used for ad measurement and personalised ad selection where consent has been granted. | 13 months |
NID / IDE | Third-party (Google) | Set by Google domains (doubleclick.net, google.com) when AdSense iframes load. Used by Google to remember your preferences and to personalise ads outside the EEA / UK / Switzerland unless you have opted out. | Up to 13 months |
GTM container cookies | Third-party (Google) | Set by Google Tag Manager when the container loads. Coordinate which tags (Analytics, AdSense) should fire and capture basic consent state. | Session to 2 years |
color-mode (localStorage) | First-party | Stores your light / dark theme preference so the site loads in the right colour scheme on your next visit. Not a cookie — it is held in browser local storage and is never sent to any server. | Until cleared by you |
Consent and personalised advertising
For visitors in the European Economic Area, the United Kingdom, and Switzerland, Google's consent management framework shows a consent prompt the first time AdSense loads. If you decline personalised advertising you will still see ads, but they are selected on the basis of the page you are on (contextual targeting) rather than your behavioural profile. Analytics continues to record aggregate, anonymised events because that processing relies on legitimate interest rather than consent.
You can revisit the consent choice at any time through Google's controls at adssettings.google.com. Outside the regions above, ads are personalised by default unless you change those same settings.
How to disable cookies in your browser
Most modern browsers let you block or delete cookies per-site or globally. Blocking all cookies will not break the visual builder (the cron logic runs entirely in your browser) but it will prevent the colour-mode preference from persisting between visits and will reset your consent choice on every reload. Browser-specific instructions:
How Analytics and AdSense interact with consent
Google Analytics on this Service runs with IP anonymisation enabled by default and is treated as processing under legitimate interest. AdSense runs with the consent-mode signal forwarded by Google Tag Manager — when consent has not been granted, AdSense switches to non-personalised mode and the __gads and __gpi cookies are still written but are used only for frequency capping and aggregate measurement.
Changes
When the list of cookies changes — for example if a new tag is added through Google Tag Manager — the table above is updated and the “Last updated” date is bumped. Material changes are summarised in a notice on the home page for at least thirty days.
Contact
Questions about cookies on the Service can be sent to tech@serviceproviderskenya.com.