megaloop — Terms of Service

Effective date: 2026-08-28 Last updated: 2026-08-28

What changed on 2026-08-19. Section 11 — we now record the IP address a request arrived from and the user-agent your client sent, on the same per-request metadata row, deleted with it after ninety days. We previously kept neither and said so. The address comes from our CDN's own reading of the connection, never from a header your client can set. Nothing else about what we store changed. See the Privacy Policy for the full column list. What changed on 2026-08-22. Section 11 — keeping a copy of your requests is now off unless you turn it on, and a new account starts with it off. When it is on, a copy is kept for seven days, encrypted, then deleted. The superseded text is preserved verbatim and available from support@megaloop.dev.

These terms are an agreement between you and AI PWRD Inc., a Delaware corporation ("megaloop", "we", "us"), covering the megaloop service at megaloop.dev and everything you reach through it: the inference endpoint, the dashboard, the management API, and the MCP server.

By creating an account or sending a request through megaloop, you agree to these terms. If you do not agree, do not use the service.

"You" is the account holder. "Provider" is whoever actually runs the model — the service whose subscription you linked.

One other document goes with this one. It is a notice we owe you rather than a term you agree to, so read it — we do not ask you to accept it:

• Privacy Policy (/privacy) — what we store, what we send to third parties, and what you can delete. The technical disclosure page at /trust says the same things with the source files named beside each claim.

1. What megaloop does

You already pay a flat monthly fee for one or more AI subscriptions. megaloop lets you link those subscriptions and use them as a single API endpoint, with requests spread across the accounts you linked.

Concretely, the service:

• holds the credentials for the provider accounts you link, encrypted;
• gives you one base URL and one API key;
• picks one of your linked accounts for each request and forwards the request to that provider;
• moves to another of your accounts when one hits its rate limit;
• shows you which of your accounts served what, and which are running out of headroom.

That is the whole of it. megaloop is a router that uses your accounts. It is not an AI model, not an inference provider, and not a reseller of anyone's capacity.

Forwarding is not byte-for-byte. Headers are added and replaced on the way out, and on one provider's path a fixed line is prepended to your system prompt — your own prompt kept in full after it, nothing you wrote removed. Section 3 sets out the main ones, because they are done on your account and you agree to them there; the Privacy Policy carries the same disclosure in fuller form and is the authoritative list. Read both before you link a subscription.

2. Who runs this, and what stage it is at

megaloop is early software run by a very small operation — at the time of writing, one person.

Being direct about what that means for you:

• There is no support team and no on-call rotation. Messages get answered when a human is awake.
• There is no uptime commitment (section 10) and no third-party security audit of anything here.
• Features change, break, and occasionally get removed. Interfaces are not frozen.

If you need a vendor with an SLA, a support contract, and a compliance package, megaloop is not that vendor today. Buy accordingly.

3. The accounts you link, and what you promise about them

When you link an account you are pointing megaloop at a relationship between you and that provider. That relationship is governed by their agreement with you, not by ours. This section is what you promise us about it, and it is a promise, not a guideline: breaking it is a breach of these terms.

You represent and warrant, each time you link an account and for as long as it stays linked, that:

1. you lawfully own or control that account;
2. you hold every right, permission and authorisation needed to authorise us to access and use it the way this service does, which includes automated access on your instruction;
3. linking it and using it through megaloop complies with that provider's agreement, policies, plan restrictions and technical requirements, and with the law; and
4. the information you gave us about it is accurate.

Not that: an account borrowed from a friend, an employer's account you were not given for this, an account bought or rented from someone, a credential found or scraped, or an account created to get around a limit on another account.

You also agree not to use megaloop to share an account with anyone outside your own control, use credentials that are not yours, evade a rate limit, quota, suspension, ban or restriction a provider has placed on you or on an account, circumvent an access control, present your traffic as another person's or another account holder's, or reach data your account is not authorised to reach.

