Skip to content
Remove Registered Agent

Privacy policy

Last updated:

1. Introduction and Consent

This Privacy Policy ("Policy") explains what information Sandeep Arneja LLC, a New York limited liability company that operates the Remove Registered Agent service and the website at removeregisteredagent.com ("we," "us," or "our"), collects, and how it uses, shares and protects that information. The Policy covers that website (the "Site"), its record check, the request form, the contact form, our phone, and the service we provide by email, phone and text after you send a request.

Remove Registered Agent is an administrative document filing service for New York LLCs. At your request, we prepare a Certificate of Change for your LLC, you sign it, and we file it with the New York Department of State. We are not a law firm, and we do not provide legal, tax, or financial advice. Remove Registered Agent is not affiliated with the New York Department of State or any other government agency, and it is not a registered agent.

When you visit the Site, use the record check, send us information, or use our service, you agree that we may collect, use and share information as this Policy describes. If you send a request, this Policy is also part of our Terms of Service. Our request form has a box you must tick before you can send it. By ticking it, you agree to our Terms of Service, this Policy and our Refund Policy. You then accept our Terms of Service for your request when you reply in writing to our confirmation email to confirm your request and state that you accept them. The version of this Policy in effect on the day you reply applies to your request.

IF YOU DO NOT AGREE WITH THIS POLICY, PLEASE DO NOT USE THE SITE OR OUR SERVICE, AND DO NOT SEND US INFORMATION.

2. Information We Collect

What you type into the record check

  • The LLC name or the New York Department of State ID number ("DOS ID") you search for.

Your browser sends it to our server, and our server sends it to the Department of State's public search. Our database and logs never store your search text (our logs record only its length). If you send the request form, the name or number you typed goes with your request. If you start on the home page, the text you typed is handed to the check page inside your own browser tab (see section 8), never through the page address. If our server cannot reach the State's record, an error line may include the DOS ID number it was looking up (a public record number, never a name). Each time you open an LLC's record, our server also writes one row in our record-check log, with no name or contact details (section 9).

The "Get started" request form

When you send the form, we receive:

  • your name;
  • your email address;
  • your phone number;
  • how you heard about us: one choice from a list, and, if you choose "Somewhere else," up to 120 characters in your own words;
  • the LLC you chose: its DOS ID, its name on the State's record when our server could read it as you sent the form, and the name or number you typed into the search, if any;
  • a random request key your browser creates, so we can tell a double send from a new request;
  • that you ticked the box agreeing to our Terms of Service, this Policy and our Refund Policy (the form cannot be sent without it);
  • where you came from, as described below.

The form also has a hidden field that people never see. If it is filled in, we treat the request as automated, and we keep nothing.

Our server adds to your request:

  • a reference number and the date and time (New York time);
  • a record of your agreement: the words of the sentence beside the box, the version date of each of the three policies, and the time our server received your request;
  • its own fresh reading of the LLC's public record, and what that record means for the filing: which situation applies, which boxes the State's form would use, whether the record permits electronic service of process, and any point we must confirm with you by hand;
  • whether our bot check could verify your browser (section 10);
  • your browser's user agent (the text a browser sends that names its type and version);
  • the country and region our hosting provider estimates from your IP address. Our code does not store your IP address itself.

The contact form

When you send the contact form, we receive:

  • your name and email address;
  • your phone number, and your LLC's name or DOS ID, if you give them;
  • the topic you choose from a list, and your message (up to 5,000 characters);
  • where you came from, as described below.

Our server adds a reference number, the date and time (New York time), whether our bot check could verify your browser (section 10), your browser's user agent, and the country and region our hosting provider estimates from your IP address. It also records in one word whether your visit came from an AI assistant, as for a request. The form has a hidden field like the request form's, and a message sent too quickly for a person to have typed it is treated as automated: we keep nothing from either.

Your message goes to our tracking sheet and to our mailbox, and we reply from our mailbox to the email address you gave. The Site sends you no automatic email about it.

Where you came from

