What the forms collect
This site has six. The signup in the footer of every page collects one thing: your email address. The filing request at Start a Filing collects your business name, the entity type you picked, the state you are filing in, the services you ticked, your name, your email address, your phone number if you give one, and anything you write in the notes box.
Four more ask for your email address and nothing else about you. The compliance calendar on Compliance Calendar and on each state page will email you the schedule instead of downloading it, and sends the state you were looking at along with the dates it just showed you. The multi-state builder on Multi-State sends the list of states you assembled so the team can quote it. The quote form on each change of registered agent page sends that state, the rough number of entities and the number of states you picked. None of the four asks for a name or a phone number. The quick request on each state page sends that state, what you need (for example appointing or changing an agent), the rough number of entities and your email address.
Email is the one field the site itself refuses to send without — an enquiry we cannot answer is no use to either of us. The filing form asks for more before it will let you move on: the business name and entity type, the state, and at least one service. Anything beyond that is optional, and each text field is trimmed and capped in length before it is passed on.
Where it goes
To the LLCity mailbox, [email protected], unless the site is configured to route enquiries to another LLCity address. The site turns your submission into an email and hands that email to Resend, the delivery service we use to send it. Your address is set as the reply-to, so the filing team answers you directly rather than through the site.
Before that email is sent, your submission is written down. It becomes a row in a private database LLCity controls, and only then does it become an email. That order is deliberate: delivery can bounce, time out or be held by a spam filter, and when it does the row is still there, so a request nobody received is not a request nobody can answer. Stored with it is the page you sent it from, as your browser reports it, and the first-visit note described under “Analytics and cookies” below: how you first reached the site and the first page you saw.
That table is not public and it is not a portal: there is no login here for you, and no page on this site reads from it. The LLCity team reaches it through a separate, password-protected desk. Nothing in the site sends your submission anywhere else — there is no advertising network, no data broker and no lead exchange in the path.
If neither step works — no row written and no email sent — the form falls back to opening a pre-filled draft in your own mail app instead. It opens only in that case: if the row was written, your request has reached us whether or not the email went out, and you are told so rather than asked to send it again. When the draft does open, the site has kept nothing and transmitted nothing: the message is in your drafts, you can read it, edit it or throw it away, and it reaches us only when you press send.
Analytics and cookies
The site sets no cookies of its own and asks for no login. It runs Google Analytics 4, loaded from googletagmanager.com, which sets Google’s own analytics cookies and processes the data on Google’s terms. Google signals and ad personalization are switched off, and the consent defaults deny advertising storage, so none of it feeds advertising.
What it records: the pages you view and how you arrived; which of our links and buttons you click (by our page address, or the domain of an outside site); how far you scroll and roughly how long a page stays open, in ranges; which questions you open; how you use the tools — the state you pick, the steps of the filing form you reach, the entity type and how many services you tick; that a form was started, sent or failed; page speed; and the type of any script error.
What it never receives: your business name, your name, your email address, your phone number, your notes, or anything else you type. Addresses are trimmed before they are sent — any parameter other than campaign tags and a state name is removed, which is how a business name carried from the homepage into the filing form stays out of it.
Your browser keeps one small note for 30 days: whether you first arrived from an AI assistant (such as ChatGPT or Perplexity), the domain of the site that sent you, any campaign tags, the first page you saw and the date. It is read by the analytics above and sent with an enquiry if you make one. A second flag, cleared when you close the tab, stops a visit from an AI assistant being counted twice. Clearing this site’s data in your browser removes both.
When you click our phone number or email address, the site also writes a short line to the same private database: that it was the phone or the email link, which of our numbers or addresses it was, the time, the page and the spot on the page you clicked from, and the first-visit note above. It records nothing about you and cannot tell whether a call was made — it only lets the team see when people reach for the phone.
The typefaces are served from this site rather than from a font service, so simply loading a page here contacts nobody else.
What the site never asks for
No payment details — this site takes no payment. No Social Security number, no EIN, no government-issued ID, no uploaded documents. Where a filing genuinely needs information of that kind, it is collected by the filing team once you are working with us, not by a public web form.
Hosting
The site is served from Vercel. Like any host, Vercel handles the request data needed to deliver a page — the IP address it came from, the browser user agent, the URL requested — as part of serving it.
Asking us about your information
Write to [email protected] from the address you used, or call 212-202-5750, and ask what we hold or ask us to delete the message you sent. Since the record is an email, deleting it is exactly that.
Changes to this page
If what the site collects changes, this page changes with it — it describes the current behaviour of the code that runs here, and it is meant to keep doing so.