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

GDPR Data Notice and Rights Request Component Rules

Section:COMPLIANCE BANNER SPEC · Reviewed:2026-11-20 · Template asset

Key takeawayThis section defines the structure template, field dictionary, integration points and compliance boundaries for 「GDPR Data Notice and Rights Request Component Rules」 in COMPLIANCE BANNER SPEC. Templates are for reference only; verify local regulations and platform rules before launch.

Industries and use cases

  • Sites serving users in the European Union
  • Sites that must handle access, deletion and correction requests
  • Sites that must explain data use and retention periods
  • Platform customers with explicit privacy compliance requirements
Template / code snippethtml
<!-- 隐私设置入口(页脚常驻) -->
<section class="privacy-hub" id="privacyHub">
  <h2>Your privacy choices</h2>
  <p>
    You can access, correct, export or delete your personal data,
    and withdraw consent at any time.
  </p>
  <ul class="ph-actions">
    <li><a href="/privacy/">Read our privacy policy</a></li>
    <li><a href="/privacy/#cookies">Manage cookie preferences</a></li>
    <li><a href="/privacy/#requests">Submit a data request</a></li>
  </ul>
  <p class="ph-contact">
    Data requests: <a href="mailto:${privacyEmail}">${privacyEmail}</a>.
    We respond within 30 days.
  </p>
</section>

<!-- 数据请求表单 -->
<form class="dsr-form" method="post" action="/api/privacy-request">
  <label>Request type
    <select name="type" required>
      <option value="access">Access my data</option>
      <option value="correct">Correct my data</option>
      <option value="export">Export my data</option>
      <option value="delete">Delete my data</option>
      <option value="withdraw">Withdraw consent</option>
    </select>
  </label>
  <label>Email address
    <input type="email" name="email" required
      placeholder="the address you used on this site"></label>
  <label>Details
    <textarea name="detail" rows="4"
      placeholder="Describe your request"></textarea></label>
  <label class="dsr-consent">
    <input type="checkbox" name="identity" required>
    I confirm the email address above belongs to me
  </label>
  <button type="submit">Submit request</button>
  <p class="dsr-note">
    We may ask for additional information to verify your identity.
    Requests are free of charge and handled within the statutory period.
  </p>
</form>
Fields and parameters
Field / parameterTypeDescription and values
Request typeEnumAccess / correct / export / delete / withdraw consent
Email addressRequiredUsed to verify identity
DetailsOptionalHelps locate the data
Identity confirmationCheckboxPrevents requests made on behalf of others
Response periodTextStates the handling time
CostTextStates whether a fee applies
ContactTextDedicated privacy email address

SEO and structured-data notes

SEO and structured-data checkpoints
The rights entry must be discoverableA privacy entry buried several levels deep in the footer is generally judged not "easily accessible" in compliance checks
Cover all five rightsAccess, correction, deletion, portability and withdrawal of consent; missing any one leaves the set incomplete
Identity verification is requiredDeletion cannot proceed on an email address alone, but excessive proof must not be demanded either
No handling feeA fee may only be charged for manifestly excessive or repetitive requests
State the response periodIt tells users how long to expect and makes it easy to check internally for overruns
Use a dedicated privacy addressOrder or customer service inboxes should not receive privacy requests

Compliance risk notes

  • Exercising a right must not be conditioned on registering first
  • Unreasonable obstacles must not be placed in the way of requests
  • Identity evidence beyond what is necessary must not be demanded
  • Marketing content must not be attached to a response
  • Data must not be retained after a deletion request, except where retention is legally required

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

Modification example

<!-- Modification example: consolidate scattered entries into one privacy centre -->
<!-- Original: split across the footer -->
<ul>
  <li><a href="/privacy/">Privacy Policy</a></li>
  <li><a href="/cookie-policy/">Cookie Policy</a></li>
  <li><a href="mailto:info@example.com">Contact</a></li>
</ul>

<!-- Modified: single entry point with the five rights stated -->
<section class="privacy-hub" id="privacyHub">
  <h2>Your privacy choices</h2>
  <p>
    You can access, correct, export or delete your personal data,
    and withdraw consent at any time.
  </p>
  <ul class="ph-actions">
    <li><a href="/privacy/">Read our privacy policy</a></li>
    <li><a href="/privacy/#cookies">Manage cookie preferences</a></li>
    <li><a href="/privacy/#requests">Submit a data request</a></li>
  </ul>
  <p class="ph-contact">
    Data requests: <a href="mailto:${privacyEmail}">${privacyEmail}</a>.
    We respond within 30 days.
  </p>
</section>

<!-- Three improvements:
     1. the five rights are stated at the entry point, so users need not read the whole policy first
     2. a separate privacy address, kept apart from business inboxes
     3. the response period is stated
     These three points are the items most often examined in compliance reviews. -->

FAQ

Which rights must be offered?
Access, correction, deletion, data portability and withdrawal of consent. Objection to automated decision-making also falls within scope in specific situations.
How far should identity verification go?
Proportionate to the sensitivity of the data involved. Verification that is too elaborate is treated as an obstacle.
How long is the response period?
Usually 30 days; complex cases may be extended by two months with the reason explained.
Should this be a separate page?
Keep it as a distinct section with anchors inside the privacy policy, so users do not have to search a long document.
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.