This policy explains what personal data CySec 2026 collects, why, and how it is handled, in line with the Personal Data Protection Order (PDPO) of Brunei Darussalam. It covers this website and the sponsor application process it runs; ticketing, check-in and the CySecBuddy companion app are operated separately by BCSA's events platform, which shares the same commitment to your data described below.
Last updated: September 2026.
CySec 2026 is organised by the Brunei Cybersecurity Association (BCSA), with Cyber Security Brunei (CSB). BCSA is the data controller for the personal data described in this policy.
For any privacy query, or to exercise the rights set out below, contact cysec [at] bcsa [dot] bn.
Sponsor applications — company name and address, sponsor contact name, email and phone number, your uploaded logo, and proof of payment. We use this to process your sponsorship, allocate booths or exhibition slots, issue invoices, coordinate the event with you, and — only if you tick the marketing consent box — send you sponsorship-related updates.
Newsletter and event updates — if you sign up for updates about CySec 2026, we collect your email address to send them, and you can opt out at any time.
Attendee and ticketing data — registration, check-in and the CySecBuddy companion app are run by BCSA's events platform, not by this website. That platform holds your name, email and organisation to run your ticket and personal schedule. If you choose to take part in on-site networking, it may also hold your session bookmarks and, only where you explicitly opt in at the time, booth visits, contact-card shares with exhibitors, and connections with other attendees. Nothing in this category is collected unless you take an affirmative action to enable it.
Technical data — like most websites, our servers keep basic access logs (such as IP address and request timing) for security, abuse prevention and rate-limiting. We do not use this data for tracking or profiling.
We rely on your consent (for example, ticking the sponsorship terms box, or opting in to marketing updates or on-site networking features) and on our legitimate interest in administering the event securely and reliably, consistent with the PDPO.
We use personal data to administer CySec 2026: processing sponsorships, issuing invoices, running registration and check-in, and keeping the event secure. We do not sell personal data, and we do not share it with third parties beyond what is described here.
Sponsor and exhibitor lead data — such as a contact card or booth visit shared through the networking features — is passed to the specific exhibitor concerned only when you explicitly confirm that share. It is never shared automatically.
We use a small number of service providers to run the event — for hosting, email delivery and payment processing — who act as processors under our instructions and are not permitted to use your data for their own purposes.
We keep personal data only as long as needed for the event and a limited period afterwards — for example, to finalise invoicing or respond to queries — after which it is deleted or anonymised. Networking data such as leads and connections shared during the event is automatically purged on a set schedule after the conference ends.
You can ask to access the personal data we hold about you, ask us to correct it, withdraw consent you previously gave (for example, for marketing updates or networking features), or ask us to delete it. Email cysec [at] bcsa [dot] bn and we will respond as soon as we reasonably can.
This website uses only the cookies and local storage needed for it to function, including remembering that you have seen our cookie notice. See our Cookie Policy for details.
We apply technical and organisational measures to protect personal data against unauthorised access, alteration, disclosure or loss, including encrypted transport (HTTPS), a strict per-request content security policy, and access controls on sponsor and application data. No system is perfectly secure, but we take these obligations seriously.
We may update this policy from time to time, for example as the event or its tooling evolves. The date above shows when it was last updated.