Version 1.4 · Published October 15, 2026
Privacy Policy
1. Scope and responsible operator
This Privacy Policy explains how Beewip, the operator of beewip.com based in Puerto Rico, handles information in connection with its website, accounts, promotional campaigns, internal credits, payments, and support. It applies to information Beewip receives through its own services. Independent destination websites and payment-provider pages have their own operators and privacy practices. This policy does not represent those independent businesses. For questions about a particular transaction or a privacy request, use the contact form and identify the account or request involved without supplying your password, authentication token, full card number, or unnecessary sensitive documents.
2. Information you provide
Account information includes the email address, display name, password information, and account preferences you submit. Passwords are processed for authentication and stored as password hashes rather than as a customer-readable password field. Campaign information can include campaign names, destination URLs, selected categories, targeting choices, requested quantities, and related moderation communications. We also receive support messages, names and reply addresses supplied through support, and information you choose to include when reporting an error. Do not place confidential credentials or sensitive personal information inside a public campaign name, destination URL, or support message unless specifically necessary and requested through an appropriate secure process.
3. Activity and transaction records
Using the service can create records of campaign submissions, moderation decisions, task claims, completion requests, credit movements, account changes, and legal-document acceptance. Records may include account identifiers, timestamps, request context, technical characteristics, and the applicable document version or content hash. Orders and payment records may identify the provider, provider transaction reference, amount, currency, status, and relevant subscription period. These are not equivalent to a stored copy of your complete card details. We use the distinction between pending, confirmed, reversed, purchased, promotional, and earned amounts to administer the service and investigate inconsistencies.
4. Technical and security information
Our infrastructure and application can process IP addresses, network information, browser or user-agent details, request timestamps, error information, and session identifiers. Some application security records use hashed network identifiers, while ordinary infrastructure logs may contain network addresses needed to operate and protect the website. Hashing is a security measure and does not mean that every record is anonymous. Session records support authentication, expiration, revocation, and investigation of unauthorized access. We may relate technical events to an account when necessary to protect that account, investigate abuse, verify a transaction, or comply with a lawful obligation.
5. Purposes of processing
We use information to create and maintain accounts, authenticate users, display account activity, deliver requested campaigns, evaluate eligible tasks, maintain the credit ledger, process authorized orders, and provide support. We also use relevant records to prevent duplicate claims, investigate suspicious destinations, reconcile provider confirmations, address payment disputes, enforce published policies, and maintain reliable services. Public content and service-level statistics may help explain the platform, but publishing private account information is not necessary merely because someone purchases advertising. We do not treat account registration as unlimited permission to use private support messages for unrelated promotional purposes.
6. Grounds and choices
Depending on the circumstances and the law that applies, processing can be necessary to perform your requested service, comply with legal obligations, pursue legitimate security and operational interests, or carry out a choice for which consent is required. We do not claim that a single consent checkbox supplies every possible legal basis. You can decline to provide optional information, but missing information necessary for authentication, billing, or a support investigation can prevent the related function from being completed. Where processing genuinely depends on consent, withdrawal applies prospectively and does not automatically invalidate earlier lawful processing.
7. Hosting and operational providers
Beewip uses hosting, network, database, and operational infrastructure to make the website and its records available. Providers supplying those functions may handle the information necessary to deliver their contracted service, maintain infrastructure security, or meet legal requirements. Administrative access should be limited to operational need rather than made available to every website user. Information is not made public simply because it passes through hosting infrastructure. Where operational arrangements change in a way that materially affects the disclosures in this policy, we will update the policy instead of claiming that an unnamed new integration was already covered by a specific promise.
8. Email, payment, and optional integrations
When transactional email is enabled, the configured email service processes message recipients, delivery information, and the content needed for verification, password recovery, account notices, or a requested message. Stripe or PayPal may process payment information when that provider is actually offered and selected at checkout. A payment provider can act under its own privacy terms for fraud prevention and regulatory duties. A configured background queue may temporarily handle protected job data to deliver operational messages. An integration being listed in an administrative console does not mean it is active or has received your information. Provider availability and actual use determine the relevant processing.
9. Browser storage and measurement
Beewip uses authentication-related browser storage to support account access, including a first-party session cookie and a browser-local authentication token used by the client. The Cookie Policy explains their purposes and controls. Campaign and account measurements can also be generated from server-side records; rejecting an optional cookie does not necessarily eliminate records essential to fulfill a transaction or prevent fraud. Beewip does not describe an optional advertising pixel or cross-site tracking service as active merely because an administrator can configure integrations. If optional tracking is introduced, appropriate notice and any consent required by applicable law must precede its use.
10. Disclosure and external destinations
We disclose information when reasonably necessary to operational providers, a payment provider you use, authorized account representatives, or a recipient required by applicable law. Relevant evidence may be shared to address fraud, defend a legal claim, or investigate an authorized payment dispute, with attention to the information reasonably needed. Advertisers are not entitled to receive members' passwords, private messages, or authentication tokens. Visiting an advertised destination directly exposes your browser and network connection to that independent operator. The destination may receive its usual visit information or apply its own storage rules; read its policy before supplying personal information or making a purchase.
11. Retention and deletion
We retain information for periods reasonably related to its purpose, the life of the account or transaction, legitimate security needs, and applicable legal obligations. Different records can require different retention periods. Financial reconciliation, unresolved disputes, fraud prevention, and evidence of accepted legal terms may require retention after an account stops using the website. We do not promise that closing an account instantly deletes every backup, transaction, or audit entry. Information no longer reasonably needed should be deleted or appropriately deidentified through operational processes. A retention obligation does not authorize unrelated marketing or unlimited public disclosure of retained personal information.
12. Security and incident handling
Beewip uses measures such as protected connections, password hashing, authenticated access, restricted administrative functions, and session revocation to reduce risk. These measures do not create a guarantee that no intrusion, device compromise, or service error can occur. Protect your own email account and devices, use a strong unique password, and report unexpected account changes promptly. If an incident affects personal information, we will investigate and take steps appropriate to its nature, scope, and applicable legal requirements. Required notices will not be replaced by a general claim that all information was anonymous or that a provider is responsible for every part of the incident.
13. Requests, minors, and international access
Depending on applicable law, you may be entitled to request access, correction, deletion, information about disclosures, or other restrictions concerning your personal information. Submit requests through the contact form; these processes are handled through support rather than an assumed automatic export or deletion button. We may request proportionate verification and explain a lawful limitation on a request. The service is intended for adults eighteen and older, not for children. Report a suspected underage account so we can investigate. Accessing the website outside Puerto Rico can involve processing across jurisdictions, subject to protections and obligations actually applicable to the circumstances.
14. Changes and related policies
This policy is interpreted alongside the Terms of Service, but contractual language does not remove privacy rights that cannot legally be waived. We will publish a revised version when material practices change and provide additional notice or obtain consent where required. A change does not turn a previously undisclosed optional purpose into a necessary account function. When raising a privacy concern, describe the category of information involved and any support reference so we can locate the relevant records. You remain entitled to pursue a complaint or remedy available under applicable law, including contact with a competent authority where that right applies.
Verification records, connection IPs, and pending credentials
Before email verification, Beewip temporarily stores the requested email address, a password hash rather than a readable password, the proposed display name, the registration IP, browser information, verification-token hash, and references to the policies accepted with the request. This pending record does not grant access to the platform. The request expires 72 hours after its original creation, including when another verification email is requested. A cleanup process checks expired records every minute while the service is running and removes pending credentials from active storage. Expired links are rejected immediately based on their deadline.
For older incomplete accounts that already have linked legal or accounting records, Beewip can remove the original email and password hash, revoke access, and retain a de-identified internal record rather than destroy required records. This does not delete verified accounts. Restricted backups and legally required records may follow separate retention and rotation procedures; deletion from the active registration store is not a promise that every historical backup is rewritten immediately.
When registration is completed, its original connection IP is associated with the account. Successful sign-ins record the login IP, time, and browser information, and a session stores its connection IP. Security events also record IPs for failed or blocked sign-in attempts and math-check failures without storing the attempted password or math answer. Access-event rows are routinely removed after 90 days, and raw IPs in older session rows are cleared on the same maintenance schedule. The account's registration IP remains associated with that account for account-security purposes unless removed under an applicable retention or deletion process.
These records are available only through authorized account-security and administration functions; they are not published in member profiles. An IP may be shared by a household, workplace, proxy, or mobile network and is not conclusive proof of identity or wrongdoing. Registration is limited to the public email domains listed in the Terms of Service. An arithmetic challenge and a short-lived essential cookie help bind an attempt to the requesting browser; they are not used to create advertising profiles.
Optional public profiles, campaign measurement, and Beewip assistant
Member accounts, dashboards, email addresses, connection IPs, payment details, passwords, and private sessions are not public profile content and are not placed in Beewip's search-engine sitemap. A member may separately choose to publish a profile consisting only of their chosen public display name, description, and optional website link. Publication requires that member's explicit agreement and, for ordinary members, administrative approval. Members may disable publication in their profile settings; Beewip removes disabled profiles from its live website and generated sitemap, although third-party search engines may take additional time to update previously indexed copies. Profiles and outbound member website links remain subject to the Acceptable Use Policy and may be hidden following an abuse review.
When a campaign or member task is used, Beewip can record the destination opened through its tracking redirect, a pseudonymous tracking identifier, request metadata, approximate elapsed time, browser-reported visibility or media playback signals, declared task completion, and, where independently provided by an advertiser's server, a signed event identifier and duration. Browser reports and a timer alone are not evidence that an external platform recognized a view, installation, sale, or other conversion. Approved advertiser event callbacks may be checked against the campaign and task to review credit eligibility, detect duplicates, and attribute an optional app first-open event. The Traffic Quality Policy, Advertiser Terms, and Member & Rewards Terms explain the promotional rules and review process.
The optional Beewip assistant answers from published policies, published blog articles, approved public pages, public plan information, and other public platform material; it does not retrieve private account, session, credit, or payment records. A question typed into the assistant may be compared with that public information. If the administrator activates one AI provider, the question and selected public website excerpts are sent to that provider solely to select relevant published passages; the assistant displays exact Beewip excerpts and links, not a free-form provider answer. The current selected provider and available support channels are shown through the assistant settings. Do not submit passwords, payment details, secret keys, or other sensitive information in chat. Provider processing may be governed by that provider's terms and retention practices; the assistant remains available as an internal website search when no provider is activated. Contact Beewip through the contact form for privacy questions and requests.
Related policies and contact
Terms of Service · Cookie 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.