On each page you open, the Site keeps a small record in your own browser (section 8). It holds, for your first visit and for your latest visit that came from somewhere:

  • the campaign tags in the link you followed, if any (the "UTM" source, medium, campaign, term and content);
  • an advertising click ID, if the link carried one (Google's or Microsoft's);
  • the page you landed on, without anything after a question mark in its address;
  • the domain of the site that sent you (only its domain, never the full address of the page).

It also keeps the time of each visit, in your browser only, for the 90-day rule. The time is not sent to us.

It also keeps your device type (desktop, tablet or mobile), worked out from your browser's user agent.

This record is sent to us in full when you send the request form or the contact form. When you open an LLC's record in the record check, part of it goes with that request: for your first and your latest visit, the domain of the site that sent you and the campaign source and medium, never the landing page, a click ID, the other campaign tags or your device type (section 9).

From the referring domain or the campaign source, our server records in one word whether your visit came from an AI assistant (ChatGPT, Perplexity, Claude, Gemini, Copilot, or another), so we can compare it with what you told us in "how you heard about us."

What you give us by email, phone or text

After you send a request, everything happens by hand, by email from our mailbox. Before or after a request, you may give us:

  • your replies: confirming your LLC and the change, the new service of process address (the post office address to which the Secretary of State mails a copy of any process against the LLC served on it) if one is needed, your choice about the email address for notice of electronic service of process (add, change, delete or keep), the signer's name and capacity (member, manager or authorized person), and your acceptance of our Terms of Service;
  • if you choose to send it, a copy of the filing receipt the State issued when it filed your LLC's articles of organization (or, for a foreign LLC, its application for authority). We use it only to compare the LLC's name and filing date with the State's record. This step is optional;
  • a phone call or text with the operator, from the operator's own mobile phone, to confirm the request;
  • a call or text you make to our phone number, (631) 813-7738: your phone number, and what you tell us;
  • the Certificate of Change you sign and return;
  • anything else you write to us.

We also receive the State's filing receipt and any message from the State about your filing.

Information about other people. Your replies may name another person, such as a co-member who signs, or a person named on the "Name:" line of the LLC's service of process address. Please share another person's information only if you are allowed to.

Payment information

When it is time to pay, we email you a payment link.

Who takes your payment. Sandeep Arneja LLC, which also operates LLC Publishers, takes your payment and issues any refund. The payment page, the card checkout, the receipt and any refund email show the name LLC Publishers, and your card statement shows the payment request number (PR-...).

Payments on that page are processed by Stripe. You enter your card or other payment details on Stripe's checkout page, and we do not see or store your full card number. We receive the payment's status, the amount, the payment request number and your email address. The payment page also records when you ticked its agreement box, with your IP address and browser. Section 13 explains what else applies on that page.

Public records

  • The LLC's live record from the New York Department of State: its name, DOS ID, type, status, county, date of initial filing, the registered agent's name and address, the name and address for service of process, and whether electronic service is permitted. The record check shows these to anyone who searches for the LLC, because they are public.
  • The State's search results for the name you searched (section 7).
  • Our own records of the other services Sandeep Arneja LLC operates, for the same LLC. Before we file, we check them so that two filings for one LLC do not collide.

Technical information

  • What any website receives: your IP address, browser and device details, the pages you request, and the time.
  • Analytics, performance and session-recording data (section 9).
  • Signals from our bot check (section 10).

3. How We Use Your Information

We use information to:

  • run the record check and show you what the State's record says;
  • reply to your request, confirm the details with you, and answer your questions;
  • prepare the Certificate of Change, send it to you to sign, file it with the Department of State, and check the State's live record afterward;
  • confirm that a request comes from someone connected to the LLC, and protect LLCs from changes nobody asked for;
  • send the payment link, and handle payments, refunds and the related records;
  • avoid conflicting filings, by checking our other services' records for the same LLC;
  • understand how people find us (the campaign tags, the AI-assistant reading, and your own answer), and measure demand for the service, including record checks that end without a request (section 9);
  • understand how the Site is used and make it work better (section 9);
  • block automated abuse, fraud and errors (section 10);
  • keep the copy of public company records described in section 7 up to date for all the services we operate;
  • keep business, tax and legal records, meet legal obligations, and enforce our Terms of Service.

