Privacy Policy

CloserLeague LLC, doing business as CloserLeague ("CloserLeague," "we," "us," or "our"), provides a sales competition, leaderboard, recognition, and presentation platform. This Privacy Policy explains how we handle personal information in connection with our Services.

1. Scope

This Privacy Policy explains how we handle personal information in connection with:

• Our marketing website at https://closerleague.win;
• The CloserLeague application at https://app.closerleague.win;
• Live leaderboards, competition history, seller achievement walls, and team-management interfaces;
• The GroupMe, Slack, and Discord integrations, and any later integration that links to this Policy;
• Subscription, billing, onboarding, support, and related services; and
• Other CloserLeague services that link to this Policy.

Together, these are the Services.

This Policy may apply to customer organizations, managers, sellers, team participants, public viewers, prospective customers, and other individuals whose information is processed through the Services.

2. CloserLeague's role and the customer's role

The legal role of CloserLeague depends on the information and the purpose for which it is processed.

CloserLeague generally acts as a controller, "business," or similar responsible entity for information used for our own purposes, such as:

• Operating our websites and business;
• Creating and securing manager accounts;
• Administering subscriptions and billing;
• Providing support and service communications;
• Preventing fraud, abuse, and security incidents;
• Maintaining legal and business records; and
• Performing internal analytics using information we are permitted to use for those purposes.

For seller, sales-performance, competition, team, and similar information that a customer organization submits, configures, or directs us to process, the customer generally determines the business purpose for the processing. Depending on applicable law, CloserLeague may act as the customer's processor, service provider, contractor, or similar provider for that processing.

Customer organizations are responsible for determining whether their use of CloserLeague is lawful, including responsibility for:

• Providing legally required employee, contractor, seller, workplace-monitoring, and privacy notices;
• Establishing any required lawful basis for processing participant information;
• Obtaining any consent or authorization required for monitoring of a connected messaging integration, competitions, public display, or publication of participant information;
• Determining what sales information may lawfully be submitted;
• Choosing whether supported leaderboard and achievement pages are publicly accessible or restricted to authorized team users;
• Responding to participant disputes and privacy requests when the customer controls the relevant information; and
• Complying with employment, labor, privacy, contest, and other laws applicable to the customer's activities.

If your information was provided to CloserLeague by your employer, agency, manager, or another customer organization, that organization may be the appropriate party to contact first. We will assist customers with legally required requests as required by applicable law and our agreements.

3. Personal information we process

The information we process depends on how the Services are used.

3.1 Website, inquiry, and business-contact information

We may process information such as: name; email address; telephone number; company, agency, or team name; job title; team size; information submitted through contact, onboarding, pricing, subscription, or support forms; communication preferences; and the contents of communications with us.

3.2 Manager and account information

Owners, administrators, and other authenticated account holders may provide or generate: name and display name; email address; password hash and authentication information; team membership and role; team-registration or invitation information; account and display preferences; session and login information; and support and administrative communications.

CloserLeague does not need a user's readable plaintext password to provide the Services. Passwords are intended to be stored using one-way password hashing.

3.3 Team and organization information

We may process: team or organization name; public team slug or URL identifier; time zone; team, competition, and presentation settings; manager-registration information; messaging-integration status and configuration; subscription and plan information; billing contact information; and other settings selected by authorized managers.

3.4 Seller and participant information

Under the current product model, sellers may be non-login identities created and maintained through a customer's connected messaging workflow rather than through a seller account.

Seller information may include: name and display name; messaging-platform sender or user identifier; avatar URL or profile image; team association; current and historical placement; sales totals and daily sales count; spree, Arena Leader, and Sales Leader status; competition history; trophies and achievements; and current leaderboard-card or presentation information.

A seller identity may be created when a previously unmapped sender in a connected chat submits a message that CloserLeague identifies as a sale for the connected team. Sellers do not currently receive a CloserLeague login merely because a seller identity or achievement wall exists.

3.5 Sales and competition information

We may process information such as: annual premium or other sale value supported by the applicable product configuration; carrier information; effective date; sale date and time; seller identity; source and source-message identifier; parsed sale fields; parsing or review status; manager corrections, assignments, approvals, or rejections; duplicate-review information; competition name, type, dates, and status; rankings and standings; leader and spree status; and completed competition results, history, and trophies.

