Legal

Terms of Service

The terms governing use of Janomate. Ops software for cleaning contractors — dispatch, QA, invoicing, and renewals in one place. This is a placeholder document covering the standard sections of a SaaS End-User License Agreement.

1. Acceptance of terms

Placeholder — the acceptance clause belongs here. Replace with the finalized language stating that by creating an account, accessing the dashboard, or using any of Janomateʼs services, the user agrees to these terms. Spell out who the agreement is between (the operating entity behind Janomate and the named account holder), what constitutes acceptance (creating an account, clicking an “I agree” checkbox, continued use), and that the user is at least 18 years old and authorized to bind the organization they represent.

Note for the founder: if you operate multiple sub-products (e.g. a contractor app and a separate facility-manager portal), this is also where you call out that those sub-products may carry their own supplemental terms layered on top of this document.

2. License grant

Placeholder — the license grant clause belongs here. Replace with the finalized grant language describing what users may do with Janomate, the scope of the license (the subscription term, the number of permitted users or seats, the geographic reach if applicable), and any limits. Make it explicit: this is a license to USE the software, not a transfer of ownership; the source code, design, and underlying IP remain with the operating entity; and the license is revocable per the termination provisions below.

3. Usage rules and restrictions

Placeholder — the acceptable-use clause belongs here. Replace with finalized rules covering what users cannot do with the service: reverse engineering, decompiling, attempting to extract source code; reselling or sublicensing access; interfering with security features; uploading malware or content that infringes third-party rights; using the service to build a competing product; scraping or automated harvesting; and any activity that would violate applicable law. Whenever possible, phrase each rule as a concrete prohibition the user could understand in plain English.

4. Your account and subscription

Placeholder — the account and subscription clause belongs here. Replace with finalized language describing who is responsible for activity under an account; how passwords and credentials must be safeguarded; what happens when a subscription lapses, is downgraded, or is canceled; billing cycles and renewal; and the founderʼs refund policy (or an explicit “all sales are final” statement, depending on your jurisdiction). If you sell via Stripe, point to Stripeʼs billing terms without reproducing them verbatim.

5. Intellectual property

Placeholder — the IP clause belongs here. Replace with finalized language confirming that Janomate, the brand, the logo, the dashboard design, the mobile checklist tooling, and all related materials are the intellectual property of the operating entity. State what user-generated content the service may store (facility addresses, cleaner rosters, QA photos and notes, invoices) and assert that the user retains ownership of that data while granting Janomate a limited license to host and process it for the purpose of operating the service.

6. Data handling and privacy

Placeholder — the data-handling clause belongs here. Replace with finalized language pointing to the separate Privacy Policy (which should describe what data is collected, why, how long it is retained, and the userʼs rights) and stating that, where this document and the Privacy Policy conflict on a data matter, the Privacy Policy controls. If the service transfers data across borders or uses sub-processors (e.g. a cloud host, an email vendor, Stripe), call out the categories of sub-processors at a high level and link to a sub-processor list if one exists.

7. Disclaimer of warranties

Placeholder — the warranty disclaimer belongs here. Replace with finalized language asserting that the service is provided “as is” and “as available,” with no warranty of any kind, express or implied, including warranties of merchantability, fitness for a particular purpose, non-infringement, or uninterrupted operation. State explicitly that the founder does not warrant that the service will be error-free, that defects will be corrected, or that the service will meet the userʼs particular requirements.

8. Limitation of liability

Placeholder — the liability cap belongs here. Replace with finalized language, conforming to the laws of your governing jurisdiction, stating that to the maximum extent permitted by law the operating entity, its officers, employees, and contractors are not liable for any indirect, incidental, special, consequential, or punitive damages; for lost profits, lost revenue, lost data, or business interruption; or for the cost of substitute services. Pair this with a defined cap on aggregate direct liability (commonly tied to fees paid in the prior 12 months, or another amount your counsel recommends).

9. Indemnification

Placeholder — the indemnification clause belongs here. Replace with finalized language describing the conditions under which the user agrees to defend, indemnify, and hold harmless the operating entity, its officers and contractors, from third-party claims arising out of the userʼs misuse of the service, the userʼs violation of these terms, or the userʼs infringement of any third-party right. Make sure the language is reciprocal only as far as your jurisdictionʼs case law allows.

10. Governing law and dispute resolution

Placeholder — the governing-law clause belongs here. Replace with finalized language naming the jurisdiction whose laws will interpret the agreement (commonly the state or country where the operating entity is incorporated). Include the chosen dispute-resolution mechanism — state courts, binding arbitration under a named provider, or mediation before litigation — and any required notice period before a dispute is filed.

11. Changes to these terms

Placeholder — the changes clause belongs here. Replace with finalized language describing how Janomate will notify users of material changes to these terms (commonly by email and an in-app banner, with a stated minimum notice window — 30 days is typical), what happens to users who continue to use the service after the effective date, and whether users on a fixed-term subscription get to keep the prior version of the terms until the end of that term.

12. Contact

Placeholder — the contact clause belongs here. Replace with finalized language naming the contact email for any questions, notices, or counter-notices relating to these terms. The companyʼs contact address for service of legal process (which may differ from the support inbox) belongs here as well, along with the registered legal name of the operating entity.

Last updated:

Questions about these terms? Email janomate@polsia.app.