Privacy

Last updated 2026-10-31.

ImmigrationLayer's tools take form numbers, categories, dates, and countries, not names, A-numbers, or other case identifiers. Our database does not store tool arguments or case data from tool calls. Our API server's logs keep the full URL of each request for 7 days. REST API calls carry their arguments in that URL, for example the form number in /v1/forms/I-765/edition, so these logs keep those arguments for 7 days. Cloudflare's request records, described below, keep REST API paths for 31 days.

For sign-in, we send a link to the email address you provide. Cloudflare delivers that email and keeps the delivery records described below. Our temporary sign-in record holds a keyed hash of that address, not the address itself. Our account database stores a keyed hash of the address, not the address itself. If you create an API key, we store a hash of the key, not the key itself. When you sign in on the web, we set a cookie named il_session that holds a session ID. It expires after 30 days or when you sign out.

If you subscribe without signing in, Stripe sends us the email address you enter at Checkout. We use it once to find or create your account, and our account database stores the same keyed hash, not the address itself.

For MCP usage analytics, we record the tool called, duration, outcome, request and response sizes, and trace identifiers a client sends. Signed-in calls include a pseudonymous account identifier; anonymous calls do not. These analytics do not store tool arguments. We store a Stripe customer ID and subscription status, while Stripe handles checkout and payment card details. Stripe also holds the email address and billing details you give at checkout. Stripe calculates and collects tax on paid plans.

If you email an address at immigrationlayer.com, immigrationcontext.com, or visacontext.com, Zentered Studios' mail service receives the message, stores it, and forwards it to our operations inbox. The stored copy is the full message as received, including its headers, the sender and recipient addresses, subject, message body, and any attachments. Cloudflare's logs for the mail service keep the sender address, the recipient address, and the size of each message the mail service receives for 7 days. If a message passes none of the SPF, DKIM, or DMARC sender checks, the mail service may store it marked as spam and not forward it. Email to security@immigrationcontext.com or security@visacontext.com is forwarded by Cloudflare Email Routing and is not stored by the mail service. The mail service runs on Cloudflare Email Routing, Workers, D1, and R2. It is not part of the ImmigrationLayer tools or API.

If you use the contact form, we email your name, work email address, chosen plan, and message to our sales address at immigrationlayer.com. The mail service described above stores that email and forwards it to our operations inbox. The application does not store or log your submission, and the retention statements on this page do not cover the operations inbox. To limit abuse, we keep a submission counter keyed to a hash of your IP address for up to one hour. The form asks you not to include case details or sensitive personal information.

The contact form uses Cloudflare Turnstile to check that a person is submitting it. Your browser loads a script from challenges.cloudflare.com, and we send the Turnstile result for your submission to Cloudflare to verify it.

Sign-in link records expire after 15 minutes and are deleted when used. Web sessions expire after 30 days or end when you sign out. We have not set an automatic deletion period in our database for account, API-key, usage-analytics, or billing records, or for email stored by the mail service. The product does not currently offer self-service account deletion.

To limit abuse, Cloudflare Rate Limiting counts requests in one-minute windows. Free-tool requests are counted by connecting IP address. Paid-tool requests are counted by account. Sign-in requests are counted by connecting IP address and by the same keyed hash of the recipient address that our account database stores.

Cloudflare hosts the service and handles email routing and delivery. Stripe handles paid checkout and billing. We do not sell product data.

Cloudflare keeps HTTP analytics for immigrationlayer.com, immigrationcontext.com, and visacontext.com for 31 days. Each record holds the request path, your IP address, your country, and your user agent. REST API calls carry their arguments in the path, for example the form number in /v1/forms/I-765/edition, so these records keep those arguments for 31 days. If a Cloudflare security rule acts on a request, Cloudflare also keeps a security event for 31 days with your IP address, the request path and query string, and your user agent. Our website's logs keep entries for 7 days. Each entry holds the request path, your user agent, your country, and details of any error. When a request fails, Cloudflare also groups the error into an issue record. The error details in it are kept for 7 days. The issue record, titled from the error message, stays listed after that, and Cloudflare does not state when it is removed.

