About this publication

PRIVACY POLICY

Your visit.
No fine-print mystery.

What the site does today, what is only planned, and how your information is handled.

Last updated taskertax.com
/01

Who is responsible, and what this covers

Tasker Tax at taskertax.com is operated by Tyler Heinrichs in British Columbia, Canada. In this policy, “Tasker Tax,” “we,” and “our” refer to that publication and its operator. This document addresses visits to the site, not how an employer, task platform, tax preparer, or government agency handles your information.

The publication’s subject is US taxes, but the operator is in Canada. BC privacy law and, depending on the activity, Canadian federal or other applicable privacy laws may apply. This document is not a claim that every privacy law applies, or that the site has been certified compliant.

Privacy requests

The operator is responsible for privacy questions. A dedicated request channel is being added and will be published here; a separate contact page is not required, but a working way to reach the operator is. Until it is published, do not send sensitive information. This does not remove any legal rights you have.

/02

The current setup, at a glance

ACTIVE IN THE APPLICATIONA reading preference

Light, dark, or system mode, stored locally in your browser.

NOT INSTALLEDVisitor analytics

Fathom is planned soon. Google Analytics is planned for later. Neither is in the current application.

The current site has no accounts, comments, contact forms, file uploads, tax calculators, payments, newsletter sign-ups, advertising pixels, or session-replay tools. It does not ask you to enter income, deductions, identification numbers, or tax documents. There is no application database of reader tax profiles.

Vercel is the selected production host. Hosting infrastructure can process personal information even when the application itself has no collection form.

At present, the application does not sell personal information, share it for cross-context behavioral advertising, or use it to train AI models. These statements describe the current implementation; they are not permission to add undisclosed processing later.

/03

Information that may be involved—and why

InformationPurpose & current boundary
Technical request dataDelivering pages, preventing abuse, and troubleshooting hosting may involve an IP address, request time, URL, referrer, browser/device details, and approximate location derived from an IP address. The exact production records and retention depend on the host’s configuration.
Theme preferenceThe browser’s localStorage entry tasker-tax-theme contains “light,” “dark,” or “system.” The application reads it to display the chosen theme, not to identify you or track visits across sites. The theme code does not send that preference to an analytics provider.
Future correspondenceNo public inbox or submission form is currently offered. When a channel is added, information you choose to send—such as a reply address and the question—would be used to handle the request. The notice must be updated for the actual channel and its provider.
Future analyticsReadership measurement is planned, but is not active in the application. The next section describes the selected tools without treating them as installed.

A URL can reveal that someone visited a page about a tax topic. Do not put names, Social Security numbers, platform credentials, financial details, or other sensitive information in URLs or query parameters when linking to the site. Analytics and logs should not receive that information.

/04

Fathom and Google Analytics are planned—not active

Fathom Analytics — Not installed

Fathom is intended to help understand which pages are useful and where visits come from. According to its current documentation, its ordinary analytics does not set analytics cookies, but its collection service still receives request information, including IP address and user-agent details. It uses those details to create site-specific visitor signatures with a salt that rotates daily.

Page information can include the site, path, referrer, and relevant query parameters; reports can include device and approximate country information. Fathom also describes separate security and abuse-prevention processing. Daily signature rotation does not delete previously stored analytics records, and hashing alone is not a guarantee that information is legally anonymous.

Before installation, the operator needs to confirm the configuration, data-processing terms, retention, processing locations, and any required consent or other legal basis. Cookie-free is not a blanket exemption from privacy or device-access rules. See Fathom’s data journey and its cookies and consent explanation.

Google Analytics — Not installed

Google Analytics is a possible later addition, not a current collection tool. A standard web implementation can use first-party cookies and process browsing events, page/referrer details, device information, identifiers, and approximate location information. Google says Analytics does not log or store individual IP addresses, but an incoming request still involves IP processing.

No Google Analytics property, advertising integrations, Google signals, consent configuration, or retention period has been confirmed for this site. If introduced, the operator must first disclose the actual setup and implement appropriate choices and consent where required. This policy, the Terms, and simply continuing to browse do not constitute consent to future analytics. See Google’s data safeguards and choices.

/05

Service providers, disclosures, and international processing