Sales-performance information may be professional or employment-related information under applicable law. CloserLeague is a competition and presentation platform, not an employment decision system, payroll system, commission system, or regulatory system of record.

3.6 Messaging integrations and message data

When a customer connects a messaging integration (GroupMe, Slack, or Discord), the integration must receive and evaluate messages delivered through it in order to determine whether each message appears to contain a sale. This means CloserLeague may process a message even when the message is ultimately determined not to be a sale.

The integration may process: group and bot configuration information; sender identifiers; display names and avatar URLs; message identifiers; message text while it is being evaluated; message timestamps; seller mappings; integration status; and technical information needed to receive or respond to integration events.

Current message-retention practice. CloserLeague does not operate a general archive of a customer's connected-chat conversations and does not currently intend to persist the full text of ordinary non-sale messages as individual message records. Information extracted from a valid sale, along with identifiers and review-related metadata needed to operate the Services, may be retained as part of the resulting sale or competition record.

As of the Effective Date, CloserLeague does not intentionally retain the full text of individual chat messages as a general product feature. A future version may retain the text of messages classified as sales or potential sales where needed for review, troubleshooting, or another disclosed purpose. We will update this Policy or provide other legally required notice before beginning a materially different message-retention practice.

Because connected-chat messages may be evaluated before CloserLeague knows whether they are sales, customers must instruct participants not to use a connected chat to transmit sensitive information that is unnecessary for the sales workflow.

GroupMe, Slack, and Discord are third-party services, and each service's own terms and privacy practices govern its independent processing.

3.7 Public and restricted leaderboard information

CloserLeague supports pages that may be configured for public viewing and, where the applicable access-control feature is enabled, pages that may be restricted to authorized team users.

Information displayed on a public page may include: team and competition information; seller display name and avatar; placement; sales or premium totals; daily activity and spree status; Arena Leader or Sales Leader status; competition history and final standings; trophies; and seller achievement-wall information.

Information made public may be viewed without authentication and may be photographed, recorded, indexed, copied, reposted, or retained by third parties. CloserLeague cannot control copies made by third parties after information has been published.

Customers are responsible for determining whether participant information may lawfully be displayed publicly and for selecting appropriate access and display settings.

3.8 Subscription and payment information

CloserLeague currently uses Stripe for payment processing. In connection with subscriptions, we may receive or process: billing name and contact information; billing address where provided or required; subscription plan; transaction amount and status; invoice and receipt information; payment-method type; limited payment identifiers; and tax-related information where applicable.

Payment-card credentials are ordinarily submitted directly to Stripe rather than stored by CloserLeague. Stripe's privacy practices apply to Stripe's independent processing.

CloserLeague offers both monthly and annual subscriptions, billed through Stripe.

Cancellation feedback. If a subscription is cancelled, we record the reason chosen from the list we offer, together with any optional comment the person cancelling chooses to write, which we store as written. This is linked to the account and, where applicable, to the subscription and the team. It is used to understand why subscriptions end and is not disclosed to a third party. Please do not include information in that comment that you would not want retained — see Section 3.11. Cancellation feedback is deleted 24 months after the cancellation it records.

3.9 Device, log, and technical information

Depending on the part of the Services used, we may automatically process: IP address; browser and operating-system information; device information; referring or exit page; pages or features viewed; date, time, and duration of activity; login and session events; application errors and performance information; realtime connection information; and security-related events.

We may infer approximate location from an IP address for security or ordinary technical purposes. We do not request precise geolocation for the core Services.

First-party product measurement. CloserLeague records a limited set of product events on its own servers, from within the operation being measured, to understand how the Services are adopted and used and to improve them. These cover a team’s first completion of setup milestones; each time an integration is connected, configured, fails, is disconnected, or is reconnected; and bucketed counts of inbound messages that were not recorded as sales. A record may be linked to the account, the team, and a pseudonymous identifier for the acting user, and otherwise holds only enumerated values and counts. This measurement sets no cookie, stores nothing on your device, and uses no device identifier. No product event, and nothing derived from one, is disclosed to a third party or used for advertising or advertising measurement. Product events are deleted 24 months after the activity they record.

