Cookie Policy
This Cookie Policy explains the necessary and optional cookies used across taskmachine.io and its application subdomain. It should be read with the Privacy Policy.
Last updated: 7 August 2026
Who is responsible
Task Machine is operated by Fabian Schucht, C. General Vives 1 6E, 35006 Las Palmas de Gran Canaria, Spain, NIE: Z1096165J. For cookie or privacy questions, email support@taskmachine.io .
How cookies are used
Necessary cookies keep sessions, forms, account-specific browser features, saved generated-playbook references, and your analytics choice working. These cookies do not require analytics consent because they provide a service you request, protect the service, or remember the privacy choice itself. Blocking them can prevent sign-in, forms, or saved preferences from working.
Optional DataFast analytics cookies measure how public visitors find Task Machine, continue a consented journey across our current and legacy public domains, and connect that journey with a later checkout. Task Machine does not create these identifiers or initialize DataFast until you accept analytics. We do not use advertising cookies.
Cookies and retention
| Cookie | Category and purpose | Retention |
|---|---|---|
| _task_machine_key | Necessary. Signed session data keeps you authenticated, carries requested navigation state, and supports cross-site request forgery protection. | 1 year, or until sign-out |
| tm_browser_device | Necessary app preference. Assigns a random identifier to a signed-in browser profile for browser-specific notification setup and status. It is not created on ordinary public website pages. | 1 year |
| tm_generated_playbook | Necessary saved reference. Lets a visitor return from the playbook gallery to a generated playbook proposal they previously opened. | 1 year |
| tm_analytics_consent | Necessary consent record. Remembers whether you accepted or rejected optional DataFast analytics so the website honors your choice. | 1 year |
| datafast_visitor_id | Optional analytics. Recognizes a consented returning browser for acquisition and conversion attribution. | 1 year |
| datafast_visitor_first_seen_at | Optional analytics. Records when the consented browser was first observed. | 1 year |
| datafast_visitor_session_count | Optional analytics. Counts sessions for journey and attribution analysis. | 1 year |
| datafast_session_id | Optional analytics. Groups consented public website activity into a session. | 30 minutes |
| datafast_session_start | Optional analytics. Records the start time used to expire the current session. | 30 minutes |
The DataFast SDK may mirror its consented identifiers in local or session browser storage to preserve its analytics state. Rejecting or withdrawing analytics removes the known DataFast cookie and browser-storage keys and prevents Task Machine from forwarding those identifiers to checkout.
Analytics
DataFast runs on the public website only after you select Accept. It can process page paths, referrers, campaign parameters, IP address, user agent, visitor and session identifiers, and checkout attribution. Links between taskmachine.io and iterationlayer.com may carry DataFast journey parameters after consent, and the receiving page removes them after use.
Product activity in the signed-in app is measured server-side through PostHog Cloud (EU) without analytics cookies, a browser SDK, or session replay. PostHog events use identifiers and bounded operational metadata rather than prompts or content.
Your analytics choice
The first public website visit presents equally available Reject and Accept choices. Rejecting does not limit public website access. Use Cookie settings in the footer at any time to review or change your choice. Withdrawing consent stops future DataFast browser tracking and removes known DataFast identifiers from the browser.
You can also delete or block cookies in your browser. Browser controls can remove necessary cookies too, which may sign you out, reset saved proposal references, or prevent parts of the service from working.
Changes and contact
We may update this Cookie Policy when browser storage or providers change. Material changes update the date above and may require a new choice. Personal data is handled under the Privacy Policy.