Legal information

White-label Terms

These White-label Terms govern branded CourseBoot solutions, enterprise infrastructure, custom integrations and related business cooperation.

Last updated: July 27, 2026

1

Introduction

1.1General provisions

These White-label Terms govern the provision, use and management of CourseBoot white-label solutions, including branded platform access, custom integrations, enterprise infrastructure and other business services. They define the rights, obligations and cooperation rules applicable to clients using CourseBoot through a white-label partnership.

The purpose of these Terms is to support legally compliant enterprise cooperation, protect platform infrastructure and provide transparent conditions for scaling partner businesses.

1.2Who these Terms apply to

These White-label Terms apply to users and organizations that use or plan to use CourseBoot white-label services.

White-label functionality is not part of standard platform access and is provided only through separate business cooperation.

  • Business clients and agencies.
  • Creators and enterprise partners.
  • SaaS clients and education businesses.
  • Consulting companies and corporate training providers.
  • Franchise operators and white-label resellers.

1.3White-label access only with platform approval

Access to white-label services is granted only after prior approval by CourseBoot. CourseBoot may take the following actions without being required to provide a detailed explanation.

White-label access is not an automatic user right.

  • Approve access or reject an application.
  • Request business verification and legal documentation.
  • Define the service scope and restrict available integrations.
  • Determine onboarding conditions.

1.4Related legal documents

These White-label Terms form part of the platform's legal framework and should be applied together with the following documents and rules.

Where related documents conflict, CourseBoot may determine how the relevant rules apply in accordance with legal compliance requirements and mandatory law.

1.5Platform control and enforcement

CourseBoot may monitor and control the use of white-label services and apply enforcement measures concerning clients and infrastructure.

These measures may be applied for violations of these Terms, fraudulent activity or misuse of services.

For severe violations, CourseBoot may act without prior notice.

  • Restrict access or suspend services.
  • Freeze operations or terminate cooperation.
  • Remove integrations or request a compliance review.
  • Initiate legal review.
2

White-label eligibility

2.1Who may access white-label services

White-label access is available only to business clients, agencies, enterprise partners and other commercial entities that satisfy CourseBoot's internal requirements and receive approval.

White-label cooperation is intended for genuine business activity and not for ordinary individual platform use.

2.2Approval only by CourseBoot

CourseBoot independently determines the following elements of white-label access.

Approval is granted solely at CourseBoot's discretion.

  • Applicant eligibility and business suitability.
  • Access levels and available integrations.
  • Onboarding conditions and pricing models.
  • Enterprise cooperation format.

2.3Business verification

CourseBoot may require a client to complete business verification covering the following matters.

Access may be delayed or restricted until verification is completed.

  • Legal business status and company ownership.
  • Operational activity and source of payments.
  • Tax compliance and legitimacy of the business model.
  • Compliance with local law.

2.4Required company information

CourseBoot may request the following company information and documents.

Providing false or misleading information may result in refusal or termination of services.

  • Legal entity name and registration details.
  • Jurisdiction and business address.
  • Authorized representatives and billing or payment details.
  • Compliance documentation.

2.5Compliance review

CourseBoot may conduct a compliance review evaluating the following factors.

CourseBoot may refuse cooperation where internal standards are not satisfied.

  • Legal and fraud risks.
  • Business reputation and content compliance.
  • Anti-money laundering considerations.
  • Intellectual property compliance and platform safety.

2.6Final approval decision

CourseBoot independently makes the final decision to grant, restrict or deny white-label access under internal compliance, fraud prevention and business protection procedures.

3

Services provided

3.1White-label services

CourseBoot may provide access to branded platform infrastructure, custom integrations and enterprise functionality under the agreed service scope.

The specific service set is determined individually according to the cooperation model, business requirements, onboarding needs and commercial agreement.

White-label services are not part of a standard platform tariff and are provided only under a separate agreement.

3.2Branded platform access

A client may receive branded platform access using its own brand identity and a customized interface within CourseBoot's agreed technical capabilities.

All brand elements must comply with applicable law and CourseBoot compliance requirements.

  • Custom domain options.
  • Company branding.
  • Branded student area.
  • Branded Creator Dashboard.
  • Logo integration.
  • Visual identity customization.
  • White-label interface settings.

3.3Core platform functionality

A white-label package may provide access to the following CourseBoot systems.

