Effective date: September 2, 2026 • Updated: September 12, 2026 • MinuteKeep, 2 Simcoe Street South, Oshawa, Ontario, L1H 8C1
This Cookies & Tracking Policy explains the cookies, browser storage, and tracking technologies MinuteKeep (the "Service") uses, what each one does, and how to control it. It forms part of, and is incorporated into, our Privacy Policy and Terms of Service.
Required for the Service to work. These cannot be turned off within the Service; blocking them will sign you out and break functionality.
| Name / type | Purpose | Storage |
|---|---|---|
| Authentication token | Keeps you signed in so you do not have to re-authenticate on every page | Browser local storage and/or an HTTP-only session cookie |
| Session identifier | An anonymous identifier that ties a browsing session together, including before you create an account | Browser session storage |
| Security and abuse prevention | Rate limiting, request integrity, and protection against automated abuse | Server-side, keyed to request metadata |
| Preferences | Remembers interface settings and dismissed notices | Browser local storage |
| Technology | Provider | What it does |
|---|---|---|
| First-party product analytics | MinuteKeep (our own database) | Records events such as page views, wizard steps, document generation, checkout starts, and payments, with limited properties, to measure how the Service is used and where people get stuck |
mk_vid experiment cookie | MinuteKeep (first-party) | A random visitor identifier keeps your landing-page test version consistent across visits. It expires 90 days after your last eligible visit during an active test. The cookie is HttpOnly, so page scripts cannot read it, and Secure, so browsers send it only over HTTPS. |
| Landing-page experiment measurement | MinuteKeep (our own database) | Links the test version you see to browsing-session identifiers and, after authentication, your internal account identifier. We use that link to measure signup, checkout and a verified paid Pro subscription within seven days of your first recorded exposure. |
| Google Analytics 4 | Google LLC (United States) | Website and application usage measurement, traffic sources, and conversion measurement |
| Clarity (session replay and heatmaps) | Microsoft Corporation (United States) | Records a reconstruction of your session — pointer movement, clicks, scrolling, navigation, rage- and dead-clicks, and page structure — and aggregates it into heatmaps |
Experiment version metadata contains the experiment and version identifiers, not your name, email address, company details or document contents. The separate account link allows us to associate a paid Pro outcome with a version; it is not anonymous once linked to your account.
About session replay. Clarity's default configuration masks text typed into form fields, so it is not intended to capture the contents of the fields you fill in. We do not warrant that every field is masked in every circumstance, and you should assume that anything visible on your screen may be captured. If you are not comfortable with that, block it using the methods in Section 3.
| Technology | Provider | What it does |
|---|---|---|
| Meta (Facebook) Pixel | Meta Platforms, Inc. (United States) | Measures the effectiveness of our advertising, attributes signups and purchases to campaigns, and enables audience building and retargeting |
| Google Ads conversion tracking | Google LLC (United States) | When you arrive from a Google ad, the Google click identifier (gclid, gbraid, or wbraid) is stored and your signup or purchase is reported to Google Ads as a conversion, including by server-side upload; no name or email address is included |
| Refgrow affiliate tracking | Refgrow | Loads a tracking script and reads a first-party mk_ref cookie to attribute a signup or purchase to the affiliate who referred you |
mk_ref referral cookie | MinuteKeep (first-party) | Stores a referral code from a ?via= link so an affiliate can be credited; set only when you arrive via such a link |
Stripe sets cookies on its checkout and billing pages for payment processing and fraud prevention. Google and Microsoft may set cookies when you use single sign-on. Embedded content, such as video, may set its own cookies. These are governed by those providers' policies, not this one.
clarity.ms in your browser, an extension, or your network, or use a tracker-blocking browser. See Microsoft's privacy statement.mk_ref cookie, or arrive without a ?via= link.mk_vid cookie through your browser controls. This may change the version you see or prevent us from linking visits and purchases. It does not prevent you from using the core Service. Deleting the cookie does not delete records already held on our servers; account and deletion choices are described in the Privacy Policy.All of the analytics, session replay, advertising, and affiliate providers above are located outside Canada, predominantly in the United States, and information collected by them is processed there and potentially elsewhere. See Privacy Policy, Section 8. We do not guarantee Canadian data residency for any of it.
There is no accepted standard for responding to browser "Do Not Track" signals and we do not currently alter our practices in response to them. Where a browser transmits a recognized opt-out preference signal, we will honour it to the extent applicable law requires and our tools support. The controls in Section 3 are effective regardless.
Retention periods for analytics events, session replay recordings, and related data are set out in Privacy Policy, Section 9. Cookie lifetimes are set by the issuing party and may change without notice.
The mk_vid cookie expires 90 days after your last eligible visit during an active test. Returning during a test renews it without changing your assigned version. Experiment exposure records and their session and account links are product analytics subject to the existing retention period of up to 24 months in Privacy Policy, Section 9. The cookie lifetime and the server-side retention period are separate.
We may add, remove, or change the technologies we use at any time. This page is updated to reflect current practice; routine updates take effect on posting. Material changes are notified in accordance with Terms, Section 22.1.
Questions: support@minutekeep.ca.