Why Does the Privacy Policy Gate Keep Appearing?

SoftwareRoad Knowledge Base can display a privacy policy gate before visitors access the public knowledge base.

When a visitor accepts the gate, that acceptance is stored only for the current browser session.

This means the gate may appear again after the visitor closes the browser, opens a private window, clears browser storage or starts a new browsing session.

This is expected behaviour and does not normally mean the privacy gate is broken.

How the privacy policy gate works

The privacy gate asks visitors to confirm that they have read or accepted your privacy information before continuing to the knowledge base.

Once accepted, the browser stores a temporary session value.

The plugin then allows the visitor to continue using the knowledge base during that browser session.

The acceptance is not normally stored as a permanent customer record in WordPress.

Acceptance is stored for the current browser session

A browser session usually lasts until the browser or tab session ends.

During the same session, the visitor should normally be able to move between:

• Knowledge base homepage
• Category pages
• Knowledge base articles
• Search results
• Related Articles
• Recommended Articles

without being asked to accept the gate on every page.

When the session ends, the stored acceptance can be removed automatically.

Closing the browser can remove acceptance

If the visitor closes the browser completely and opens it again later, the privacy gate may return.

This happens because the previous browser session has ended.

For example:

1. The visitor opens the knowledge base.
2. The visitor accepts the privacy gate.
3. The visitor reads several articles.
4. The browser is closed.
5. The visitor returns later.
6. The privacy gate appears again.

This is normal for session-based storage.

Closing one tab may not always end the session

Browser behaviour can vary.

Closing one tab may keep the wider browser session active if other tabs remain open.

In other cases, reopening the website in a new tab may create a fresh session.

This depends on:

• Browser
• Device
• Privacy settings
• Session restore settings
• Browser extensions

The plugin relies on the browser session rather than creating a permanent server-side record.

Private browsing creates a new session

Private or incognito browsing uses a separate temporary browser session.

Acceptance saved in a normal browser window is not shared with a private window.

The privacy gate may therefore appear again when the visitor uses:

• Chrome Incognito
• Edge InPrivate
• Firefox Private Browsing
• Safari Private Browsing

Closing all private windows normally clears that temporary session.

Each browser has separate storage

Acceptance in one browser does not automatically carry over to another.

For example, accepting the gate in Chrome does not normally save acceptance in Firefox.

The gate may appear again when the visitor changes:

• Browser
• Device
• Browser profile
• Mobile app browser
• Desktop computer
• User account

Each browser session manages its own temporary storage.

Each device has a separate session

A visitor who accepts the gate on a laptop may still see it on a mobile phone.

This is expected because the acceptance is not connected to a permanent user account.

The same applies when switching between:

• Desktop computer
• Laptop
• Mobile phone
• Tablet
• Work device
• Home device

Clearing browser storage removes acceptance

The privacy gate acceptance can be removed when the visitor clears browser data.

This may include clearing:

• Session storage
• Website data
• Browser history
• Cookies and site data
• Cached site data
• Privacy data

Even if the visitor does not deliberately clear it, some privacy-focused browsers or extensions may remove session data automatically.

Browser extensions can clear the session

Privacy and security extensions may remove or isolate website storage.

Examples include tools that:

• Clear data when tabs close
• Block website storage
• Use temporary containers
• Isolate each website
• Delete browser data automatically
• Prevent session persistence

If the privacy gate appears more often for one browser than another, test without extensions.

There is no permanent server-side acceptance record

SoftwareRoad Knowledge Base does not normally create a permanent WordPress record showing that a named person accepted the privacy gate.

The acceptance is stored only in the visitor’s browser session.

This means the plugin does not normally save:

• Visitor name
• Email address
• WordPress account
• Customer ID
• Permanent acceptance date
• Permanent acceptance history

The gate is intended as a temporary access confirmation rather than a formal signed consent system.

The gate is not a legal consent management platform

The privacy policy gate is a simple knowledge base access feature.