The actual functionality depends on the agreed commercial package.

  • Creator Dashboard access.
  • Course management and Course Builder.
  • AI tools and AI avatars.
  • Subscription and certification systems.
  • Affiliate integrations and partner dashboards.
  • Payment integrations and analytics systems.
  • Student and client management tools.

3.4Payment and monetization infrastructure

CourseBoot may provide integrations supporting the following payment and monetization functions.

Availability depends on jurisdiction, compliance review and CourseBoot's technical capabilities.

  • Payment providers.
  • Subscription billing and recurring payments.
  • Creator and affiliate payouts.
  • Commission systems.
  • Enterprise invoicing.
  • Custom monetization flows.

3.5Service scope limitations

CourseBoot may apply the following service scope limitations.

The final service scope is determined by CourseBoot or by a separate agreement between the parties.

  • Define available functionality and restrict integrations.
  • Change the service scope or reject custom requests.
  • Establish onboarding conditions.
  • Apply technical limits.
4

Custom agreements

4.1Individual cooperation terms

White-label cooperation may include individual terms based on business scale, integration type, user volume and enterprise requirements.

Standard platform terms may be supplemented by business agreements, enterprise contracts or custom service arrangements.

4.2Custom pricing

White-label pricing is determined individually and may include the following charges.

CourseBoot determines the final pricing structure after business review.

  • Setup and onboarding fees.
  • Monthly subscription fees.
  • Enterprise billing.
  • Custom development and API integration costs.
  • Branded platform fees.
  • Support packages and infrastructure scaling fees.

4.3Negotiated commissions

The parties may use the following financial models within white-label cooperation.

Commission terms are agreed separately according to the cooperation format.

  • Negotiated commissions.
  • Custom revenue share models.
  • Fixed-fee agreements.
  • Enterprise payout structures.
  • Partner revenue allocation.
  • Custom affiliate logic.

4.4Separate contracts

The following documents may apply to individual white-label clients.

A separate agreement may take precedence over these general Terms within the relevant business relationship.

  • Separate service agreements.
  • Enterprise and partnership contracts.
  • Reseller agreements.
  • Non-disclosure agreements.
  • Compliance documents and custom legal addenda.

4.5Service Level Agreement where applicable

Enterprise or large-scale infrastructure cooperation may include a separate Service Level Agreement covering the following matters.

An SLA is available only under a separate agreement.

  • Support response times.
  • Uptime expectations.
  • Technical escalation procedures.
  • Incident handling.
  • Maintenance windows.
  • Priority support conditions.

4.6Onboarding terms

White-label onboarding may include the following steps.

Onboarding and launch conditions are determined individually.

  • Business verification and legal review.
  • Branding approval and technical setup.
  • Payment configuration and domain connection.
  • Integration approval.
  • Compliance verification and launch preparation.

4.7Custom service scope

CourseBoot may determine the available service scope for each white-label client based on the following factors.

White-label services are not a fixed package and may change during a particular collaboration.

  • Business model and legal risks.
  • Infrastructure load and payment requirements.
  • Compliance standards.
  • Enterprise scale and partner reliability.
5

Payments and billing

5.1General payment terms

Use of CourseBoot white-label services is paid under the agreed business model, custom agreement or enterprise contract.

Financial terms are determined individually according to the service scope, integration level, branded solutions and client requirements.

5.2Subscription fees

White-label cooperation may include recurring subscription fees for platform infrastructure, branded access, creator systems, affiliate integrations, payment modules and other enterprise services.

Billing may use the following formats.

  • Monthly or annual subscriptions.
  • Recurring enterprise billing.
  • Usage-based pricing.
  • Negotiated recurring fees.

5.3Setup fees

One-time setup fees may apply to the following launch activities.

Setup fees are determined individually according to project complexity.

  • Onboarding and technical integrations.
  • Custom branding setup and domain connection.
  • Platform and creator system configuration.
  • Affiliate and certification module setup.

5.4Custom invoices and enterprise billing

Payments may be made through the following methods.

CourseBoot determines available payment methods according to jurisdiction, compliance requirements and partnership type.

  • Custom invoices and enterprise billing systems.
  • Stripe or bank transfer.
  • Approved payment providers.
  • Separate financial agreements.

5.5Payment terms

Payment terms, billing cycles, due dates, invoice periods and financial obligations are defined by the applicable individual agreement or enterprise contract.

The client must satisfy all payment obligations on time under the agreed billing terms.

5.6Late payment rules

For late payment, CourseBoot may take the following actions.