When deployed on Vercel, hosting and security services process request information to operate the site. Fathom and Google are planned analytics providers only; this policy does not describe them as currently receiving this site’s analytics events. Vercel hosting does not, by itself, mean Vercel Web Analytics is enabled.

Information necessary to operate the site may be processed by service providers and their subprocessors. It may also need to be disclosed where legally required, to respond to valid legal process, or as reasonably necessary to investigate abuse or protect legal rights and security. This is not permission for unrelated marketing or unrestricted disclosure.

The operator is in Canada, and selected providers may process information in the United States or other countries. Information processed abroad may be subject to foreign laws and lawful access by authorities. No promise is made that all data stays in Canada or that an EU-isolation setting has been enabled. Relevant provider terms, safeguards, and actual processing locations must be reviewed before launch or adding a service.

Provider reference: Vercel’s data processing addendum. A provider’s own obligations and account privacy notice do not replace Tasker Tax’s responsibility for information under its control.

/06

Browser storage and retention

The application sets no analytics or advertising cookies. Its own persistent browser storage is the theme preference described above. Your browser normally retains that entry until you clear the site’s storage, the browser removes it, or you change browser profiles. Choosing “System” stores that choice; it does not delete the entry. Clearing storage resets the site to your device’s preference.

Hosting or security services may use technical mechanisms separate from the application. Their actual production behavior must be checked; this notice does not promise that no infrastructure component could ever use a cookie.

No fixed production-log retention period has been verified. Before this policy is finalized, the operator must identify what records are available, set or document appropriate retention, and confirm provider deletion and backup limits. It would be misleading to promise a specific number of days now.

Future correspondence should be retained only as needed to handle the request and meet applicable recordkeeping or legal obligations. Any future analytics retention must be documented separately. A shorter-lived visitor identifier does not necessarily mean the underlying records have been deleted.

/07

Your choices, requests, and complaints

  • You can choose a theme or clear this site’s browser storage without losing access to the articles.
  • You can limit third-party requests through browser settings or content blockers. No third-party analytics script is currently installed in the application.
  • The current site performs no cross-site advertising tracking, and does not change its behavior in response to a Do Not Track setting. There is currently no sale or cross-context advertising sharing for a Global Privacy Control signal to opt out of. Future integrations need their own signal-handling review.

Depending on the law and circumstances, you may have rights to learn about information held about you, access it, request correction or deletion, withdraw consent, or complain. Rights, exceptions, response periods, and verification requirements vary. This document does not claim universal CCPA, GDPR, or other-law coverage, and does not restrict rights that do apply.

A dedicated request channel is being added. When it is published, the operator will request only information reasonably needed to verify and respond to a request—not your tax return or government identification by default.

For BC privacy questions and complaints, see the Office of the Information and Privacy Commissioner for BC. Its guidance generally asks individuals to first raise a concern with the organization. The missing contact method must therefore be resolved; a regulator link is not a substitute for one.

/08

Sensitive tax information and children

Do not send Social Security numbers, SINs, ITINs, W-9s, 1099s, tax returns, bank details, login credentials, or client/platform-confidential materials to Tasker Tax. The site is not a secure client portal and does not provide tax-preparation or identity-verification services. Reading a page does not create professional confidentiality or privilege.

This publication is written for a general adult working audience, not directed to children under 13. It does not offer child accounts or knowingly seek tax or contact information from children. If the operator learns that children’s information has been received, the situation must be addressed under applicable law. There is no age-verification system currently installed.

/09

Security and websites you visit from here

The current application minimizes collection: it has no reader accounts, payment processing, or document-upload features. That reduces exposure but does not make the internet or a hosting provider risk-free. No website can guarantee that transmission, storage, or access will always be secure.

Links to IRS.gov and other resources take you to independent websites. Those sites have their own privacy practices. An ordinary link does not itself embed their tracking tools here, but opening it sends a request to the destination, which may receive your IP address and referrer information according to your browser and the site’s referrer policy.

/10

Changes and the details still needed for launch

The date above records this version. A dedicated privacy-contact method will be added before the first article goes live, and this notice will be updated if production hosting or analytics settings differ from what is described — including which analytics tools—if any—are actually enabled.

If practices change, the notice should be updated before the new processing begins, with an effective date and appropriate notice of material changes. Consent will be requested separately where required. A policy edit cannot retroactively authorize an incompatible use of information or remove mandatory rights.