Cookie Policy

Adapted from the Basecamp open-source policies, used under CC BY 4.0.

This policy explains how Ziptask uses cookies and similar browser storage technologies.

What are cookies?

Cookies are small text files stored on your device when you visit a website. They allow the site to remember information about your visit. We also use browser local storage, which works similarly but stores data locally rather than sending it with every request.

What we use

Authentication tokens

When you log in, Ziptask stores a secure authentication token in your browser's local storage. This token is used to keep you signed in between sessions. It is never shared with any third party and is deleted when you log out or when it expires.

Sign-up attribution

When you arrive from a campaign link or another website, we store the link's campaign tags (UTM parameters), the page you landed on, and the referring site in your browser's local storage so we can attach them to a sign-up inquiry if you start one. We keep both the first campaign that brought you to us and the most recent one, because people often find us one way and sign up later another way. This is first-party context we measure ourselves — it is not an advertising cookie, is not shared with any advertising network, and is never used for profiling or retargeting. It is kept for 90 days from your last visit and then deleted automatically; you can remove it at any time by clearing your browser's site data. Because it involves no advertising identifiers, it is recorded whether or not you accept cookies.

Google Analytics

We use Google Analytics (GA4) to understand how visitors use our marketing site — which pages are visited, how long people stay, and where they come from. GA is only loaded after you accept cookies. If you decline, no GA cookies are placed and no analytics data is collected. See Google's privacy policy for details on what GA collects.

Google Ads conversion tracking

When we run advertising campaigns, we use Google Ads conversion tracking to measure which ads lead people to sign up for Ziptask. This sets a Google cookie (_gcl_au) and records an advertising click identifier (gclid, or its iOS/privacy-context equivalents gbraid/wbraid) so a sign-up or subscription can be attributed back to the ad that drove it. These are only used after you accept cookies. If you decline, no advertising cookies are set and no conversion data is collected. See Google's advertising policy for details.

Error tracking (Sentry)

We use Sentry for error tracking. Sentry may store a small session identifier in your browser to help associate related errors. This data is used solely to diagnose and fix technical issues — it is not used for advertising or profiling. See Sentry's privacy policy for details.

What we don't use

• Social media pixels — we do not use tracking pixels from any social media platform (e.g. Meta/Facebook)
• Cross-site behavioral profiling — we do not build advertising profiles or retarget you across unrelated sites; our advertising cookies are used only to measure conversions from our own campaigns
• Selling your data — we do not sell your personal information

Summary

Storage	Purpose	Set by	Requires consent	Expires
Local storage — auth token	Keeps you signed in	Ziptask	No (strictly necessary)	On logout or token expiry
Cookie — Sentry session	Error grouping	Sentry	No (functional)	Session or short-lived
Local storage — sign-up attribution	Which channel brought you to us, first and most recent (UTM tags, landing page, referrer)	Ziptask	No (first-party, no advertising ids)	90 days from your last visit
Cookie — Google Analytics (_ga, _ga_*)	Site analytics	Google	Yes — only set after acceptance	Up to 2 years
Cookie — Google Ads (_gcl_au)	Advertising conversion measurement	Google	Yes — only set after acceptance	Up to 90 days

Your choices

You can configure your browser to block or delete cookies and clear local storage at any time. Be aware that blocking authentication storage will prevent you from staying signed in to Ziptask.

Changes to this policy

We may update this policy as our use of cookies or storage technologies changes. We will post updates here and revise the "last updated" date at the top of the page.

Contact

Questions? Email us at [email protected].