3.10 Cookies and analytics

CloserLeague uses cookies and local storage for authentication, security, session management, and user preferences. Separate nonessential storage and Microsoft Clarity analytics may operate on consent-eligible public marketing and acquisition-funnel surfaces, subject to the controls described below.

Public acquisition surfaces. Eligible surfaces include public pages on closerleague.win and app.closerleague.win, signup, plan selection, checkout handoff, and verified conversion confirmation. Clarity measures visits and movement through this bounded funnel by using session replay, heatmaps, page and interaction data, and limited custom tags and events.

First-party attribution. When permitted by your consent choices, CloserLeague may retain the following UTM fields in first-party attribution storage: utm_source, utm_medium, utm_campaign, utm_content, and utm_term. We may also retain raw fbclid, gclid, msclkid, and ttclid values in that storage. This information may be handed to the eligible acquisition flow on app.closerleague.win and is retained for no more than 90 days.

Information available to Clarity. Clarity may receive the listed UTM fields, eligible public-page interaction data, and limited tags or events that indicate acquisition-funnel activity. For an advertising click identifier, Clarity receives only its kind and presence, never its raw value.

Information excluded from Clarity. Strict masking applies to Clarity recordings, with explicit masking for signup and checkout-related interfaces in the eligible public funnel. Private form contents, names, email addresses, payment details, account, customer, transaction, or other private identifiers, and private application state are not included in recordings, custom tags, or events.

Clarity is excluded from login, authenticated product use, team, chat, and sales workflows, the customer billing portal, payment-entry surfaces, and all other private application areas.

Microsoft processes Clarity information under its own privacy practices and may combine it with other information it holds. The Microsoft Privacy Statement describes that independent processing.

Meta advertising measurement. On the public acquisition surfaces described above, and only while you have allowed optional tracking, CloserLeague uses the Meta Pixel and Meta’s Conversions API to measure advertising performance. Neither operates anywhere in the authenticated product.

The Meta Pixel runs in your browser on those surfaces and sets Meta’s own cookies, _fbp, and _fbc where you arrived from a Meta advertisement. It records which pages you view, when you click one of our calls to action, and the steps you take up to the point of subscribing. It receives no email address, name, phone number, account, team, customer, or transaction identifier, no payment detail, and no form contents. Automatic advanced matching and automatic event collection are disabled.

Meta’s Conversions API reports the signup and checkout steps from CloserLeague’s servers, together with completed purchases and the amount charged. So that Meta can match an event to an account, these server reports include a one-way hash of your email address, the _fbp and _fbc values, your IP address, and your browser’s user agent. Your email address itself, your name, and your phone number are never sent, and the hash is not stored.

Where you arrived from a Meta advertisement, the fbclid value described above may be used to reconstruct the _fbc value when the Pixel did not set that cookie itself.

Meta processes this information as an independent controller under its own privacy practices and may combine it with other information it holds. Advertising identifiers retained for a signup are deleted after no more than 90 days.

Clarity receives no Meta identifier, no hashed identity, and no raw advertising click identifier, and Clarity information is not used for advertising targeting.

Your choices. Where consent is legally required, Clarity and nonessential acquisition storage are not enabled before you accept. You may change your choice at any time through the “Your Privacy Choices” link in the site footer. Withdrawal stops further nonessential collection, clears or suppresses nonessential acquisition state and Clarity cookies, stops the Meta Pixel and clears the cookies it set, and deletes the advertising identifiers held on our servers for that visit. Section 11 explains how we respond to Global Privacy Control.

3.11 Information you should not submit

Do not intentionally submit through CloserLeague or a chat connected to CloserLeague:

• Social Security, national-identification, or government-benefit numbers;
• Bank-account credentials;
• Complete payment-card information outside an authorized payment form;
• Medical, health, or protected health information;
• Biometric identifiers;
• Precise geolocation;
• Consumer-credit information;
• Passwords or authentication secrets for third-party services;
• Policyholder, patient, or end-consumer information that is not necessary for the sales competition; or
• Other sensitive or confidential information unnecessary to record a seller's sale.

