Stasora Terms of Service

Version 0.9, last updated October 30, 2026.

1. Who we are and how you accept these Terms¶

1.1 Stasora, Inc. ("Stasora", "we") is a Delaware corporation with its registered office at 131 Continental Dr, Suite 305, Newark, DE 19713. We provide the Stasora platform: the web app at app.stasora.ai, the Stasora iOS app, and the pages we host for your clients (together, the "Service").

1.2 These Terms are a contract between Stasora and the business that creates an organization on the Service (the "Customer", "you"). You accept by creating an organization, clicking accept, or using the Service, and you confirm you have authority to bind your company.

1.3 Stasora is a business tool for general contractors, remodelers and specialty trade contractors. Your clients (property owners or upstream GCs) are not parties to these Terms; §6 covers what they see.

1.4 Which document wins. If these documents conflict, they apply in this order: a signed Statement of Work (§4), then the Design Partner Agreement, then the Founding Partner Terms, then these Terms. A more specific document controls on the subjects it addresses; on every other subject these Terms govern.

2. Accounts and organizations¶

2.1 Sign-in is through Clerk: email, Google or, on an Enterprise plan, enforced single sign-on through your own identity provider (§3.1).

2.2 Your users. Every user belongs to an organization you control. You assign roles (Owner, Office, Field and Read-only; custom roles are available on an Enterprise order, §3.1) and decide what each role sees, including cost data and AI chat history. You are responsible for everyone you invite and for removing them when they leave.

2.3 Invitees are free. Subcontractors, vendors and clients you invite to portal, e-sign or payment pages are never charged and never count against your plan.

2.4 Eligibility and authority. You must be at least 18 and have authority to bind the company you create an organization for. Only the Customer and its users are bound by these Terms. People you invite (subcontractors, vendors and clients) are bound only by the notices on the pages they use, not by these Terms.

2.5 Account security. Each user keeps their sign-in credentials private and turns on multi-factor sign-in where the Service offers it. Tell us at security@stasora.ai as soon as you suspect a credential or an account has been compromised. You are responsible for everything done under a user's credentials until you tell us and we have had a reasonable chance to act.

3. Plans, billing and changes¶

3.1 Plans are flat company prices with unlimited users:

The published price of Field and Office steps down the longer you stay. Your tenure is counted in calendar months from the day your current subscription started, and each month is billed at the price for its step:

These steps, at months 7, 13 and 25, are the published price, not a change to it: each takes effect on the first day of its tenure month with no further notice, and the notice in §3.4 does not apply to them. Switching between Field and Office keeps your tenure: month 14 on Field becomes month 14 on Office, priced at the Office step. Cancelling ends it: if you subscribe again, your tenure starts again at month 1. There is no pause that keeps tenure. A customer without a founding seat never pays less than a founding partner with the same tenure.

Founding partners join the ladder at their tenure step. A founding partner pays its founding rate under the Founding Partner Terms. When its Lock Term ends, it pays the price in the table above for its tenure step: for a founding partner subscribed without a break since its First Charge, that is the step for month 25 on. That move is an increase from the founding rate, so it takes effect at the later of the end of the Lock Term and 60 days after we give written notice (§3.4). A founding partner that cancels and comes back before its Lock Term ends pays its founding rate for what remains of that Lock Term (Founding Partner Terms clause 5); when that Lock Term ends it joins the ladder at the step its tenure has reached, its tenure having restarted at month 1 when it came back. One that comes back after its Lock Term ends restarts its tenure at month 1, like anyone, and pays the price in the table from month 1 (Founding Partner Terms clause 5). The Design Partner's founding rate has no end date and does not join the ladder (Design Partner Agreement).

3.2 Month-to-month. Paid plans bill monthly in advance through Stripe, on a Stripe-hosted checkout page. Subscription billing is built but not yet switched on: until we tell you in writing that it is, nothing is charged. No annual commitment, no lock-in. Cancel any time in Settings, under Plans and billing in the web app, or by email to support@stasora.ai; your plan runs to the end of the paid month and does not renew. No partial-month refunds unless the law requires them.

3.3 AI allowances. Each plan includes a monthly AI usage allowance measured in dollars of metered spend, never "credits": Pipeline $2, Field $60 and Office $180 per month. From 80% of the allowance, Ask Stasora on the web and on iOS shows you, in dollars, how much of it is used and when AI features will pause, and an AI request refused at the allowance tells you why in the same words. At the allowance the Service pauses AI features until your next month begins. We never charge overage without your opt-in: no pay-as-you-go charge exists today, and if we offer one later it applies only to a customer who has opted in.

