=== SevenSS Cookie Consent ===
Contributors: 7thStreetSystems
Tags: cookie notice, cookie consent, cookie banner, privacy, script blocking
Requires at least: 6.0
Tested up to: 7.0
Requires PHP: 7.4
Stable tag: 1.0.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

A lightweight cookie notice and consent plugin for WordPress, built for simple setup, respectful visitor choices, and optional script management.

== Description ==

7SS Cookie Consent helps WordPress site owners add a clean cookie notice to their website without adding a heavy compliance dashboard or forced front-end branding.

The plugin includes two modes:

* Simple Acknowledgment Notice: shows a basic cookie message with one acknowledgment button. This is the default mode and the recommended starting point for most sites.
* Full Consent Controls: shows Accept, Reject, and Customize options. Optional scripts added through the Script Manager can be held until a visitor allows the related category. When adding scripts manually, paste the complete snippet including the opening and closing <script> tags.

7SS Cookie Consent is designed to be straightforward, lightweight, and honest about what it does. It provides tools for cookie notices, visitor choices, and script management. It does not claim to automatically identify or control every script, cookie, or privacy requirement on a site.

= Features =

* Simple acknowledgment notice mode
* Full consent controls with Accept, Reject, and Customize options
* Analytics and marketing Script Manager
* Bottom banner, floating corner card, and center modal layouts
* Auto-match theme styling mode
* Light, dark, and custom color options
* Optional footer Cookie Settings link
* Manual preferences shortcode: [sevenss_cookie_settings]
* No forced front-end branding

= Recommended starting point =

Start with Simple Acknowledgment Notice while you review your site and decide which optional scripts should be managed.

Switch to Full Consent Controls after adding analytics or marketing scripts to the Script Manager.

This helps avoid giving visitors the impression that optional scripts are being managed before the plugin has been configured to manage them.

= Script Manager =

The Script Manager is where site owners can place optional tracking or marketing scripts that should only run after visitor consent.

Examples may include:

* Google Analytics
* Meta Pixel
* Microsoft Clarity
* Hotjar
* ad tracking scripts
* remarketing scripts

Scripts added through the Script Manager are changed to non-executing scripts until visitor consent allows the selected category.

Important: 7SS Cookie Consent controls scripts added through its Script Manager. It does not automatically identify, remove, or control every script loaded by your theme, another plugin, embedded services, or third-party code.

= Privacy and legal note =

7SS Cookie Consent is a privacy and consent tool. It is not legal advice and does not guarantee compliance with any specific privacy law. Site owners are responsible for reviewing their website, privacy policy, scripts, and legal obligations.

== Installation ==

1. Upload the plugin ZIP through Plugins > Add New > Upload Plugin, or install it from the WordPress Plugin Directory when available.
2. Activate the plugin.
3. Go to Settings > 7SS Cookie.
4. Start with Simple Acknowledgment Notice, or switch to Full Consent Controls after configuring the Script Manager.
5. Test your banner and script behavior in a private/incognito browser window.

== Frequently Asked Questions ==
= What should I paste into the Script Manager? =

Paste the complete non-essential script snippet from your analytics, marketing, or tracking provider. Include the opening and closing script tags, for example:

`<script>
/* your optional script here */
</script>`

Scripts added to the Script Manager are only controlled in Full Consent Controls mode.

= Why do I see two Cookie Settings buttons? =

If the auto footer preferences link is enabled and you also place the `[sevenss_cookie_settings]` shortcode on the same page, the plugin will suppress the auto footer button on that page so the visitor only sees one manual preferences button.


= Does this plugin automatically block every cookie on my site? =

No. 7SS Cookie Consent controls scripts added through its Script Manager. It does not automatically scan, remove, or control every script that may be loaded by your theme, plugins, embeds, or third-party services.

= What mode should I use first? =

Simple Acknowledgment Notice is the default and recommended starting point. Use Full Consent Controls after you add optional analytics or marketing scripts to the Script Manager.

= What happens when a visitor rejects non-essential cookies? =

In Full Consent Controls mode, scripts added to rejected categories in the Script Manager stay blocked.

= What happens if a visitor changes their mind? =

Visitors can reopen preferences using the optional footer link or the [sevenss_cookie_settings] shortcode. Updated preferences are saved and apply on future page loads. If scripts were already loaded on the current page, a reload is the cleanest way to fully apply the new choice.

= Does the plugin add public 7SS branding to my site? =

No. 7SS Cookie Consent does not add a forced “Powered by” badge or public branding to your visitor experience.

= Is this legal advice? =

No. This plugin provides cookie notice and consent tools, but it is not legal advice and does not guarantee legal compliance.

== Screenshots ==

1. Simple Acknowledgment Notice mode displays a clean cookie message with one acknowledgment button.
2. Full Consent Controls mode lets visitors accept, reject, or customize optional script categories.
3. Visitors can review and update optional cookie/script categories from the preferences panel.
4. The settings screen keeps cookie mode, layout, and style options in one simple place.
5. The Script Manager lets site owners add optional scripts that should only load after visitor consent.
6. The optional footer link and shortcode let visitors reopen cookie settings later.

== Changelog ==

= 1.0.0 =
* Initial public release.