For insurance-oriented workflows, customers should structure sale messages around the seller and sale information actually needed by CloserLeague, such as seller identity, carrier, annual premium or configured value, and effective date, rather than including policyholder information.

4. Sources of personal information

We may receive personal information:

• Directly from an individual;
• From a customer organization, employer, agency, manager, or team owner;
• From a connected messaging integration (GroupMe, Slack, or Discord) or another customer-authorized integration;
• From messages sent through a connected integration;
• Automatically from browsers, devices, sessions, and application logs;
• From Stripe and other providers that support the Services; and
• In connection with a financing, acquisition, merger, restructuring, or similar business transaction.

5. How we use personal information

We may use personal information to:

5.1 Provide and administer the Services

Create and maintain teams and manager accounts; authenticate account holders; connect and operate integrations; evaluate incoming messages and process sales; create and map seller identities; calculate rankings and competition status; present live leaderboards and achievement pages; maintain competition history and trophies; apply team settings; synchronize connected displays; administer subscriptions and billing; and provide onboarding and support.

5.2 Maintain accuracy, integrity, and security

Detect duplicate delivery attempts; route uncertain information for review; apply manager corrections; diagnose errors; prevent fraud and misuse; investigate security incidents; and protect CloserLeague, customers, participants, and the Services.

5.3 Operate and improve CloserLeague

We may use account, technical, usage, support, and appropriately aggregated or de-identified information to understand product performance, improve reliability and usability, plan capacity, and develop the Services.

Machine-learning training. As of the Effective Date, CloserLeague does not use identifiable connected-chat message content or identifiable Customer Content to train general-purpose artificial-intelligence or machine-learning models. The current sale parser is deterministic rather than an AI-powered parser.

If CloserLeague later proposes to retain sale or potential-sale message content for model training or another materially different secondary use, we will first evaluate the contractual and legal basis for that use, update applicable notices, and obtain customer authorization or individual consent where required. De-identification or redaction must be sufficient for the intended legal treatment; simply removing a name does not by itself determine that information is legally de-identified.

5.4 Communicate and transact

We may use contact information to respond to inquiries and support requests; provide security, account, billing, and legal notices; send onboarding information; request feedback; and send marketing communications where permitted.

Marketing communications may be unsubscribed from. Necessary service, security, billing, or legal communications may still be sent while an account or customer relationship remains active.

5.5 Legal and corporate purposes

We may process information where reasonably necessary to comply with law or lawful process; maintain tax, accounting, and corporate records; establish, exercise, or defend legal claims; enforce agreements; obtain professional advice; or complete a financing, acquisition, merger, restructuring, or sale of all or part of the business.

6. Automated processing and rankings

CloserLeague uses deterministic software logic to parse sale information, determine whether review is needed, calculate totals and placements, determine leader or spree status, and generate presentation events.

These functions are intended to administer sales competitions and recognition. They are not designed to make employment, compensation, promotion, termination, discipline, insurance-eligibility, credit, housing, education, or other decisions producing legal or similarly significant effects.

Customer organizations are responsible for appropriate human review and may not rely on CloserLeague as the sole decision-maker for legally significant decisions.

7. How we disclose personal information

We may disclose personal information as follows:

7.1 Customer organizations and authorized users

Information may be made available to the relevant customer's owners, administrators, managers, or other authorized users according to product permissions and configuration.

7.2 Public viewers

Information configured by a customer for public leaderboards, public history, final standings, or seller achievement walls may be disclosed to anyone who accesses those pages.

7.3 Service providers

We may use vendors that provide infrastructure, hosting, databases, payment processing, email, authentication, security, error monitoring, support, and professional services. Those providers may process information on our behalf or, where applicable, for their own disclosed purposes.

7.4 Stripe and integrations

We exchange information with Stripe as needed for subscriptions and payments, and with the connected messaging platform (GroupMe, Slack, or Discord) as needed to operate the customer's connected chat workflow. Future integrations will be addressed by this Policy or additional notice before materially different processing begins.

7.5 Legal, safety, and professional disclosures

