SaaS Terms example
This example shows how a small software-as-a-service product could explain accounts, subscriptions, beta features, support limits, data export, and service availability without turning the page into unreadable legal boilerplate.
Page plan
Example output
These Terms of Use apply to access to and use of Northstar Notes, a subscription-based software-as-a-service product for organizing team notes, task context, and lightweight internal workflows.
By creating an account, starting a trial, subscribing to a paid plan, inviting a teammate, or using the product, the customer agrees to these terms and to the policies linked from the signup, checkout, and account areas.
Each workspace should have at least one administrator who is responsible for inviting users, removing access when someone leaves the team, managing billing details, and deciding which information is appropriate to store in the product.
Users must keep login details secure, use the product lawfully, and avoid uploading passwords, payment-card details, health records, legal secrets, or other sensitive information unless the customer has independently decided the product is suitable for that use.
Paid access is provided according to the plan, billing cycle, user limits, storage limits, and feature set shown at checkout or in the account billing area. Any free trial should clearly state when it ends, whether a payment method is required, and what happens if the customer does not cancel before paid access begins.
Customers should be able to find cancellation instructions in the account area or through the support channel. Cancellation may stop future renewals, but it should not be described as automatically refunding past charges unless the refund policy actually says so.
Northstar Notes may publish target support response times, maintenance notices, or service-status updates, but those statements should be separated from any legally binding service-level commitment unless a separate agreement expressly creates one.
Experimental, preview, or beta features may change, break, disappear, or produce incomplete results. The terms should say this plainly so customers do not confuse early access with a stable production promise.
A SaaS Terms page should explain whether customers can export workspace content, how long access continues after cancellation or non-payment, and whether deleted or expired data may remain in backups for a limited period.
The exact export tools, retention periods, and deletion process should match the live product. If the product does not support self-service export yet, the terms should not imply that it does.
This example is a drafting model, not legal advice. Before publishing, the SaaS operator should verify pricing, cancellation, refund, privacy, data-processing, support, and consumer-law language against the actual product and the markets served.