3.4 Price changes. A change to a published price takes effect no sooner than 60 days after we give you written notice, and then at your next billing cycle. This applies to every customer. Cancel before then if you disagree. The scheduled tenure steps in §3.1 are the published price, not a change to it, and need no notice. A rate locked by the Founding Partner Terms changes only as that document says, and a founding partner's move onto the tenure ladder (§3.1) is a change that takes the full 60 days' written notice.

3.5 Founding pricing. The founding rate is claimed with a founding code at checkout, which opens on a Stripe-hosted page; the Founding Partner Terms are accepted there, and no founding seat exists before that checkout. A founding partner who starts before subscription billing is switched on uses the Service free under these Terms and claims the code when checkout opens. The founding rate, its lock period and the cohort cap are set out in the Founding Partner Terms and are not restated here; what a founding partner pays after its Lock Term is in §3.1.

3.6 Taxes. Prices exclude sales, use, VAT and similar taxes, which you pay; we pay taxes on our income.

3.7 Non-payment. If a payment fails, Plans and billing in the web app and on iOS tells you so and asks you to update your payment method. If it stays unpaid we may downgrade you to Pipeline or suspend under §12. Your data is kept under §9 either way.

4. Professional services¶

4.1 We offer Jumpstart ($2,500), Field Embed ($12,500) and the AI Operations Retainer ($1,500/month, three-month minimum, then 30 days' notice to cancel) only under a signed Statement of Work stating scope, deliverables and exclusions. A Field Embed engagement carries its own founding rate under its engagement terms, outside the founding cohort cap in the Founding Partner Terms (§3.5).

4.2 Work outside a Statement of Work is done only by written change order at $250/hour. Nobody at Stasora can expand scope verbally.

4.3 Services deliverables (imported data, price books, templates, trained settings) are your Customer Data (§9). Our methods and tooling stay ours.

5. AI features¶

5.1 AI drafts; a named person approves. The AI drafts estimates, proposals, change orders, invoices, client updates and reminders. Nothing client-facing or financial leaves draft state until a named human in your organization approves it in the Service. Nothing sends itself and nothing bills itself. You are responsible for every approved document.

5.2 Not professional advice. AI output is a drafting aid, not legal, accounting, engineering, architectural, safety or code-compliance advice, and not a licensed professional's opinion. Where a suggestion touches structural, electrical, plumbing, gas or code matters, the Service shows a licensed-professional and local-building-department notice. The Service never advises skipping a permit or inspection; do not rely on it to decide whether one is required.

5.3 Accuracy is not guaranteed. Estimates are ranges built on stated assumptions and exclusions; AI-extracted quantities carry confidence flags. AI can be wrong, incomplete or stale. Check quantities, prices, scope and terms before approving. Stasora is not liable for a bid, contract or invoice you approved.

5.4 How AI runs. AI requests run on our servers, never from your device: against Anthropic's models; for design visualization renders, against OpenAI's image model or, when OpenAI cannot render, Google's (the Gemini API, on Google's paid service); and, when you dictate into a text box, against OpenAI's speech-to-text model, which returns the text and keeps no recording of ours. Every output is stored with its prompt version, a reference to its inputs, and its approver, so you can see what ran, when, and who approved it. Standing instructions you give the AI are yours; you remain responsible for outputs that follow them. Usage is metered in dollars and capped (§3.3), so AI features may pause at a cap.

5.5 Pre-release features. A feature we label pre-release, beta or preview may be incomplete, may change, and may be paused or withdrawn without notice. §5.1 to §5.3 apply to it in full. Pre-release features are excluded from the core-functionality warranty in §14.1.

6. Client-facing features and electronic signatures¶

6.1 Your clients are yours. They reach Stasora only through pages you send: a signing link, a project portal, or a Stripe-hosted payment page. When your client signs a proposal, the Service treats the signed proposal as the contract between you and your client and files it as an executed agreement. Stasora is not a party to that contract or to any other contract between you and your client, represents neither side, and guarantees neither side's performance.

6.2 Signing links. A signing link is a private link that opens exactly one document, and only that document: the same document you previewed, notices included. A link stops opening 30 days after it is sent, or sooner if you revoke it; sending the document again makes a new link and closes the old one. A closed link shows your client only that it has expired and to ask you for a new one. Only a document a named person in your organization has approved can be signed; an unapproved document cannot be signed even with a link. Once signed, the document is the contract between you and your client (§6.1): while the link is open it shows the executed agreement, and a second signature is not recorded; the first stands.