Staying inside your plan is yours to manage. Providers describe what ordinary use of a plan looks like, and several offer a paid mechanism for going beyond it, such as usage credits or overage billing. Whether your use of a linked account stays within what your plan allows, and whether to enable any paid overflow the provider offers, are your decisions and your cost. We do not meter your subscription for you, we do not enable or authorise spending on your provider account, and the readings we show you come from the provider and may be stale or absent.

You appoint us as your limited technical agent for one purpose only: transmitting the requests you initiate, using the credentials you linked, subject to these terms. No other agency is created, and nothing here gives us authority from any provider.

What we are not. We are not affiliated with, endorsed by, sponsored by or approved by any provider. We do not represent that any provider permits its service to be used through megaloop, and cannot indemnify you if it does not. We do not evaluate your agreement with a provider, we cannot interpret it for you, and nothing on our site, in our documentation or in a support reply is advice about whether your use is permitted. Provider names appear in our product only so you can tell your own accounts apart.

Five honest notes about what megaloop does to your request, because the covenant above asks you not to misrepresent whose request it is and you are entitled to know what the software does on your behalf before you agree to it:

• It sets a session identifier on every request, replacing yours if you sent one. The identifier is derived from your tenant and account, so it identifies that account consistently. It is not there to hide anything and it never makes traffic look like it came from a different account — but it is an override, not a fill-in. (The matching identifier in the request body is a fill-in: if your client already put a user id there, megaloop leaves the body alone.)
• When your client does not present a recognised SDK platform block, megaloop supplies one — platform headers, a direct-access flag, and a CLI user-agent if you sent none — so the request has the shape the provider's API expects from a first-party client. When your client does present its own block, megaloop touches neither it nor your user-agent — on the Anthropic path. On the Codex path your user-agent is replaced whatever you sent; that is the note after next. This is a real thing the product does to your traffic, on your own account, and it is disclosed rather than buried.
• On the Anthropic path, megaloop prepends a fixed line to your system prompt. One sentence — You are Claude Code, Anthropic's official CLI for Claude. — is put at the top of the system field of your request body, and your own system prompt is kept and follows it, unchanged and in full. Nothing you wrote is deleted, edited, reordered, or relocated into the message list; if your system is a block array, your blocks and their cache settings are kept behind one new block. If your client already sends that line first, nothing is added and your bytes go out as they arrived; if you sent no system field at all, megaloop creates one holding just that sentence. It is there because the upstream refuses premium-model requests (sonnet, opus) on a subscription credential whose system prompt does not begin with that exact line (packages/providers/src/anthropic/body-marker.ts).
• On the Codex path, megaloop replaces your client's identity with the Codex CLI's, on every request. Your user-agent, originator and version headers are dropped and megaloop's are set instead — originator codex_cli_rs, and a matching codex_cli_rs/<version> user-agent — whether or not you sent any of them. This one is a replacement, not a fill-in: there is no case in which your own user-agent reaches that provider. The backend gates which models an account may reach on the client version reported this way (packages/providers/src/codex/forward.ts).
• It removes forwarding and proxy-hop headers before forwarding, because the provider APIs expect a direct client. That is request fidelity, not anonymity. Do not rely on any of the above to disguise the origin of anything, and do not treat it as megaloop's assurance that your provider permits what you are doing — see the paragraph above.

The last two exist because the upstream checks for a first-party client and refuses or downgrades a request that is not one, so both make your request look like one. Whether your provider permits that is between you and them, under the covenant above. The account it lands on is yours, and so is the consequence.

What may happen to a linked account. A provider may rate-limit, restrict, suspend, terminate, require reauthentication of, or otherwise act against an account at any time, for its own reasons. That is not an outage on our side and not a breach of these terms by us. It does not entitle you to a refund of what you paid that provider, and we cannot appeal it for you; our liability for it is addressed in section 16. If a provider tells us to stop serving your traffic, we will (section 13).

4. Your megaloop account

