Cookie Policy
Effective date: 1 August 2026
Last updated: 2 August 2026
Table of Contents
- 1. About This Cookie Policy
- 2. What Are Cookies?
- 3. Similar Technologies
- 4. First-Party and Third-Party Technologies
- 5. Categories We Use
- 6. Strictly Necessary Technologies
- 7. Analytics Technologies
- 8. Advertising Technologies
- 9. Cloudflare Security and Turnstile
- 10. Payment-Related Technologies
- 11. Browser Storage Used by LetsGoSolar
- 12. Current Cookie and Technology Inventory
- 13. When We Request Consent
- 14. Cookie-Banner Choices
- 15. How to Reject Non-Essential Technologies
- 16. How to Change or Withdraw Consent
- 17. Browser-Level Controls
- 18. Third-Party Privacy Choices
- 19. International Processing
- 20. Changes to This Cookie Policy
- 21. Contact Us
1. About This Cookie Policy
This Cookie Policy explains how LETSGOSOLAR LIMITED, trading as LetsGoSolar, uses cookies and similar technologies when you visit or interact with letsgosolar.co.
It explains:
- What cookies and similar technologies are;
- The categories of technologies we use;
- Which technologies require your consent;
- How you can accept or reject non-essential technologies;
- How to change or withdraw your choices; and
- How to contact us about our use of these technologies.
This Cookie Policy should be read together with our Privacy Policy.
2. What Are Cookies?
Cookies are small text files that a website or service places on your browser or device.
Cookies may allow a website to:
- Recognise a browser or device;
- Remember choices;
- Maintain security;
- Prevent fraud and automated abuse;
- Understand how visitors use the website;
- Measure advertising performance; or
- Support a checkout or payment process.
Some cookies expire when you close your browser. These are commonly called session cookies.
Others remain on your device for a defined period or until you delete them. These are commonly called persistent cookies.
3. Similar Technologies
When this Policy refers to cookies, it also includes comparable technologies where appropriate, such as:
- Browser local storage;
- Session storage;
- Tracking pixels;
- Web beacons;
- Software development kits;
- Tags;
- Device or browser identifiers;
- Security tokens;
- Conversion identifiers; and
- Scripts that collect website-interaction information.
For example, Meta Pixel is not merely a traditional text cookie. It is a website tag that may collect interaction information and set or read browser identifiers.
4. First-Party and Third-Party Technologies
4.1 First-party technologies
First-party technologies are placed or stored under the LetsGoSolar website domain.
They may be created directly by LetsGoSolar or by a service provider operating through our domain.
4.2 Third-party technologies
Third-party technologies are provided by another organisation, such as:
- Google;
- Meta;
- TikTok;
- Cloudflare; or
- Paystack.
Those providers may receive information from your browser when their services are activated.
Their handling of information is also governed by their applicable privacy and cookie terms.
5. Categories We Use
We divide cookies and similar technologies into the following categories:
- Essential (strictly necessary);
- Analytics; and
- Advertising.
Separately from these consent categories, we keep two small first-party campaign-attribution records that are not consent-based: records used for our own order attribution and business reporting under legitimate interests. They are described in Section 11 and in our Privacy Policy.
6. Strictly Necessary Technologies
Strictly necessary technologies are required to:
- Load and operate the website;
- Maintain website security;
- Detect bots, fraud or malicious activity;
- Remember your cookie choices;
- Process checkout steps;
- Enable a payment requested by you;
- Maintain essential order information; or
- Provide another feature specifically requested by you.
These technologies cannot ordinarily be disabled through our cookie-settings panel because the website or requested service may not function properly without them.
Strictly necessary technologies are not used by LetsGoSolar for behavioural advertising.
They may be used without optional cookie consent where their use is genuinely necessary for website security, checkout, payment or another service requested by the visitor.
LetsGoSolar does not use a separate "Preferences" cookie category. Cookie-choice, checkout-step and other interface state needed to operate the website is remembered using the strictly necessary technologies described above, not an optional category.
7. Analytics and Aggregate Performance Technologies
Analytics technologies help us understand how visitors use the website.
They may collect information such as:
- Pages viewed;
- Approximate session duration;
- General traffic source;
- Browser and device type;
- General geographic area;
- Buttons or links selected;
- Website errors;
- Checkout-stage interactions; and
- Aggregated purchase or conversion events.
7.1 Cloudflare Web Analytics
We use Cloudflare Web Analytics for privacy-first aggregate traffic and performance measurement.
Cloudflare states that its Web Analytics beacon:
- Does not use or access cookies;
- Does not use or access localStorage or sessionStorage;
- Collects page-performance information, landing paths and referrer information;
- Receives a source IP address through normal HTTP request handling; and
- Discards that source IP address rather than storing it in its core analytics data.
Cloudflare Web Analytics is used for general site performance and traffic patterns and is not used by LetsGoSolar to create cross-site advertising profiles.
Because it does not place or access optional analytics cookies or browser storage, it is disclosed separately from the optional Google Analytics toggle.
7.2 Google Analytics 4
With Analytics consent, we use Google Analytics 4 for website analytics.
Google Analytics may use first-party browser identifiers such as:
_ga; and_ga_<measurement-id>.
Google Analytics cookies have a default expiration period of up to two years, although the duration may be changed through configuration, renewed when the visitor returns or limited by the browser.
Google Analytics 4 will not be loaded or activated until you consent to Analytics technologies.
Advertising-related Google storage and processing will remain disabled unless you separately consent to Advertising technologies.
Rejecting optional Analytics technologies will not prevent you from browsing the website or placing an order.
LetsGoSolar must not send your name, telephone number, email address, complete delivery address, card information or other direct customer identifiers to Google Analytics.
7.3 LetsGoSolar First-Party Analytics
With Analytics consent, we also use our own first-party analytics, run by LetsGoSolar on our own infrastructure. It exists so that we can answer basic questions about our own website β how many people visited, which pages and sections they looked at, which buttons they selected, and which campaign or referring website brought them β without depending on a third party for the answer.
It uses two first-party cookies, which are set only after you consent to Analytics technologies:
lgs_vidβ a random identifier that distinguishes one browser from another so repeat visits can be counted as one visitor rather than several. It expires 180 days after your most recent visit.lgs_sidβ a random identifier that groups the pages you view into a single visit. It is a browser-session cookie and is discarded when you close your browser. A visit is also treated as ended after 30 minutes without activity, or after 12 hours.
Both cookies are:
- Set only after Analytics consent. Before you consent, neither is created, no measurement request is made, and no record of your visit exists;
HttpOnly, so website scripts cannot read them;- Restricted to
letsgosolar.coitself and not shared with any subdomain; - Random values that mean nothing on their own, and are stored by us only in irreversible hashed form; and
- Not shared with Google, Meta or any other third party.
Through these cookies we record:
- The page you viewed, as its address without any query string;
- Whether you reached each main section of that page β the specifications, what it can power, user-generated content reward, the price, delivery, customer stories, the game, the order section, the campaign introduction, the campaign entry form, the campaign questions, the campaign prizes, the product introduction, the 3D product viewer, the customer video reviews, the lifestyle use cases, the trust and specifications summary, the WhatsApp appliance check, and the frequently asked questions. Only the name of the section is recorded, from that fixed list;
- Which button or link you selected, from a short fixed list β the order buttons, the WhatsApp contact link, and the warranty page. Only the name is recorded, from that fixed list;
- Whether you started the timed game, and whether that round was won or lost β nothing else about how you played;
- Whether the game invitation was shown, and how you responded β accepted or dismissed, and nothing else about the invitation;
- Whether you interacted with the product viewer β that you changed the viewing angle, not which angle or how many times;
- Which customer review video you played β an identifier for that video from a fixed list, and nothing else about the playback;
- Whether you used the solar calculator or started the generator β that you used them, not the values you entered or the results you saw;
- Whether you viewed or started the checkout β that it was opened or begun, not the information you entered;
- Which checkout step you progressed to β one of a fixed list of step names;
- Which checkout field you interacted with, and at which step β one of a fixed list of field names (your name, WhatsApp number, state, LGA, delivery method, or email), not the value you typed;
- Whether you started or submitted a campaign entry, or opened a campaign question β the step and, for a submitted entry, the platform you chose, but not the content you wrote;
- Whether the saved offer was shown or dismissed, and whether you saved the offer β which of the two ways it appeared (automatically after using the runtime calculator, or your own tap on the banner's button) and, for a saved offer, an identifier for the record created β not the email address or WhatsApp number you entered;
- Whether you opened the customer-story submission form, and whether you submitted the customer-story form β and, if you did, which kinds of media you included (photo, video, or both, from a fixed list) β not the files themselves, your name, or what you wrote;
- Which customer photo or video card you selected, or which customer-submitted video you played, in the customer-proof section β that you interacted with it, not which submission it was;
- Whether you shared your referral coupon, and how β by WhatsApp or by copying the code, from a fixed list of two β not the code itself or who you shared it with;
- Whether you entered a referral code at checkout β that a code was entered and accepted, not the code itself;
- How long you were actively on the page β rounded to whole seconds, where "active" means the page was visible and you interacted within the last minute;
- The approximate country you visited from;
- The campaign or referring website that brought you; and
- The time of each of the above, which is what makes them countable.
A section counts as reached once it has been on your screen for about a second. That means it was visible to you β not that you read it, understood it, or were interested in it.
We deliberately do not record your name, telephone number, email address, delivery address, form entries, IP address, browser User-Agent string, the query string of any web address, or any device fingerprint. We also do not record your discount code, your score or completion times in the game, your card or payment details, your precise location, anything you type, or any recording or replay of your screen. Where an advertising click identifier appears in a web address, it is used only to work out which channel the visit came from and is then discarded rather than stored.
Where we cannot determine how a visit arrived, we record it as
direct_or_unknown rather than assuming a source.
If you withdraw Analytics consent, lgs_vid and lgs_sid are expired and the
first-party analytics records associated with them are deleted. Rejecting or
withdrawing consent for optional Analytics technologies will not prevent you
from browsing the website or placing an order.
8. Advertising Technologies
Advertising technologies are used to:
- Measure advertising performance;
- Understand whether an advertisement resulted in a website visit or purchase;
- Build advertising audiences;
- Limit or improve advertising delivery;
- Retarget previous website visitors; and
- Improve the relevance of advertising.
We use Meta Pixel and TikTok Pixel for advertising measurement.
Meta Pixel may use identifiers including:
_fbp, which identifies a browser for advertising and analytics purposes; and_fbc, which may record information associated with a visit originating from a Meta advertisement.
These identifiers may remain for approximately 90 days, subject to Meta's configuration, browser restrictions and whether the relevant identifier is created. _fbc will generally be relevant only where a Meta click identifier is present.
Where you have consented to Advertising technologies, the values of _fbp and _fbc may also be sent to Meta by our servers when you submit an order, together with the order reference, the order value, the product ordered and your browser's user-agent information. This is the same advertising measurement described above, sent by a second route so that it is not lost to browser or network conditions.
If your browser holds no _fbc β for example because Meta Pixel did not load β we may instead construct one from the Meta advertisement click identifier recorded when you arrived on our website and the time we first recorded it, provided that click was within the previous 90 days. We do this only where you have consented to Advertising technologies, and never otherwise.
Meta Pixel will not be activated until you consent to Advertising technologies.
We also use TikTok Pixel for advertising measurement. TikTok Pixel may set or use first-party identifiers including:
_ttp, which identifies a browser for TikTok advertising measurement;ttcsidandttcsid_<pixel-id>, which group interactions within a TikTok session; andttclid, which may be set when you arrive from a TikTok advertisement.
These identifiers may remain for approximately 90 days or less, subject to TikTok's configuration and browser restrictions. ttclid will generally be relevant only where a TikTok advertisement click identifier is present in the web address.
TikTok Pixel will not be activated until you consent to Advertising technologies. TikTok's Automatic Advanced Matching and Enhanced Data Postback features are disabled. First-party cookies are enabled so that TikTok can attribute visits from TikTok advertisements.
Where you have consented to Advertising technologies, we may also send limited information to TikTok directly from our servers (the TikTok Events API) when a payment is verified, in addition to the information TikTok Pixel sends from your browser. What we send is limited to:
- That a purchase was verified;
- The order reference (used for deduplication so that TikTok counts each purchase once);
- The order value and currency;
- The address of our website without any query string;
- The
_ttpidentifier, where your browser supplied one at the time of payment; and - The
ttclid, where one was recorded when you arrived from a TikTok advertisement and it is within the 90-day attribution period.
We do not send your name, telephone number, email address, delivery address, IP address, external identifiers or anything else you typed.
If you withdraw Advertising consent while a prepaid checkout is open and payment has not yet been verified, the site associates the withdrawal with that checkout through the same payment-attempt capability cookie that identifies the checkout this browser opened. Where the association succeeds, the server-side purchase event that would otherwise be sent to TikTok when payment is verified is suppressed. If you withdraw consent from a different browser or device, or the capability cookie has been cleared or expired, the site cannot connect that withdrawal to the pending order and the purchase event may still be sent when payment is verified.
Rejecting Advertising technologies will not prevent you from accessing the website, placing an order or receiving customer support.
LetsGoSolar must not configure Meta Pixel, the server-side Meta Conversions API, TikTok Pixel or the TikTok Events API to transmit complete checkout-form contents, payment information, unrestricted text fields or complete delivery-address information.
9. Cloudflare Security and Turnstile
We use Cloudflare to help:
- Deliver the website;
- Protect it against malicious traffic;
- Detect bots;
- Apply rate limits;
- Prevent fraudulent submissions; and
- Maintain website availability and security.
We also use Cloudflare Turnstile to determine whether a website interaction is likely to have been made by a genuine visitor rather than an automated system.
Cloudflare security technologies are treated as strictly necessary because they protect the website, checkout forms and customer information.
Depending on the Cloudflare services and settings enabled, Cloudflare may use technologies including:
9.1 __cf_bm
Cloudflare may set __cf_bm where Bot Management or Bot Fight Mode is enabled.
It is used to support bot detection and ordinarily expires after approximately 30 minutes of continuous inactivity. Cloudflare generates this cookie independently for each protected website and states that it is not used to track a visitor between different Cloudflare customer websites.
9.2 cf_clearance
Cloudflare may set cf_clearance after a visitor successfully passes a security challenge or where Turnstile pre-clearance or another relevant Cloudflare configuration is enabled.
It stores proof that the challenge was passed so that the visitor is not repeatedly challenged.
Its duration depends on Cloudflare and LetsGoSolar configuration. It may not be created by every Turnstile interaction.
9.3 _cfuvid
Cloudflare may set _cfuvid where the corresponding rate-limiting feature is enabled.
It helps distinguish separate visitors who share the same internet address so that one visitor's activity does not unfairly affect another visitor's access.
Its use and duration depend on the Cloudflare rate-limiting configuration.
9.4 Other Cloudflare technologies
Cloudflare may temporarily use additional security cookies where services such as:
- Challenge Platform;
- Load Balancing;
- Always Online;
- Waiting Room; or
- Additional rate-limiting tools
are enabled.
LetsGoSolar will update the cookie inventory if additional Cloudflare functions that materially change the technologies used on the website are activated.
10. Payment-Related Technologies
Online payments are processed through Paystack.
When you choose to pay online, Paystack may use cookies, scripts, browser storage or comparable technologies to:
- Open and operate the secure payment interface;
- Maintain the payment session;
- Authenticate the transaction;
- Prevent fraud;
- Process the payment;
- Remember transaction state;
- Communicate with your bank or payment channel; and
- Complete or verify the transaction.
Paystack's checkout may require access to cookies or browser local storage. Blocking all third-party cookies or browser storage may prevent an embedded Paystack checkout from loading correctly.
Payment technologies necessary to complete the payment method you selected are treated as strictly necessary for that requested transaction.
When you start an online payment, LetsGoSolar also sets one of its own strictly necessary cookies, __Host-lgs_payment_attempt. It holds a random value that identifies the payment attempt you opened and nothing else β no name, email, address, order details or payment information. It is set with HttpOnly, so page scripts cannot read it, and it is only ever sent back to LetsGoSolar's own website.
Its purpose is to protect you if a price changes. If you leave a payment, later unlock a discount and place a replacement order, this cookie is how the website can be certain which earlier unpaid attempt belongs to you, so that attempt can be closed and any payment link already emailed for it stops working. Without it the website will not close the earlier attempt at all; it simply leaves it alone, and your replacement order is unaffected either way.
Paystack controls the names, functions and durations of technologies used within its hosted or embedded payment environment. These may change as Paystack updates its payment and security systems.
LetsGoSolar does not use Paystack's necessary transaction technologies for its own behavioural advertising.
11. Browser Storage Used by LetsGoSolar
LetsGoSolar may use browser local storage to show a limited order-confirmation summary on the thank-you page.
The stored record may include:
- Order identification number;
- First name;
- Delivery method;
- Product subtotal; and
- Order creation date.
The complete customer address, telephone number, email address and full order record should not be stored in browser local storage.
The limited order-confirmation record should be configured to expire or be removed after 30 days.
Because browser local storage is not always automatically deleted when a browser session ends, you may clear it through your browser's site-data settings.
Deleting this browser record will not delete the official order record retained by LetsGoSolar.
If you win the Pack the Box game, LetsGoSolar may store a short-lived first-party record containing the discount code, issue time and expiry time so the code can be pre-filled in checkout. This record supports a feature requested by the visitor, should not contain complete customer contact or delivery information and should expire no later than five hours after the code is issued.
LetsGoSolar also stores two small first-party campaign-attribution records in browser local storage, lgs_attribution_first_touch and lgs_attribution_last_touch. They are written only when you arrive with campaign information in the web address, and they record the first and the most recent such arrival. Each holds the campaign parameters and advertising click identifiers from that address (including TikTok's ttclid where present), the landing address, the referring address and the time it was captured. They do not hold your name, contact details, delivery address or anything you typed. Recording ttclid in our own first-party attribution is a separate activity from sending it to TikTok: the attribution record exists for our own order-attribution and reporting, while the ttclid value is only sent to TikTok where Advertising consent is in effect and has not been withdrawn.
These two records are kept under legitimate interests so that an order can be attributed to the campaign that produced it. They are not an essential technology and they are not governed by your Analytics or Advertising choice, so they are limited by time instead: each record is deleted automatically 90 days after the visit that created it, and the website removes any record older than that the next time it loads. You may also clear them yourself at any time through your browser's site-data settings.
If you place an order, the attribution information current at that moment is copied into that order's business record. That copy is part of the order record and is retained under our order-retention rules, described in the Privacy Policy; deleting the browser records does not remove it.
12. Current Cookie and Technology Inventory
The following table describes the technologies expected from the planned website configuration as at the effective date of this Policy.
The actual cookies present may differ depending on:
- The visitor's choices;
- Browser settings;
- Cloudflare security events;
- Whether the visitor begins a payment;
- Provider configuration; and
- Future service updates.
| Name or technology | Provider | Category | Purpose | Expected duration |
|---|---|---|---|---|
| Cookie-consent preference record | LetsGoSolar | Strictly necessary | Remembers whether the visitor accepted or rejected optional categories | Retained for a reasonable period and refreshed when preferences change or consent is requested again |
| Limited order-confirmation local-storage record | LetsGoSolar | Strictly necessary | Displays limited order details on the thank-you page | Up to 30 days |
lgs_checkout_draft (browser sessionStorage, not a cookie) |
LetsGoSolar | Strictly necessary | Temporarily remembers the contact and delivery information you typed into checkout, so it can be restored if you return from the payment flow. It is not used as payment authority, nor as proof of identity or of who an order belongs to | Valid for up to 60 minutes, and may be cleared earlier when the checkout completes or a new checkout journey begins. Because it is sessionStorage, closing the tab, window or browser session may remove it sooner, depending on your browser |
| Pack the Box discount eligibility record | LetsGoSolar | Strictly necessary for the requested game-discount feature | Remembers the issued code and expiry so it can be pre-filled in checkout | Up to 5 hours after issue |
__cf_bm |
Cloudflare | Strictly necessary | Bot detection and website protection, where enabled | Approximately 30 minutes after inactivity |
cf_clearance |
Cloudflare | Strictly necessary | Records that a security challenge was passed, where applicable | Depends on Cloudflare and LetsGoSolar configuration |
_cfuvid |
Cloudflare | Strictly necessary | Supports rate limiting for visitors sharing an internet address, where enabled | Depends on Cloudflare configuration |
| Turnstile token and security signals | Cloudflare | Strictly necessary | Validates forms and detects automated or abusive activity | Short-lived or session-related; cf_clearance may apply if pre-clearance is enabled |
| Paystack checkout cookies, scripts and browser storage; names may vary | Paystack | Strictly necessary when online payment is selected | Operates, authenticates and secures the requested payment | Determined by Paystack and transaction requirements |
__Host-lgs_payment_attempt |
LetsGoSolar | Strictly necessary when online payment is selected | Set only after an online payment is started. Lets the website recognise the payment attempt this browser opened, so that if the customer returns and places a replacement order at a different price, the earlier unpaid attempt can be closed and its payment links withdrawn. It contains a random value with no personal information, cannot be read by page scripts, and is never shared with Paystack or any other third party | Up to 6 hours after the payment is started |
| Cloudflare Web Analytics beacon | Cloudflare | Cookie-free aggregate performance analytics | Measures page performance, landing paths and referrers without using browser storage | Current page request; performance data is ephemeral |
lgs_vid |
LetsGoSolar | Optional Analytics | Distinguishes browsers so repeat visits are counted as one visitor, in LetsGoSolar's own first-party analytics, after Analytics consent | 180 days from the most recent visit |
lgs_sid |
LetsGoSolar | Optional Analytics | Groups the pages viewed in one visit, in LetsGoSolar's own first-party analytics, after Analytics consent | Until the browser is closed; a visit also ends after 30 minutes of inactivity or 12 hours |
_ga |
Google Analytics | Optional Analytics | Distinguishes website visitors for statistical measurement after Analytics consent | Default up to two years; configurable and browser-dependent |
_ga_<measurement-id> |
Google Analytics | Optional Analytics | Maintains GA4 session and property information after Analytics consent | Default up to two years; configurable and browser-dependent |
_fbp |
Meta | Optional Advertising | Identifies a browser for advertising measurement and analytics after Advertising consent; the value may also be transmitted to Meta by our servers as part of the same measurement | Approximately 90 days, subject to provider and browser controls |
_fbc |
Meta | Optional Advertising | Records information associated with a Meta advertisement click after Advertising consent, where applicable; the value may also be transmitted to Meta by our servers as part of the same measurement | Approximately 90 days, subject to provider and browser controls |
_ttp |
TikTok | Optional Advertising | Identifies a browser for TikTok advertising measurement after Advertising consent; the value may also be transmitted to TikTok by our servers when a purchase is verified | Approximately 90 days, subject to provider and browser controls |
ttcsid / ttcsid_<pixel-id> |
TikTok | Optional Advertising | Groups interactions within a TikTok session after Advertising consent | Session-duration, subject to provider controls |
ttclid |
TikTok | Optional Advertising | Records a TikTok advertisement click identifier after Advertising consent, where applicable | Approximately 90 days, subject to provider and browser controls |
lgs_attribution_first_touch (browser localStorage, not a cookie) |
LetsGoSolar | Not a consent category; kept under legitimate interests | Records the first arrival that carried campaign information, so an order can be attributed to the campaign that produced it. Holds campaign parameters, advertising click identifiers, the landing address, the referring address and the capture time only β no name, contact details, delivery address or form entries | Maximum 90 days from the visit that created it, then deleted automatically |
lgs_attribution_last_touch (browser localStorage, not a cookie) |
LetsGoSolar | Not a consent category; kept under legitimate interests | As above, for the most recent arrival that carried campaign information | Maximum 90 days from the visit that created it, then deleted automatically |
The Cookie Settings panel should display the actual technologies detected in the live production environment.
A technology should not be added to the website without being:
- Classified;
- Added to the applicable inventory;
- Assessed for consent requirements; and
- Described in this Policy or the Cookie Settings panel where appropriate.
13. When We Request Consent
We request consent before activating non-essential:
- Analytics technologies; and
- Advertising technologies.
Consent must be given through a positive action.
The website must not treat:
- Silence;
- Continued browsing;
- Closing the banner;
- A pre-selected option; or
- Failure to change default settings
as consent to Analytics or Advertising technologies.
Strictly necessary technologies remain active because they are required for website security, checkout, payments, consent management or another service requested by the visitor.
14. Cookie-Banner Choices
When you first visit the website, the cookie banner should provide clear choices to:
- Accept all optional categories (the button labelled Accept All & Munch);
- Continue with strictly necessary technologies only (the button labelled Essential Only); or
- Manage choices by category (the control labelled Choose My Cookies).
The essential-only option should be reasonably easy to find and use.
Google Analytics, Meta Pixel and advertising-related Google technologies must be switched off by default until the visitor makes the relevant affirmative choice. Cloudflare Web Analytics is disclosed separately because it does not use or access optional cookies or browser storage.
The visitor must be able to use the core website and checkout after rejecting Analytics and Advertising technologies.
15. How to Reject Non-Essential Technologies
You may reject non-essential technologies by selecting:
Essential Only
on the cookie banner. Closing the first cookie prompt with the X control or the Escape key has the same effect: only strictly necessary technologies remain active.
You may also open Choose My Cookies (also reachable later through the footer Preferences control) and save your choices with the Analytics and Advertising categories left disabled.
Rejecting optional technologies means that LetsGoSolar will not activate Google Analytics 4, Meta Pixel, TikTok Pixel or advertising-related Google measurement for that browser unless you later change your choice. Cloudflare Web Analytics may continue to provide disclosed cookie-free aggregate performance measurement.
16. How to Change or Withdraw Consent
You may change or withdraw your choices at any time through the Cookie Settings link or panel.
The Cookie Settings link should be accessible from:
- The cookie banner;
- The website footer or another permanent website control;
- This Cookie Policy;
- The Privacy Policy; and
- The Cookie Settings panel.
Withdrawing consent:
- Does not affect processing that occurred lawfully before withdrawal;
- Prevents future activation of the rejected categories on that browser;
- Should remove first-party analytics or advertising cookies that LetsGoSolar can technically remove;
- May not automatically delete information already received and retained by a third-party provider; and
- If you withdraw Advertising consent while a prepaid checkout is open and payment has not yet been verified, and the withdrawal can be associated with that checkout through the payment-attempt capability cookie in this browser, suppresses the server-side TikTok purchase event that would otherwise be sent when that payment is verified.
You may also clear existing cookies and site data through your browser.
If you use another browser, device or browser profile, you may need to set your preferences again.
Deleting the consent-preference record may cause the cookie banner to be shown again.
17. Browser-Level Controls
Most browsers allow you to:
- View stored cookies;
- Delete individual cookies;
- Delete all site data;
- Block first-party or third-party cookies;
- Block cookies from selected websites;
- Clear data when the browser closes; or
- Restrict browser local storage.
The location and name of these controls depend on the browser and device.
Blocking all cookies or browser storage may interfere with:
- Security checks;
- Checkout;
- Paystack payment functionality;
- Cookie-consent storage;
- Order-confirmation display; and
- Other website features.
Browser controls operate separately from the LetsGoSolar Cookie Settings panel.
18. Third-Party Privacy Choices
Google, Meta, TikTok, Cloudflare and Paystack may provide their own privacy, advertising or cookie controls.
Using a provider's control may affect that provider across multiple websites or services.
Using the LetsGoSolar Cookie Settings panel controls whether LetsGoSolar activates the relevant optional technology on our website. It does not necessarily change settings held directly in your Google, Meta, TikTok, browser, bank or Paystack account.
19. International Processing
Google, Meta, TikTok, Cloudflare and Paystack may process cookie, device, security, analytics or payment information outside Nigeria.
Further information about international processing, service providers and safeguards is provided in our Privacy Policy.
20. Changes to This Cookie Policy
We may update this Cookie Policy where:
- We add or remove a website technology;
- A provider changes its cookies or retention periods;
- We change our analytics or advertising configuration;
- We add a consent-management platform;
- Cloudflare security settings change;
- The Paystack checkout implementation changes; or
- Legal or regulatory requirements change.
The updated version will be published on this page with a revised effective date.
Where a change materially expands non-essential tracking, we will request new consent where appropriate.
21. Contact Us
Questions, complaints or requests concerning cookies and similar technologies may be directed to:
LETSGOSOLAR LIMITED
Trading as LetsGoSolar
Registered business address:
6, Emmanuel Folorunsho Street
Badore, Ajah
Lagos, Nigeria
Email: hello@letsgosolar.co
WhatsApp: +234 901 325 5928
Website: letsgosolar.co
Use the email subject line:
Cookie or Privacy Enquiry