The details, in plain language
JBR Invest LLC
Cookie policy
Information about JBRSignal and its automated website analysis service.
What this policy covers
This policy, dated 2026-09-06, covers browser storage used by the website and its payment interface. Cookies are small values a browser stores and sends with matching requests. They differ from information retained in the application database: deleting a cookie does not erase an order, report or support conversation. Some storage is needed to provide a requested function, while selected preferences help keep the interface consistent. The descriptions below concern implemented features, not a claim that every possible tracking technology is installed.
This notice applies to JBRSignal at jbrsignal.com and distinguishes storage set by this application from storage controlled by an embedded provider. A cookie can contain a session identifier or preference rather than the full information shown on a page. The identifier can still be relevant to privacy because the server may use it to associate requests with information stored elsewhere.
Other browser mechanisms are different from cookies. A browser can cache public images or style files, keep a history of visited URLs, and save a downloaded report as a file. These functions do not mean that the application has placed an advertising identifier in local storage. Our own public scripts do not use a separate localStorage or sessionStorage profile to track browsing behavior.
The visual light or dark theme is configured for the storefront by the operator. It is not currently a user theme preference stored in a new cookie. Your browser or device may apply its own display settings independently. The privacy notice describes server-side processing, while this page explains browser behavior relevant to using the interface. If you are trying to remove information rather than change how a page looks, choose the control that actually applies to that information.
Session and form-security cookies
The application uses a first-party session cookie to associate requests with a session, retain temporary form information and support staff authentication. Form-security tokens help reject forged submissions. Session expiry follows the configured application lifetime; choosing a staff remember-me option can create separate persistent authentication state. Blocking or deleting these cookies can sign staff out or interrupt a secure form. These browser mechanisms are not a public customer-account system: customer reports remain accessible through their private links, subject to the applicable access checks.
The configured first-party session cookie is named llc-signal-session. Its configured inactivity lifetime is 120 minutes; activity and server-side session handling can affect when a session expires. This is not the retention period for an order, an invoice or a downloaded report. A session can hold temporary validation messages, a saved checkout quote and the interface preferences used while moving between pages.
The session is also used for form-security checks. A form submission may be rejected if its security token no longer matches the active session, for example after you clear cookies or leave a page open for a long time. Reloading a form can establish fresh state, but check the existing order before repeating a payment. A form-security error does not prove that an earlier card authorization failed.
Administrative sign-in uses the application’s authentication state; a staff member who chooses remember-me can create a separate persistent authentication cookie. Ordinary customers do not need staff credentials to open a valid private report link. Blocking session cookies can interrupt forms even when public reading still works. These cookies support the requested interaction and security functions; they are not presented as permission to add unrelated analytics or advertising technology.
Language and currency preferences
When you save preferences, the application sets first-party cookies named locale and currency for the selections supplied. Each is set for up to one year and may be replaced when you save another selection. The preferences are also reflected in the current session. They remember interface language and browsing currency; they are not advertising identifiers. A currency change does not modify a saved order amount, invoice or payment. Clear the cookies in your browser if you do not want a selection remembered between visits.
Saving a language or currency selection sends that preference to the application and writes the corresponding first-party cookie. The cookies are named locale and currency, are scoped to the website path and are set for up to 525,600 minutes, approximately one year. Browser settings can remove them sooner. Saving a new choice replaces the relevant preference rather than creating a new paid order.
On a first visit without a saved preference, the interface starts in English and displays prices in USD. It does not use your IP address or browser language to select a different language or currency. A supported language explicitly selected in the URL is retained in the session for subsequent forms. A saved manual choice takes priority over the first-visit defaults. Only languages and currencies actually offered by the interface can be selected; this does not imply that every country has a separate storefront.
Preferences concern presentation. Changing them does not translate text you wrote in a support conversation, alter an already issued invoice or reprice an existing payment. A report retains its own generated content and order language. If you clear the preference cookies, the next visit may use another supported default. You can continue reading without deliberately saving a year-long preference; the session and requested form functions remain separate.
Stripe and the payment interface
The embedded payment form loads Stripe functionality when you open the payment step. Stripe may use cookies and related technology for secure payment, fraud prevention, authentication and continuity of the payment session, under its own policies. Its interface requires JavaScript. We do not describe provider-controlled cookie names or lifetimes as fixed application settings because those can vary with the payment flow. If browser restrictions prevent the form loading, your pending order is not proof of payment; check its confirmation status before attempting another payment.
Stripe functionality is loaded on the private payment page, where the card form is embedded. The application does not load the same payment script on every ordinary informational page. Requests made by that interface go to Stripe or related payment domains as required for the checkout, including authentication or an optional accelerated-payment feature when presented by Stripe.
The payment provider controls its own cookie and storage behavior. Its names, lifetimes and purposes can depend on the flow, device, region and choices made in the provider interface. Review Stripe’s published cookie and privacy information for those provider-controlled details. A browser may also recognize a payment identity previously saved with that provider; this does not mean JBRSignal has obtained your saved card number or created a public customer account for you.
Some browser privacy tools block embedded frames, scripts or payment cookies. If the form does not load, you can adjust the relevant site permissions if you choose, try another supported browser, or ask support. Do not disable security protections indiscriminately. A failed display is not a reliable payment-status check: reopen the saved order and wait for verified status rather than entering payment details repeatedly into newly created orders.
Optional tracking is not enabled
This public interface does not load advertising pixels, retargeting scripts or behavioral analytics scripts. It does not require acceptance of advertising cookies to run a scan or view a report. No general-purpose cookie-consent manager is claimed to exist. If optional tracking is introduced later, its purpose, provider information and applicable controls must be supplied before the relevant use. Marketing email preferences and the delivery events recorded by an email provider are separate from a browser preference cookie and do not create an advertising-cookie requirement.
The current public website does not include an advertising-cookie category that you must accept in order to request the service. No advertising pixels, remarketing tags or general behavioral-analytics scripts are loaded by our own public interface. A payment provider’s fraud-prevention functionality is a separate processing context and should not be described as if it were an advertising campaign operated by this storefront.
We do not infer agreement to future optional tracking merely because you read this page, use a private report link or accept the purchase terms. If a new feature requires consent for storing or accessing information on your device, the relevant information and controls need to accompany that feature. A policy update by itself is not a substitute for a legally required choice.
Server logs, application status records and email-delivery events can still exist without an advertising cookie. They are addressed in the privacy notice and do not automatically become anonymous simply because no analytics script is installed. Likewise, marketing permission and unsubscribe records concern communications to an email address. Clearing browser cookies does not withdraw that recorded permission; use the unsubscribe route or contact the operator when you want to stop marketing rather than only reset the current browser.
Managing browser storage
You can inspect, block or remove site cookies through the privacy or site-data settings of your browser. Controls vary by browser and device. Removing storage may reset language and currency choices or disrupt a form in progress; it does not cancel a purchase, reverse a payment or submit a data-deletion request. Use the private order conversation for billing issues and the data-request process for server-side records. Browser restrictions on third-party functionality can also affect Stripe, independently of cookies set by this website.
Browser settings commonly allow you to inspect site data, remove cookies for one domain, block third-party storage or delete data when a browser closes. The exact controls and their effects vary. Removing data for this storefront may not remove provider-controlled storage on a different domain, and clearing one device does not automatically clear another device that you use.
Private or incognito mode can limit what the browser keeps after the session, but it is not a guarantee that the website, your network, the payment provider or the destination website receives no information during use. Browser history, saved passwords, downloaded PDFs and cookies may be managed by different controls. Check the applicable browser instructions before removing data you need.
Before clearing storage during checkout, save the order reference or keep a safe copy of the private link. Do not put that link in a public note. After clearing storage, reopen the order to check its verified payment state rather than assuming the purchase disappeared with the cookie. For server-side access, correction or deletion, email using the instructions on the data-deletion information page. For a cancellation or billing concern, use the order or withdrawal process; those actions are not performed by a browser cleanup.
Questions and changes
Contact the operator if a cookie or browser-storage item appears inconsistent with this description. Where possible, provide its name, the page where it appeared and the browser used, but do not send session values, private-link tokens or payment details. We can distinguish application storage from provider-controlled payment functionality and investigate unexpected behavior. This policy will be revised when the implemented browser-storage functions materially change. It does not promise an analytics service, a consent dashboard or a privacy certification that the application does not provide.
To report unexpected browser storage, tell us the cookie or storage name, the domain shown by your browser, the page you were visiting and the approximate time. State whether you had opened the payment form, saved a preference or signed in as staff. Those details can help distinguish a requested feature from an unrelated browser extension or another site’s embedded functionality.
Do not copy the cookie value, authorization header, private report token or a full payment screenshot into a public message. Values that look like random characters can be access credentials. A redacted screenshot showing names and domains is usually more appropriate for an initial enquiry than an unfiltered network log. If more technical evidence is needed, ask how to supply it with unnecessary information removed.
The operator can review the application behavior and explain which party controls a particular function, but cannot change every setting of your browser or independently dictate Stripe’s cookie lifetimes. This notice will need revision when the application’s actual storage changes. The absence of a general consent dashboard is not a certification of compliance with every country’s storage rules. Applicable requirements for information, necessity and consent remain relevant to each implemented use.