• You must be at least 18 and able to enter a contract. Eighteen is the minimum age for a megaloop account, it is the same floor the Privacy Policy states, and there is no younger tier: we do not knowingly keep an account for anyone under it. If you are signing up for a company, you must have authority to bind it, and "you" means that company.
• Sign-in is a code emailed to the address you registered. There is no password. Keep access to that mailbox secure — anyone who can read it can sign in as you.
• You are responsible for everything done with your API keys. Treat a megaloop key like the provider credentials it fronts. If a key leaks, revoke it in the dashboard. Revoking blocks the key from the management API at once, but the inference gateway authenticates against a short-lived in-memory cache, so a revoked key can still be accepted for inference for up to 60 seconds after you revoke it — a real window, worth planning around.
• Tell us promptly at support@megaloop.dev if you think someone else has access to your account.
• One account per person or organisation. Do not create accounts to work around plan limits.

5. Acceptable use

Section 3 covers the accounts you link and your agreement with each provider. This section is what you may and may not do with the service itself.

Breaking this section is grounds for suspension or termination under section 13.

Do not resell or share access

Your API key authenticates your pool. Do not sell, rent, sublicense, or resell access to it, and do not hand it to people outside your own control.

Allowed: your own tools, your own agents, your own machines, your own applications — including an application you build for other people, as long as the inference runs on your subscriptions and you are responsible for the traffic.

Not allowed: turning your pool into a service other people buy inference from; distributing your key; running a shared "free API" on top of it; pooling accounts contributed by strangers.

Do not send content that is illegal or that harms people

Do not use megaloop to generate, process, or distribute:

• content that is illegal where you are or where we operate — Delaware, United States;
• child sexual abuse material, in any form, ever;
• content intended to harass, threaten, defraud, or impersonate a specific person;
• malware, exploit code intended for use against systems you do not own, or credential-stuffing and phishing material;
• content whose purpose is to cause serious physical harm.

Your provider's own usage policy applies to this content too, and it reaches them, not us — see section 11, which sets out what we can and cannot see.

Do not attack the service

Do not attempt to:

• read, write, or influence another tenant's data, keys, credentials, or usage;
• extract another tenant's provider credentials, or our encryption key;
• exploit, probe for, or disclose a vulnerability in a way that puts other users' linked accounts at risk;
• take the service down, degrade it for others, or evade its authentication;
• scrape, enumerate, or brute-force the sign-in flow.

Good-faith security research is welcome. Tell us first at support@megaloop.dev and give us a chance to fix it. Do not test against another tenant's data, ever — test against your own.

Do not automate abusively

Do not send traffic whose purpose is something other than getting an answer: load generated to exhaust the service, retry storms, requests engineered to make megaloop the expensive part, or using the endpoint as an open proxy for third parties.

Parallelism itself is not abuse — it is the product. Running ten agents at once against your own pool is exactly what megaloop is for, and if our own queues or limits bite before your subscription's do, that is our bug, not your violation (section 10).

What we do not restrict

Said explicitly, because a policy that only lists prohibitions reads as broader than it is:

• how many requests you make in parallel, within what your own subscriptions will serve;
• which models you call, or which client you call them from;
• what you build with the output;
• how many accounts you link, subject to your plan.

6. We resell no inference and hold no credits

Every request you send runs on capacity you already pay for, and leaves megaloop on a credential you linked, against a subscription in your name. megaloop holds no API credits of its own and never substitutes another source of inference for yours. This is a structural fact about how the service is built, not a marketing position, and it has consequences you should hold us to and plan around:

• What you pay us buys the software, not tokens. The subscription fee in section 7 is for access to megaloop. It is not a payment for inference and it does not include any.
• What you pay your providers is separate. We do not bill it, collect it, refund it, or have any visibility into it beyond what your linked accounts report back to us.
• When your own capacity runs out, requests fail. If every linked account is rate-limited, suspended, or out of quota, megaloop returns an error. It will never quietly serve you from some other pool, because there is no other pool.