We may disclose information when reasonably necessary to comply with law or lawful process; protect rights, safety, property, or security; investigate fraud or misuse; enforce our agreements; or obtain legal, accounting, insurance, financing, or other professional services.

7.6 Business transactions

Information may be disclosed or transferred as part of a merger, financing, acquisition, bankruptcy, restructuring, asset sale, or similar transaction, subject to applicable law.

7.7 At a customer's or individual's direction

We may disclose information when an authorized customer or individual directs us to do so.

8. Sale, sharing, and targeted advertising

As of the Last Updated date, CloserLeague does not sell personal information for money.

CloserLeague discloses limited advertising measurement information to Meta as described in section 3.10. Under some U.S. state privacy laws this disclosure may be treated as sharing for cross-context behavioral advertising, and CloserLeague treats it as such. It occurs only on the public acquisition surfaces, only while you have allowed optional tracking, and never from within the authenticated product.

Permitted attribution information may be retained in consent-eligible first-party storage and handed to the eligible app acquisition flow.

Raw advertising click identifiers are not provided to Clarity. Where you arrived from a Meta advertisement, the Meta click identifier may be used to reconstruct Meta’s own _fbc value as described in section 3.10.

You may opt out at any time using the privacy choices control described in section 3.10, or by sending a Global Privacy Control signal, which we honor worldwide.

We disclose information to service providers and contractors for business purposes. Those disclosures are not intended to be sales or targeted-advertising disclosures where the applicable contractual and legal requirements are satisfied.

If we materially change these practices, we will update our notices and provide any opt-out mechanism required by applicable law, including recognition of valid opt-out preference signals where required.

9. U.S. state privacy rights

Depending on your state of residence, the nature of the information, CloserLeague's role, and whether the applicable law covers CloserLeague or the relevant customer, you may have rights to:

• Confirm whether personal information is processed;
• Access personal information;
• Correct inaccurate personal information;
• Delete personal information, subject to exceptions;
• Obtain a portable copy of certain information;
• Obtain information about categories, sources, purposes, or recipients;
• Opt out of sale, targeted advertising, sharing, or certain profiling;
• Limit certain uses of sensitive personal information;
• Appeal a denied request where applicable; and
• Exercise rights without unlawful discrimination or retaliation.

To submit a request concerning information for which CloserLeague acts as controller or business, contact us using Section 17. We may need to verify identity, authority, and the relationship to the relevant team.

When CloserLeague processes seller or employee information on behalf of a customer, we may direct the request to that customer or assist the customer in responding.

These rights are subject to statutory thresholds, exemptions, exceptions, verification rules, and other limitations.

California disclosure

Depending on use of the Services, categories of personal information we may process include:

We use and disclose these categories for the purposes described in this Policy and retain them according to Section 12.

10. EEA, UK, and other international users

CloserLeague is a U.S.-based service and is not currently specifically marketed to individuals in the European Economic Area or United Kingdom. Nonetheless, an individual located outside the United States may encounter the Services, and a customer organization may have participants in another country.

Where the GDPR, UK GDPR, or another law requiring a legal basis applies to processing for which CloserLeague is the controller, the applicable basis may include:

• Performance of a contract or requested precontractual steps;
• CloserLeague's legitimate interests in operating, securing, supporting, and improving the Services, balanced against applicable individual rights;
• Consent where consent is legally required; or
• Compliance with a legal obligation or the establishment, exercise, or defense of legal claims.

Where CloserLeague acts as a processor for a customer, the customer is responsible for determining its lawful basis and issuing legally sufficient instructions.

International transfers and processor terms

CloserLeague and its providers may process information in the United States. If a customer requires GDPR, UK GDPR, or similar controller-processor terms or an international-transfer mechanism, the parties must put an appropriate data processing addendum or other required agreement in place before using CloserLeague for processing that legally requires those terms.

CloserLeague does not represent in this Policy that it participates in a particular privacy certification or international transfer framework unless that representation is separately published and current.

11. Global Privacy Control and Do Not Track

