0x03 Terms and conditions

What you agree to, and what is still open.

These terms cover this website and Security BSides Dehradun 0x03. The organiser-confirmed ticket refund and transfer rules are published below. Six sections still have open conditions or need legal review, including the final organiser details, ticket policy wording, after-party conditions and speaker permissions. Each is marked below.

Version
0.16 Last updated . Below 1.0 on purpose: a document with open questions in it has not had a first release.
Still open
Six sections Each is marked in place, and in the contents list, with a To be confirmed chip.
Review status
Organiser draft Speaker permissions need legal review before the CFP opens; the remaining terms need it before 0x03 ticket sales open.

3–4 April 2027 a Dehradun venue, to be announced Applies to this site and to the event

Confirmed rules and pending conditions

1 · Who these terms are between

To be confirmed

The ticket-selling organiser is Aman Kumar, acting in an individual capacity. "Security BSides Dehradun" is the event name, not a registered organisation. Aman Kumar is the seller name to appear on ticket invoices. This name was confirmed on 7 October 2026; the invoice setup still needs to be checked on KonfHub before sales open.

The volunteer organising team helps run Security BSides Dehradun 0x03, reachable at [email protected]. The event is run independently under the Security BSides framework; Security BSides is not a party to these terms and does not organise this event.

Naming the ticket seller does not complete the legal review of these terms or settle the separate speaker-permission and privacy-contact decisions. Final organiser disclosures and the contract wording still need qualified review before ticket sales open. If a registered organisation takes over later, the seller details and any affected terms will be updated explicitly.

2 · Using this website

There is no visitor account to create. Most pages are static; the contact and CTF forms are handled by server-side functions. Analytics run only after you accept them, and no advertising script runs on any page. Accept analytics and two tools set cookies; decline and neither analytics tool runs. The privacy page names both tools and lists the cookies, and it explains the contact form, CTF registration and email correspondence.

You may read, quote, print and link to anything here without asking, including deep links to a specific section; we try not to break them. The words and the design are the organising team's work. The Security BSides name and mark belong to Security BSides and are used here under their framework, which does not put us in a position to license them onward to you.

What we ask in return is ordinary: do not attempt to disrupt the site or the infrastructure behind it, and do not present yourself as the organising team. If you find a security problem we would genuinely like to hear about it, /.well-known/security.txt says how to report one and what to expect back.

3 · Tickets and registration

To be confirmed

Conference ticket sales are not open yet. When they open they will run through KonfHub, a third party, which means the payment and the ticket itself are handled under that platform's own terms and privacy policy as well as this page. Card details never reach us and we do not store them.

The published ticket calendar opens on 1 November 2026 at 12:00 AM IST and closes on 25 March 2027 at 11:59 PM IST. Published prices do not mean checkout is open. The student tier needs a valid college or university ID at entry. There is no refund for missing or invalid ID, except where required by law. A ticket admits one person for the days it covers. Corporate passes include priority seating at talks, subject to room capacity, but no pass guarantees a seat in a particular talk or workshop. Some rooms are smaller than the conference, and the villages floor is first come, first served.

Organiser-confirmed rules; legal review pending. The refund and transfer decisions below were confirmed on 5 October 2026. Fee exclusions, deadlines and final wording still need qualified legal review before sales open. These conditions do not limit rights required by applicable law.

Refunds

Voluntary attendee cancellations, no-shows, missed conference days and voluntarily unused ticket benefits are non-refundable. This does not cover benefits the organisers fail to provide. The same refund rules apply to Student, Individual, Corporate and CTF Competitor Passes.

If we cancel the conference, we will refund the ticket price paid, excluding booking and payment-processing fees. Eligible refunds will be initiated within 7 working days of the cancellation announcement.

If we postpone the conference, you may keep your ticket for the new dates or request a refund of the ticket price paid, excluding booking and payment-processing fees. Refund requests must arrive within 14 days of the announcement of the new dates. Eligible refunds will be initiated within 7 working days of receiving a valid request. Email [email protected]. Initiation is not a promise that the refund reaches your account within that period; your payment provider controls the crediting time.

Ticket transfers

A Student, Individual or Corporate pass may be transferred once, free of charge, within the same ticket category, subject to organising-team approval. A Student recipient must have a valid college or university ID.

