Skip to content

Your store's policies

Your store has seven policies, written for your business from its settings, your country and what your store runs. Each change is a new draft version; shoppers see a version only once you approve it, and every earlier version is kept for the orders placed under it.

kindServed at
terms_of_sale/policies/terms
returns/policies/returns, with the model cancellation form
delivery/policies/delivery
privacy/policies/privacy
cookies/policies/cookies
accessibility/policies/accessibility
product_safety/policies/product-safety
draftlivesupersededyou approvenext approved

POST /v1/site_policies/generate drafts every policy whose words would change, and nothing for the rest. Tuppence also drafts one by itself when an input changes, such as a new returns window.

Terminal window
curl -sS -X POST https://api.tuppence.ai/v1/site_policies/generate \
-H "Authorization: Bearer $TUPPENCE_SECRET_KEY"

Each policy has live_version and draft_version. Approving the draft makes it live: POST /v1/site_policy_versions/{id}/approve. Versions are immutable: a correction is a new version.

POST /v1/site_policies/{id}/own_words adds up to 8 paragraphs under your terms, returns or delivery text, as a new draft. They can’t take away a shopper’s legal rights: words like no refunds are refused unless the paragraph names goods the law excepts (exception, such as made_to_order) that your store sells.

EventWhen
policy.version_draftedA new draft is written
policy.version_publishedYou approve a draft
ToolScopeDoes
list_policiespolicies:readEach policy’s address, live version and waiting draft
approve_policy_versionpolicies:writePublishes a draft. A person approves it, every time

No tool writes or edits a policy’s words.

Docs assistant

Open as a page
Loading the assistant…