Automatic reading, human check. The record check reads the public record automatically and shows which situation appears to apply. Nothing is filed on that reading alone: the operator reads the live record by hand and confirms the details with you by email first.

No AI model reads what you type on the Site. The record check matches names with ordinary database searches. What you type is not sent to any AI model.

4. Our Service Providers

We use these providers to run the Site and the service. Each receives only what its job needs.

ProviderWhat it does for usWhat it receives
VercelHosts the Site and runs its server code; Vercel Web Analytics and Speed Insights (section 9); Vercel BotID, which Vercel says is powered by Kasada (section 10); firewall rate limits by IP address, once set upEvery page request, with your IP address and user agent; the form and record-check requests as they pass through; the analytics data in section 9
Google Workspace (Gmail)Our mailbox, sandeep@removeregisteredagent.com, which sends and receives every email about your request or your messageThe notification of each request (every form field, your agreement, the record reading, where you came from, your user agent, country and region) and of each contact message; the confirmation email to you; all our correspondence and its attachments
Google SheetsOur request-tracking sheet, written by a Google Cloud service account that our other services also useOne row per request, with the same information as the notification, plus the operator's progress notes; one row per contact message; and one row per record read in the record check, with no name or contact details (section 9)
Google Analytics 4Site analytics, on the live Site onlyThe information in section 9
Microsoft ClaritySession recordings and heatmaps, on the live Site onlyThe information in section 9
NeonHosts the database that our services sharePublic company records (section 7), and the record of your payment request: your name and email, the amount, its status, and the payment page's record of your agreement, with your IP address and browser. Nothing you type on the Site is stored there.
StripeProcesses payments on LLC Publishers' payment page (section 13)Your card or other payment details and the payment; your email address
Apple iCloud DriveStores the files for each request: the record reading, the certificate before and after signing, our emails saved as files, the receiptsThose files
CloudflareManages the Site's domain name records (DNS) onlyPage requests do not pass through it

5. Information Sharing and Disclosure

Besides the providers in section 4, we share information only as follows.

Government.

  • The New York Department of State receives the search text our server sends to its public search, from our server (not from your browser, so we do not pass on your IP address).
  • It receives the Certificate of Change we file for you, with its cover sheet, through the State's online filing system. The filer details on it are ours (Sandeep Arneja LLC and our mailbox), not yours.
  • Section 6 explains what then becomes public.

Payment. LLC Publishers' payment page (section 13) and Stripe receive what they need to take your payment, send your receipt, and handle any refund or dispute.

Legal and regulatory.

  • When the law requires it: a subpoena, court order or other legal process.
  • To law enforcement, regulators and tax authorities, where the law requires or allows it.
  • To our own legal, tax and accounting advisers.

Business operations.

  • Our insurers and professional advisers, as their work needs.
  • A buyer or successor in a business transfer (section 20).

Protection of rights.

  • To protect our rights, our customers and the public.
  • To prevent fraud, abuse or unlawful activity, including changes to an LLC's record that nobody asked for.
  • To enforce our Terms of Service.

What we do not do. We do not contact your registered agent company, and we do not send it your information. Ending or not renewing your contract with that company is between you and that company.

6. What Becomes Public: the State's Record

IMPORTANT: THE CERTIFICATE OF CHANGE WE FILE FOR YOU BECOMES PART OF THE NEW YORK DEPARTMENT OF STATE'S RECORDS. BY USING OUR SERVICE, YOU ACKNOWLEDGE THAT ITS CONTENTS MAY BECOME PUBLIC.

  • Once the State files the certificate, the LLC's public record shows the change. If you give a new address for service of process, that name and address appear on the public record, where anyone can see them (on the State's online search and in the State's open data). Earlier addresses remain in the State's history and open data.
  • The certificate itself carries the LLC's name and DOS ID, the boxes you chose, any new address, any email address you give for notice of electronic service of process, and the signer's name and capacity.
  • The State's online record, as we read it, does not show the email address for electronic service.
  • A later filing you ask us to make, such as one naming a registered agent, becomes public in the same way, including the agent's name and street address.
  • We cannot unfile a filing or remove what the State has made public. Anyone may copy and use public records for any purpose, and we cannot control that.

