How We Draft Your Terms of Service and Privacy Policy: A Working Method, Not Just Template Filling - Zephyra Studio
What This Is and Who It Is For
This is a working method for producing two documents that most small and mid-sized sites treat as an afterthought: Terms of Service (sometimes called Terms of Use) and a Privacy Policy. The Terms of Service are the rules the visitor or customer agrees to when they use your site or buy from it: who can order, how payment works, what happens if they want a refund, who owns the content on the site and what limits apply to using it. The Privacy Policy is the separate document describing what personal data you collect, why you collect it, who you share it with, and for how long you keep it.
The reason we pair them deliberately rather than treating them as two unrelated files is simple: they describe the same relationship from different sides. If your Privacy Policy says you collect an email address only for order confirmations, but your Terms of Service describe a newsletter programme, the two documents contradict each other and a careful reader (or a regulator) will notice. We write both from one map of what your site actually does, so the mismatch does not happen in the first place.
This work suits anyone with a live or soon-to-launch site that collects any personal data at all: a contact form, an order form, a newsletter signup, an account login. If your site collects nothing and has no commercial function, this is not the service you need.
Why This Approach Beats Copying a Template
Free privacy policy generators and copy-pasted templates produce text that has three recurring problems. First, they describe a generic website, not yours: they list categories of data you do not collect and stay silent about the ones you do. A Privacy Policy that does not mention the specific third-party service handling your payments is not a useful document; it is a document that looks like one. Second, generators usually do not check whether the promises in your Terms of Service are technically true. If the terms say a refund is processed within five days but your payment processor takes fourteen, the terms are simply wrong. Third, a template will not tell you when you need a specific clause at all. A shop that ships physical goods needs different delivery and returns language from a SaaS tool that charges a monthly subscription.
The alternative approach, drafting both documents from a map of your actual setup, avoids all three. You get documents that name the processors you really use, match the timeframes your systems really follow, and reflect the commercial model you really have. This is not a legal opinion, and we do not present it as one: for regulated industries, high-risk data, or jurisdictions with specific statutory wording requirements, a licensed lawyer should review the result. What we produce is a precise, internally consistent, technically accurate pair of documents that most small and mid-sized businesses can publish and maintain, and that gives a lawyer something concrete to review rather than a blank page.
How We Work Through It
We start by collecting the real inputs, not by opening a document template. That means the list of forms on your site and what each one collects, the third-party services your site actually calls (analytics, payment processors, email marketing, chat widgets, hosting, CDN), how long you keep each kind of data, how a customer can request deletion or export, and how they can complain to you or to a supervisory authority. From that collected set we draft the Privacy Policy first and the Terms of Service second, in the same pass, so shared facts like data categories and retention periods are stated once and referenced, not repeated inconsistently.
You get two rounds of revision on the drafts, the same as our other projects, since wording choices in these documents are personal to how you want to run your business. Turnaround for a standard site is within the same 2-3 week window we use for smaller and medium projects, assuming the inputs come back promptly; the drafting itself is not the slow part, gathering the real facts usually is. Both documents are delivered in editable form so you can update them yourself when you add a new tool or change a process, and we can also be engaged to keep them in sync on an ongoing basis if that suits you better.
Indicative Pricing
There is no fixed price for this work, because the amount of effort is driven entirely by how complex your data flows are: a small brochure site with one contact form needs far less than a multi-currency shop with accounts, subscriptions, and several processors. The price depends on the scope you actually have, and it is agreed through the calculator on our pricing page or in a conversation with us, never as a fixed number published up front. Payment follows the same structure as all our work: 50% in advance before we start, the remaining 50% on delivery, with no instalment option.
Frequently asked questions
We write your Terms of Service and Privacy Policy together, as a linked pair, because they answer two different questions about the same data: what a customer agrees to when using your site, and what you promise to do with the data you collect. We map your actual data flows first, then draft both documents from that map.