Restrictions may remain until all financial obligations have been satisfied.

Overdue payments may affect continued use of platform infrastructure and enterprise support.

  • Suspend access to white-label services.
  • Restrict platform functionality and freeze integrations.
  • Delay onboarding or block enterprise features.
  • Terminate cooperation.
  • Apply additional recovery procedures.
6

Client responsibilities

6.1General client responsibilities

The white-label client is solely responsible for lawful, correct and compliant use of white-label services, branded infrastructure and all business tools provided by CourseBoot.

The client must ensure that its activities comply with these Terms, applicable law and internal platform rules.

6.2Legal compliance

The client is independently responsible for compliance with the following legal requirements.

CourseBoot is not responsible for legal violations committed by the white-label client.

  • Local law and tax obligations.
  • Consumer protection and privacy rules, including the GDPR.
  • Advertising compliance and licensing obligations.
  • Certification legality and educational compliance requirements.

6.3Content responsibility

The client is fully responsible for all content created, uploaded, sold or distributed through the white-label environment.

The client guarantees that its content does not infringe copyright, trademarks or other third-party intellectual property rights.

  • Courses and creator content.
  • Certifications and educational materials.
  • Marketing materials, landing pages and affiliate content.
  • Branded assets and business communications.

6.4User management

The client is independently responsible for the following user and access management matters.

Actions performed by users in the white-label environment are treated as the client's responsibility.

  • Management of internal users and creator access.
  • Team permissions and student or partner access.
  • Account security and internal fraud prevention.
  • Responsible use of platform infrastructure.

6.5Payment obligations

The client must satisfy all applicable financial obligations, including the following.

Late payment may result in service restrictions or immediate termination.

  • Subscription and setup fees.
  • Enterprise invoices and negotiated payments.
  • Custom billing obligations and payment provider charges.

6.6Brand usage responsibility

The client is responsible for lawful use of the following brand and commercial assets.

Misleading brand representation, false partnerships and unlawful use of third-party brands are prohibited.

  • Brand names, logos and commercial identity.
  • Custom domains and branded materials.
  • Partner representations.

6.7Data compliance

The client must manage personal data lawfully and in accordance with the following requirements.

CourseBoot may apply enforcement without prior notice where data compliance is violated.

  • GDPR compliance and user consent management.
  • Cookie compliance and lawful marketing practices.
  • Lawful data processing and privacy obligations.
7

Prohibited use

7.1Prohibited use

The white-label client and its creators, affiliates, partners and internal users may not use CourseBoot for illegal, fraudulent or non-compliant activity.

Misuse of platform infrastructure is treated as a serious violation of these Terms.

7.2Examples of prohibited use

  • Illegal business activity — activity that violates applicable laws or regulatory standards.
  • Fraud — fraudulent schemes, financial manipulation, fake payments or payout abuse.
  • Fake certificates — false or misleading certificates without genuine educational confirmation.
  • Copyright violations — stolen content, unauthorized materials or piracy.
  • Scam offers — deceptive sales funnels or fraudulent educational promises.
  • Trademark abuse — unlawful use of brands, logos or false brand representation.
  • Infrastructure misuse — abusive traffic, spam or unauthorized automation.

7.3Additional prohibited activity

  • Fake affiliate structures and activity creating money laundering risks.
  • Illegal use of creator payout systems.
  • Abusive refund schemes and fake subscriptions.
  • Unauthorized payment routing.
  • Illegal transfer of access to platform services.

7.4Platform enforcement

Where prohibited use is detected, CourseBoot may take the following actions.

For severe violations, these measures may be taken without prior notice.

  • Suspend access and freeze operations.
  • Remove integrations and block monetization.
  • Freeze payouts and cancel enterprise agreements.
  • Terminate white-label cooperation or initiate legal review.

7.5Final enforcement decision

CourseBoot independently makes the final decision concerning prohibited use, compliance violations and enforcement under internal security, fraud prevention and legal compliance procedures.

8

Platform rights

8.1General rights of the platform

CourseBoot may control the use of white-label services, branded infrastructure, enterprise integrations and related business activity.

CourseBoot may apply restrictions, verification and enforcement to protect platform security, legal compliance and business operations.

8.2Platform rights and available actions