7. Plans, prices, and the trial

Trial. Every new account starts on a 14-day full-feature trial. No card is required. During the trial you can link up to 20 accounts, the same as Pro. The trial starts when your account is created and ends 14 days later. When it ends you need a paid plan to keep using the service — that is the term you agree to here.

That term is enforced in software. When a trial ends without a paid plan, the gateway stops serving inference and answers with a clear error naming the reason — not silence, and not a degraded response pretending to be a real one. Your linked accounts and your data stay untouched and are available again the moment you subscribe; nothing is deleted for lapsing.

Reading the account is not affected: you can still sign in, see your accounts and usage, and subscribe. It is the serving of new requests that stops.

Plans. Two, both monthly:

Both plans are otherwise identical — the difference is the cap on linked accounts, nothing else.

The amount you are actually charged is the one shown on the payment provider's checkout page for the plan you pick, and that is the amount that binds. The figures above describe those prices; they are not themselves the mechanism. They have been checked against the configured prices and agree: $39.00 and $99.00 US, both monthly, both active.

Monthly only. There is no annual term, no prepayment, and no discount. This is deliberate and built into the product rather than being a policy we could quietly bend.

Prices are in US dollars and exclusive of tax. Any VAT, GST, or sales tax owed where you are is yours to bear on top of the price shown. We do not calculate it, add it to your invoice, or collect it on anyone's behalf: automatic tax calculation is not switched on at our payment provider, so the amount charged is the plan price and nothing else. If your own tax authority expects you to account for the tax yourself, that is on you.

Payment. Card details never reach us. Checkout, card updates, plan changes, and cancellation all happen on our payment provider's own hosted pages. We store the customer and subscription identifiers they give us, your plan tier, status, and renewal date — see the Privacy Policy.

Renewal. Subscriptions renew automatically each month at the then-current price until you cancel. Section 18 covers what happens if we change a price.

Changing plan. You can switch between Starter and Pro at any time in the billing portal. The change takes effect immediately and the difference is prorated: you are credited for the unused part of the month on the old plan and charged for the rest of it on the new one. Neither adjustment is billed on the spot — both appear as lines on your next invoice.

Downgrading with more accounts than the plan allows. If you drop from Pro to Starter while holding more than 5 linked accounts, we do not unlink anything. Your existing accounts keep working; you simply cannot link another until you are back under 5.

Failed payments. If a payment fails, your access continues while the payment provider retries. That grace period is not indefinite — if the subscription ends up cancelled, access ends with it.

8. Cancellation

Cancel any time, yourself, in the billing portal. No email, no retention call, no notice period.

Cancelling stops the next renewal. You keep access for the rest of the month you have already paid for, and the subscription ends at the end of that period. The billing portal is configured to cancel at the end of the paid period rather than immediately, and nothing is prorated back to you on the way out. Section 9 covers refunds.

Cancelling does not unlink your provider accounts or delete your data. Section 14 covers what happens to your data, and how to have it deleted.

9. Refunds

Plainly: we do not refund the current month by default. You pay monthly, you can cancel any time, and cancelling ends the next charge rather than reversing the last one.

Two exceptions, which we will honour on request at support@megaloop.dev:

• We broke it. If megaloop was materially unusable for a significant part of a month because of something on our side, ask and we will refund that month. This is a judgement call made by a human, not an automated credit scheme, and it is not an SLA (section 10).
• You were charged after cancelling, or charged twice, or charged on an account you never used. We fix billing mistakes.

If the law where you live gives you a refund or cancellation right that you cannot sign away — a statutory withdrawal or cooling-off period, a consumer guarantee, a mandatory right to a remedy — you keep it in full, and it overrides everything in this section. Nothing here asks you to waive a right your own law does not let you waive. Tell us which right you are relying on and we will apply it.

10. Availability — there is no uptime guarantee

We do not commit to any level of uptime, and there are no service credits. Not a soft target, not an internal goal we would rather not print: there is no SLA at this stage. Anyone telling you otherwise, including any earlier draft of anything, is wrong.