7. Public Records We Look Up and Keep

  • When you search by name, our server asks the Department of State's public search for matching companies.
  • We keep a copy of up to 10 of the LLCs the State returns, in a database that the services Sandeep Arneja LLC operates share. We keep every LLC in those results, not only the one you want, so the copy stays current for all our services.
  • Each copy holds only what the State's search returns: the company's name, DOS ID, date of initial filing, county, entity type, status and jurisdiction, and the State's search data as received. Our other services' systems may later add the State's detailed public record for the same company.
  • The copy never records your search text, who searched, or when you searched.
  • When you choose an LLC, we read its live record from the State, not our copy, and we do not store that live reading in the database. It goes into your request only if you send the form.

8. Cookies, Browser Storage and Similar Technologies

The Site's own code sets no cookies. It keeps three kinds of item in your browser's storage:

NameKindWhat it holdsHow long it stays
rra_attributionLocal storageWhere you came from, as described in section 2 (campaign tags, click IDs, landing page, referring domain, times, device type)Until you clear your browser's site data. A first visit older than 90 days is replaced by the next one
rra_check_qSession storageThe LLC name you typed on the home page, handed to the check pageRemoved as soon as the check page reads it
rra_lead_key: followed by the DOS ID or the LLC name you searched (lower case)Session storageThe random request key for that LLC. It goes with your request, and with each record read for that LLC (section 9)Until you close the tab

Set by the analytics services, on the live Site only (as their providers document them):