For violations, fraud indicators, compliance risks or misuse, CourseBoot may take the following actions.

  • Temporarily restrict white-label platform, dashboard or enterprise tool access.
  • Disable individual services, integrations or branded functionality in whole or in part.
  • Temporarily stop payouts, monetization flows, subscriptions or other operations.
  • Terminate white-label cooperation and the business relationship.
  • Restrict API access, partner connections, payment integrations or external services.
  • Submit the matter for internal or external legal review.

8.3Grounds for applying restrictions

Platform restrictions may be applied in the following circumstances.

CourseBoot independently assesses risk and determines the necessary restrictions.

  • Legal violations and fraudulent activity.
  • Fake certifications or copyright abuse.
  • Payment risks and data compliance violations.
  • Repeated policy violations or brand misuse.
  • Suspicious enterprise operations or platform security risks.
  • Abusive monetization behavior.

8.4Action without prior notice

For severe violations, legal threats, fraud risks or security concerns, CourseBoot may impose restrictions without prior notice or a detailed explanation.

8.5Final platform decision

All decisions concerning service restrictions, white-label suspension, enterprise restrictions and agreement termination are made by CourseBoot and are final unless applicable law expressly provides otherwise.

9

Data and privacy

9.1General provisions

The white-label client must ensure lawful, secure and compliant use of personal data in connection with CourseBoot infrastructure and its business operations.

Data collection, storage, processing and transmission must comply with the GDPR, applicable privacy rules and other relevant law.

9.2Privacy obligations

The client is responsible for the following privacy matters.

The client must maintain its own Privacy Policy where required by law or its business model.

  • Lawful data collection and user consent management.
  • Transparent privacy disclosures and a valid legal basis for processing.
  • Proper data handling and internal privacy compliance.
  • Customer communications relating to personal data.

9.3Cookie compliance

When using cookies, tracking systems, analytics or marketing pixels, the client must satisfy the following requirements.

Unlawful tracking may result in immediate enforcement.

  • Collection of cookie consent and lawful implementation of tracking.
  • User notification and browser compliance.
  • Transparency concerning data use.
  • Compliance with applicable Cookie Policy requirements.

9.4GDPR compliance

The white-label client must comply with the following GDPR obligations.

CourseBoot may request confirmation of GDPR compliance at any time.

  • GDPR requirements and data minimization principles.
  • Protection of user rights, including access, deletion and portability.
  • Consent withdrawal rights.
  • Lawful marketing practices and security obligations.

9.5Third-party processors

When using third-party processors, payment providers, CRM systems or analytics platforms, the client is responsible for the following matters.

CourseBoot is not responsible for violations by third-party services selected by the client.

  • Lawful integrations and vendor compliance.
  • Data transfer legality and processor agreements.
  • Compliance of international transfers.
  • Secure handling of customer data.

9.6Platform responsibilities

CourseBoot provides platform infrastructure, payment systems, creator tools and basic security architecture.

The client remains independently responsible for internal compliance, user behavior, business operations and lawful data use.

9.7Final compliance decision

For privacy, GDPR or data compliance violations, CourseBoot may take the following actions.

CourseBoot independently makes the final compliance enforcement decision.

  • Restrict access or suspend integrations.
  • Freeze operations or terminate cooperation.
  • Initiate legal review.
10

Termination

10.1Termination of cooperation

CourseBoot or the client may terminate white-label cooperation in accordance with these Terms, applicable business agreements, enterprise contracts or custom arrangements.

Termination may apply to the full relationship or to individual services, integrations or enterprise access levels.

10.2Either party may terminate

Either party may initiate termination in the following circumstances.

CourseBoot may terminate cooperation immediately and without prior notice for severe violations.

  • Completion of business cooperation.
  • Violation of the applicable agreement.
  • Failure to meet payment obligations.
  • Legal compliance concerns or fraud risks.
  • Business restructuring or strategic decisions.
  • Expiration of an enterprise agreement.

10.3Notice periods where applicable

Where an SLA, enterprise agreement or custom contract specifies a notice period, termination follows that contractual period.

Without specific contractual terms, CourseBoot may determine the offboarding process and final settlement conditions.

10.4Active obligations survive termination

The following obligations and matters remain effective after termination.

Termination does not release either party from responsibility for actions taken before cooperation ended.

  • Compliance and confidentiality obligations.
  • Copyright and intellectual property responsibilities.
  • Legal claims, refunds and chargeback responsibilities.
  • Accounting and archived record requirements.
  • Pending legal or fraud reviews.

10.5Payment obligations remain

Financial obligations incurred before termination remain binding until fully paid.