What that means concretely, given how the service actually runs today:

• megaloop runs in a single cloud region, on one application server and one database server. There is no redundancy and no automatic failover. A failure of either takes the service down.
• Deployments restart the service. Maintenance can interrupt requests.
• Under heavy concurrent load we may queue a request briefly and then refuse it with a retry hint, to stop one customer's traffic from degrading another's.
• We depend on your providers. If a provider is down, slow, or has rate-limited your account, your requests fail or slow down, and there is nothing we can do about it.
• We monitor the service, but nobody is paged at 3am.

Use megaloop where an outage costs you time, not where it costs you something you cannot afford to lose. If your workload cannot tolerate the service being unavailable without warning, keep a direct path to your providers as a fallback.

11. Your prompts and the responses

You keep whatever rights you have in what you send through megaloop and what comes back. We claim no licence to any of it beyond what is technically necessary to route the request to your provider and return the response to you.

We keep no copy of your requests or the responses unless you switch it on. A new account starts with it off, and while it is off nothing you send is stored at any point. If you switch it on, a copy is kept for seven days, encrypted, and then deleted permanently; it is never written to a log and nothing in the product displays it. You can switch it off again at any time in Settings → Privacy, and nothing further is written for your account from that moment.

We also keep one row of metadata per request, for ninety days, whichever way that setting is turned. The Privacy Policy is the authoritative account of both — what is kept, for how long, how it is protected, and who can read it — and this section deliberately does not repeat it, because a partial version here would be read as the whole one. Read it before sending anything through megaloop. The /trust page names the source file behind each claim.

Two things you should be clear-eyed about:

• The provider serving your request receives the full prompt and the full response. Their retention, their training practices, and their terms apply to that, and they are not ours to control or to promise anything about.
• Our infrastructure providers sit in the path. The Privacy Policy names them. Read it before sending anything through megaloop that you would not send through a hosted service.

You are responsible for having the right to send what you send, and for the consequences of what you do with what comes back.

What we can and cannot see

This matters for enforcement, so it is in the agreement rather than only in the privacy disclosure.

The consequence of not storing any of it is that we cannot police content, and we do not. We have no way to know what you sent. Your provider does. If a provider acts on your content, they act against your subscription, and megaloop cannot appeal it for you.

What we can see is the shape of traffic and the state of accounts: volume, error rates, how many tokens a provider reported for a request, which accounts are pausing, and whether a provider has started refusing.

12. Changes to the service

We will change megaloop. Features get added, reworked, and sometimes removed. We may change which providers are supported, including dropping support for one — usually because that provider changed something on their side.

Where a change would break how you use the service, we will give you as much notice as we practically can, by email. Where a change is forced on us by a provider or by law, we may have to make it immediately and tell you afterwards.

13. Suspension and termination

You can leave at any time. Cancel in the billing portal, unlink your accounts, revoke your keys from the dashboard, and stop using the service.

Linking an account you are not entitled to link is grounds for immediate suspension. A linked credential can be revoked by the provider at any time, and the subscription behind it belongs to whoever pays for it.

We may suspend or terminate your account if:

• you break section 3 or section 5 of these terms;
• your payment fails and the subscription is not restored;
• a provider requires us to stop serving your traffic, or terminates the accounts you linked;
• the law requires it;
• your use is causing damage to the service or to other customers.

There is no automated abuse detection. Enforcement starts with a human noticing, and every measure below is taken by hand. These are the measures that actually exist today:

There is no partial "suspended" state on an account — no flag in the database that half-disables one — and no automatic escalation ladder. Revoking the key is the only enforcement measure with an interface; the other two are an operator at a database prompt. That is stated so this section does not read as if a control panel exists behind it.

