Last updated: October 17, 2026
These terms are between Authflow LLC and the person or business that owns a workspace or registers an MCP server on Rails, whether or not it connects Stripe. You accept them when you create a workspace, register a resource, connect Stripe or select a button beside a notice of agreement. You confirm you can bind any business you act for. These terms add to the terms of service and acceptable use policy and control conflicts on creator matters. A separate written agreement signed by you and Authflow, including an order or enterprise agreement, controls any conflict with these terms.
Read “Claims about your service” and “Disputes with Authflow.” You must defend Authflow against certain claims about your service. For disputes about creator activity, you and Authflow waive jury trials, bring claims individually and must file within one year.
Your service, your customers
You operate your MCP server and are the seller and merchant of record. You are responsible for its content, outputs, availability, support, taxes, refunds, disputes and legal compliance. Before customers pay, give accurate pricing, billing intervals, credit costs and limits, support details, terms, privacy information and a refund policy. Check offers you or your agent publish. Obtain rights to your content and tools and use customer information only for disclosed, lawful purposes. Do not direct your service to anyone under 18.
Follow subscription and automatic-renewal laws where your customers live. Provide required renewal, receipt and price-change notices and an easy way to cancel through your Stripe billing portal. Do not charge customers for service you stop providing. You keep ownership of your service and authorize us to display its name, description, prices, merchant name and logo to provide Rails. We need your permission to name you as a customer in marketing.
Pricing and fees
You agree to pay the fees and billing basis disclosed for the offering before you use or purchase it, or set out in a separate written agreement. Depending on that offer, fees may be based on transactions, subscriptions, usage or another disclosed basis. A written order or enterprise agreement may set different rates and terms. No particular rate or billing model is guaranteed by these terms, and we do not impose undisclosed charges retroactively.
The applicable pricing states how fees are calculated. Stripe processing fees, taxes and other charges to your Stripe account are separate. You are responsible for applicable taxes on our fees unless the pricing says they are included. Where fees are collected through Stripe, you authorize Authflow to collect the applicable application fee from payments on your connected account.
Unless the applicable pricing or a separate agreement says otherwise, Authflow keeps its fees when you refund a customer or a payment is disputed. We may return them at our discretion. You remain responsible for customer refunds, Stripe fees and chargebacks. Refunding or disputing a payment does not itself end Rails access; cancel the subscription if access should end.
Unless a separate written agreement provides otherwise, we give at least 30 days’ notice before a material increase to your fees or billing basis takes effect. The notice states the affected offering and effective date. Promotional terms last for the period disclosed with the offer.
Stripe and billing
Connect an eligible Stripe account under the Stripe Connected Account Agreement and Stripe Services Agreement. Customer payments are direct charges on your account. Stripe controls your balance, payouts, reserves and account reviews. Authflow does not hold your sales proceeds and is not a bank, payment processor or money transmitter. Stripe’s account and country restrictions apply.
Connecting Stripe authorizes Authflow to create products, prices, customers, Checkout sessions and subscriptions for Rails; collect applicable fees; open billing portals; read account status and Rails-related transactions, refunds, disputes and fees; and receive related events. When requested, we may create an account and onboarding links. We may cancel Rails-created subscriptions at a subscriber’s deletion request or as these terms allow. We use this access and share information with Stripe to operate Rails, show earnings, reconcile fees, prevent fraud and meet legal duties. Authflow does not issue refunds from your account.
Use Rails-created subscriptions for paid access through Rails. Billing created outside Rails does not grant that access. Do not remove or reduce applicable fees, divert payment for the same active Rails access or exchange discounts for payment outside Rails. If your actions prevent collection of fees you owe, including after disconnecting Stripe, we may invoice those fees, payable within 30 days, and restrict resources until paid.
Operating or closing your service
Protect and rotate exposed keys, validate forwarded identities and maintain compatibility with the published protocol. You are responsible for your hosting, upstream services and usage reports. Use Authflow identifiers to serve users, not track them across creators. Verification failures and changes to a live resource can interrupt access until it is verified and published again. Rails includes no uptime guarantee.
Disabling a resource, losing Rails access or disconnecting Stripe does not automatically cancel customer billing. Before closing your service, notify subscribers, cancel or migrate subscriptions and issue refunds you owe. Stripe may continue charging while Rails no longer serves the resource; you remain responsible for those charges and refunds. Contact support@authflow.ai to close a workspace or billing@authflow.ai for billing reconciliation.
Data and confidentiality
You and Authflow each handle subscriber information for your own purposes. Our privacy policy explains account, access and billing processing. We use tool traffic only to deliver, meter and secure it and never sell it. You are responsible for your privacy notice, data practices and requests about data you hold. Review our service providers and contact privacy@authflow.ai about any data-processing agreement your use requires.
We keep your non-public information, including revenue and customer details, confidential and use it only for these purposes. We may share it with providers and advisers bound to confidentiality, Stripe, a business successor under confidentiality obligations, as part of disclosed copyright or abuse processes, or to meet legal duties, enforce terms or protect safety and rights. We may publish aggregates that do not identify you or your customers. Keep non-public information we share with you confidential.
Suspension and enforcement
Cooperate with abuse, copyright and billing investigations. We may suspend or end your resource or workspace for a breach, fraud, unusual refund or dispute rates, security or subscriber risks, Stripe restrictions, legal requirements or discontinuance of Rails. Where practical, we give notice and a chance to fix a breach. If we discontinue Rails or end your workspace for a reason other than breach, these risks, Stripe restrictions or legal requirements, we give at least 30 days’ notice.
When access ends, stop charging for the affected service and promptly cancel or refund affected subscriptions. If you do not, we may cancel Rails-created subscriptions while we retain Stripe access. Previously earned fees remain due, subject to the applicable pricing or agreement. These terms continue to apply to Rails-created subscriptions until they end. Customer duties, amounts owed, confidentiality, indemnity, liability and dispute provisions survive termination.
Claims about your service
You will defend Authflow LLC and its members, managers, officers, employees and agents against third-party claims, lawsuits or government actions arising from your service, tools, content or outputs; sales, customer duties or taxes; data practices; Stripe account; breach of these terms or law; or use of your workspace or keys. You will pay resulting damages, fines, penalties, settlements and reasonable legal fees and costs.
This does not cover the part caused by Authflow’s breach, negligence or willful misconduct, or claims that Rails itself, used as documented, infringes rights. We will promptly notify you; delay reduces your obligation only to the extent it harms your defense. You control the defense with counsel reasonably acceptable to us, and we cooperate at your expense. We may participate with our own counsel at our expense. Without our written consent, you may not settle by admitting our fault, imposing obligations on us or failing to release us fully. If you fail to defend promptly, we may do so at your cost.
Liability between us
The terms of service’s disclaimers and liability limits apply. They also limit your liability to Authflow, except for your indemnity, amounts owed, acceptable-use breaches or misuse of our software or brand. Authflow does not defend you against third-party claims, including intellectual-property claims.
Disputes with Authflow
You use Rails as a business. These rules cover disputes about your workspace, resources, Stripe connection, fees or creator terms. Your personal use of another creator’s service is governed only by the terms of service. Those terms’ Pennsylvania law, Erie County courts and notice-first process otherwise apply.
Individual claims only. You and Authflow may bring these claims only individually, not as a plaintiff or class member in a class, collective or representative action. If this restriction is unenforceable for a claim, it does not apply to that claim; the rest of the agreement remains effective.
WAIVER OF JURY TRIAL. YOU AND AUTHFLOW KNOWINGLY AND VOLUNTARILY GIVE UP THE RIGHT TO A JURY TRIAL IN ANY LAWSUIT THIS SECTION COVERS. A JUDGE WILL DECIDE THE CASE.
One year to bring a claim. Either party must file within one year after it knew, or reasonably should have known, the facts behind the claim, or the claim is barred. This does not shorten a deadline the law forbids shortening or apply to intellectual-property misuse. For creator indemnity, the year starts when Authflow pays the loss or the underlying claim is finally resolved, whichever is later.
Either party may seek urgent orders from any court with jurisdiction against misuse of intellectual property, keys or credentials, or service abuse, without first sending notice.