CourseBoot may retain access to specified data or services until all financial obligations are settled.

  • Unpaid invoices and subscription fees.
  • Setup fees and enterprise billing.
  • Outstanding balances and late-payment liabilities.
  • Refund-related adjustments.

10.6Final termination decision

CourseBoot makes the final decision concerning termination, service closure and continuing obligations under internal business policy, legal compliance requirements and the applicable enterprise arrangement.

11

Disclaimer

11.1No guarantee of results

CourseBoot provides white-label infrastructure, branded access and enterprise systems as a technology framework and does not guarantee the following results.

Results depend on the client's business model, product quality, marketing strategy and market conditions, which CourseBoot does not control.

  • Guaranteed income or revenue.
  • Guaranteed business results or ROI.
  • Guaranteed traffic or client growth.
  • Guaranteed profitability.

11.2Client responsibility

The white-label client is solely responsible for the following matters.

CourseBoot does not manage the client's business operations and is not responsible for the client's financial outcomes.

  • Business decisions and legal compliance.
  • Marketing strategy and customer acquisition.
  • Creator management and sales performance.
  • Internal operations and data compliance.

11.3No performance guarantee

Providing a branded platform, custom domain or enterprise integration does not automatically create profit or scale a business.

All business outcomes depend on the client's actions and management.

  • Specific conversion rates.
  • Affiliate performance or creator success.
  • Marketing effectiveness.

11.4Infrastructure only

CourseBoot acts only as a SaaS infrastructure provider and technology partner.

A white-label solution is infrastructure only.

Technology does not guarantee profit.

11.5Final limitation

The client uses white-label services at its own risk and accepts full responsibility for business results, monetization strategy and enterprise growth.

12

Platform final decision

12.1Platform discretion

CourseBoot may independently decide whether to provide, restrict, suspend or terminate white-label access, enterprise services, branded functionality and related business operations.

CourseBoot determines cooperation terms, access levels, integrations and service scope at its discretion.

12.2Manual review

CourseBoot may manually review business activity, white-label operations, creator systems, payment behavior, integrations and enterprise requests.

A review may be triggered by suspicious activity, additional verification needs or checks involving particular transactions or the entire relationship.

12.3Approval rights

CourseBoot is not required to approve the following requests automatically.

CourseBoot may approve, reject or request additional verification without providing a detailed explanation.

  • White-label access or enterprise onboarding.
  • Custom integrations or branded platform requests.
  • Custom domains or custom billing terms.
  • Partner privileges or creator monetization requests.
  • Payout approvals.

12.4Fraud protection

CourseBoot uses fraud prevention and compliance monitoring to protect infrastructure, the creator ecosystem and payment security.

Where fraud risks or suspicious activity are detected, the following actions may be taken without prior notice.

  • Freeze operations and suspend services.
  • Restrict integrations and hold payouts.
  • Initiate legal review or terminate cooperation.

12.5Legal compliance

White-label decisions are made in accordance with applicable law, AML requirements, GDPR compliance and CourseBoot's internal security policy.

CourseBoot's final decision is binding on the client unless applicable law expressly provides otherwise.

13

Governing law

13.1Applicable law

These White-label Terms and legal relations arising from white-label services, enterprise cooperation and platform enforcement are governed by and interpreted under Estonian law, regardless of conflict-of-law rules in other jurisdictions.

13.2Jurisdiction of disputes

Disputes, claims and legal complaints arising from white-label cooperation or these Terms are subject exclusively to the competent courts of Estonia unless mandatory applicable law expressly provides otherwise.

13.3Platform protection

CourseBoot may continue applying compliance procedures, service restrictions, payout holds and integration freezes until final legal resolution in order to protect platform infrastructure, business operations and enterprise security.

13.4Final legal framework

By using white-label services, the client agrees that legal matters relating to enterprise cooperation, branded platform use and enforcement are resolved under Estonian law and within Estonian jurisdiction.

14

Contact

14.1Official contacts

For questions concerning these White-label Terms, enterprise access, billing, integrations or business cooperation, clients should contact CourseBoot through its official support channel.

14.2Contact email

Official requests, legal notices, onboarding discussions and compliance documentation are reviewed only through CourseBoot's official communication channels.

14.3Review and response

CourseBoot may determine the review period, verification procedure and scope of legal review required for each request.

For high-risk violations, fraud concerns or severe contractual breaches, CourseBoot may apply immediate enforcement until verification is complete.