CrewBadger

Privacy Policy

Last updated: June 24, 2026

1. Introduction

This Privacy Policy explains how JKP Group LLC, a Puerto Rico limited liability company, doing business as CrewBadger ("CrewBadger," "we," "us," or "our") collects, uses, shares, and protects information in connection with the CrewBadger platform — our web dashboard, mobile technician app, public booking and payment links, and related services (together, the "Service").

CrewBadger is a field service management platform built for home-service businesses such as plumbing, HVAC, and electrical shops ("Shops"). It is a business-to-business product. The Service is intended for use by businesses and their authorized personnel, not by consumers for personal purposes. In this Policy we call these businesses "Shops"; our Terms of Service call them "Customers" — they are the same parties.

This Policy covers our practices in the United States and its territories, where the Service is offered. If you do not agree with this Policy, do not use the Service. Your use of the Service is also governed by our Terms of Service, which include a Data Processing Addendum that applies when CrewBadger processes a Shop's customer data on its behalf.

2. Who This Policy Is For — and the Roles We Play

Two broad audiences interact with the Service, and our responsibilities differ for each:

  • Shops and their staff — the owners, managers, dispatchers, and technicians who hold accounts and run their business on CrewBadger.
  • The Shop's own end customers — the homeowners and businesses a Shop serves. These people do not have CrewBadger accounts; they interact only through links a Shop sends them (a booking page, a proposal to approve, an invoice to pay, an unsubscribe link).