An active Global Privacy Control signal disables Clarity, the Meta Pixel, and nonessential acquisition storage for that browser worldwide. This applies even if the browser previously stored a consent grant. When the signal is active, we clear or suppress Clarity cookies and nonessential first-party acquisition state and do not create new nonessential acquisition storage.

We also honor a valid browser-based opt-out preference signal as an opt-out request where and to the extent applicable law requires.

An ordinary “Do Not Track” signal is different from Global Privacy Control. The Services may not respond to an ordinary “Do Not Track” signal where no applicable law requires a response.

12. Retention, deletion, and customer instructions

CloserLeague does not currently maintain a single fixed deletion period for every category of information. We retain personal information for no longer than reasonably necessary for the purpose for which it is processed, taking into account:

• The duration of the customer relationship;
• Whether an account, team, competition, or public history remains active;
• The customer's instructions where CloserLeague acts as processor;
• Competition-integrity and historical-record needs;
• Security, fraud-prevention, and dispute needs;
• Applicable limitation periods;
• Tax, accounting, and legal obligations; and
• Backup or disaster-recovery cycles, if applicable.

Completed competition results and trophies may be retained longer than active sale-processing data when the customer uses historical competition and achievement features.

Product events described in Section 3.9 and cancellation feedback described in Section 3.8 are deleted 24 months after the activity they record.

CloserLeague does not currently promise an automated self-service deletion tool. Individuals and customers may submit deletion or access requests using Section 17. We will respond as required by applicable law and contract.

Where CloserLeague acts as a processor and applicable law or a data processing addendum requires return or deletion at the end of processing, we will follow the applicable customer's lawful instructions, subject to legal retention requirements and practical backup limitations permitted by law.

Information made public and copied by third parties may remain outside CloserLeague's control after the original CloserLeague record or page is removed.

13. Security and security incidents

CloserLeague uses administrative, technical, and organizational safeguards designed to protect personal information appropriate to the nature and scale of the Services. Security measures and infrastructure may change as the Services evolve.

No method of transmission or storage is completely secure. We cannot guarantee that unauthorized access, loss, alteration, or disclosure will never occur.

Customers are responsible for protecting manager credentials and registration codes, limiting account access, using secure devices, removing access that is no longer appropriate, and promptly reporting suspected compromise.

If we become aware of a security incident involving personal information, we will investigate and provide notices to customers, affected individuals, or authorities where required by applicable law or contract.

CloserLeague does not claim SOC 2, ISO 27001, HIPAA, or another security or compliance certification unless expressly stated in a current written CloserLeague publication or agreement.

14. Children's privacy

The Services are designed for business organizations and are not directed to children under 13. Manager accounts are intended for adults who are legally capable of entering a binding agreement.

We do not knowingly solicit personal information directly from children in violation of applicable law. If you believe a child's information was improperly submitted, contact us.

Customer organizations are responsible for determining whether any minor may lawfully participate in a customer competition and for obtaining any required parental, guardian, employment, or other authorization.

15. Third-party services

The Services interact with third-party providers, including GroupMe, Slack, Discord, Stripe, Microsoft, and Meta. Microsoft provides Clarity for the bounded public acquisition measurement described in section 3.10. Microsoft receives only the Clarity information identified there; raw advertising click identifiers and information from excluded private product and payment surfaces are not part of that analytics flow. Meta provides the advertising measurement described in section 3.10 and receives only the information identified there, which it processes as an independent controller; Meta receives no information from the authenticated product.

Third parties may process information under their own privacy practices when they provide analytics, integrations, or payment services. We do not control a third party’s independent privacy practices, availability, or security. Review the applicable third party’s privacy information before authorizing an integration or payment relationship.

If we add third-party analytics or integrations, we will update our notice where legally required.

16. Changes to this Policy

We may update this Policy as CloserLeague's product, integrations, vendors, business model, or legal obligations change.

We will post the revised Policy and update the "Last Updated" date. We will provide additional notice where required by law. If a materially new use of personal information legally requires consent or customer authorization, we will obtain it before beginning that use.

17. Contact us

Questions, privacy requests, or concerns may be sent to:

When a request concerns information submitted by an employer, agency, team, or other customer, please identify that organization so we can route or evaluate the request appropriately.

See also our Terms of Service.