> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.omegatheme.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Consentik Shopline: Consent Timestamp

### What it is
The **consent timestamp** is the date and time a visitor gave their consent. Consentik stores it with every consent record and displays it back to the visitor as part of their consent receipt — proof of exactly when they agreed, which is a core transparency requirement under GDPR.
![](https://storage.crisp.chat/users/helpdesk/website/-/8/3/8/3/8383e5404a31c000/image_1nhm54i.png)

### Prerequisite
The timestamp is displayed inside the **preferences popup**. To make it visible to visitors, go to **Settings** → **Behavior** → **Show Consent timestamp button**. This requires **PLUS plan**.

### What visitors see
The timestamp appears in the information box at the top of the privacy popup, between the visitor ID and the expiry date:
```
Visitor ID:        uxn34323
Consent given on:  2026-10-21 14:32:05
Expires at:        2026-11-20 14:32:05
```

#### Format
Always **`YYYY-MM-DD HH:mm:ss`**, 24-hour, with no AM/PM. **This format is fixed and cannot be changed.**

#### Timezone
The time shown is read from the **visitor’s own device clock** — not your store timezone and not UTC. Two shoppers who consented at the same moment in Berlin and Singapore each see their own local time.
This is intentional. The receipt exists for the visitor, so it shows a time they recognize.

### Customizing the label
You can change the wording next to the timestamp, but not the value itself.
In **Settings** → **Behavior** → **how Consent timestamp button**, edit the **Given consent title** field. The default is *Consent given on*; you might prefer *You consented on* or a translation into your primary market’s language. Maximum 100 characters, and the field cannot be left empty.
The neighbouring **Expires title** field controls the label on the expiry line.

### When the timestamp is written
A timestamp is recorded **every time a visitor saves a consent decision** — accepting all, accepting selected categories, or declining.
Crucially, it is **overwritten, not preserved**. If a visitor returns and changes their preferences, the timestamp updates to the new decision. It always reflects the most recent choice, never the first one.
If a visitor uses **Withdraw consent**, the stored record is deleted along with its timestamp. A new one is created the next time they consent.

### The expiry date
**Expires at** is the consent timestamp plus your **Browser cookies lifetime (days)** setting (Settings → Behavior → Interaction & visibility settings → Browser cookies lifetime, in days). When it passes, the stored consent lapses and the banner reappears.
If you change Browser cookies lifetime after visitors have already consented, the expiry date shown in the popup may not match when their stored consent actually lapses. Existing consents keep the duration they were saved with.
###