Our websites also use Cloudflare Web Analytics, a separate service from the HTTP analytics above. Cloudflare adds its script to every page of immigrationlayer.com, immigrationcontext.com, and visacontext.com, including the sign-in, account, and checkout confirmation pages, and to our preview sites. Your browser loads the script from static.cloudflareinsights.com. It sends Cloudflare the page address, the referrer, and page performance timings. Cloudflare reports the visits to us by page, referrer, country, browser, operating system, and device type. Cloudflare states that the script uses no cookies or other browser storage. Cloudflare receives your IP address with each request. Cloudflare states that it discards the IP address at the nearest Cloudflare data center and does not store it in core databases or logs. Cloudflare's Web Analytics FAQ states that it keeps unsampled data for 7 days, then aggregates it down to about 10% and keeps that reduced data. It does not state an end date for the reduced data.

Cloudflare sends our emails: sign-in links, account notices, contact form messages, and replies to support email. For each email, Cloudflare keeps a delivery record for 31 days with the sender address, the recipient address, the subject, and a message ID. For a sign-in link, an account notice, or a reply to your support email, the recipient address is yours. Cloudflare also keeps a copy of each email as sent, including its text and any sign-in link, for about 7 days. For the contact form, that copy holds your name, work email address, chosen plan, and message. If an email to your address bounces or is marked as spam, Cloudflare may keep your address on a list that stops further emails to it. It keeps the address for 24 hours or 7 days after most bounces, and with no end date if the mailbox does not exist or the email was marked as spam.

When you reach one of our sites or connect to the MCP server through a link that carries campaign tags (utm_source, utm_medium, utm_campaign), we count that visit, connection, or successful tool call against the campaign. We store the three tag values, the site, the page path, and the day. These counts do not include your IP address, user agent, account, tool arguments, or the full URL, and they are never linked to an account.

We also record steps you take with us: a new account, a sign-in, an API key created, a checkout started, a subscription activated, and a contact form sent. Each record holds the step, the site, the page path, the day, and the campaign tags from your cookie, or the campaign tags stored with your account. For a step taken by an account, it also holds the random account ID. It holds no email address, IP address, user agent, API key, message, or the full URL. When you create an account while the campaign cookie is present, we store those three tag values with your account ID once and never change them. Because the account ID ties those values to your account, we treat them as personal data.

If you arrive through a link with campaign tags (utm_source, utm_medium, utm_campaign), we set a first-party cookie named il_attr that holds only those three values for 30 days. We use it only to attribute new accounts, checkouts, and contact form messages to a campaign, and to add those tags to the connection URL we show you. It goes to no ad network and not to Stripe. To remove it, clear your browser's cookies for immigrationlayer.com, immigrationcontext.com, and visacontext.com.

If you create an account while the cookie is set, we store those three values and the time with your account. That record is kept as long as the account and deleted with it. It holds no email address, IP address, or full URL.

If you subscribe through Stripe Checkout while the cookie is set, we keep those three values in a temporary Cloudflare record for up to 24 hours, so we can add them to the account your payment creates. The record is deleted when the payment completes or after 24 hours, whichever comes first. We do not send campaign values to Stripe.

If you arrive through a link with campaign tags (utm_source, utm_medium, utm_campaign), or hold the il_attr cookie, the MCP connection URL we show on our pages carries those three tags and nothing else. When you hold the cookie, the URL carries the tags from the cookie, even if the link you arrived through has other tags. Your MCP client keeps the URL, so its later connections and successful tool calls count against that campaign with no time limit. These counts are not linked to an account.

We do not set or read the il_attr cookie when Cloudflare places your connection in Austria, Belgium, Bulgaria, Croatia, Cyprus, Czechia, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Iceland, Liechtenstein, Norway, the United Kingdom, or Switzerland, or cannot place it. There we still count the visit, but we collect no campaign tags from a cookie, and we clear an il_attr cookie your browser already holds. Campaign tags collected earlier, where we do set the cookie, can still be stored with your account and used in the account steps above.

See Not legal advice andTerms for how the immigration data itself is scoped and licensed. We'll update this page if what we collect changes.