Mastodon Municipal Draft Trial and Subscription Terms

Draft for attorney review — not final terms

Draft prepared October 10, 2026. Effective date: [TO BE CONFIRMED after review].

This page is a proposed agreement for review. It is not an operative offer or contract, is not incorporated into an existing customer agreement, and does not ask anyone to accept it. Visiting the site, submitting an inquiry, or using a trial does not constitute acceptance of this draft. The final terms and an authorized municipal agreement must be approved through an appropriate process before they are used to create contractual obligations.

1 Parties and documents

The proposed service provider is [TO BE CONFIRMED: full legal entity name, entity type, and business address], doing business as Mastodon Municipal (“Mastodon”). The customer is the municipality or other public entity identified in its approved order or agreement (“Customer”).

Authorized users are people whom the Customer permits to access its workspace. A verified email address or a workspace administrator role establishes access permissions only. It does not establish authority to sign a municipal contract, incur charges, or waive the Customer's legal rights.

The final agreement is intended to include these terms, an order identifying the Customer and purchased service, and the Municipal Data and Security Addendum. [TO BE CONFIRMED BY COUNSEL: signature and approval process, incorporation of documents, and order of precedence.] The Privacy Notice describes information handling and should not be treated as a substitute for the municipal agreement.

2 Service and launch scope

The Core service is intended to support municipal communications and operations, including scheduling and documents, through a separate customer workspace. The enabled features and any usage or storage limits must be identified in the final order or service description.

Core is the launch offering. Pro and Enterprise are not launch subscriptions. General-ledger and utility-billing functionality are not included in the Core launch scope described by this draft.

[TO BE CONFIRMED: final feature description, supported browsers/devices, storage and attachment limits, onboarding scope, and any excluded uses.] Roadmap statements do not add a feature to a customer's purchased service unless it is expressly included in the final agreement.

3 Core trial

The intended Core trial lasts 90 days and includes five seats. Trial requests are subject to review and approval. Sending a request does not immediately create or activate a workspace.

The trial does not authorize an automatic charge. A paid subscription requires a separate affirmative choice by a properly authorized Customer representative and approval of the applicable paid terms. A trial request alone does not authorize a recurring payment method or charge at trial expiry.

[TO BE CONFIRMED: the event that starts the 90-day period, trial activation notice, exact expiry time and time zone, trial eligibility, whether extensions are available, and any trial limits beyond five seats.]

At trial expiry, the Customer may elect an available paid Core subscription. [TO BE CONFIRMED: whether access becomes read-only, is suspended, or otherwise changes if no paid subscription is selected; the advance notice and data-export process; and whether the cancellation export entitlement in Section 10 also applies to trial expiry or an abandoned trial.] No unselected paid subscription should be activated by default.

4 Core subscription pricing

The approved pricing structure for this draft is a $35 monthly base charge plus an all-seat volume rate, in US dollars:

The rate for the applicable band applies to all billable seats, rather than only the seats within that band. The monthly equivalent is $35 plus the billable seat count multiplied by its applicable rate.

For an unchanged configuration, the approved annual subscription price is 10 times that monthly equivalent for a 12-month subscription. Examples before any applicable tax or other separately approved amount:

• Five seats: $110 monthly or $1,100 for the annual subscription
• Ten seats: $185 monthly or $1,850 annually
• Eleven seats: $178 monthly or $1,780 annually
• Twenty-five seats: $360 monthly or $3,600 annually
• Twenty-six seats: $321 monthly or $3,210 annually
• Fifty seats: $585 monthly or $5,850 annually

Because this is an all-seat rate, the total decreases when moving from ten to eleven seats or from twenty-five to twenty-six seats. [COUNSEL AND BUSINESS REVIEW: confirm this intended boundary behavior in the pricing page, order, and billing implementation.]

Pricing and availability above fifty seats are [TO BE CONFIRMED]. No price above that limit is established by this draft.

[TO BE CONFIRMED: who counts as a billable seat, treatment of pending invitations or inactive users, minimum seats, zero-seat workspaces, when the seat count is measured, and how additions, removals, proration, and annual-plan changes work.]

5 Orders billing and payment

The final order should state the selected billing term, seat count, price calculation, billing contact, service start date, payment method, and payment due dates. A municipal purchase order or other approval may also be required.

Stripe is planned or in testing for billing and is not represented in this draft as an active production payment service. Any later payment authorization must be explicit and limited to the approved charges and billing terms.

[TO BE CONFIRMED: whether annual charges are collected upfront or on another schedule; card, invoice, or other supported payment methods; invoice due dates; purchase-order handling; applicable taxes and exemption documentation; disputed invoice procedure; and any lawful late-payment provisions.] No unconfirmed fee or payment penalty is established by this draft.

Refund, credit, and early-cancellation treatment are [TO BE CONFIRMED BY COUNSEL AND BUSINESS OWNER]. This draft does not establish a no-refund policy.

6 Subscription term renewal and changes

The final order must state the initial monthly or annual service term, its start and end dates, whether renewal is automatic or requires another order, and the cancellation or nonrenewal method and deadline.

[TO BE CONFIRMED: renewal mechanism, renewal notices, renewal pricing, price-change notice period, and any applicable cancellation requirements.] No automatic renewal or automatic paid trial conversion is created by this draft.

