TNPath — Your TN application, step by step

Privacy Policy

Effective October 31, 2026

The short version: your answers stay in your browser while you build. After purchase, when you generate your packet, the finished files pass through our server to our email provider so we can email them to you. TNPath discards them after sending; our providers have their own retention policies described below. We don’t keep copies of your packet. We count anonymous events, such as how many people reach the preview, but never your answers. If you use the optional free proofread, or choose AI proofreading when you generate your packet after paying, the text being checked is sent to Anthropic’s Claude AI. We don’t store it.

Buyers in Mexico. The same applies if you are a Mexican citizen buying TNPath for the consular route: the builder, your documents and our support are in English. A Spanish notice summarizing this policy is available in our aviso de privacidad.

Your packet answers

The builder runs in your web browser. Your answers (such as your name, credentials, employer, job details and pay), and any company logo image you add to the letter, are saved in your browser’s local storage so you can come back later. Nothing you enter is sent to TNPath while you build, unless you choose the free proofread (see “AI proofreading and review” below). Your documents are generated on your device. You can erase your saved answers, saved AI review and proofreading corrections with “Erase my answers” in the builder. This keeps the saved purchase reference so we can still confirm access. Clearing the browser’s site data also removes that reference. Neither action deletes emails or downloaded files; delete those separately if you wish.

Emailing your files

After your payment is confirmed and you choose “Generate my packet”, your browser sends your two finished files (your employer letter and packet guide, which contain the answers you entered) to our server, together with your Stripe checkout session ID. Our server asks Stripe for the email address you used at checkout and sends the files to that address through our email delivery provider, Resend. If Stripe has no email address for your purchase, the builder asks you to type one, and the files go to that address instead. The files are held in memory only long enough to send the email, then discarded. TNPath doesn’t store your files or your answers.

Resend processes the message to deliver it and keeps records of sent emails, which may include the message and its attachments, for a limited period under its own policy (currently up to 30 days on our plan). The copy in your inbox is yours to keep or delete.

To prevent misuse, our server counts how many times files have been emailed for each purchase (up to three). The count is stored under a scrambled code and contains no files, answers or email addresses.

If you lose your files

If you’ve lost both the email and your browser data, email us. We’ll confirm your purchase in Stripe using your email address and send you a one-time link. So that each link works only once, our server stores your email address with the link’s status. Unused links expire after 14 days, and that link record deletes itself about 30 days after the link expires. The 14 days here is about the unused link itself; it is separate from the 14-day window in §5 of the Terms for emailing about a technical problem. Once you use a link, our server keeps an access record with your email address so your restored access keeps working; it deletes itself 400 days after it was created or last used. None of these records contain your packet or your answers. When you use the link, you rebuild your packet in your browser as before.

AI proofreading and review

You can generate with or without AI proofreading. If you choose proofreading, your letter text is sent to Anthropic for that check, and you can review and undo applied corrections. Generating without proofreading sends no text to the AI service.

Availability and usage limits are shown in the builder. The descriptions below explain what is sent when a feature runs; they do not depend on an availability check. Your packet can still be generated if an AI check is unavailable.

TNPath uses AI for automated writing feedback on your letter: proofreading, consistency, duty wording, clarity for a reader and tone. It is not legal advice and not an eligibility assessment. Three features send text for checking:

Our server sends the text to Anthropic’s Claude API to generate the review and returns the results to your browser. TNPath doesn’t store the text or the results: they’re held in memory only while the review runs. Anthropic processes requests under its commercial terms. Its standard API policy deletes inputs and outputs within 30 days, with exceptions such as legal obligations or usage-policy enforcement and model-specific requirements. See Anthropic’s data-retention policy for the current details.

Your latest review, the local before-and-after record for fixes you apply or undo, and your place when editing from a review are saved in your browser. Applying or undoing a suggested fix stays local and sends no new AI request. You can download it, or ask us to email it to you in the same way as your files. To prevent misuse, we count reviews per purchase (kept for 180 days) and free proofreads per connection per day, stored under scrambled codes without any content.

Payments

Payments are processed by Stripe on Stripe’s own checkout page. Stripe collects the information needed to process your payment, such as your email address and card details. TNPath never receives your full card details. Stripe shares order information with us (for example, your email address, the amount and the date) so we can email your files, provide receipts and give support. Stripe’s handling of your information is described in the Stripe Privacy Policy.

When you return from checkout, your browser sends the Stripe checkout session ID to our server so we can confirm the payment with Stripe. Your browser then remembers that session ID (or, if we sent you a one-time link, your unlock code) in local storage. Each time you open the builder, it sends that ID to our server so we can confirm the purchase with Stripe, or with our unlock records, before downloads unlock. These checks don’t include your packet answers.

When your browser sends you to Stripe’s checkout page, it adds a client reference that begins “tnp_” to the checkout link. The reference is generated at random in your browser, contains no personal data and none of your answers, and our server never reads it.

Hosting, fonts and security

The site is hosted by Cloudflare, which processes technical information such as IP addresses and browser details to deliver the site and protect it from abuse. Fonts and all other site files are served from our own domain. The only third-party script the site may load is Cloudflare’s Web Analytics script, described below. We don’t load advertising or cross-site trackers. Our server also writes short-lived operational logs (for example, that an AI check ran, how long it took and whether it failed), which Cloudflare keeps for a limited time. These logs don’t contain your answers, your letter or your files.

Anonymous usage counts

