Legal · Terms of service

Terms of service

Last updated: 19 September 2026.

These terms are the agreement between you and [Legal entity name] ("MeshArc", "we") for the web app at https://mesharc.dev, the API at https://api.mesharc.dev, the mesharc SDKs and the MCP server (together, "the service"). You accept them by creating an account, joining a workspace, or using an API key. If you are accepting for a company, you confirm you may bind it, and "you" means the company. How we handle personal data is in the privacy policy, which is part of these terms.

What the service is#

MeshArc reads web pages on your instructions, stores what came back, records what changed between runs, and delivers the result where you ask. You choose the sites, the scope, the schedule, the formats and the destinations. We provide the machinery; we do not choose what is crawled, and we do not review what comes back.

Your account#

You need a work email address you control, and you must keep your password and API keys secret. Anything done with your credentials is done by you until you tell us they were compromised, at which point we will help you revoke them.
A workspace has an owner; the owner and its admins decide who joins and what each member may do. Members act on behalf of the workspace, and the workspace is responsible for what they do.
You must be 18 or older, and must not be barred from using the service under the law that applies to you.

Acceptable use#

The service reads other people's websites. That is lawful for a great deal of the web and unlawful for some of it, and the difference depends on where you are, where the site is, what the site says, and what you do with the pages. You are responsible for making sure your use is lawful and that you have the right to collect, store and use what you crawl. In particular, you agree that you will not use the service to:

Access a site or content you are not permitted to access, whether by law, by the site's terms, or by a technical measure that exists to keep you out. The ladder climbs past bot detection because many sites block every automated reader by default; it does not make it lawful to read what you may not read.
Override robots.txt or rate limits on a site without the right to do so. Both are on by default, and turning either off is your decision and your responsibility.
Collect personal data in a way that breaks the data protection law that applies to you or to the people the data is about.
Collect content protected by copyright for use beyond what the law or the rights holder allows.
Overload, disrupt or damage any site, or the service itself, or probe it for weaknesses other than under the security page.
Resell the service as your own, share one account across companies, or use it to build a competing crawler by copying how it works.
Do anything illegal, or anything that makes us the vehicle for something illegal.

If a site owner, a rights holder, a regulator or a court asks us about your crawl, we may tell them which workspace ran it, pause the project, and delete the pages, and we will tell you unless the law says we may not. Repeated or serious breaches end the account.

Your data#

The pages you crawl are yours. We store them, diff them and deliver them to you; we claim no rights in them, we do not read them for our own purposes, and we do not train models on them. For that data you are the controller and we are the processor, on your instructions only; see Pages you crawl.
What we keep. Pages live for the retention you set on each project and are deleted after it. Deleting a project deletes its runs and pages. When a workspace closes, its data is deleted within 30 days, except records we must keep by law.
What we may do with it. Run the service, meter it, bill it, keep it secure, and look at a specific page when you report a problem, when there is an abuse report, or when the law requires — and then only as far as the task needs.
Destinations. When you connect a database, a bucket or a vector store, we write rows there because you told us to. What that provider does with the data, and what it costs, is between you and them.
Aggregate numbers — how many pages the service read, how often a site refuses, which engine tends to succeed — may be used and published without identifying you, your sites or your pages.

Credits and plans#

A credit is the unit. A page costs what it took to read it: a plain fetch is one credit, a render four, a residential render sixteen, and so on, as set out on the pricing page and in the billing chapter. Every response says what it cost. A refused page, a 404, a page served from your cache, and a page the sitemap says did not change cost nothing.
Plans give a monthly allowance, a tier ceiling, and limits on projects, pages per run, concurrency and rate. The current plans are on the pricing page; the limits that apply to you are under Settings → Limits. A limit agreed with you in writing overrides the plan's number.
When credits run out, runs stop and say so; nothing is read on credit. Starter buys top-ups; Growth and Scale may overrun at the published rate, which appears on the next invoice.
The free plan is a trial: 1,000 credits once, no renewal, 7-day retention, no top-ups. We may close free workspaces that have been idle for 90 days.
Prices may change. A change to a plan's price or allowance applies from your next billing period, and we email workspace owners at least 30 days before it takes effect. A change never takes away a limit agreed with you in writing.

Payment#

Payments are taken by Razorpay. Your plan renews monthly, or annually if you chose that, until you cancel. Cancel any time in Billing → Manage; the plan runs to the end of the period you paid for, and does not renew.
Prices exclude tax. Where tax applies, it is added to the invoice.
Credits and top-ups are not refundable, except as the law requires. If we end your account for our own reasons rather than a breach, we refund the unused part of the current period.
An invoice unpaid 14 days after its date may pause the workspace until it is settled.

The API, the SDKs and the MCP server#

Every /api/v1 route needs a key. Keys carry scopes, an optional project list, an expiry and a rate limit; a key may not do more than the member who made it could do. Do not put a key in browser code.
The SDKs and the MCP server are open source under the MIT licence, in mesharc-python and mesharc-node. The licence governs the code; these terms govern the service the code talks to.
We may change the API. Changes that break an existing call are announced to workspace owners at least 60 days before, with the old behaviour kept for that time. Additions — new fields, new endpoints — are not breaking and come without notice.

Availability and support#

We aim to keep the service up, and we email workspace owners about planned maintenance and about any outage that lasts more than an hour. We do not promise a specific uptime unless a contract with you says so.
Support is by email at [email protected]; Growth and above get priority. We answer in working hours, in English.
The ladder climbs only as far as a site allows. A page a site refuses at every rung is recorded as refused, not read, and is not charged — but we do not promise that any particular page can be read.

Ending the agreement#

You may close a workspace at any time by writing to [email protected] from the owner's address. Closing deletes its data within 30 days.
We may suspend or end your account if you break these terms, if the law requires it, or if we stop offering the service. For a breach we warn you first unless the breach is serious or continuing; if we stop offering the service we give 90 days' notice and refund the unused period.
After ending, the sections on your data, liability, and disputes continue to apply.

What we promise, and what we do not#

The service is provided as it is. We promise to run it with reasonable skill and care, to keep the security measures on the security page, and to handle personal data as the privacy policy says. We make no other promise: not that the service is uninterrupted or error-free, not that any page can be read, and not that anything you crawl is accurate, complete, or lawful for you to use.

Liability#

To the extent the law allows:

We are not liable to you for lost profit, lost data you could have retrieved from the service before it expired, lost business, or any indirect or consequential loss.
Our total liability to you for everything arising from these terms in any twelve months is limited to what you paid us in those twelve months.
Nothing in these terms limits liability for death or personal injury caused by negligence, for fraud, or for anything else the law does not allow to be limited.

You indemnify us — you will cover our losses and costs, including reasonable legal fees — for any claim by a third party that arises from what you crawled, how you used it, or a breach of the acceptable use section, because those are your decisions, not ours.

Changes to these terms#

When these terms change we update the date at the top. For a change that reduces your rights or increases your obligations, we email every workspace owner at least 30 days before it takes effect, and you may close your workspace before then without charge. Continuing to use the service after that date is acceptance.

Disputes and governing law#

These terms are governed by the law of [governing law: country, and state if applicable]. Disputes are brought in the courts of [city, country], and both sides accept their jurisdiction. Before that, we both agree to try to resolve the matter by email first, within 30 days of it being raised.

If any part of these terms is found unenforceable, the rest stands. These terms, the privacy policy, and any written agreement between us are the whole agreement; where they conflict, the written agreement wins.

Contact#

[email protected] · [Legal entity name], [registered address].