6.3 Electronic-signature consent. Before signing, your client is shown who operates the signing page and links to these Terms and our Privacy Policy. Your client then gives, by ticking a box of its own, the consents federal law asks of a consumer signing electronically (ESIGN §101(c)):

• consent to receive and sign this record electronically;
• that they can ask you for a paper copy at any time;
• that they can withdraw consent for future documents by telling you, without undoing a document already signed; and
• that an ordinary, current web browser is all that is needed to open, sign and keep a copy.

Your client also types their full name and confirms that they have read the document, including its terms and notices, and agree to it, and that their typed name and signature are recorded electronically with the date and time. By using e-sign you agree, and will ensure your client agrees, that electronic signatures and records may be used in place of paper under the U.S. Electronic Signatures in Global and National Commerce Act (ESIGN) and applicable state law, including UETA where adopted. A client who prefers paper can print, sign and photograph the document; that path is supported.

6.4 What the record contains. On signing, Stasora records the signer's typed name; the signer's email address as you entered it when you sent the document; the date and time; an audit note with the signer's IP address and a short user-agent note (not a full fingerprint); the drawn signature path, if any; the contract total frozen at signing; the version of the consent wording the signer was shown; and the document as signed, carrying the jurisdiction-varies and attorney-review notices. Stasora also records the first open of a link and any decline with its reason. These records are yours (§9).

6.5 Your responsibilities. You are responsible for every document you send, for disclosures your state requires for your trade, and for confirming the signer is who they say they are.

7. Payments¶

7.1 Stripe Connect. Client payments run on Stripe. You onboard your own Stripe connected account under Stripe's terms, which you accept directly with Stripe. Your client pays your connected account. Stasora never holds, receives or controls your client's funds, and card data never touches Stasora's servers; every payment page is hosted by Stripe.

7.2 You are the merchant of record. Refunds, chargebacks, disputes, sales tax on your work and processing fees are between you, your client and Stripe. The Service records, per invoice, whether you intend to pass processing fees to your client; no fee is added to an invoice until fee rates are configured in the Service, and any pass-through is your responsibility, where your state allows it.

7.3 Payment links are created only for an invoice a named person has approved, and only for the balance still owed. Card and ACH are supported as configured on your connected account.

7.4 Our fees. Your subscription is billed separately by Stasora through Stripe, once subscription billing is switched on (§3.2). We take no share of client payments unless a plan, a signed order or the Founding Partner Terms expressly say so.

8. Templates: contracts and lien waivers¶

8.1 Contract terms, template classes and lien waivers are templates only. Every render carries a visible "terms vary by jurisdiction" notice and an "attorney review" notice, and the Service is built so those notices cannot be removed.

8.2 Lien-waiver templates (conditional/unconditional, progress/final) are pure fills of statutory wording from stored facts (no AI writes a word), and each render names its state and statute. The v1 set is California. A template for one state is not valid in another.

8.3 Nothing in the Service is legal advice or a substitute for an attorney licensed in your state.

9. Customer Data¶

9.1 You own it. Everything you and your users put into the Service (contacts, projects, estimates, documents, photos, daily logs, captures, financial records) is "Customer Data" and is yours.

9.2 License to operate. You grant Stasora a non-exclusive license to host, process, transmit, back up and display Customer Data solely to provide, secure and improve the Service for you, run the AI features you use, and comply with law. "Improve" means fixing and evaluating the product, never training a model on your data, and never building a product for someone else from it. We do not sell Customer Data and never resell contractor data to lead marketplaces or anyone else.

9.3 Cost firewall. Your internal cost data (unit costs, crew rates, margins, "our cost") lives in fields that client-facing pages (proposals, change orders, invoices, portal) structurally cannot read, and every client-facing render is checked automatically for cost leaks. You still control which of your users see cost data (§2.2).

9.4 Portability and export. You may take a full export of your Customer Data at any time, and it covers everything: your records as CSV and JSON, your files and photos in their original formats, signed documents as PDF, your activity ledger, your AI drafts and your e-sign audit notes. The scope is the same whether you take the export yourself or ask us for it. Stasora intends to ship self-serve export before subscription billing turns on. Until it ships, our binding promise is this: we deliver a full export within 10 business days of a written request to support@stasora.ai.