A pause is also not a lock we hold against you: the management API has a resume route, so an account we pause is one you can put straight back in rotation yourself. It is there because the gateway pauses accounts of its own accord when a provider blocks them, and until that route existed an account taken out by a transient block stayed out for good. Revoking a key is a stop rather than a lock for the same reason — you can mint another from the dashboard. Sustained enforcement is therefore closing the account, and the measures above are how we stop something quickly.

Notice. Normally we will contact you first, at the address you sign in with, give you a chance to explain or fix it, and tell you what we saw. Where a provider or the law forces our hand, we may act first and explain afterwards.

Suspension without notice. We may revoke your key or pause a linked account immediately, with no warning, if we believe your use is putting other users' linked accounts at risk — or your own. This is not boilerplate. A user's linked subscription is worth roughly what they pay for it every month and a provider can revoke it over a pattern of traffic they object to. If something you are doing looks likely to make a provider act against accounts — yours or, through a shared signal, somebody else's — we will stop it first and discuss it afterwards. We will tell you what we did and why, at your sign-in address, as soon as we have done it. The same applies to anything that threatens the confidentiality of stored credentials, and to anything that endangers the service's availability for other users.

We may also shut the service down. This is a very small operation and that is a real possibility, so it is written down rather than left to be discovered. If we wind megaloop down we will give you 30 days' notice by email, stop charging you, and give you that time to unlink your accounts. We will not sell your credentials or your data to anyone as part of any such wind-down.

14. Your data when the agreement ends

Ending your subscription does not by itself delete anything. What you can do, and what is honestly true today:

• Unlink an account in the dashboard. That is a real delete: the row and its encrypted credentials are removed. It does not revoke the access grant at your provider. For an account linked by browser approval, megaloop stays authorised on your provider account until you revoke it there yourself, in their connected-apps settings. Do that too.
• Revoke your API keys in the dashboard. A revoked key stops working on the management API at once. On the inference gateway it can still be accepted for up to 60 seconds afterwards, because the gateway authenticates against a short-lived in-memory cache rather than reading the database on every request. The row stays so an audit can account for every key that existed. What is left with it is a one-way hash and the visible prefix — revoking destroys the encrypted copy that let you read the key back.
• Close the account yourself. Settings → Account → Close account. You retype your sign-in address to confirm, and it happens immediately: any live subscription is cancelled first, then your linked provider accounts and their stored credentials, your API keys, your request history and every setting are deleted. There is no undo and no export, so take anything you want first. You can still email support@megaloop.dev instead if you would rather a human did it.
• What a full deletion does not currently remove, stated because a policy that overclaims is worse than no policy: some records — the audit log, the records of sign-in codes that were issued, and any support messages you sent us — contain your email address and are not removed by that deletion today. The Privacy Policy says the same thing in more detail. We consider this a gap, not a design.
• Request metadata outlives the provider account it describes. Unlinking an account does not remove the metadata rows for requests it already served — that is on purpose, so the history of what ran stays readable. Those rows go when your megaloop account is deleted, and nothing prunes them on a schedule before that.
• Backups keep a copy for a while longer. A deletion removes the live row immediately, but encrypted database backups taken before it can still contain that row until they age out, which takes up to 14 days. We do not reach into a backup to edit it. The Privacy Policy describes the backup arrangement in full.

15. Disclaimers

The service is provided "as is" and "as available", without warranties of any kind, to the fullest extent the law allows. We do not warrant that megaloop will be uninterrupted, error-free, secure, or fit for any particular purpose.

We specifically do not warrant:

• that any provider will permit or continue to permit your use of megaloop, or that your accounts there will not be rate-limited, suspended or terminated;
• that any given request will be served, or served by any particular account;
• that the outputs you get from a provider are accurate, lawful, or fit for anything.

16. Limitation of liability

To the fullest extent the law allows:

• We are not liable for indirect or consequential loss. That includes lost profits, lost business, lost or corrupted data, wasted engineering time, the cost of a stalled or failed automated run, and the cost of buying inference elsewhere to replace what you could not get through megaloop.
• We are not liable for what a provider does to your account. Including suspension, termination, rate-limiting, credential revocation, and any money you lose as a result. This is the risk you accept in section 3.
• Our total liability is capped at the total amount you paid us in the 12 months before the event that gave rise to the claim.