It should not be treated as a replacement for specialist legal, cookie or consent management tools where those are required.

Whether your website needs additional consent records depends on:

• What information the website collects
• Which cookies are used
• Which third-party services are loaded
• Local laws and regulations
• Your own privacy policy

Seek suitable legal advice where necessary.

The gate appears after restarting the browser

This is expected.

Restarting the browser normally starts a new session, so the temporary acceptance no longer exists.

The visitor will need to accept the gate again before entering the knowledge base.

The gate appears after restarting the device

Restarting a computer, phone or tablet can also end browser sessions.

When the browser is opened again, the gate may return.

This does not mean the visitor’s previous acceptance failed to save.

It means the previous temporary session ended.

The gate appears in a new private window

Each private browsing session is temporary.

The gate will normally appear when:

• A new private session starts
• All previous private windows were closed
• The browser cleared private session data
• A separate private browser profile is used

This is expected behaviour.

The gate appears after clearing cache

Clearing only image and page cache may not always remove session storage, but many browser cleanup tools clear several types of website data at once.

If session storage is removed, the privacy gate will appear again.

A visitor may believe they only cleared the cache when the browser also cleared site data.

The gate appears after changing website domain

Browser storage is tied to the website origin.

If the website changes from:

http://example.com

to:

https://example.com

or from:

example.com

to:

www.example.com

the browser may treat it as a different website.

The privacy gate acceptance saved under the old address will not necessarily apply to the new one.

HTTP and HTTPS are separate origins

The browser may treat these as separate storage locations:

http://example.com

https://example.com

Always use the final HTTPS website address consistently.

Check WordPress settings under:

Settings > General

Make sure the WordPress Address and Site Address use the correct HTTPS domain.

www and non-www can be separate

These may also be treated separately:

https://example.com

https://www.example.com

Use one preferred version and redirect the other to it.

Inconsistent website addresses can make the privacy gate appear again because the browser sees a different origin.

The gate appears after moving from staging to live

A staging website and a live website are separate origins.

For example:

staging.example.com

and:

example.com

Acceptance on the staging website does not carry over to the live website.

This is expected.

Test the privacy gate separately on the final live domain.

The gate appears on every page

The gate should normally remain accepted while the visitor moves around the knowledge base during the same session.

If it appears on every page or after every click, check whether session storage is being cleared or blocked.

Possible causes include:

• Browser privacy settings
• Security extensions
• Incorrect domain redirects
• HTTP to HTTPS switching
• www to non-www switching
• Cached pages using different addresses
• JavaScript errors
• Storage access being blocked
• Custom code clearing session data

Check for domain redirects

Open several knowledge base pages and watch the browser address bar.

Make sure the website does not switch between:

• HTTP and HTTPS
• www and non-www
• Main domain and staging domain
• Different language domains
• Different subdomains

A redirect between origins can make the saved session value unavailable.

Check WordPress site addresses

Open:

Settings > General

Review:

• WordPress Address
• Site Address

Both should use the correct live domain and HTTPS where available.

For example:

https://example.com

Avoid using one address with www and the other without it.

Check browser session storage

This step is intended for advanced users.

Open the browser developer tools and inspect the website’s session storage.

After accepting the privacy gate, a SoftwareRoad Knowledge Base session value should normally be present.

If it disappears immediately, something may be clearing the browser session.

Do not manually change storage values on a live visitor’s browser.

Use this only as a troubleshooting test.

JavaScript must be enabled

The privacy gate uses browser-side behaviour to store the temporary acceptance.

If JavaScript is disabled or broken, the gate may not remember that the visitor accepted it.

Check the browser Console for JavaScript errors.

A script error from another plugin or theme can stop the acceptance value from being stored.

Check the browser console

Open the browser developer tools and select the Console tab.

Accept the privacy gate and look for errors.

Possible causes include:

• JavaScript syntax errors
• Missing plugin scripts
• Content Security Policy restrictions
• Script optimisation errors
• Storage access being denied
• Another plugin stopping execution