9.5 Retention. Jobsite evidence (photos, daily logs and captures) is retained for 10 years after its project closes, then deleted, whether or not your account is open. When your account closes we retain all other Customer Data for 10 years, then delete it. You may request earlier deletion in writing. We honor it except where law, a litigation hold, or Stripe/tax record-keeping requires otherwise; in that case we keep only what is required, for as long as it is required, and tell you what we kept and why. Deleted data can remain in our database provider's backups until those backups expire, at most 30 days later.

9.6 Offline capture. The iOS app holds captures on the device only as a queue until they sync; the cloud is their home.

9.7 Sub-processors. We use these providers, each under its own terms and, where required, a data-processing agreement. This is the one sub-processor list for the Service; the Privacy Policy carries the same list.

The marketing site at stasora.ai loads Google Fonts, which sends your IP address to Google, and counts page views through Vercel Web Analytics and PostHog without a cookie; the one cookie it sets is its own stasora_vid, described in the Privacy Policy. We update this list before adding a sub-processor that will process Customer Data.

9.8 Security. Each organization's data is isolated by database row-level security, financial changes are written to an audit trail, and no secrets ship in the apps. No system is perfectly secure; report suspected exposure to security@stasora.ai.

9.9 Your obligations. You must have the right to upload Customer Data, including photos of people and property, and give any notices your clients or employees are owed.

9.10 Service-provider terms. Where personal information in Customer Data is covered by the California Consumer Privacy Act or a similar state law, Stasora acts as your service provider, and:

• we do not sell or share it;
• we use it only to provide the Service to you under these Terms, and for no other purpose;
• we do not combine it with personal information from other sources, except as the Service itself requires;
• we tell you if we can no longer meet these obligations; and
• you may take reasonable steps to check that we do, and to stop and fix any unauthorized use.

A data-processing addendum is available on request to legal@stasora.ai.

10. Accounting integrations¶

10.1 If you connect QuickBooks Online, you authorize Stasora, through Intuit's own consent screen, to read and write accounting data in your QuickBooks company under the single accounting scope. Stasora never touches payroll.

10.2 Invoices and payments sync one way, Stasora to QuickBooks, only after a named person approved them here. Contacts sync both ways, field by field. If a record changed in both systems, nothing is overwritten: it halts and is listed for a person to settle.

10.3 Disconnect QuickBooks any time in Settings. Intuit's terms govern your QuickBooks account; Stasora is not responsible for your books.

10A. API and MCP access¶

10A.1 Who gets it. The Stasora API and its MCP server are included with the Office plan and on an Enterprise order (§3.1). A user who holds the Owner role creates keys in Settings and can revoke any key at any time. Each key belongs to your organization only, is shown once at creation, and both creating and revoking are written to your activity log with the person's name.

10A.2 Read-only. Today every key is read-only: it can read your organization's projects and invoices, and nothing else. There is no write endpoint. An AI agent you connect over MCP gets exactly the same reads through the same key, nothing more.

10A.3 Rate limits. Requests are limited per key (in the current build, 120 requests per key every 60 seconds), and every response tells the caller where it stands. We may change the limit and will publish it in the API reference.

