Version 1.3 · Published October 15, 2026
Cookie Policy
1. Purpose and scope
This Cookie Policy describes browser cookies, local storage, and related storage practices used in connection with beewip.com. Beewip operates the website from Puerto Rico. This policy should be read with the Privacy Policy and Terms of Service. Its purpose is to explain actual storage functions and the choices available to visitors and account holders. A cookie notice is not permission to run every possible analytics or advertising technology, and an integration appearing in an administrative list is not evidence that the integration sets cookies or processes visitors' information.
2. How browser storage works
A cookie is a small item stored by a browser for a website and sent back with requests according to its scope and security settings. Browser local storage is a separate mechanism that allows a website's client code to save information on that website's origin. Unlike a cookie, local storage is not automatically attached to every network request. Storage can support account continuity, protection against unauthorized actions, or optional preferences. Its legal classification depends on its actual purpose, not on whether a developer calls it a cookie, token, preference, or security feature.
3. First-party authentication cookie
The production account system uses a first-party cookie named __Host-beewip_session to carry the authentication token used for an account session. It supports access to protected account and administrative pages and allows the server to recognize an authorized session. In production, the cookie is configured with Secure and HttpOnly protections, a root path, and a SameSite setting intended to support ordinary first-party use while restricting some cross-site contexts. HttpOnly means ordinary website scripts cannot directly read the cookie value. These settings reduce certain risks; they do not guarantee that a compromised browser, device, or authorized session can never be misused.
4. Local authentication storage
The browser client also uses a local storage item named beewip_token for authenticated application requests. It contains an authentication token rather than your plain-text password or full payment-card information. Code running with access to the website's origin can access local storage, so it must be treated as sensitive session material. Do not copy it into a public message, give it to someone offering account help, or leave an authenticated browser available to another person. Clearing local storage removes the stored client value, but it does not automatically erase server-side transaction history or cancel an independently active subscription.
5. Duration, expiration, and sign-out
The authentication cookie expires according to the lifetime assigned to the issued session or when the browser clears it. The account server also checks session status and expiration; a retained token does not grant permanent access. Local storage can remain on a device until the application or browser removes it, but a token stored there becomes unusable when its server-side session is expired or revoked. Signing out is intended to revoke the applicable server session and remove the client's authentication storage. Password and session controls can be used to address other active sessions. Closing a browser window alone should not be assumed to sign out every persistent session.
6. Necessary storage and available services
Authentication storage is used for functions you request when you sign in and access a protected account. Disabling it can prevent protected pages from opening, interrupt an authenticated action, or require another sign-in. Public pages and policies do not require an account merely to read their content. Necessary account storage should not be repurposed as undisclosed advertising consent. If a feature cannot operate because you have blocked required storage, Beewip may explain the limitation, but it will not treat that technical limitation as authorization to activate an unrelated optional tracker.
7. Optional analytics and marketing technology
Beewip does not characterize optional advertising pixels, behavioral profiling, or cross-site analytics as necessary simply because they can be useful to a website operator. At the publication of this policy, the website's account and campaign records should not be confused with a consent-based third-party advertising-cookie program. If optional measurement or marketing technologies are introduced, Beewip must describe their actual purposes and provide the consent or choice mechanism required by applicable law before collecting information on that basis. This policy does not promise a cookie preference dashboard where no optional categories are being offered or activated.
8. Server-side records are different
Campaign accounting, credit transactions, order confirmation, session revocation, and abuse prevention can create server-side records even when a visitor clears browser storage. Those records are not cookies on the visitor's device. A credit ledger may need to identify a completed task or verified purchase to avoid counting the same event twice. Infrastructure may also retain network and error information needed to operate the service. Removing a cookie does not itself delete these records, reverse a payment, withdraw a legal acceptance, or prove that an activity never occurred. The Privacy Policy describes the associated purposes and retention principles.
9. Payment-provider storage
When an enabled checkout redirects you to Stripe, PayPal, or another expressly offered provider, that provider can use its own cookies or similar technologies on its services for authentication, payment completion, security, and fraud prevention. These technologies are governed by the provider's notices and actual checkout experience. Beewip does not set a provider's terms or promise that a provider will process a payment without its necessary security checks. A provider name shown in Beewip's configuration interface does not mean that provider has set a cookie in your browser. A payment that has not been independently confirmed is not converted into a completed purchase by storing a browser value.
10. Storage on advertised destinations
Clicking or visiting an advertised destination creates a connection to an independent website. That site can receive ordinary request information and apply its own cookies, storage, and tracking choices. Beewip's approval of a campaign does not mean it controls every change made by that destination or has granted consent on your behalf. Review the destination's notices before providing information, accepting optional tracking, downloading software, or completing a purchase. Advertisers must not use a Beewip campaign to conceal tracking, evade a user's storage choices, or force unrelated consent as a condition of recording an activity that does not require it.
11. Browser and device controls
Most browsers allow you to inspect site data, delete cookies, clear local storage, block selected storage, or use a private browsing session. Instructions and available controls vary by browser and device. To remove Beewip browser data, use the browser's site-data settings for beewip.com and consider signing out first. Shared-device users should sign out, close account pages, and avoid saving credentials on a device they do not control. Blocking all storage can affect other websites as well as Beewip. Private browsing does not prevent a destination, network provider, or payment service from receiving the information needed for the connections you initiate.
12. Consent, withdrawal, and signals
Where applicable law requires consent for a nonessential technology, Beewip must obtain that consent before using the technology for the relevant purpose. Consent must not be inferred solely from accepting a paid order, refusing a support request, or remaining on a page. Withdrawal affects future optional processing and does not automatically eliminate records lawfully retained for payment, security, or legal purposes. Browser privacy signals and preference settings will be handled to the extent required by the laws and technologies actually applicable. This policy does not claim that every browser signal produces an account-wide deletion or that a control exists when it has not been implemented.
13. Security, reports, and policy changes
Report unexpected account access, suspected unauthorized storage, or a concern about a destination through the contact form. Describe the page, approximate time, browser, and storage item involved without sending the item's authentication value. We may request additional nonsecret information to reproduce a problem. When storage practices materially change, Beewip will revise this policy and any required notice or control rather than rely on a generic statement that every technology might be used. The laws of Puerto Rico and applicable United States federal law inform the operator's obligations, without limiting mandatory protections available to users in other applicable jurisdictions.
Essential registration and sign-in challenge cookie
The production website uses an additional essential cookie named __Host-beewip_math when a registration, sign-in, or verification-resend math challenge is requested. It contains a random browser-binding value, not the answer, password, email address, or authorization to access an account. It is restricted to the website host and root path, marked Secure and HttpOnly, and uses SameSite=Lax. Its browser lifetime is ten minutes from issuance. The associated server challenge expires after five minutes and can be used only once for its designated action. Expired challenge records are removed by routine cleanup.
This cookie supports security checks requested through the account forms. It is not an advertising cookie and cannot create an authenticated session. A pending registration does not receive dashboard access, an account bearer token, or the authenticated session cookie merely for submitting a form. Those access credentials are issued only when an eligible, verified account successfully signs in. Blocking the essential challenge cookie can prevent the affected form from working; request a new challenge after enabling the necessary site storage.
New verification messages place their confirmation token in the email link's URL fragment rather than its query string. Browser scripts read that fragment to prepare the confirmation action and remove it from the visible page address. The fragment is not sent as part of the initial HTTP page request. The token is submitted to Beewip only when the recipient presses the confirmation button, and it is not saved in local storage by the verification page. Refreshing the page may therefore require reopening the original email link. No automatic account activation occurs merely because a mail scanner retrieves the landing page.
Related policies and contact
Terms of Service · Privacy Policy · Advertiser Terms · Member and Rewards Terms · Traffic Quality Policy · Billing and Subscription Terms · Refund Policy · Acceptable Use Policy · Contact Beewip
Last updated on October 15, 2026.