The original buyer must email [email protected] from the email address used for the booking. The request must be received, approved and the transfer completed by . Sending a request before the deadline does not permit completion afterwards. CTF Competitor Passes are non-transferable. Sharing a ticket or QR code is not an approved transfer; the booking must be updated through the organising team.

CTF Competitor Pass

The flat-price ₹799 Competitor Pass is for verified, qualified players only and admits the holder to day one and the on-site CTF final on 3 April 2027. It does not cover day two. Verification and finalist notifications will be complete by . Competitor Pass sales open on and close on . A qualified player with a full-conference pass does not need an extra Competitor Pass. Upgrades cost the difference to the current full-pass price and remain available by [email protected] or through the team on site, including after general sales close. This is an upgrade route, not general ticket sales at the gate.

After-party access and planned hospitality

Corporate passes include an after-party invitation at every price stage, for the pass holder only. There is no accompanying-guest entitlement. Speakers and organisers can attend without purchasing a Corporate Pass. Sponsor representatives can use their allotted social invitations with a valid conference pass; those invitations do not themselves provide conference admission.

Existing sponsor social allocations are 4 for Presenting, 2 for Principal and 1 for Core. Supporting and Contributor sponsorships do not include social invitations. The After-Hours Social sponsorship includes 4 invitations, each requiring a valid conference pass. These authorised attendees are not accompanying guests.

Our hospitality plan funds food and non-alcoholic drinks, with alcohol service within a capped budget. It does not promise unlimited alcohol or a fixed number of drinks per person. Final arrangements are subject to venue rules, age conditions, permissions and bar-service requirements.

Alcohol service is restricted to attendees aged 21 or older. The conference itself sets no minimum age. Alcohol eligibility does not determine venue admission. The after-party venue, admission-age rules and entry-check method are not confirmed. These conditions will be published before sales open. The remedy for a buyer unable to use an included benefit because of an entry restriction also needs confirmation and legal review. The voluntary no-refund rule must not be treated as a waiver for benefits organisers fail to provide. Sales remain closed while these launch conditions are unresolved.

4 · Code of conduct

The code of conduct applies to everyone at the event and in its online spaces: attendees, speakers, sponsors, volunteers and organisers, with no group exempt. By registering or attending you agree to it. It is a term of this agreement, not a suggestion sitting alongside it.

It sets out what is expected, what is not acceptable, how to report an incident, and what the organising team can do in response, up to and including removal from the venue. Reports go to [email protected], and the code of conduct lists two other routes, one of them to the founder and lead organiser. Where a consequence would interact with money already paid, section 3 governs, and section 3 has not been finalised for publication.

5 · Photography and recording

To be confirmed

Consent for photographing people is already settled, and it is settled in the code of conduct rather than here: ask before you photograph or record an identifiable person, and accept the answer. Wide shots of a full room, a stage or the venue may be taken by the team and by press. That is the rule on the floor and nothing below changes it.

We plan to record talks where equipment and venue conditions allow. A speaker may decline recording without affecting selection. Before confirming a place, each accepted speaker will be asked separately whether they agree to recording and publication. A yes covers a complete recording on our official YouTube channel, a link or embed on this website, and short excerpts on our official social channels as one choice. We will not seek a second approval for each clip. No talk recording is published without the speaker's agreement.

Audience questions may be audible in a recorded session, as the code of conduct explains. We plan to mark recorded rooms at the entrance. The formal recording permission, including who receives it and how long it lasts, still needs legal review.

6 · Speakers and content

To be confirmed

Speakers keep ownership of the talks, slides and other material they create, and may reuse them elsewhere. Speaking here transfers no copyright or exclusive rights. Submissions are read on merit through the call for papers, with sponsorship, employer and reputation left out of that reading.

After a speaker accepts an invitation, we may publish their name, accepted talk title and abstract in the programme and event announcements. We ask separately before publishing a bio or photo; a photo is optional. We publish a final slide deck only if the speaker supplies it for public sharing and agrees to that use. A deck is not required with a CFP submission, and submitting one does not permit us to publish it.

Speakers should only offer third-party material for public sharing when they have the rights needed to do so. If a rights concern arises, we will work with the speaker to resolve it, which may include removing affected material. We have no planned automatic removal date for recordings or decks; a later removal request will be considered individually, without a promise that every request can be granted.

