BuildWithPXLAI Agent Launchpad ↗
HomeWorkspaceInfoAboutContactPricing
Sign in

BuildWithPXL Privacy Policy

Effective Date: October 13, 2026

1. Who this policy covers

PXLWorld LLC, a Texas limited liability company, operates BuildWithPXL. This Privacy Policy describes how we handle personal information in connection with the website, Workspace, client portals, AI Agent Launchpad, custom-build services, and related support.

The Services are intended for adults age 18 or older and business-oriented users. We do not intend to collect children’s information or create child accounts.

2. Information we may handle

  • Account, identity, profile, contact, support, and service-request information that you provide.
  • Client Content, including Workspace messages, files, prompts, generated materials, client-portal information, and information submitted through forms or intake flows.
  • Connected-account information and content when you authorize a third-party connection, limited by the applicable connection, permissions, and feature.
  • Voice and recording information when a feature or cohort recording is used with the applicable participant consent. Group recordings are available only to participants in that cohort, and one-on-one recordings are available only to the instructor and the relevant participant for 12 months after the cohort ends. Consent to record group or one-on-one sessions is separate from explicit permission for marketing use of either type of recording.
  • Payment, billing, subscription, and entitlement information received from payment providers; we do not need to receive full payment-card numbers to provide the Services.
  • Device, browser, request, security, cookie, and service-use information used to operate, secure, troubleshoot, and improve the Services.

3. How we use information

  • Provide, support, secure, maintain, and improve requested Services and customer access.
  • Process transactions, subscriptions, PXLS, course enrollment, service communications, and support requests.
  • Operate requested AI, voice, file, client-portal, and connected-tool features, subject to the applicable feature and provider boundaries.
  • Prevent fraud, abuse, unauthorized access, and other security incidents; comply with applicable legal, accounting, tax, dispute, and recordkeeping obligations.
  • Send transactional or service communications. Optional promotional emails are sent only with a separate opt-in and are separate from transactional communications; marketing measurement is handled separately from necessary service functions.

BuildWithPXL does not use private Client Content to train BuildWithPXL models or populate another client’s service. Necessary processing by authorized providers to deliver a requested feature is distinct from that policy.

4. Client relationships and authority

For a business client, the client may determine why and how information in its Workspace or client portal is used, while BuildWithPXL may process that information to provide the contracted Services. Roles and responsibilities can vary by service, instructions, and applicable law; this policy does not assume a single controller or processor role for every relationship.

If you act for a client, you are responsible for ensuring you have authority to submit information, connect accounts, invite users, request access, or make a privacy request. We may ask for reasonable information to confirm identity, authority, and the scope of a request before acting.

5. Providers and disclosures

We may disclose information to authorized providers that help us provide hosting, authentication, payment, communications, analytics, security, AI, or connected-account functionality, and when reasonably necessary for a requested service. We may also disclose information where required by law, to protect rights or safety, or in connection with a business transaction subject to applicable law.

Connected-account and AI features can involve provider processing of information you choose to submit or authorize. Provider processing and access are governed by the applicable provider configuration, terms, and permissions. We do not represent that all providers use the same location, retention, training, or access practices.

SMS opt-in and contact information

We do not sell mobile numbers, SMS opt-in data, consent records, or contact information to third parties. We do not share this information with third parties or affiliates for marketing, advertising, audience matching, marketing measurement, or advertising attribution, including Meta or other marketing partners.

SMS opt-in data and consent are not shared with third parties for their own use. We may provide the minimum information necessary to service providers such as Twilio and telecommunications carriers solely to deliver messages you have consented to receive and administer the messaging service on our behalf, not for their own marketing or advertising.

These restrictions apply to all sharing categories described in this policy, including the Meta Pixel disclosure below. Consent to optional website analytics or marketing cookies does not authorize sharing your mobile number, SMS opt-in data, consent records, or contact information with Meta or other marketing partners.

6. Essential cookies, optional analytics, and marketing choices

Necessary cookies and similar technologies may be used for core functions such as security, authentication, preferences, and service delivery. Optional analytics and marketing measurement are separate from necessary cookies and are subject to the choices and controls presented where applicable.

If you opt in through Marketing preferences, BuildWithPXL uses Meta Pixel for page views and selected button and link clicks on specified public marketing pages, including our homepage, About page, pricing, and Info stories. Selected interactions include opening anonymized project examples. Click events contain a fixed button identifier and public page path, not form contents or link destinations. We use it to measure attribution and advertising performance.

After marketing consent, approved public campaign links may also be measured when they contain only supported UTM campaign tags and Meta click identifiers (fbclid). These values may be included in the public-page URL received by Meta and used for ad attribution. Do not put personal information in campaign labels. Unknown, malformed, duplicate, or oversized parameters disable Pixel tracking on that page. Account, Workspace, checkout, payment, and API pages remain excluded.

When enabled, Meta may receive cookie identifiers and browser, device, IP-address, referrer, and visited public-page URL information as part of its processing. Meta processes information under its own policy: https://www.facebook.com/privacy/policy/.

You may accept, reject, or later revoke optional marketing consent through the Marketing preferences control. Necessary cookies are separate and are not changed by this choice. Withdrawing consent stops future Pixel tracking; it does not erase processing that already occurred.

Automatic Advanced Matching, form scraping, Conversions API, and email or phone transmission are not enabled in the current implementation. Hashing identifiers would not make personal information anonymous.

7. Retention, exports, and deletion requests

We retain information for periods that may be needed to provide the Services, maintain security, resolve disputes, meet legal or financial obligations, and support reliable operations. Retention varies by data type and service; we do not state a universal automatic deletion period.

After service termination, a client may request an available export of Client Content within 30 calendar days by emailing hello@buildwithpxl.com. The request window does not promise that every item is exportable in every format, and it does not mean all copies are automatically deleted after 30 days.

Information may remain in backups, security logs, payment or tax records, legal or dispute records, and other systems where retention is reasonably necessary or required. Backup services do not include guaranteed restoration or a fixed retention period.

8. Your privacy requests

Depending on applicable law and the circumstances, you may request access, correction, deletion, export, restriction, or objection regarding personal information. To make a request, email hello@buildwithpxl.com with enough information for us to understand the request and verify identity and authority reasonably. We will handle requests in accordance with applicable law and the circumstances, including any lawful retention or security limitations.

If information is held for a business client, the client may need to direct or authorize the request. This policy does not pre-judge statutory exemptions, deadlines, or legal conclusions for any particular person or jurisdiction.

9. International use, security, and changes

The Services may be used internationally and information may be processed in locations where BuildWithPXL or authorized providers operate. We do not make a blanket claim about data residency or provider safeguards; service-specific arrangements may be needed for particular requirements.

We use measures intended to protect information appropriate to the Services and circumstances, but no method of transmission, storage, or processing is completely secure. Please do not send credentials or other information through an unapproved channel.

We may update this Policy by posting an updated effective date or providing notice where appropriate. Privacy questions and requests may be sent to hello@buildwithpxl.com. Mailing address: PXLWorld LLC, 108 Lakehouse Landing Dr, Katy, Texas 77493.