CookieSet byTypeWhat its provider says it is for
_gaGoogle AnalyticsFirst-partyDistinguishes visitors (2 years by default)
_ga_ followed by our measurement IDGoogle AnalyticsFirst-partyKeeps session state (2 years by default)
_clckMicrosoft ClarityFirst-partyKeeps the Clarity visitor ID and preferences for this site
_clskMicrosoft ClarityFirst-partyJoins page views into one session recording
CLIDMicrosoft ClarityThird-partyNotes when Clarity first saw this browser on any site using Clarity
MUIDMicrosoftThird-partyIdentifies browsers visiting Microsoft sites; used for advertising, site analytics and other operational purposes
ANONCHK, MR, SMMicrosoftThird-partyFlags for the MUID cookie (Clarity says ANONCHK is always 0 because Clarity does not use the advertising ID it refers to)
  • Vercel Web Analytics and Speed Insights set no cookies (Vercel's documentation).
  • Vercel BotID runs a check in your browser when you search or send the form.

Your choices. You can block or delete cookies and clear site data in your browser's settings. The Site works without them; clearing local storage only means a later request will not say where you first came from. Google offers a browser add-on that opts you out of Google Analytics (tools.google.com/dlpage/gaoptout (opens in a new tab)).

9. Analytics, Performance and Session Recordings

Google Analytics and Microsoft Clarity load only on the live Site, never on test copies. We never tell either service who you are: we send them no name, email address, phone number or anything you typed, and we never ask Clarity to identify a visitor.

Google Analytics 4 records the pages you view and how you arrived, with your browser, device and approximate location, using the cookies in section 8. Depending on our settings, it also records some interactions it measures automatically. We also send it events of our own, each named by a short code. They carry only short codes, small counts and the part of the page you were on, and Google Analytics adds the page's address, as it does for every page view. They never carry your name, email address or phone number, anything you typed, or the address of a link you clicked. These are our events:

From the record check:

  • check_search, when a search is sent: whether it was by name or by DOS ID, and where it started (the home page, the check page, a new search, or a link that opens a record);
  • check_result, what came back: one match, a list, no match, or no answer from the State's system, with the number of rows in a list;
  • pick_row, when you choose a row in the search results: its place in the list and the number of rows;
  • pick_list_none, when you choose "None of these" in the search results;
  • case_shown, the situation the record check showed (a short code), whether it asked you to confirm a detail by email, and whether the form would ask about the email address for notice of electronic service of process;
  • not_mine, when you choose to search for a different LLC, with the screen you were on;
  • lead_open, when the request form opens: from a record or by hand, the screen you were on, and the situation.

From the request form:

  • lead_form_start, the first time you click or tab into the form, with the situation;
  • lead_field_error, when a field or the agreement box is marked for a fix: which one (never what you typed), and whether it was when you left it or when you sent the form;
  • lead_failed, when the form could not be sent, with a short reason code;
  • generate_lead, when a request is recorded, with the situation and the service price ($100) as the event's value.

From the contact form:

  • contact_submitted, when a message is recorded, with the topic you chose.

From clicks on any page:

  • cta_click, a click on a link to the record check, with the part of the page it was in;
  • contact_click, a click on our phone number or our email address, with which one it was and the part of the page;
  • dos_record_open, a click on a link to the Department of State's DOS Public Inquiry, with the screen or the part of the page it was in.

Google states that Google Analytics 4 does not log or store IP addresses. Google explains how it uses information from sites that use its services at policies.google.com/technologies/partner-sites (opens in a new tab).

Microsoft Clarity. We use Microsoft Clarity to see how visitors use the Site, through behavioral metrics, heatmaps and session recordings. Clarity records page content, mouse movement, clicks, taps and scrolling, using first-party and third-party cookies (section 8). We use it to see which pages work and where people get stuck, so we can improve the Site. By using the Site, you agree that we and Microsoft can collect and use this data. To learn how Microsoft collects and uses data, see the Microsoft Privacy Statement (microsoft.com/privacy/privacystatement (opens in a new tab)).

What Clarity does not record:

  • every box you type in, and every place the Site repeats what you typed, is masked: Clarity receives no characters from them;
  • Clarity also masks the content of all input boxes on its own.

Clarity may record:

  • the public record facts the Site shows (the LLC's name, its agent and address lines, its DOS ID);
  • the option you choose for "how did you hear about us."

We send Clarity the same events as Google Analytics, by name only, and two labels for a recording: the situation shown, and the situation of a recorded request. Clarity keeps recordings for 30 days, and a few saved or randomly sampled recordings for up to 9 months (Microsoft's documentation).

Vercel Web Analytics and Speed Insights count page views and measure how fast pages load. Vercel says they collect no personal identifiers and use no cookies; Web Analytics tells visitors apart by a hash created from the request, and discards the visitor's session after 24 hours. Each data point holds the page address (with some query parameters), the referring site, your browser, operating system, device type and approximate location, and, for Speed Insights, page-speed measurements and network speed.

Our record-check log. Each time you open an LLC's record in the record check, our server writes one row in our tracking sheet, so we can count the checks that end without a request. The row holds:

  • when the record was read (New York time);
  • the DOS ID, and whether the State's record was found, not found, or could not be read. When the State has no record for a 9- or 10-digit number, the row keeps only how many digits it had, since it may be a phone number typed by mistake;
  • for a record that was found: the LLC's name and entity status on the State's public record, the name of the registered agent company the record names when it is one on our list (never a person's name), and what the record means for the filing, in the same short codes as a request (the situation, the form and which of its statements apply, the electronic service of process status, and any point we would confirm by hand);
  • how your visit arrived, from the record in your browser (section 2): the domain of the site that sent you, the campaign source and medium, and whether it came from an AI assistant;
  • the random request key your browser tab keeps for that LLC (section 8).

The row never holds your IP address, your name, email address or phone number, anything you typed, your country, region or device, the page you landed on, an advertising click ID, or your browser's user agent. Our server writes it only after our bot check lets the request through (section 10). If you then send a request about the same LLC from the same browser tab, your request carries the same random key, so we can see that the check and the request were one visit. If you never send a request, the row does not say who you are.

What reaches analytics in a page address. We never put the name you type into a page address. A page address may hold a DOS ID number, for example when you open a search result in a new tab, and page analytics may record it.

10. Bot Protection and Security Checks

  • Vercel BotID. When you search, open a record, or send the request form or the contact form, an invisible check runs in your browser and our server asks BotID whether the request came from a person. An unverified automated request is refused, and we keep nothing from it. A verified assistant acting for its user (for example an AI agent) is let through.
  • If the check cannot answer (an outage, or no answer within 3 seconds), we still record your request or your message, marked as not verified, so a real person does not lose it. In that case we send no confirmation email to the address on the form; the operator contacts you directly. No record-check log row is written for that record read.
  • Rate limits. Vercel's firewall may limit how many searches, record reads and requests one IP address can send in a short time.
  • The hidden field in section 2 catches simple form robots.

11. Data Retention

We keep information for as long as we reasonably need it for the purposes in this Policy, including our legal, tax and record-keeping obligations. In practice:

InformationWhereHow long
Your request (the form, your agreement and our reading of the record), and your contact messagesThe tracking sheet and our mailboxKept as our business record
Record-check log rows (section 9)The tracking sheetKept as our business record
Emails, the certificate (unsigned and signed), the receipts, your optional filing receiptOur mailbox and the request's folderKept as our business record
Copies of public company recordsThe shared databaseKept and refreshed while our services use them
Browser storageYour browserAs in section 8
Clarity recordingsMicrosoft30 days; up to 9 months for a few saved or sampled recordings
Google Analytics dataGoogleAs set in our Google Analytics property
Vercel's visitor hashVercelDiscarded after 24 hours
Server logsVercelAs Vercel's service keeps them

We also keep a copy of each dated version of our Terms of Service and this Policy, and, for each request, the record of the box you ticked on our request form (section 2) and a record of which dated Terms you accepted in your reply.

12. Data Security

We use reasonable measures to protect information. Some of them:

  • What we keep out of logs. The log lines our code writes record reference numbers, steps, error codes, DOS ID numbers, the page path and user agent of known AI crawlers, and the user agent of each fetch of our llms.txt file. They never record your name, email address, phone number, the text you typed, a company's name, or an IP address, and email errors have every address removed before they are logged.
  • What we keep out of page addresses. We never put what you type into a page address.
  • Spreadsheet values stored as text. The sheet stores each value exactly as text, so a value is never run as a formula.
  • Short confirmation emails. Of your details, the confirmation email we send you repeats only your name and the LLC's name as the State records it. It never repeats your phone number or anything else you typed, because a mistyped email address would send it to a stranger.
  • Limited access. Our mailbox, sheet and folders are open only to the operator.

Even so, please understand that:

  • no way of sending or storing information is completely secure;
  • we cannot guarantee the security of your information, and you send it at your own risk;
  • we are not responsible for unauthorized access, breaches or incidents beyond our reasonable control;
  • we may change our security measures at any time.

13. Third-Party Services, Links and the Payment Page

  • The Site links to other sites, such as the Department of State's public search. Their own policies apply there, and we are not responsible for them.
  • The payment page. As section 2 explains, you pay on LLC Publishers' payment page. LLC Publishers' Privacy Policy also applies on that page. That page loads LLC Publishers' own analytics and advertising-measurement tools, which may record your visit. Stripe's privacy policy (stripe.com/privacy (opens in a new tab)) applies to your payment. Your receipt, and any refund email, come from LLC Publishers' mailbox, and a reply to them goes to that mailbox, where LLC Publishers' systems, including AI models, read it automatically. For anything about a charge or your request, write to our email address, not to the LLC Publishers receipt.

14. Reviews on This Site

The Site may show reviews that customers of Sandeep Arneja LLC posted publicly on Google, with each reviewer's name as Google shows it, the stars and the words. The Site shows them from a copy we take from time to time, not live from Google. We do not collect information from you through them.

15. Emails and Communications

  • We use your email address and phone number to handle your request: to confirm the details, send the certificate to sign, send the payment link, tell you when the State files it, and answer your questions. We use what you send through the contact form, or tell us when you call, to answer you.
  • We do not run a newsletter today. We may email you about our services, and each such email lets you opt out.
  • If you did not send a request and receive our confirmation email, you can ignore it: nothing happens without your reply.

16. International Data Transfers

We and our providers process information in the United States, and our providers may process it in other countries too. Those countries' data protection laws may differ from yours. By using the Site or our service, you agree to this transfer and processing.

17. Children's Privacy

The Site and our service are for adults acting for an LLC, and are not directed to children under 18. We do not knowingly collect information from children. If we learn that we have, we may delete it without notice.

18. Your Rights and Choices

Depending on where you live, the law may give you rights over your personal information, such as to see it, correct it, or have it deleted. To ask, email us (section 25). Please note:

  • we may ask you to confirm your identity, and your authority to act for the LLC, before we act on a request;
  • we may decline a request that is unreasonable or excessive, or that the law does not require us to honor;
  • we keep what we must keep for legal, tax or record-keeping reasons;
  • we cannot change or remove the State's public record (section 6);
  • Microsoft Clarity cannot delete one visitor's recordings on their own, only a whole project's data, so we may not be able to delete a single visitor's Clarity data before it expires (section 9);
  • we respond within a reasonable time, and within any time the law sets.

You can also block cookies, clear your browser's site data, and use the Google Analytics opt-out add-on (section 8).

19. State-Specific Privacy Rights

California. The California Consumer Privacy Act may give California residents rights over their personal information. In our context some of those rights may be limited, because:

  • much of what we handle is information about a business, its public record and its filings;
  • much of our processing is needed to provide the service you ask for, or is required by law;
  • the filings we make become public records (section 6);
  • we may decline a request that conflicts with a legal obligation.

Other states. Residents of other states may have rights under their own state's laws. We meet the obligations that apply to us.

Do Not Track and Global Privacy Control. The Site's own code does not respond to "Do Not Track" or Global Privacy Control signals. We do not sell personal information or share it for targeted advertising (section 24).

20. Business Transfers

If Sandeep Arneja LLC, or the Remove Registered Agent business, is merged, sold or otherwise transferred, the information we hold may pass to the new owner without further notice or consent. The new owner may use it under this Policy or under its own privacy policy.

21. Changes to This Policy

We may change this Policy from time to time, and we will update the "Last updated" date above when we do. The version in effect when you send information applies to that information, and for a request, the version in effect on the day you reply to our confirmation email applies (section 1); a changed version applies to information collected after it is posted. We keep a copy of each dated version.

22. Limitation of Liability

TO THE FULLEST EXTENT THE LAW ALLOWS, WE ARE NOT LIABLE FOR DAMAGES ARISING FROM HOW WE COLLECT, USE OR DISCLOSE INFORMATION, INCLUDING SECURITY INCIDENTS, PRIVACY CLAIMS, OR WHAT OTHERS DO WITH PUBLIC RECORDS. OUR LIABILITY IS LIMITED AS OUR TERMS OF SERVICE PROVIDE, AND IN ANY CASE WILL NOT EXCEED THE AMOUNT YOU PAID US FOR THE REQUEST THAT GAVE RISE TO THE CLAIM.

23. Governing Law and Disputes

This Policy is governed by the laws of the State of New York. Any dispute about it is resolved by binding arbitration in New York County, New York, as our Terms of Service set out. You give up any right to a jury trial or to bring or join a class action.

24. Sale of Personal Information

We do not sell personal information, and we do not share it for targeted advertising. We share it only as this Policy describes: to provide our service, to meet legal obligations, and to run our business. If that changes, we will update this Policy and its "Last updated" date first, and give any notice and choices the law requires.

25. Contact Information

For questions about this Policy, or to make a request about your information, contact us at:

Sandeep Arneja LLC, operator of Remove Registered AgentEmail: sandeep@removeregisteredagent.comPhone: (631) 813-7738, Monday to Friday, 9 AM to 5 PM EasternWebsite: removeregisteredagent.comAddress: 8 Chatham Pl, Dix Hills, NY 11746

You can write to us or call us. What you decide for a request, you give us in writing.

We may need to confirm your identity, and your authority to act for the LLC, before we respond. How long a response takes depends on the request.

IMPORTANT PRIVACY NOTICE. BY USING THE SITE OR OUR SERVICE, YOU ACKNOWLEDGE THAT:

  • the Certificate of Change we file becomes part of the State's records, and its changes appear on the LLC's public record;
  • we share information with the providers and others this Policy names;
  • you pay on LLC Publishers' payment page, where LLC Publishers' Privacy Policy also applies;
  • no way of sending or storing information is completely secure;
  • you agree to the practices this Policy describes;
  • we may update this Policy, and a changed version applies to information collected after it is posted.