General Privacy Statement

Key Definitions

To make the policy practical, we explain terms using examples relevant to our executive workshops and case-study format. Each definition is followed by a short scenario showing how that term applies when a director registers for a cohort or submits a case study for group review.

Personal data means any information relating to an identified or identifiable person. Example: when a participant registers for a training cohort, their name, business title and email are collected to manage enrollment and to include them in group case discussions.

Processing covers any operation performed on personal data, such as collection, storage, analysis, or sharing. Practical case: anonymizing a business scenario submitted by an owner before using it in a public workshop.

User refers to any individual who visits the site, registers for programs, attends workshops or submits materials. Scenario: a CEO who uploads a growth-case study to request feedback from a peer cohort.

Service means our suite of educational offerings, including live workshops, recorded modules, peer review sessions and downloadable tools. Example: the recorded module on mindful decision-making combined with budget modeling.

Cookies are small data files stored in a browser to help the site remember preferences and support analytics. Example: a persistent cookie that keeps a logged-in director in the correct cohort portal between sessions.

User-Provided Data

Information participants supply when they sign up, join a cohort, submit a case study, or communicate with our team. Each item below includes a brief example of how it is used in training scenarios.

• Contact details: name, business title, company name, email and phone. Example: used to send cohort schedules and speaker notes for a board-level scenario workshop.
• Business data and case materials: business summaries, organizational charts, and workshop case submissions. Example: anonymized case materials are used during peer-review sessions to explore decision pathways.
• Registration information: payment details, billing address and VAT or business ID when required. Example: used to issue receipts for company management departments and to validate corporate participation.
• Preferences and learning goals: submitted during onboarding surveys. Example: tailoring scenario selections to emphasize succession planning or availability management for a specific cohort.
• Communications: messages platform with instructors or support, including feedback on practical exercises. Example: an platform outlining how a director applied a scenario in their board meeting.
• Multimedia submissions: recordings or slides uploaded for group review. Example: a recorded presentation of a transformation case used for structured critique within the training.

Third-Party Data Sources

In certain cases we receive data from external providers or partners to support payments, training verification or collaborative case studies. We include examples below to illustrate typical flows.

• Payment processors: limited billing information and transaction identifiers to confirm enrollment and issue receipts. Example: confirming a company invoice for a leadership cohort.
• Third-party collaboration platforms: when a cohort uses an external forum or conferencing tool, basic participation records may be shared to coordinate sessions.
• Public sources or professional directories: optional enrichment of public business profiles when participants consent to include their company case in an aggregate study.

Legal Bases for Processing

We rely on appropriate legal bases depending on the processing activity. Below are the primary bases and practical examples relevant to participants from corporate and executive backgrounds.

• Contract performance: processing needed to deliver training and materials once you enroll. Example: storing registration details so we can grant access to cohort resources.
• Legitimate interests: improving program quality, platform security, and preventing fraud, balanced with participant rights. Example: analyzing anonymized engagement metrics to enhance case selections.
• Consent: where participants opt in to optional uses such as public case publication or marketing communications. Example: requesting consent before a director's case study is included in a public seminar.
• Legal compliance: processing required to satisfy tax and reporting obligations in Thailand or other applicable jurisdictions. Example: retaining invoices and transaction records for statutory audits.

Data Sharing and Disclosure

We share personal data only when necessary for service delivery, legal obligations or with explicit consent. The examples below illustrate typical sharing scenarios tied to our case-based training model.

• With service providers: payment processors, hosting and conferencing platforms to deliver services. Example: sharing billing contact information to issue a corporate invoice.
• With instructors and cohort members: limited case materials shared within a cohort when the participant consents. Example: anonymized business summaries used for group analysis.
• For legal reasons: when required by law, court order, or to comply with regulatory audits. Example: disclosing records in response to a lawful tax authority request.
• With professional advisors: accountants or auditors engaged for compliance, under confidentiality obligations. Example: sharing transaction records with an auditor appointed to review program resources.
• With corporate partners: only when a participant has approved co-branded program participation or public case publication. Example: a company authorizes publication of a transformation case for a joint seminar.
• Aggregated and anonymized data: shared for research or program improvement without identifying individuals. Example: sharing anonymized engagement trends to illustrate program impact to potential corporate clients.

Data Retention

We retain personal data only as long as necessary to fulfill the purposes set out or to meet legal and regulatory requirements. Retention times are illustrated with relevant training scenarios below.

Account and profile data: retained while the account is active and for a reasonable period after inactivity to allow reactivation and record keeping for audits. Example: maintaining a director's access to cohort materials for one year after course completion to support follow-up mentoring.

Communications and support records: kept to resolve disputes and improve services, typically for up to three years unless a longer retention is justified by law. Example: preserving an email thread documenting advised adjustments to a submitted case study.

Technical logs: stored for a limited period to support security monitoring and incident response, commonly for 6 to 12 months. Example: log retention used to contribute an access issue during a live peer-review session.

Deletion procedures: when retention periods expire or upon a valid deletion request, we remove or irreversibly anonymize personal data except where legal obligations require continued retention.

Your Rights

Participants and visitors have rights regarding their personal data. We describe how to exercise these rights and provide practical examples so executives understand the expected timelines and documentation needed.

• How to exercise rights: submit a request to [email protected] or by postal mail to our office at Thanon Kosi, Pak Nam Pho Sub District, Amphoe Mueang Nakhon Sawan District, Nakhon Sawan Province 60000, Thailand. Include sufficient details to locate your records and a copy of government ID if required for verification.
• Response timeframe and possible exceptions: we aim to respond to access and correction requests within a month and will inform you if more time is required. Some requests may be limited where legal or contractual obligations require retention (for example, invoices for tax purposes).
• Right to request correction of inaccurate personal data we hold about you, including updates to contact information and professional details submitted to becybrixlo.
• Right to request deletion of personal data where processing is no longer necessary or where consent has been withdrawn and no legal basis for retention applies.
• Right to restrict processing of your personal data if you contest accuracy or lawfulness of processing while we verify or resolve the issue.
• Right to data portability for information you provided directly to becybrixlo in a structured, commonly used and machine-readable format when applicable.
• Right to object to processing for direct marketing or profiling where such processing is based on legitimate interests; we will cease such processing unless a compelling lawful basis exists.
• Right to lodge a complaint with a supervisory authority in Thailand if you consider our handling of personal data infringes applicable data protection law.

Marketing Communications

becybrixlo may send targeted emails, event invitations, and updates about training programs, case studies and industry insights relevant to business leaders. Marketing messages are based on preferences you set and interactions such as program attendance, downloads, or expressed interests.

You can opt out of marketing communications at any time by using the unsubscribe link in emails or by contacting [email protected]. Opting out will not affect non-marketing messages related to transactions, account administration, or programs you actively participate in.

Links to Third-Party Sites

Our website and communications may include links to third-party sites used for registration, payment processing, analytics, or content hosting. These sites have their own privacy policies. becybrixlo is not responsible for third-party privacy practices and recommends reviewing their policies before providing personal data.