One unrelated JavaScript error can sometimes prevent later scripts from running.

Test without optimisation

Performance tools can interfere with the privacy gate script.

Temporarily test without:

• Delayed JavaScript
• Deferred JavaScript
• Combined JavaScript
• Removed unused JavaScript
• Aggressive minification
• Script execution delay

Clear all caches and open a new private browser window.

If the gate begins working correctly, exclude the relevant SoftwareRoad Knowledge Base script from that optimisation.

Check Content Security Policy

A strict Content Security Policy can block scripts or browser storage behaviour.

Open the browser Console and look for CSP errors.

Review whether the policy allows:

• The plugin’s JavaScript
• Inline configuration where required
• Same-origin script execution
• Browser storage access

Update the policy carefully rather than weakening it across the whole website.

Check cookie and privacy tools

A cookie consent or privacy plugin may block scripts until the visitor accepts a separate consent banner.

This can result in two different gates:

• Website cookie or privacy consent
• SoftwareRoad Knowledge Base privacy policy gate

If the knowledge base script is blocked by the main consent tool, the gate may not remember acceptance.

Review the consent tool’s script categories and blocking rules.

The privacy gate and cookie banner are different

The SoftwareRoad Knowledge Base privacy gate is not the same as a cookie consent banner.

The privacy gate controls access to the knowledge base.

A cookie banner controls how the wider website handles cookies or tracking services.

Your website may use both, but they serve different purposes.

Avoid using identical wording for both because visitors may find it confusing.

Check custom code

Custom JavaScript may clear session storage.

Search custom theme code or snippets for methods such as:

sessionStorage.clear()

or code that removes all storage values.

A broad cleanup script can remove the SoftwareRoad Knowledge Base acceptance whenever a page loads.

Test custom code on a staging website before making changes.

Security plugins can affect storage

Some security tools can change browser behaviour by:

• Adding strict headers
• Blocking scripts
• Redirecting visitors
• Injecting challenge pages
• Preventing storage in embedded pages
• Isolating sessions

Review recent security changes if the gate started reappearing unexpectedly.

Embedded knowledge base pages

If the knowledge base is displayed inside an iframe or embedded on another domain, browser privacy restrictions may affect session storage.

Third-party storage rules are stricter in modern browsers.

SoftwareRoad Knowledge Base is intended to run directly on the WordPress website rather than inside an external iframe.

Open the knowledge base at its normal public URL for testing.

The gate appears after opening a direct article link

During a fresh browser session, opening a direct article link may show the privacy gate before the article.

This is expected if the visitor has not accepted it during that session.

Once accepted, the article should open and other knowledge base pages should remain accessible during the same session.

The gate appears after using a bookmark

A bookmark can open the knowledge base in a new browser session.

If the previous session has ended, the gate will appear again.

The bookmark itself is not broken.

The gate appears after a long period of inactivity

Some browsers may discard inactive tabs or end sessions to save memory.

Mobile browsers are particularly likely to close background sessions.

When the visitor returns, the gate may reappear.

This is controlled partly by the browser and device.

The gate appears after browser crash or forced shutdown

A browser crash, forced restart or device shutdown can end the session unexpectedly.

The temporary acceptance may be lost.

The visitor will need to accept the gate again.

The gate appears only for some visitors

Different visitors may use different:

• Browsers
• Privacy settings
• Extensions
• Devices
• Networks
• Website addresses
• Browser profiles

Ask affected visitors whether the gate appears:

• On every page
• Only after reopening the browser
• Only in private browsing
• Only on mobile
• Only after clearing data
• Only with one browser

This helps separate expected session behaviour from a genuine problem.

The gate appears only on mobile

Mobile browsers often clear background sessions more aggressively than desktop browsers.

The operating system may close the browser to save memory.

Other possible causes include:

• Mobile privacy settings
• In-app browsers
• Mobile cache
• Browser data cleanup
• App switching
• Different domain version
• Mobile-only JavaScript optimisation