10A.4 Your responsibility. Whoever holds a key (a bookkeeper's script, an integration, or an AI agent you connect) reads your organization's data under your responsibility. Treat a key like a password; revoke it the moment you suspect it has leaked.

10A.5 Cost firewall. The cost firewall in §9.3 applies to API and MCP responses: internal cost fields are structurally excluded from what the API can return.

11. Acceptable use¶

You will not: use the Service to break the law or a building code; upload malware or try to reach another organization's data; scrape, resell or sublicense the Service or its data; use AI outputs to impersonate a licensed professional or forge a signature; send unsolicited bulk messages through client-facing features; reverse-engineer the Service; or overload it deliberately. We may remove content and act under §12 if you do.

Feedback. If you send us suggestions or feedback about the Service, we may use them freely and without obligation to you. Your documents and Customer Data are not feedback.

12. Suspension and termination¶

12.1 By you. Cancel any time (§3.2). Ask us to close your organization and retention (§9.5) begins.

12.2 By us, for cause. We may suspend access to the Service for all users in your organization if a subscription payment stays unpaid after notice; you materially breach these Terms and do not cure within 10 days of notice; your use threatens the Service or other customers; or law requires it. We give notice before suspending unless that would cause harm or is prohibited. While your organization is suspended, its users cannot use the Service and the links you sent your clients do not open; a payment your client already made is still recorded.

12.3 By us, without cause. We may terminate on at least 30 days' written notice; you keep access through the notice period and receive a full export (§9.4) at no charge. The price lock binds Stasora too: we will not terminate without cause a Founding Partner during its 24-month Lock Term, or the Design Partner while it remains a customer. Termination for cause under §12.2 (non-payment, breach, abuse of the Service, or a legal requirement) is not affected.

12.4 These survive termination: accuracy (5.3), your clients are yours (6.1), merchant of record (7.2), templates (8), Customer Data (9), confidentiality (13), warranties (14), liability (15), indemnity (16), disputes (18) and notices (19).

13. Confidentiality¶

Each party keeps the other's non-public business information confidential, uses it only under these Terms, and protects it with reasonable care, for three years after these Terms end (indefinitely for Customer Data). This excludes information that is public through no fault of the recipient, already known, or required by law to be disclosed, with notice where allowed.

14. Warranties and disclaimers¶

14.1 We warrant that we provide the Service with reasonable skill and care and will not materially reduce its core functionality during a paid term without notice. Pre-release features (§5.5) are excluded from this warranty.

14.2 Otherwise the Service is provided "as is." We disclaim all other warranties, express or implied, including merchantability, fitness for a particular purpose and non-infringement. We do not warrant that AI outputs are accurate, that estimates match actual cost, that a template is enforceable in your jurisdiction, that a client will pay, or that the Service is uninterrupted or error-free. In plain terms: beyond the promise in 14.1, we do not guarantee results: not that an estimate will match what the job costs, not that a form will hold up in your state, not that a client will pay.

14.3 Stasora is a software provider, not a contractor, engineer, architect, lawyer, accountant, payment processor or escrow agent.

15. Limitation of liability¶

15.1 To the fullest extent the law allows, neither party is liable for indirect, incidental, consequential, special or punitive damages, or for lost profits, bids, contracts or data, even if advised of the possibility. In plain terms: neither side pays the other for losses that flow indirectly from a problem with the Service (a lost bid, a lost contract, lost profit), only for direct losses, and only up to the cap in 15.2.

15.2 Stasora's total liability is limited to the fees you paid Stasora in the 12 months before the event giving rise to the claim. If you paid Stasora nothing in those 12 months (for example, on the $0 Pipeline plan), it is limited to $100.

15.3 These limits do not apply to breach of §13, to indemnity under §16, to gross negligence or willful misconduct, or where the law forbids limitation.

16. Indemnity¶

16.1 By you. You will defend and indemnify Stasora against third-party claims arising from:

• documents you approved and sent;
• your contracts with clients;
• your work, jobsite or licensing;
• your use of templates;
• client payments and disputes;
• Customer Data you had no right to use.

16.2 By us. We will defend and indemnify you against third-party claims that the Service, as we provide it and as used under these Terms, infringes a U.S. patent, copyright or trademark, except where the claim arises from Customer Data, your modifications, or combination with things we did not supply.

16.3 The indemnified party gives prompt notice, lets the indemnifying party control the defense, and cooperates reasonably.

17. Changes to these Terms¶

We may update these Terms. For material changes we give at least 30 days' notice by email to the users who hold the Owner role in your organization. Continued use after the effective date is acceptance; cancel before then if you disagree. Changes required by law may apply sooner.

18. Governing law and disputes¶

18.1 These Terms are governed by the laws of the State of Delaware, without regard to its conflict-of-laws rules.

18.2 Before filing a claim, the parties will try in good faith to resolve it by written notice and a call between principals within 30 days. Unresolved claims are brought exclusively in the state and federal courts located in San Francisco County, California, and both parties consent to the jurisdiction of those courts.

18.3 Either party may seek injunctive relief in any court for breach of §13 or misuse of the Service. In plain terms: if one side leaks the other's confidential information or abuses the Service, the harmed side can ask a court to make it stop right away, without waiting for the 18.2 process.

19. Contact and notices¶

• Stasora, Inc., 131 Continental Dr, Suite 305, Newark, DE 19713 (registered office), attention David Campos, Founder and Chief Executive Officer
• Email: legal notices to legal@stasora.ai · support and account requests to support@stasora.ai · security reports to security@stasora.ai · general to hello@stasora.ai
• Notices to you go by email to the users who hold the Owner role in your organization and are effective on delivery.