Material reductions in purchased functionality or changes to these terms should follow a defined notice and approval process. [TO BE CONFIRMED BY COUNSEL: amendment procedure and any customer remedy.] Publishing a revised webpage alone should not be used to assume authorization for new municipal obligations.

7 Customer access and appropriate use

The proposed access license permits the Customer and its authorized users to use the subscribed service for the Customer's authorized municipal operations during the agreed term.

The Customer would manage user permissions, notify Mastodon of unauthorized access it discovers, and provide lawful instructions concerning its records. Users should protect account access and avoid sharing individual credentials.

Proposed prohibited conduct includes accessing another tenant's data without authorization, uploading malicious code, bypassing security controls, or using the service for unlawful activities. [TO BE CONFIRMED BY COUNSEL: final acceptable-use restrictions, enforcement process, and any limits required by public-sector obligations.]

Uses involving highly sensitive or specially regulated information require a separate suitability assessment and any necessary written arrangements before that information is uploaded. These general terms do not establish HIPAA, CJIS, biometric, student-data, or other specialized compliance arrangements.

8 Municipal data and intellectual property

The Customer retains its rights in its records and content. The proposed permission granted to Mastodon is limited to hosting, transmitting, processing, supporting, securing, and exporting that information to provide the agreed service and comply with lawful instructions or applicable law.

The Customer's use of the platform does not transfer ownership of municipal data to Mastodon. Mastodon would retain its rights in the platform software and its own materials, subject to the Customer's agreed access license and any applicable third-party licenses.

The Municipal Data and Security Addendum should govern data-processing instructions, confidentiality, service providers, security, incident response, public-records assistance, retention, and deletion. No broad license to sell municipal records, use them for advertising, or train models is granted by this draft.

9 Support availability and accessibility

Support contact, support hours, maintenance practices, service availability commitments, response targets, and any service credits are [TO BE CONFIRMED]. This draft promises no specific uptime percentage, restoration time, backup frequency, or guaranteed support response time.

The final service description and security schedule should accurately describe tested backup and recovery arrangements and accessibility status. Accessibility requirements and any agreed remediation process should reflect the Customer's use and applicable obligations. No accessibility certification or unconditional compliance warranty is made in this draft.

[TO BE CONFIRMED: emergency-use limitations, supported operational dependencies, accessibility contact, testing status, and any accessibility documentation available to customers.]

10 Cancellation termination and data export

The final agreement should provide a clear cancellation contact and process. The intended customer commitment is a full-data export entitlement for 90 days after cancellation.

[TO BE CONFIRMED before activation: whether the 90 days begin on receipt of a cancellation request or the effective service-end date; how the Customer receives notice of the deadline; export access and assistance; formats; attachments and metadata included; whether user, role, and audit information is included; and any exclusion that would conflict with describing the export as “full-data.”]

The service should not treat day 91 as automatic authorization to destroy municipal records. Before removing records, the parties must address applicable retention schedules, preservation holds, lawful Customer instructions, and records-commission authorization where required. The final agreement must specify a lawful handoff and deletion process, including backups.

The export entitlement also does not promise indefinite free hosting after the export period. [TO BE CONFIRMED: arrangements if a hold or other legal duty requires retention beyond the export window, ongoing access, responsibility for costs if any, and eventual authorized deletion.] Unresolved retention issues must be addressed rather than assuming either immediate deletion or unlimited hosting.

Grounds and procedures for suspension or termination, including nonpayment, serious misuse, a security emergency, or material breach, are [TO BE CONFIRMED BY COUNSEL]. Notice, cure opportunities, proportionality, data access, and preservation responsibilities need to be addressed. Suspension should not be assumed to override legal preservation or export duties.

11 Public sector requirements

The Customer's obligations may include purchasing rules, limits on contracting authority, public-records disclosure, records retention, accessibility, and appropriation requirements. The final agreement must accommodate applicable mandatory requirements.

Counsel must decide whether a nonappropriation provision is needed and how it affects service, payment, and export. This draft does not assume that a municipality can agree to unrestricted indemnification, arbitration, a particular venue, a waiver of immunity, or a financial obligation beyond its lawful authority.

12 Risk allocation and dispute terms

The following material terms require counsel and business approval before this draft can become an agreement:

• Express service warranties and the scope of any lawful disclaimers: [TO BE CONFIRMED]
• Remedies for service failures and material breach: [TO BE CONFIRMED]
• Any liability limit, calculation period, exclusions, and treatment of confidentiality, security incidents, data loss, infringement, and willful misconduct: [TO BE CONFIRMED]
• Indemnities, if any, consistent with municipal authority: [TO BE CONFIRMED]
• Insurance requirements, if any: [TO BE CONFIRMED]
• Governing law, venue, dispute process, and any required claim notices: [TO BE CONFIRMED]

No liability cap, waiver, indemnity, arbitration agreement, or governing-law selection is adopted by this placeholder.

13 General provisions and notices

Legal notice contacts and addresses, assignment, use of subcontractors, force majeure, severability, waiver, the entire-agreement clause, and provisions surviving termination are [TO BE CONFIRMED BY COUNSEL].

Proposed general contact: nick@mastodonmunicipal.com [TO BE CONFIRMED for legal and cancellation notices]. Posting this address does not establish an agreed delivery method for formal legal notices.

Draft for attorney review — not final terms. All bracketed items remain open.