Test in a normal mobile browser rather than inside a social media or email app browser.

In-app browsers

Links opened inside applications such as social media, messaging or email apps may use their own temporary browser.

The acceptance saved there may not carry over to the normal browser.

The next time the visitor opens the link, the in-app session may be new.

This is expected behaviour.

The gate appears only for administrators

Administrators may see a different page because of:

• Logged-in cache
• Admin toolbar
• Preview mode
• Page builder editor
• Role-based scripts
• Security extensions

Test while signed out in a private browser window.

The public visitor experience is the most important check.

The gate appears only for signed-out visitors

This may be normal depending on how the feature is intended to work.

Administrators may bypass or see different behaviour while managing the knowledge base.

Always test the public version while signed out.

The gate does not appear at all

If the privacy gate is enabled but does not appear, check:

• The setting is saved
• The visitor has already accepted it in the current session
• The page cache is not showing an old version
• The licence is active
• JavaScript is working
• The correct knowledge base page is being tested
• The article is public

Open a completely new private browser session to test it.

Clear session storage for testing

To test the gate again, close all private browser windows and open a new one.

You can also clear the website’s session storage through browser developer tools.

Do not ask normal visitors to do this unless troubleshooting requires it.

A new private session is usually the simplest test.

Check the active licence

The privacy access gate is part of SoftwareRoad Knowledge Base and requires an active Monthly or Yearly licence.

Open:

Knowledge Base > Licence

Confirm that the licence is active.

If the licence is inactive, the public knowledge base may display an unavailable message instead of the normal gate and content.

Clear caches after changing privacy settings

After enabling, disabling or editing the gate, clear:

• WordPress page cache
• Object cache
• Hosting cache
• Server cache
• CDN cache
• Browser cache

Then open a new private browser session.

A cached page may continue showing the previous privacy gate behaviour.

Change the privacy gate wording

Open:

Knowledge Base > Settings

Find the privacy access gate settings.

Depending on your plugin version, you may be able to edit:

• Gate heading
• Explanation text
• Privacy policy link
• Acceptance button wording

Keep the wording clear and concise.

Explain what the visitor is confirming before they continue.

Use a valid privacy policy link

Make sure the privacy policy page:

• Is published
• Opens publicly
• Uses HTTPS
• Does not return a 404 error
• Is not restricted by the gate itself
• Opens on the same website where possible

Visitors should be able to read the privacy policy before accepting.

Avoid putting the privacy policy behind the gate

If the privacy policy page itself is blocked by the knowledge base privacy gate, visitors may be unable to read the policy before accepting it.

Link to a normal public WordPress privacy policy page outside the protected knowledge base structure.

Explain the session behaviour where helpful

You may want to mention that acceptance lasts for the current browser session.

For example:

Your acceptance will remain active during this browser session.

This can reduce confusion when visitors return later and see the gate again.

There is no “remember me permanently” option

The privacy gate does not normally create a permanent acceptance cookie or server-side record.

It is designed to reset after the browser session ends.

This reduces the amount of persistent visitor information stored by the feature.

If your organisation needs permanent legal acceptance records, use a specialist system designed for that purpose.

Do not change browser storage manually for visitors

Avoid using unsupported custom code to force permanent acceptance without understanding the privacy and security implications.

Custom code could:

• Store the value longer than stated
• Conflict with privacy policy wording
• Break after plugin updates
• Fail in private browsers
• Create inconsistent behaviour
• Introduce security problems

Use the built-in session behaviour unless you have a clear technical and legal reason to change it.

Privacy gate worked before but now appears repeatedly

Review recent changes such as:

• Website domain change
• HTTP to HTTPS migration
• www redirect change
• Caching update
• JavaScript optimisation
• Security plugin update
• Content Security Policy change
• Cookie consent tool change
• Theme update
• Plugin update
• Browser extension installation

Test recent changes one at a time on a staging website where possible.