The formal speaker permission is still to be confirmed, including the identified recipient, licence scope and duration, and any future change of organiser. We will not assume an automatic transfer to an entity that does not yet exist. The full wording needs legal review and publication here and in the speaker invitation before the call for papers opens on 25 October 2026.

On content itself: a talk may describe attacks, tooling and real vulnerabilities. That is the field. It may not disclose somebody else's unpatched vulnerability with no disclosure process behind it, release material you do not have the right to release, or demonstrate against systems you are not authorised to touch. The review board will raise it with you if a submission looks like it crosses one of those lines, rather than rejecting it silently.

7 · Sponsorship

No sponsor is confirmed for 0x03 yet. Sponsorship is agreed in writing, one sponsor at a time, and that written agreement, not the sponsors page, and not this page, governs the relationship. The tier names and inclusions published there are the current prospectus and can change until a particular one is signed.

The two boundaries stated on that page are terms rather than marketing: sponsorship does not buy a speaking slot, and it does not buy the attendee list. Attendee data is not sold, shared or handed to a sponsor in any tier, at any price.

8 · Liability and force majeure

To be confirmed

The ticket seller is named in section 1. The liability and force-majeure wording still needs qualified legal review for that organiser and the confirmed venue arrangements. This draft does not add a limitation of liability.

What can be said plainly now: come to a conference in a hill town in April with the care you would take anywhere. Look after your own laptop and your own bag. This is a room full of people who find things interesting. The venue has its own rules and its own safety requirements, and while you are on their premises those apply to you. If you have a medical condition a volunteer might need to know about, tell us at the desk.

Force majeure is the other half of it. An event can be stopped by things nobody chose: weather, a public-health order, a venue withdrawing, a transport shutdown. Our organiser-confirmed cancellation and postponement response is set out in section 3's refund policy. Its final wording still needs legal review before sales open; this section does not remove that refund commitment.

9 · Changes to the programme

The programme will change. Speakers withdraw, talks get swapped, a village lands or does not, and a schedule published in December is not the schedule you will walk around in April. The current version is always the one on this site, and material changes are announced here and to ticket holders.

Coming because one particular talk is on the schedule is a reasonable thing to do, so it is worth saying that no individual session is guaranteed. The dates, 3–4 April 2027, are the part we would only move for something serious, and any move would be announced rather than quietly edited into a page. The venue is still to be announced, and it will go up the same way, in the open.

10 · Governing law

To be confirmed

The event is held in Dehradun, Uttarakhand. Aman Kumar is the confirmed individual ticket seller. The governing-law and dispute wording remains open for qualified legal review; naming the seller does not select a court or finalise this section.

Separately from all of that: if you have a problem with something we did, write to [email protected] first. That is the founding team and the team leads, which is as close to an escalation as a volunteer conference has. There is no adversarial machinery here and nobody wants any. Almost everything that goes wrong at one is fixed by an email and an apology.

11 · About this document

Version 0.16, last updated . It sits below 1.0 because six sections are still open. When the last chip goes, the version becomes 1.0 and this page stops being partly a description of what is not yet final. Version 0.12 made the current speaker recording plan and permission choices visible while leaving the formal licence open. Version 0.13 adds the Student ID rule and Corporate seating and after-party disclosures. Version 0.14 publishes the organiser-confirmed refund, transfer and CTF sales rules and after-party access, while retaining legal-review and venue/age conditions. Version 0.15 confirms the 21+ alcohol-service rule; venue admission rules remain pending. Version 0.16 names Aman Kumar as the individual ticket-selling organiser, while retaining invoice-verification and legal-review requirements.

It was written by the organising team, not by a lawyer, and has not yet received a complete legal review. An advocate should review it before 0x03 ticket sales open, and the reviewed text should replace this page rather than sit beside it. Nothing on this page is legal advice, and nobody organising this conference is in a position to give any.

If something here is unclear, or you think a section is wrong, tell us, a term nobody understands is not a term worth having. The contact form reaches the team, or write to [email protected]. The privacy page covers what happens to personal data and is versioned separately from this one.

Six open areas

Questions about an open term? Ask us.

The remaining open terms are marked above. Speaker permissions need final wording before the CFP opens; ticket and liability terms need it before ticket sales. If a term matters to you, ask us about it.