Open Source Platform for DTC, B2B Commerce, Marketplaces & Omnichannel. REST APIs, TypeScript SDKs, and production-ready Next.js storefront. Self-host it. Own your data. No vendor lock-in. Zero platform fees.
Ruby b2b-commercee-commerceecommerceecommerce-apiecommerce-frameworkecommerce-platformheadlessheadless-commerceheadless-ecommercemarketplacemulti-tenantmulti-vendormulti-vendor-ecommerceopen-sourcespree-commerce
---
title: "Policies"
description: "Learn how to write and publish your store's terms, privacy, returns and shipping policies in Spree Commerce."
---
Your policies are the legal documents customers can read: your terms, your privacy notice, and how returns and shipping work. They matter for trust and for compliance, and in most places you are required to publish at least some of them.
Every new store starts with four, already created and ready to write:
- **Terms of Service**
- **Privacy Policy**
- **Returns Policy**
- **Shipping Policy**
To manage them, navigate to **Settings → Policies**, under the **Store** group.
<Note>Each policy has an address of its own, which Spree's Next.js storefront publishes as a page automatically. A custom or headless storefront reads policies through the API, so where they appear is up to whoever built it.</Note>
<Warning>The four built-in policies start empty. Writing them is a launch task rather than an optional one, because a customer following a link to a policy you have not written finds nothing there.</Warning>
## Reviewing Your Policies

Each row shows:
- **Name** - What the policy is called, with its address beneath it.
- **Content** - A preview of the document. A policy you have not written yet reads **Nothing written yet**.
- **Updated at** - When it was last changed.
Use the search box to find a policy by name. The **Content** column is the quickest way to see at a glance which policies are still outstanding.
## How to Write a Policy
Click a policy's row to open it. The panel is titled with the policy's name.

- **Name** - The title shown at the top of the document.
- **Slug** - The address for this policy, such as `returns-policy`. Leave it blank and it follows the name.
- **Content** - The document itself.
The editor has a formatting toolbar covering **Bold**, **Italic**, **Strikethrough**, bullet and numbered lists, blockquotes, links, images, and undo and redo. Use headings and lists rather than long unbroken paragraphs, because these are documents people scan for one specific answer rather than read end to end.
Click **Save**. The policy is published immediately.
<Note>Changing the **Slug** changes a published policy's address, so any link you have shared pointing at the old one stops working. Set it once and leave it.</Note>
## How to Add a Policy
Click **Add policy** for a document the four built-in ones do not cover, such as a warranty, an accessibility statement or a cookie notice.
Fill in the **Name**, leave **Slug** blank unless the address needs to differ, write the **Content**, and click **Create policy**.
## How to Delete a Policy
Open the row menu and choose **Delete**.
<Warning>Deleting a policy removes it permanently and its address stops working. Clearing a policy's content is not a way to take it down: the text goes, but the address still resolves and customers reach an empty page.</Warning>
## Further Reading
- [<u>Returns & Reasons</u>](/user/settings/returns-and-reasons) - The reasons behind the returns your policy describes
- [<u>Emails</u>](/user/settings/emails) - Where your support address is set
- [<u>Store Details</u>](/user/settings/store-details) - Your store's name and regional defaults