Privacy law distinguishes between a controller (sometimes called a "business"), which decides why and how personal information is processed, and a processor (or "service provider"), which processes that information only on the controller's instructions. CrewBadger plays both roles depending on the data:

  • For a Shop's end-customer data (the customer records, job notes, addresses, photos, signatures, and communications a Shop enters or generates in the Service) and for booking-lead data (out-of-service-area prospects a Shop captures on its public booking page), the Shop is the controller and CrewBadger is the processor / service provider. We process that data to provide the Service under the Shop's direction and the automation rules the Shop configures. The Shop is responsible for the lawfulness of that data, including obtaining any consents required for text messages, email, and electronic signatures from its own customers. If you are an end customer with a question about your information, contact the Shop you did business with first; we will support the Shop in responding to you.
  • For Shop-account and business data (Shop-staff identity and login data, the business's own profile and settings) and for de-identified, aggregated data we derive from platform activity, CrewBadger is the controller.
  • For referral-program participants ("Ambassadors"), CrewBadger is the controller, and that relationship is governed by a separate Master Ambassador Agreement. See Section 14.

3. Information We Collect

We organize the information we collect by the four classes of people it relates to, followed by business and usage data.

3.1 Shop staff (account holders — owners, managers, dispatchers, technicians)

  • Identity and login: name, email address, phone number (in E.164 format), and, where used, your Google sign-in identity. Passwords are managed by our authentication provider and are never stored in our application database in readable form.
  • Role and permissions: your permission level (admin, manager, standard), your work roles (technician, dispatcher), and any finance role assigned to you.
  • Workforce and pay data: for staff, information such as hourly cost, pay basis (hourly, commission, hybrid, or flat), and a starting work address with approximate coordinates. This information is used for scheduling and payroll-related features and is restricted from technician-facing screens.
  • Preferences: language preference (English or Spanish) and notification settings.
  • Calendar connection: if you connect Google Calendar, your calendar identifier and an authorization (refresh) token, used to push job times to your calendar and to pull your personal events back as "blocked" (busy) time. Your personal calendar remains your own data, and you can disconnect the integration at any time to revoke our access.

3.2 End customers (the Shop's customers)

This information is entered or generated by the Shop in the course of serving its customers. CrewBadger processes it on the Shop's behalf.

  • Contact details: first and last name, an optional title, one or more phone numbers (E.164), email address, and preferred contact method.
  • Communication-consent flags: whether the customer has opted in to text messages and to email.
  • Service location: street address, city, state, ZIP, approximate geocoded coordinates, and access notes the Shop records (for example, gate codes, lockbox locations, or notes about pets or parking).
  • Equipment: equipment type, make, model, serial number, install date, and warranty expiration for equipment the Shop services.
  • Account and CRM details: customer type (residential or commercial), service history, lifetime value, preferred technician, internal notes, and tags.
  • Jobs and proposals: job numbers and descriptions, checklist responses, job photos, proposals and their line items, and — where a customer signs a proposal electronically — the captured signature image and the consent details required by the federal ESIGN Act and state UETA laws (the signature, plus the IP address and browser/device string at the time of a remote web signature), along with a generated PDF and an integrity hash of it. CrewBadger itself presents the ESIGN/UETA consumer disclosure (including, for a consumer signer, the ESIGN § 101(c) consent disclosure) within its own signing interface before signature, and records the consent and the disclosure version with the signature — the Shop is responsible only for the business-level accuracy and authority of the document it sends.
  • Invoices and payments: invoice numbers, line items, totals, due dates, discounts, purchase-order numbers, payment amounts, methods, and status, payment-processor identifiers, and the card brand and last four digits only. Full card numbers never reach CrewBadger's servers.
  • Communication history: logs of the text messages, emails, and push notifications sent through the Service (channel, direction, message content, provider message identifier, status, and the automation that triggered it), and inbound replies such as "STOP" or a review score.

3.3 Booking leads

When someone tries to book a job through a Shop's public booking page but is outside the Shop's service area, we capture the email, phone number, and attempted location so the Shop can follow up. This is held on the Shop's behalf and scoped to that Shop, and the Shop is the controller for it (see Section 2).

3.4 Referral participants (Ambassadors)

If you participate in our referral program, we collect identity and payout information, application details, tax forms (such as a W-9 and taxpayer identification number) and your related delivery and consent preferences, and your referral activity. This data and its handling are governed by the separate Master Ambassador Agreement and are summarized in Section 14, not detailed here.

3.5 Business (Shop) metadata

About the Shop as an organization: legal business name, brand or "doing business as" name, business type, Employer Identification Number, trade license number and state, business address and its coordinates, payment-processor account and status, telecom subaccount and messaging-registration status, tax-rate and numbering configuration, plan tier, subscription and trial status, and account lifecycle (such as a pending closure). Sensitive identifiers such as the Shop's EIN and any taxpayer identification numbers are encrypted at rest.

3.6 Usage, device, and analytics data

When you use the Service, we and our analytics and error-monitoring providers collect technical and usage information such as IP address, device and browser characteristics, pages and features used, timestamps, and diagnostic error traces. Our error-monitoring is configured to mask personal information, and our product-analytics events are keyed to a Shop identifier rather than to individuals by design. For referral links, we collect click data described in Section 7.

4. How We Use Information

We use the information above to:

  • Provide and operate the Service — run the CRM, dispatch and schedule jobs, build proposals and invoices, process payments, and synchronize calendars and (optionally) accounting.
  • Send communications on a Shop's behalf — deliver the appointment reminders, on-the-way alerts, review requests, payment links, and similar messages a Shop configures, always subject to the customer's consent flags.
  • Enable lead follow-up — let a Shop follow up on out-of-service-area booking leads captured through its public booking page.
  • Process payments — through our payment processor, including fraud prevention and required identity and compliance checks (see Section 8).
  • Provide AI-assisted features — such as drafting job descriptions, a support assistant, margin guidance, and monthly business insights (see Section 5).
  • Secure, maintain, and improve the Service — monitor for errors and abuse, debug, measure feature usage, and develop new functionality.
  • Communicate with account holders — send transactional and service messages about the account, and optional product updates you can opt out of.
  • Comply with law and enforce our terms — including tax, telecom, and electronic-signature requirements, and to establish, exercise, or defend legal claims.

We do not sell personal information, and we do not share it for cross-context behavioral advertising. We do not use a Shop's data, or its customers' data, to target advertising.

5. AI Features and Cross-Shop Insights

CrewBadger offers AI-assisted features. We want to be precise about how data is handled.

We do not use your identifiable data — or your customers' identifiable data — to train AI models. Any model improvement we perform uses only de-identified, aggregated data (see below). CrewBadger currently uses Anthropic and may use additional AI providers over time, including open-source or self-hosted models. When an AI feature runs, the relevant text (for example, a job-description prompt or a support question) is sent to the applicable model only to generate that one result; any retention of that request data is transient and only as needed to deliver the feature. We achieve the no-training commitment in two ways depending on how a model runs: hosted AI providers are used under terms or configurations (such as enterprise or zero-retention tiers) that prohibit training on your content, and any self-hosted or open-source model is operated and controlled by CrewBadger and is not trained on identifiable customer data. For each AI suggestion we keep an internal audit record of the model used, the outcome, and cost, but where the Service is designed to do so we store only a hashed reference to the input — not the raw input itself.

De-identified, aggregated insights (cross-shop learning). To make the Service smarter for everyone, CrewBadger creates and maintains de-identified, aggregated benchmarks and patterns derived from activity across the platform — for example, common pricing signals by region and trade, or how categories are typically mapped to accounting accounts. These aggregates carry no business identity: they contain no Shop name, no customer information, no individual records, and no exact dollar amounts attributable to any identified or identifiable business or customer.

Reasonable measures against re-identification. We de-identify this data using measures designed so it cannot reasonably be linked back to any business or person, and we maintain those measures:

  • a signal is published only after at least twenty (20) independent businesses have contributed to the cell (a k≥20 anonymity floor); cells below that floor are suppressed entirely, never rounded or estimated;
  • geography is generalized as needed (for example, rolling a ZIP up to a broader region) so no thin ZIP-by-trade cell is identifiable; and
  • pricing is reported only in banded ranges, never exact amounts, so no small ZIP × trade × price cell can identify a contributor.

Our public commitments. Consistent with the CCPA's de-identification standard (Cal. Civ. Code § 1798.140(m)), we publicly commit that we (i) maintain and use this data only in de-identified, aggregated form; (ii) will not attempt to re-identify it; and (iii) contractually obligate any recipient of it to the same de-identification standard and the same no-re-identification commitment.

Because, and only so long as, this data is validly de-identified, aggregated, and non-personal:

  • it is covered by your agreement with us as a controller-level use of CrewBadger, and no separate consent is required;
  • a Shop may opt out of contributing to these aggregates at any time in Settings (the resulting insights remain available to read either way). This opt-out is a discretionary courtesy we provide, not a privacy-rights opt-out — because the data is not sold, shared, or used for targeted advertising, there is no statutory opt-out it represents; and
  • because validly de-identified data is not personal information and is not attributable to any Shop, it survives account deletion — deleting your account removes your identifiable data, but does not unwind anonymous, aggregate figures that were already de-identified under the measures above.

Insights and similar AI outputs are informational only and are not professional financial, accounting, tax, or legal advice. Where the Service's AI support assistant interacts with a person, that person is told they are interacting with an automated, AI-based assistant.

6. Text Messaging and Consent (SMS / TCPA)

The Service lets a Shop send text messages to its own customers — appointment reminders, on-the-way alerts, review requests, payment links, and similar service communications. The Shop initiates and controls these messages and is responsible for having the proper consent from its customers under the Telephone Consumer Protection Act (TCPA) and related law. CrewBadger enforces the consent and opt-out controls as hard, server-side mechanisms.

  • Consent: A customer's phone number is associated with consent the Shop obtains (for example, through the SMS consent checkbox on the booking page, where "Message and data rates may apply" is shown). Our send path sends only when the customer's opt-in flag is set; no manual, bulk, or automated action can override that suppression.
  • STOP: A customer can opt out at any time by replying STOP to any message. Our system immediately records the opt-out and stops further automated messages to that number. Other keywords required by carriers (such as UNSUBSCRIBE, CANCEL, END, QUIT) are honored equivalently. This opt-out cannot be overridden from within the Service.
  • HELP: Replying HELP returns assistance information identifying the sending Shop and how to opt out; customers can also contact the Shop directly.
  • Quiet hours and frequency caps: For automated sends, the Service applies quiet-hours windows and frequency caps designed to limit nuisance messaging.
  • A2P 10DLC: Business messaging in the United States runs over registered application-to-person (A2P 10DLC) channels, and we block sends on unregistered or revoked channels. To enable messaging, the Shop's business details (such as legal name, address, and EIN) are shared with our messaging provider and the carrier registry for the required registration.

Message and data rates may apply, and message frequency varies with the lifecycle of the customer's service. We do not sell phone numbers or message content.

7. Cookies and Tracking

CrewBadger is a business application, not an advertising-driven service. We use a limited set of cookies and tracking technologies:

  • Essential and authentication cookies — required to keep you signed in and to operate core features.
  • Referral attribution (cb_ref) — when someone arrives through an Ambassador's referral link, we set a signed cb_ref cookie (with a 30-day lifetime) and log the click at our edge layer, capturing the IP address, browser/user-agent, referring URL, coarse geographic region (country/region/city level), and any campaign tags in the link. This is used solely to attribute referrals and detect referral fraud — not for advertising or retargeting. A disclosure appears on referral landing pages.
  • Product analytics and error monitoring — we use PostHog for product analytics (keyed to a Shop identifier, configured to avoid collecting personal information) and Sentry for error monitoring (configured to mask personal information).

Because we do not use advertising or cross-site tracking cookies, the Service does not respond to browser "Do Not Track" signals; the universal opt-out preference signals recognized under certain state laws are addressed in Section 11. You can control cookies through your browser settings, though disabling essential cookies may break core functionality.

8. How We Share Information — Sub-Processors

We do not sell personal information. We share information only as described here: with the third-party services that help us run the Service (our "sub-processors"), to comply with law, and in a business transfer. Two parties — Stripe and Intuit (QuickBooks Online) — act as independent controllers for the data they handle, not as our sub-processors; they are listed below for transparency, but they receive data as a controller-to-controller transfer you authorize when you enable the relevant feature, and they are not bound by the sub-processor flow-down that governs the others.

All of our sub-processor accounts are dedicated to CrewBadger; we do not share infrastructure or credentials with any other business. Each sub-processor is bound by contract to protect the data, to use it only to provide its service to us, and (consistent with our Data Processing Addendum) to be bound by the same service-provider restrictions that apply to CrewBadger. The current sub-processors and independent controllers are:

Core infrastructure (the Service cannot run without these):

Sub-processor Purpose
Supabase Primary database, authentication, and realtime updates; stores business data and login credentials. (United States region.)
Stripe Card and bank payment processing, payouts, and identity/compliance (KYC) checks under Stripe's Connected Account Agreement. Stripe acts as an independent controller for the payment and compliance data it handles. Full card numbers are handled by Stripe and never reach our servers.
Twilio Text-message delivery and A2P 10DLC carrier registration; processes customer phone numbers, message content, and the business details needed for registration.
Resend Sending transactional and notification email.
Cloudflare R2 Encrypted object storage for logos, job photos, proposal signatures, tax documents, statements, and export files.
Railway Hosting for our API servers and application logs.
Vercel Hosting for the web application and the edge functions that handle referral tracking.
Google Sign-in (OAuth), Calendar synchronization, and maps/geocoding and routing for addresses and dispatch.
Upstash Job queues and edge key-value storage that temporarily hold message payloads and referral click data while they are processed.

Optional integrations (used only if a Shop enables them):

Sub-processor Purpose
Intuit (QuickBooks Online) Two-way accounting synchronization, if a Shop connects QuickBooks; shares financial data, the customer list, invoices, expenses, and tax data. Intuit acts as an independent controller for the tax-compliance data it handles.
Stripe Financial Connections Securely linking a bank account for reconciliation, if a Shop enables it.
Expo (EAS) Building and delivering updates to the mobile app.

Observability and AI (used to monitor quality and power AI features; each is inactive unless configured):

Sub-processor Purpose
Sentry Error and crash monitoring across web, mobile, and API (personal information masked). (United States region.)
PostHog Product analytics keyed to a Shop identifier.
AI model providers (CrewBadger currently uses Anthropic and may use additional providers over time, including open-source or self-hosted models) The AI models and providers that power AI-assisted features such as description generation and the support assistant. Hosted providers are used under terms or configurations that prohibit training on your content; any self-hosted or open-source model is operated and controlled by CrewBadger and is not trained on identifiable customer data. Each processes only the request content needed to generate a result, with only transient retention and no training on your content (see Section 5).
Voyage AI Generating the search embeddings that power help-center semantic search.
Langfuse Optional monitoring of AI requests and responses for quality and cost.

We may also disclose information to comply with law (for example, in response to a valid subpoena, court order, or legal process, or to protect the rights, safety, and property of CrewBadger, our users, or the public), and in connection with a business transaction such as a merger, acquisition, financing, or sale of assets, in which case this Policy will continue to apply to the transferred information or you will be notified of any new policy.

If we add or change a sub-processor, we will update this list and provide advance notice through a subscribable mechanism (such as an email list or a published changelog) before that sub-processor begins processing your data, so a Shop can vet the onward transfer. As a developer, CrewBadger also commits to handle data obtained through the Google APIs in accordance with the Google API Services User Data Policy, including its Limited Use requirements, and to handle Intuit (QuickBooks Online) data in accordance with Intuit's applicable developer requirements.

9. Data Security

We maintain a security program that uses commercially reasonable technical and organizational measures designed to protect information. Our program includes measures such as the following, and these measures may evolve over time:

  • Encryption in transit — we use TLS for connections to the Service.
  • Encryption at rest — we use storage-layer (volume) encryption for the database, and we additionally apply application-layer field encryption to designated sensitive fields, such as EINs, taxpayer identification numbers, and accounting-integration (QuickBooks) authorization tokens.
  • Tenant isolation — each Shop's data is isolated primarily through application- and service-layer authorization controls (route authorization and per-actor scoping in our API), which is the live isolation gate because the application's database connection operates with elevated privileges. We additionally use database row-level security as a defense-in-depth measure; it is not the sole or primary isolation control.
  • Scoped, least-privilege credentials for our integrations, with secrets kept in managed secret storage rather than in our code.
  • Sensitive-action safeguards — sensitive operations (such as refunds or accessing sensitive tax fields) are designed to require a fresh step-up confirmation.
  • Audit logging — high-value changes (job, payment, permission, and deletion events) are designed to be recorded in an append-only log with the actor and before/after state.
  • PCI compliance through Stripe — all card data is handled by Stripe, which maintains PCI DSS compliance; we never receive full card numbers.

These descriptions explain how the Service is designed to operate; they are not a warranty of a specific outcome, and the measures may change as the Service evolves. We do not currently hold a third-party security certification (such as SOC 2) and make no representation that we do. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

Where CrewBadger acts as a Shop's processor, and we become aware of, or form a reasonable belief of, a breach affecting personal information we process on the Shop's behalf, we notify the affected Shop (as the controller) without undue delay and in any event within seventy-two (72) hours, so the Shop can meet its own notification obligations; we do not notify the Shop's end customers directly. Where CrewBadger is the controller (such as for Shop-account data), we provide breach notice as required by applicable law. The security terms in our Terms of Service (Section 14) and Data Processing Addendum (Section 13) govern in the event of any conflict with this Section.

10. Data Retention and Deletion

We keep information for as long as needed to provide the Service and for the legitimate and legal purposes described below.

  • Active accounts: business, customer, and booking-lead data is retained while the account is active.
  • Soft deletion: when records such as customers, jobs, or invoices are deleted in the app, they are first marked deleted and become recoverable before purge; ordinary reads exclude them immediately. Routine backups are overwritten on a rolling cycle, ordinarily within ninety (90) days.
  • Financial records: to meet tax and audit obligations, a financial "skeleton" — invoices, payments, and the financial and audit-log spine — is retained for a defined period of seven (7) years, based on the recordkeeping periods applicable to U.S. tax and financial records (including IRS recordkeeping guidance), even after a customer or account is erased, with personal information anonymized while amounts and dates are preserved. After that period it is purged.
  • Help-center view/search signals: retained in raw form for about 90 days, then aggregated.
  • Referral click data: retained on an ongoing basis for commission audit; rejected ambassador applications are retained for about 24 months.
  • De-identified aggregates: the non-personal benchmarks described in Section 5 are retained indefinitely and are not tied to any account.

Deletion and export rights we have built in:

  • Account deletion (Shop): a Shop owner can request deletion of the account. We provide a 30-day grace window during which the request can be cancelled; deletion is blocked while there are unsettled invoices or open payment disputes. After the grace window, we run an automated purge that anonymizes personal information, hard-deletes operational records, retains the seven-year financial skeleton described above, records a tamper-evident deletion certificate in the audit log, and disconnects external services (for example, deauthorizing the payment integration, releasing the messaging/telecom registration, clearing the accounting connection, and applying storage lifecycle rules). On account deletion, any connected Google Calendar access is automatically revoked — the stored authorization token is revoked — so CrewBadger's access ends as part of the purge. You can also end CrewBadger's access to your Google Calendar at any time by disconnecting the integration in Settings, which revokes the stored authorization token.
  • Per-customer erasure: a Shop can erase an individual end customer's personal information through the Service. This anonymizes that customer's personal data, deletes their communications, scrubs the financial and audit spine, and removes stored photos (signatures held under the legal-document retention lock are kept to satisfy the seven-year requirement), with an erasure certificate recorded.
  • Data export: a Shop owner can export the organization's data as a downloadable archive of CSV files, invoice PDFs, and documents, including during the deletion grace window.

To make any of these requests, or to ask about retention of your information, contact us at hello@crewbadger.com. If you are an end customer, please contact the Shop you did business with; the Shop controls that data and can use the tools above, and we will assist the Shop as its processor.

11. Your Privacy Rights

Depending on where you live, U.S. state privacy laws — including the California Consumer Privacy Act, as amended by the CPRA, the Virginia Consumer Data Protection Act, the Colorado Privacy Act, the Connecticut Data Privacy Act, the Utah Consumer Privacy Act, and similar laws in other states — give you rights regarding personal information. Subject to those laws and their exceptions, you may have the right to:

  • Know and access the personal information we hold about you and how we use and share it;
  • Correct inaccurate personal information;
  • Delete your personal information;
  • Obtain a portable copy of your personal information; and
  • Not be discriminated against for exercising your rights.

Sale, sharing, and targeted advertising. We do not sell personal information, and we do not "share" it for cross-context behavioral advertising or use it for targeted advertising, as those terms are defined under these laws. There is therefore no sale or targeted-advertising activity to opt out of, and we do not process personal information for those purposes. Because we do not sell or share personal information or use it for targeted advertising, there is no opt-out to which a Global Privacy Control (GPC) or similar universal browser opt-out signal would apply; we honor the underlying right by not engaging in those activities at all. We also do not use personal information for profiling that produces legal or similarly significant effects.

How roles affect your request. Much of the personal information in the Service relates to a Shop's end customers, for which the Shop is the controller and CrewBadger is the processor/service provider. If you are an end customer, please direct rights requests to the Shop you interacted with; we will help the Shop fulfill them. For information for which CrewBadger is the controller (such as Shop-account data), you can exercise your rights with us directly.

How to exercise your rights. Email hello@crewbadger.com with your request. We will verify your request — typically by confirming control of the account or contact information associated with the data — before acting on it, and we will respond within the timeframes the applicable law requires. You may use an authorized agent where the law permits; we may ask the agent for proof of authorization.

Appeals. If we decline your request and your state provides an appeal right, you may appeal by replying to our decision at the same address. We will inform you of the outcome and, where required, of how to contact your state attorney general.

12. Data Location and International Note

CrewBadger stores and processes information in the United States and its territories. Some of our sub-processors may operate from other locations; where that is the case, we will do so only with notice and with appropriate contractual protections in place. We do not currently offer the Service in the European Union, the United Kingdom, or other regions governed by the GDPR, and this Policy is written for U.S. and territory privacy law. If we begin serving customers in those regions, we will add the additional GDPR-specific terms and safeguards (such as a representative and standard contractual clauses) that those laws require.

13. Children's Privacy

The Service is for businesses and their authorized personnel. Account holders must be at least 18 years old to use it. The Service is not directed to children, and we do not knowingly collect personal information from account holders under 18. If you believe a child has provided us with personal information as an account holder, contact us at hello@crewbadger.com and we will delete it. Information about a Shop's end customers is entered by the Shop, which is responsible for the lawfulness of that data as the controller.

14. Referral Participants (Ambassadors)

If you take part in CrewBadger's referral program as an Ambassador, your participation — and the collection and use of your identity, payout, tax, and referral-activity data — is governed by the separate Master Ambassador Agreement you accept when you join the program. That agreement, together with this Policy where it applies, describes how that information is handled. For questions about the referral program, contact us at hello@crewbadger.com.

15. Changes to This Policy

We may update this Privacy Policy from time to time. If we make material changes, we will notify account holders by email or through the Service at least 30 days before the changes take effect, unless a shorter period is required to comply with law. The "Last updated" date at the top reflects the most recent revision. Your continued use of the Service after a change takes effect means you accept the updated Policy.

16. Contact Us

Questions or requests regarding this Privacy Policy, or to exercise your privacy rights, can be directed to:

JKP Group LLC, d/b/a CrewBadger 1498 Ave Fernandez Juncos San Juan, PR 00909 Email: hello@crewbadger.com