Baxtlilar
How we review proposals

From application to launch — value and boundaries come first

Baxtlilar reviews every partnership proposal separately: from the idea itself and the value for users to the terms of integration, privacy and technical feasibility.

Even a proposal that fits the subject matter is not connected automatically — the format must match the platform’s principles and be clear to the user.

A partnership starts not with placement, but with checking why the user needs it at all.

  1. 01

    Application

    Tell us what you would like to offer.

    First we understand the idea

  2. 02

    Initial check

    We check the fit with the basic principles.

    A category is not approval

  3. 03

    Value and risks

    We assess value, privacy and safety.

    Value must outweigh risk

  4. 04

    Format and boundaries

    We agree the scenario, labelling and data.

    Boundaries first

  5. 05

    Pilot

    If needed, we test the format at a limited scale.

    We test the scenario

  6. 06

    Decision

    We launch, refine or decline.

    An application does not guarantee a launch

Partnership proposal status

Organisation
Family Education Lab
Category
Education
Format
Expert materials
  1. Application received
  2. Initial check
  3. Value and risk assessment
  4. Format agreement
  5. Pilot
  6. Decision

Currently checking

  • Value for usersMeets the bar
  • PrivacyNo data sharing required
  • LabellingExpert material
  • MatchingNo effect

Next step

Clarify the format of interaction

A review status does not mean the partnership is automatically approved.

What shapes the decision

Value

Whether there is clear value for the user.

Reputation

How well-founded trust in the organisation is.

Transparency

Whether the offer and its terms are clear.

Privacy

Whether personal data is needed, and why.

Safety

Whether there is pressure or added risk.

Product fit

How naturally the integration complements Baxtlilar.

Not every proposal becomes a partnership

We may decline cooperation if a proposal:

  • creates no clear value
  • requires unjustified access to data
  • involves hidden advertising
  • interferes with matching
  • puts pressure on the user
  • misleads the user
  • conflicts with safety principles
  • cannot be implemented properly at this stage

Declining a format is not a negative judgement of the organisation — sometimes a service simply does not fit the Baxtlilar architecture.

Before an agreed integration, no user data is shared

Reviewing a proposal opens none of the following to a partner:

  • the user base
  • contacts
  • questionnaires
  • segments at the level of individual people
  • matching results
  • messages
  • behaviour history

To assess a partnership we use information about the partner’s proposal, not data about users.

Reviewing a partner ≠ guaranteeing their services

Admitting an organisation to a partnership format does not entitle anyone to claim that Baxtlilar guarantees the quality of its services or that the service is “fully verified”.

We use wording that matches the actual scope of the review: “Baxtlilar partner” when the cooperation is in force, “Partner service” for a specific integration.

Value and safety first — integration after

We check the value

Whether there is a real reason to add the service.

We fix the boundaries

It is clear what a partner can and cannot do.

We test when needed

Complex formats go through a limited check.

We launch only after a decision

An application or a pilot is not yet a permanent partnership.

Propose a partnershipSee the requirements for partners