None of that applies to the things that cannot lawfully be excluded. Nothing in these terms excludes or limits our liability for death or personal injury caused by our negligence, for fraud or fraudulent misrepresentation, or for any other liability that the law where you are does not permit us to exclude or limit. Where a limit above runs into one of those, the limit gives way and the rest of this section stands.

17. If someone brings a claim because of your accounts

This is the counterpart to section 3. You promised the accounts you link are yours to use this way; this says what happens if that turns out not to be true and somebody comes to us about it.

You will defend and indemnify us against any third-party claim, and any loss, damages, settlement, penalty, and reasonable legal costs arising out of it, where the claim arises from:

1. an account you linked, including a claim by the provider of that account;
2. your use of megaloop, or instructions you or your software gave it;
3. your breach of section 3 or of a provider's terms; or
4. content you sent through the service.

It does not reach our own conduct. This does not apply to the extent a claim results from our breach of these terms, our negligence, or our wilful misconduct.

How it works in practice, because an indemnity nobody can operate is worth nothing:

• We will tell you about the claim promptly. If we are late, your obligations are reduced only to the extent the delay actually prejudiced you.
• You control the defence, with counsel competent to conduct it. We may take part at our own cost.
• You may not settle in a way that admits fault on our behalf, imposes any obligation on us other than paying money you are paying, or restricts how we run the service, without our agreement.
• We may take over the defence, at your cost, if your interests and ours conflict, if you do not defend it, or if someone is seeking an injunction against us.

This section survives the end of your account.

18. Changes to these terms

We may update these terms. When we do, we will change the "last updated" date and, for anything that materially affects you, email you before it takes effect. A change that narrows what you are allowed to do always counts, whether or not we think it affects you much: you get told at your sign-in address before it takes effect.

For a price increase on your plan, we will give you notice before the renewal it applies to, so you can cancel first. A price increase never applies to a month you have already paid for.

Continuing to use the service after a change takes effect means you accept the updated terms. If you do not accept them, cancel.

19. Communications

While you have an account we will email you about the service: sign-in codes, billing, security, and changes to these terms. You cannot opt out of those while your account exists — they are how the service works.

Usage alerts, such as an account approaching its limit, are optional and you can turn them off in the dashboard.

20. General

• Governing law. These terms are governed by the laws of the State of Delaware, United States, without regard to its conflict-of-laws rules. Disputes go to the state and federal courts located in Delaware, and we both submit to their jurisdiction. If you are a consumer, this does not take away any right your local law gives you to bring proceedings in the courts where you live, or to rely on the protections of your own law.
• Indemnity. If a provider or another third party brings a claim against us because of the accounts you linked to megaloop, or because of the way you used it, you will cover our reasonable costs in dealing with that claim. This is limited to that: it does not cover a claim arising from our own breach of these terms, our negligence, or our wilful misconduct, and it does not make you responsible for anything we did. Section 17 sets out how it is run.
• Assignment. You may not transfer this agreement without our consent. We may transfer it as part of a sale or reorganisation of the business, on notice to you.
• Severability. If a clause is unenforceable, the rest still stands.
• Entire agreement. These terms are the whole agreement between us about the service, and they replace anything said earlier. The Privacy Policy is a notice we give you alongside them, not a term of them.
• No waiver. Not enforcing something once does not mean we have given it up.

21. Contact

megaloop is operated by AI PWRD Inc., a Delaware corporation.

Write to support@megaloop.dev for support, refunds, deletion requests, security reports, abuse reports, and any notice you have to give us under these terms. One address is deliberate at this size: one person reads it, and more of them would mean some went unread.

If you believe someone is using megaloop against section 5, tell us there. If it involves stolen credentials or a compromised account, say so — that gets handled first.