Test for a plugin conflict

On a staging copy:

1. Keep SoftwareRoad Knowledge Base active.
2. Disable other plugins temporarily.
3. Clear all caches.
4. Open a new private browser session.
5. Accept the privacy gate.
6. Visit several articles.
7. Check whether it stays accepted.
8. Reactivate plugins one at a time.

Pay particular attention to:

• Caching plugins
• Security plugins
• Privacy plugins
• Cookie consent tools
• JavaScript optimisation plugins
• Redirect plugins

Test for a theme conflict

On staging, switch temporarily to a standard WordPress theme.

Test the gate in a new private session.

If it works correctly, review the original theme for:

• JavaScript errors
• Session storage cleanup
• Redirects
• Custom privacy scripts
• Content Security Policy headers
• Page template differences

Reinstall plugin files

If the privacy gate script is missing or damaged:

1. Create a full WordPress backup.
2. Download a clean copy of SoftwareRoad Knowledge Base.
3. Replace or reinstall the plugin files.
4. Activate the plugin.
5. Confirm the licence.
6. Save the privacy gate settings.
7. Clear all caches.
8. Test in a new private session.

Do not uninstall plugin data unless you understand what will be removed.

A practical privacy gate test

Use this process to confirm normal behaviour:

1. Confirm the Monthly or Yearly licence is active.
2. Enable the privacy policy gate.
3. Save the settings.
4. Clear all page and server caches.
5. Close all private browser windows.
6. Open a new private browser window.
7. Visit the knowledge base.
8. Confirm the gate appears.
9. Open the privacy policy link.
10. Return and accept the gate.
11. Open several articles and categories.
12. Confirm the gate does not reappear during the same session.
13. Close all private windows.
14. Open a new private session.
15. Confirm the gate appears again.

This confirms the intended session-based behaviour.

When the behaviour is normal

The gate is working normally when it appears again after:

• The browser session ends
• All private windows are closed
• Browser storage is cleared
• A different browser is used
• A different device is used
• A different website origin is used
• The website moves from staging to live

When the behaviour may indicate a problem

Further troubleshooting is needed when the gate appears:

• On every page during the same session
• Immediately after acceptance
• After every article click
• Only because the domain switches between www and non-www
• With repeated JavaScript errors
• When session storage disappears instantly
• Only after enabling a particular caching or security feature

Contact SoftwareRoad support

Contact support if:

• The gate appears again on every page during the same session
• The website uses one consistent HTTPS domain
• Session storage is allowed
• JavaScript errors have been checked
• Caches have been cleared
• Plugin and theme conflicts have been tested
• The behaviour continues in a standard browser

Include:

• Website address
• Knowledge base page address
• SoftwareRoad Knowledge Base version
• WordPress version
• PHP version
• Browser and device used
• Whether the issue happens in private browsing
• Whether the gate returns immediately or after navigation
• Browser console errors
• Caching, security and privacy plugins in use
• Whether the website redirects between domain versions

Do not publicly share your full product key.

Privacy gate troubleshooting checklist

Before contacting support, check that:

• The privacy gate is enabled
• The Monthly or Yearly licence is active
• The privacy policy page is published and accessible
• Acceptance works during the same browser session
• A new browser session is expected to show the gate again
• Private browsing creates a separate session
• Different browsers and devices have separate storage
• Clearing browser storage removes acceptance
• The website uses one consistent HTTPS domain
• WordPress Address and Site Address match
• The website does not switch between www and non-www
• JavaScript is enabled
• Browser console errors have been checked
• Session storage is not blocked or cleared
• Caching and optimisation have been tested
• Security and privacy extensions have been considered
• Cookie consent tools are not blocking the gate script
• Plugin and theme conflicts have been tested on staging
• The gate has been tested in a fresh private session

The privacy policy gate will normally appear again whenever a new browser session begins because acceptance is stored temporarily in the visitor’s browser rather than as a permanent WordPress record.