LEYUN · SITE SPEC & COMPONENT LIBRARY独立站技术规范手册

Multilingual Privacy Policy Template and Compliance Points for Independent Sites

Section:MULTILINGUAL COPY SPEC · Reviewed:2026-11-20 · Template asset

Key takeawayThis section defines the structure template, field dictionary, integration points and compliance boundaries for 「Multilingual Privacy Policy Template and Compliance Points for Independent Sites」 in MULTILINGUAL COPY SPEC. Templates are for reference only; verify local regulations and platform rules before launch.

Industries and use cases

  • Sites targeting the EU market (within GDPR scope)
  • Independent sites with cookies, tracking and form collection
  • Sites using third-party analytics or advertising tools
  • Sellers previously complained about over privacy in target markets
Template / code snippettext
<!-- 英文版:结构骨架(具体条文需按目标市场法律调整) -->
<section class="privacy">
  <h2>Privacy Policy</h2>
  <p class="pv-updated">Last updated: ${date}</p>

  <h3>1. Data controller</h3>
  <p>${companyName}, ${address}, is the controller responsible for
     the processing of personal data described in this policy.</p>

  <h3>2. What we collect</h3>
  <ul>
    <li>Data you submit: name, company, email, message content</li>
    <li>Data collected automatically: IP address, browser type,
        pages visited, referring URL</li>
    <li>Cookies: see the cookie policy</li>
  </ul>

  <h3>3. Why we collect it</h3>
  <table class="pv-table">
    <caption>Processing purposes and legal bases</caption>
    <thead><tr><th scope="col">Purpose</th><th scope="col">Data</th>
      <th scope="col">Legal basis</th></tr></thead>
    <tbody>
      <tr><td>Handling enquiries</td><td>Contact details</td>
        <td>Pre-contractual steps</td></tr>
      <tr><td>Site operation</td><td>Usage data</td>
        <td>Legitimate interest</td></tr>
    </tbody>
  </table>

  <h3>4. How long we keep it</h3>
  <p>Enquiry data: ${retentionEnquiry}. Analytics data: ${retentionAnalytics}.</p>

  <h3>5. Recipients</h3>
  <p>${processorList}</p>

  <h3>6. Your rights</h3>
  <p>${rightsText}</p>

  <h3>7. Contact</h3>
  <p>${companyName}, ${contactAddress}</p>
</section>
Fields and parameters
Field / parameterTypeDescription and values
Data controllerTextLegal company name and address
Data categories collectedListThree groups: actively submitted, automatically collected, cookies
Purposes and legal basesTableThree columns: purpose, data, legal basis
Retention periodsTextWritten per data category
Recipients / processorsListThird-party tools and service providers
User rightsTextAccess, rectification, erasure, restriction, portability and others
Cross-border transfer noticeTextMandatory when data leaves the region
Contact and complaint channelsTextA clearly stated, reachable contact address

SEO and structured-data notes

SEO and structured-data checkpoints
Map legal bases item by itemEvery processing purpose needs its own basis; one blanket basis for the whole document is not enough
Write retention periods per categoryDifferent data categories have different retention needs; a single blanket figure usually fails compliance
Third-party tools must be listedAnalytics, advertising and support tools must all be disclosed; this is the most commonly missed item
Express the data mapping as a tableA purpose-basis table expresses the correspondence most clearly and is easiest to audit
The contact address must be deliverableA form mailbox cannot replace the legal address
Version number and update dateUpdate the page and record the version when regulations change

Compliance risk notes

  • Privacy policies cannot be translated verbatim across legal jurisdictions
  • GDPR regions and California CCPA regions have different requirements; draft them separately
  • Do not collect personal information unrelated to the service
  • Do not use unreachable contact details
  • Do not reuse data for other purposes without notice
  • Situations involving children or sensitive data need additional assessment

Do not reuse this template verbatim in regulated contexts; verify local regulations and platform rules before going live.

Modification example

<!-- Modification example: replace "we collect information" with an item-by-item mapping -->
<!-- Original: one summarizing sentence -->
<p>We collect information you provide and may also collect technical data
   automatically to improve our services.</p>

<!-- Modified: purpose-data-basis aligned in three columns -->
<table class="pv-table">
  <caption>Processing purposes, data categories and legal bases</caption>
  <thead>
    <tr><th scope="col">Purpose</th><th scope="col">Data</th>
      <th scope="col">Legal basis</th></tr>
  </thead>
  <tbody>
    <tr>
      <th scope="row">Handling enquiries</th>
      <td>Name, company, email, message content</td>
      <td>Pre-contractual steps (Art. 6(1)(b) GDPR)</td>
    </tr>
    <tr>
      <th scope="row">Site statistics</th>
      <td>IP address (truncated), browser type, pages viewed</td>
      <td>Legitimate interest (Art. 6(1)(f) GDPR)</td>
    </tr>
    <tr>
      <th scope="row">Marketing measurement</th>
      <td>Cookie identifiers, campaign parameters</td>
      <td>Consent (Art. 6(1)(a) GDPR)</td>
    </tr>
  </tbody>
</table>

<!-- Key improvement:
     the third row is marked as consent-based — this directly determines whether
     the cookie banner must offer a "reject" option, a pivotal compliance judgment.
     Row-by-row mapping also gives auditors explicit checkpoints. -->

FAQ

How long should a privacy policy be?
No fixed length, but it must cover: controller, collection scope, purposes and bases, retention periods, recipients, cross-border transfer, how to exercise rights, and contact. EU-market policies usually run 1200-2000 words.
Can all language versions share one policy?
EU member states implement privacy law differently. Localize for non-English markets, but the main structure can be shared.
Is lawyer review needed?
Yes. The template provides structure and common clauses; the actual text must be confirmed by a professional in the target market under local law.
How do we maintain the third-party tool list?
Extract the tool list into a separate data source; when a tool is added, update the privacy policy and the cookie banner together.
Version notes2026-11-20: first release, compiled from official Google documentation and public technical sources; updated as engine rules change. Engine behaviour details follow the latest official Google documentation.

Note: this page is a summary of publicly documented search-engine rules and is for self-check reference only. Engine behaviour is subject to the latest official Google documentation; verify against your own Search Console data.