To understand how the site is used and to catch problems, the site counts a small set of anonymous events: page views (including which guide was viewed); the profession category chosen in the builder (for example, “accountant”); the builder step reached; reaching the preview; clicks toward checkout; a return from checkout, and whether the payment was confirmed; use of a free tool such as the letter checker, and viewing a free tool’s result (the letter checker, the document checklist generator and the cost and renewal calculators — never the text you paste or the answers you enter); use of a one-time unlock link; a later visit on which the purchase saved in the same browser is confirmed again; generating your packet; copying the employer email or the HR page link offered in your post-purchase next steps; Word and PDF downloads; emailed file backups; policy-alert signups; and major errors, such as a payment check that couldn’t be completed. We also count opening the sample packet, and a preview that stays open for a minute or more without going to checkout.

Each event contains only its name and a fixed page label. For builder events, that fixed label now also distinguishes the route — Canada or Mexico — so anonymous builder counts can separate the two routes without recording any answers or personal data. The anonymous counts also include the type of page a visit started on (for example, the home page, a profession guide, a Spanish page or a free tool), recorded only as that fixed type, together with the route, when the builder is started. It never includes your answers, name, employer, salary, credentials, duties, email address or document text. We don’t attach a cookie, identifier or IP address to these counts. They’re stored as daily totals in a Cloudflare D1 database we control — aggregate numbers only, with no visitor or customer rows — and totals older than 90 days are deleted. There is no public report page; the totals are visible only inside our own Cloudflare account. When a session starts, we also record once — as the same kind of anonymous daily count — the site that sent you here, reduced to a fixed category (for example a search engine, an AI assistant, a social network, another site, or “direct” when your browser reports no referring site) and never the referring address itself, plus any utm_source or utm_campaign tag on the link, reduced to lowercase letters, digits, hyphens and underscores and at most 30 characters. When the builder is opened, we also record whether the screen is phone-sized or larger (a single mobile/desktop category based on the window width), as part of the same anonymous count.

If you arrived through a link carrying a referrer code (an address ending in ?ref= followed by a short code, for example from a recruiter), the browser keeps that code for this browser session only — in session storage, never in a cookie and never in permanent storage — and three of the counts above (landing on the site, starting the builder, and completing a purchase) are recorded with the code itself as their page label, so we can tell which referrers send visitors who use the tool. A code that isn’t lowercase letters, digits or hyphens, or is longer than 32 characters, is ignored. Nothing else about the link is stored.

If your browser sends a Global Privacy Control or Do Not Track signal, the site doesn’t send these events at all, and our server rejects them too. You can also turn off usage counts in this browser:


We may also use Cloudflare Web Analytics to measure page views and page speed. Cloudflare states that it “does not use any client-side state, such as cookies or localStorage, to collect usage metrics” and doesn’t fingerprint visitors. When it’s on, your browser loads a small script from static.cloudflareinsights.com that reports page-level information such as the page address, referring page, browser type and load times. See Cloudflare Web Analytics.

Optional post-purchase feedback

After a purchase, the download screen offers an optional feedback block: whether you were admitted (Yes, No or Not yet), anything we should improve (free text, up to 1,000 characters), and a checkbox that lets TNPath quote the feedback anonymously. It is never required, and your downloads never depend on it.

If you send feedback, we store exactly those answers — the admitted answer, the free text if you wrote any, whether the quote consent box was ticked, and the date submitted — in the same Cloudflare KV storage as policy-alert signups. No name, email address, packet answers or purchase details are stored with feedback, and the free text is quoted publicly only if you ticked the consent box. The quote consent is optional and unticked by default, and a quoted comment never carries your name, your employer or any detail that identifies you. No automatic deletion period is set for feedback entries; they stay until we clear them from storage.

Cookies and tracking

TNPath doesn’t use advertising cookies or cross-site trackers, and the anonymous counts above use no cookies. Cloudflare may set strictly necessary security cookies. We use your browser’s local storage only to save your builder progress, which purchase to confirm (your Stripe checkout session ID or unlock code), whether your files were emailed, the random checkout reference described above (saved as tnpath.v1.ref) and the time you started checkout (tnpath.v1.checkoutAt), the I-94 “Admit Until Date” you save for renewal reminders (tnpath.v1.i94date), your latest AI review and the list of AI proofreading corrections. The saved purchase details don’t unlock anything by themselves: our server confirms them each time.

Email

We use the email address from your purchase only to send your files, to send renewal reminders if you opt into them (see below), and to respond when you contact us. Apart from TN policy change alerts and renewal reminders you sign up for, we don’t send marketing emails.

TN policy change alerts. If you sign up, we store only your email address and the date you signed up, with our hosting provider, Cloudflare, and use them only to email you when TN fees, forms or policy guidance change. To unsubscribe, use the unsubscribe page or email [email protected] and we’ll delete your address. We keep your signup until you unsubscribe or we stop sending alerts. To prevent abuse, we also count signups per connection per day under a scrambled code that expires after two days.

TN renewal reminders. After a purchase, the download screen offers an optional renewal reminder, separate from policy change alerts. If you tick the box, we store your checkout email address, the end date you requested in your packet, the two reminder dates (about six and three months before that end date), the time you consented and whether your packet was for the Canada or Mexico route, with our hosting provider, Cloudflare. We use them only to email those two reminders. The record is deleted after the last reminder date has passed, or sooner if you unsubscribe: on the unsubscribe page you choose what to cancel — policy change alerts, renewal reminders, or both — and we delete only the records you choose for your address; emailing [email protected] works too. To prevent abuse, we also count reminder signups per connection per day under a scrambled code that expires after two days.

Your choices

You can erase your builder answers at any time. To ask about information connected to a purchase, email [email protected].

Changes

If we change this policy, we’ll post the new version here with a new effective date.

Contact

[email protected]