Privacy Policy and Terms
Turn on the draft privacy policy and terms pages by filling in your legal details.
Dirstarter ships a draft privacy policy at /privacy and draft terms of service at /terms. In production both stay hidden until you fill in your legal details: they answer 404, and the footer shows no link to them, so a boilerplate default never goes live by accident. In development they show as a draft with placeholder details and a banner, so you can read them before you launch.
Not legal advice
The pages are a starting template, not legal advice. Read both with a lawyer before you publish them, and change any section that does not match how your site runs.
Fill in legalConfig
Open config/legal.ts and fill in the five required fields:
export const legalConfig: LegalConfig = {
name: "Acme Ltd",
address: "1 Main Street, 00-001 Warsaw, Poland",
email: "[email protected]",
jurisdiction: "Poland",
governingLaw: "the law of Poland",
// ...
}Once all five have a value, both pages render with your details. The footer links to them in its bottom bar, and the sitemap and /llms.txt list them.
The other fields are yours to decide:
| Field | Default | What it sets |
|---|---|---|
courts | empty | The courts that hear disputes. Empty, the terms name none. |
registrations | [] | Tax or company numbers, each printed on its own line. |
supervisoryAuthority | empty | The data protection authority people can complain to. Empty, the policy names the one where the person lives. |
minimumAge | 16 | The youngest age at which a person may create an account. |
refundDays | 0 | Days after a payment in which the payer can ask for a full refund. 0 means no refunds beyond what the law requires. |
usStateLaw | false | Adds a section on the rights US state privacy laws give, such as California's CCPA. |
hosting | [] | Your hosting and database providers, listed in the policy's table of services. |
updated | empty | The date the text last changed, as yyyy-MM-dd. Empty, the pages show the date the template last changed. |
What the privacy policy covers
The policy follows the services your site has configured. Each part appears only when that service's environment variables are set:
- Stripe: payments for paid listings.
- Resend: sign-in links, listing emails and the newsletter.
- S3: stored images and videos, named after your provider (Amazon S3, Cloudflare R2 or your endpoint).
- Highseat: visit counts, clicks on
/golinks and calls to the MCP server. - Revinel: ads.
- Google: sign-in with Google.
- The admin MCP server: only when
MCP_SECRETis set. - ScreenshotOne and the Vercel AI Gateway: listed among the services that receive no personal data.
The public MCP server, the /go redirect, video embeds and website scraping are always part of a Dirstarter site, so the policy always describes them.
The wording follows the GDPR by default, since most directory sites have visitors in the EU. It states the legal basis for each use of data, how long each kind of data is kept, and the rights people have. Turn on usStateLaw to add the section US state laws need.
What the terms cover
The terms are short on purpose: listings and their review, paid placement and refunds (when Stripe is on), advertising (when Revinel is on), acceptable use, the MCP servers, links to other websites, liability, and the governing law. Add whatever else your business needs.
Changing the text
The text lives in content/legal/ as TypeScript, so each section can depend on the services your site has configured:
privacy.tsandterms.tshold the sections of each page.facts.tsholds what both pages state, such as your details and the table of services.
Page titles, descriptions and footer labels are translations in messages/en/pages.json and messages/en/navigation.json. When you change the text, set updated in legalConfig to the day of the change.
Last updated on