Organiser terms

Section 0. About these terms

These are the terms on which Pilarres EOOD ("we", "us") provides Bicyr Cangor, the platform on which you publish events and sell tickets for them, to you, the organiser ("you").

There are two versions of these terms. This one is for private individuals organising an event of their own outside any trade, business or profession, such as their wedding or a family celebration. If you organise the event as part of a trade, business or profession, or through a company, association or other organisation, the business version applies to you instead.

You can read these terms before you accept them, for as long as you use the platform, and after you stop. Each version is published at its own address, which never changes, and every earlier version stays published at its own.

These terms were drafted without a lawyer. We have no legal counsel: we researched and wrote them ourselves from the legal texts they cite, and no qualified adviser has reviewed them. The French, Dutch and German versions have not been reviewed by a native legal speaker. We tell you this because you are entitled to know it. It does not reduce anything we promise you here.

These terms do not govern the contract between you and the people who buy your tickets. That contract is yours. What we tell your buyers about it is in our Terms of Sale and Refund Policy, which every buyer is shown. Where these terms ask you to do something for your buyers, it is because we have told your buyers that you will.

Section 1. Payouts, the payout hold and negative balances

1.1 Where your money is. Payments for your events are processed by Stripe on your own Stripe account, under the Stripe Connected Account Agreement and the Stripe Services Agreement it incorporates, which you accept when Stripe onboards you. Each payment goes into your Stripe account, less our platform fee. Our platform fee includes Stripe’s fee for processing the payment, which we pay out of it, so Stripe takes no separate processing fee from the payment. Our platform fee is the only part that reaches us, and when you refund a ticket that fee comes back with it.

1.2 When you are paid, and the payout hold. We set your Stripe account so that Stripe pays out the money from your sales only once 7 days have passed after the end of the event it was paid for, and not later, except as 1.3 and 1.5 say; for an event that lasts several days, the 7 days run from its last day. Once they have passed, Stripe pays out the money available in your account to your bank account. We set it this way because refunds, chargebacks and disputes for an event mostly arise before it takes place and shortly after, and under 1.4 you carry them. You can see what is still to be paid out, from when, and what has been paid out, where you manage your payouts on the platform. Your first payout can take longer, because Stripe holds new accounts to a longer settlement period.

1.3 Stripe can still restrict your account. Stripe may stop your account taking new payments, or delay a payout, while information it requires about you is outstanding or while it reviews your account, as the Stripe Connected Account Agreement allows. That is Stripe’s decision, not ours. When Stripe needs more information from you, the platform shows you what it needs, where you manage your payouts.

1.4 Refunds, chargebacks and negative balances are yours. If an event does not go ahead as sold, refunding the people who bought tickets is yours to do. You are liable for every refund, chargeback and disputed amount on your sales, and for a negative balance on your Stripe account to the extent those refunds, chargebacks or disputed amounts cause it. A refund or chargeback is taken from your Stripe balance. A disputed amount is taken from it when the dispute opens, and comes back if the dispute is decided in your favour. If a dispute is decided against you, we return our platform fee on that ticket. Stripe also charges a fee for each dispute: we pay that fee, and it is not passed on to you. You never owe more under 1.4 than buyers paid for the tickets concerned, less the fees we return. You are not liable for any part of a negative balance that our own error caused, such as a payment or refund that neither you instructed nor 3.2 required, or evidence you gave us under section 5 that we did not submit to Stripe in time.

1.5 Set-off against your later sales. While your Stripe balance is negative, the money from your later sales on the platform goes first to reduce it, and nothing is paid out to you until it is back above zero. You agree that what you owe under 1.4 is set off against those later sales in this way. We never set off more than you owe. Each time your balance becomes negative, we tell you by e-mail, with the amount and the refunds, chargebacks or disputes that caused it.

1.6 Paying what is left. If your later sales have not brought your balance back to zero, we may ask you in writing to pay what is still owed, and you pay it within 14 days of that demand. The payment goes to our own account and settles our own claim against you. The demand names the amount, the refunds, chargebacks or disputes that make it up, and how to pay. If you think the amount is wrong, tell us within those 14 days, under section 14, and we look at it again; you need not pay the part you contest until we have answered, and you then pay what our answer confirms within 14 days of it.

You also authorise Stripe to debit the bank account your payouts go to for any negative balance on your Stripe account that your later sales have not covered. Stripe does this automatically, under the Stripe Connected Account Agreement you accept when you connect the account; you give us no separate mandate. Stripe's debit does not wait for a demand under 1.6 or for a contest of it: where you contest an amount Stripe has already debited and we uphold your contest, we pay it back to you within 14 days of our answer. We tell you the amount by e-mail when your balance goes negative (1.5). Nothing here limits the right the law gives you to ask your bank to refund a direct debit. Where Stripe does not debit, or the debit fails, you pay what 1.6 demands within the 14 days it gives. [COUNSEL REVIEW: negative-balance-debit -- SESSION_DRAFTED 29 Oct 2026 (bicyr/cangor#1236), unreviewed: the debit is Stripe’s automatic debit of the payout bank account (Balance Settings debit_negative_balances, bicyr/bicyr#2593), with no mandate collected by Cangor; counsel settles this wording before the owner publishes]

1.7 Why. For a Stripe account created under these terms, we, not Stripe, answer to Stripe for a negative balance, under our agreement with Stripe. These terms pass back to you what arises from your own sales, and they do not make you answer for anything else. An account created under version 1.0 stays as it was (section 20).

Section 2. Personal data

2.1 Who decides what, activity by activity. For your event’s sale, you decide and we act for you. When a guest buys a ticket, registers, is admitted at the door, asks for a refund or writes to you through the platform, the personal data involved is processed to perform your contract with your guest. You are the controller of that processing and we are your processor. We process it only to run the platform for you, on your documented instructions, which are these terms and what you set in the product.

For our own purposes, we decide, and we are an independent controller. These are: your and your team’s platform accounts and sign-in; the security of the platform, fraud prevention and the audit trail of privileged actions; invoicing and accounting for our platform fee; our own legal obligations, including notices under the Digital Services Act and answering authorities; and service messages about your account. We never use your guests’ data for a purpose of our own that is not on this list. In particular, we do not sell it, we do not market to your guests, and we build no profile across organisers.

Stripe processes payment data under its own agreement with you, as your payment provider and as an independent controller for its own legal obligations. We are not a party to that.

2.2 Our commitments as your processor (GDPR Art. 28(3)). For the processing in 2.1 that we carry out for you, we:

• (a) process the data only on your documented instructions (these terms and your settings), unless EU or Member State law requires otherwise, in which case we tell you first where the law allows;
• (b) ensure that everyone we authorise to process it is bound to confidentiality;
• (c) apply the security measures described in our record of processing (tenant isolation, encryption in transit, access limited to what support requires, an append-only audit log);
• (d) use sub-processors only with your general authorisation, which you give by accepting these terms for those listed at /legal/sub-processors; we tell you at least 15 days before adding or replacing one, you may object, and if we cannot accommodate the objection you may terminate. We impose the same obligations on each sub-processor and remain liable to you for it;
• (e) help you answer your guests’ requests to exercise their rights, including by giving you a self-serve export and erasure of a guest’s data;
• (f) help you with security, breach notification (we tell you without undue delay after becoming aware of a breach affecting your data), and any impact assessment or prior consultation, as far as the information we hold allows;
• (g) at the end of our service, at your choice, return your data (the exit export) and delete it, except what EU or Member State law requires us to keep;
• (h) make available the information needed to show we comply, and allow for audits, which we meet first with our documentation and records; and we tell you immediately if we think an instruction of yours breaks data-protection law.

Subject-matter and duration: the platform services for your events, for as long as you use them and then until deletion under (g). Nature and purpose: hosting, sale, ticketing, communication, admission and refund processing for your events. Data: guests’ and buyers’ names, contact details, language, orders, tickets, admission records and messages; accessibility preferences only if you enable them, with the guest’s explicit consent. Data subjects: your guests, buyers and ticket holders.

2.3 If you are organising in a purely private capacity. If you are a private individual organising a purely personal or household event — for example your own wedding, for guests you invite — data-protection law may not apply to you (GDPR Art. 2(2)(c)). It still applies to us, as the provider of the means (GDPR recital 18), and we remain responsible as controller for the processing we carry out on the platform, under the same limits as in 2.1. As soon as an event is open to the public or organised as part of a business, association or other professional activity, the exemption does not apply and 2.1 and 2.2 govern.

2.4 What we do not do. We do not decide, for your event, whether to sell, to whom, at what price, or whether to refund; those are yours. Where we act beyond your instructions for a purpose of our own, we are a controller for that act and answer for it ourselves (GDPR Art. 28(10)).

Section 3. Your events and your sales

3.1 You are the seller. Every ticket sold for your event is sold by you, and the contract for it is between you and the buyer. We are not a party to it. You decide what you sell, to whom, at what price and on what conditions, and whether the event goes ahead. Your name, as you give it to us, is shown as the seller on each event page and at checkout.

You sell as a private individual. Before a buyer pays, the checkout tells them that you are not selling as a business, and that EU consumer rights therefore do not apply to their contract with you. That changes nothing you promise them under 3.2.

Your address. Before you first receive payments through the platform you give us your home address, and you keep it up to date. We need it to know who we have a contract with and to be able to write to you. We do not show it to your buyers: the law requires a seller’s address to be given to buyers only when the seller is a trader.

3.2 Your refund policy, and the floor under it. Before an event goes on sale you declare its refund policy, and we show it to every buyer before they pay and in their confirmation. We do not supply a policy of our own in place of yours.

Whatever your policy says, it gives no buyer less than our Refund Policy promises every buyer, and you honour at least this:

• If the event is cancelled, for whatever reason, you refund each buyer the full price they paid, in money, to the means of payment they used. You may offer a credit note or a ticket for another event beside the refund, never instead of it; a buyer who has not clearly chosen the credit note is refunded in money.
• If the event is postponed, the ticket stays valid for the new date, and a buyer who asks for a refund instead is refunded in full.
• If the event moves to a place a buyer cannot reasonably be expected to travel to, a buyer who asks is refunded in full.
• If an event of several days or parts is cut short after it has begun, you refund the part not delivered.
• A refund costs the buyer nothing.

Your policy may be more generous than this, and once you have published it you are bound by it. Refunding is yours to do, from your own Stripe balance (1.4); we cannot refund your buyers for you.

3.3 Receipts and tax. As the seller, you issue any invoice or receipt for a sale, and you are responsible for the VAT and other taxes on your sales.

3.4 What you may not sell. You may sell tickets only for events you organise or are authorised to sell. You may not use the platform to resell tickets for more than their original price, to sell before the official sale opens, or to sell for an event that is unlawful or that you do not intend to hold.

Section 4. Our fee

4.1 For every paid ticket sold through the platform, we charge a platform fee of 3.5% of the total the buyer pays for the order, plus €0.40 per ticket, and at least €0.40 per order. The fee includes Stripe’s fee for processing the payment, which we pay: Stripe takes no separate processing fee from your sales. Free events and free tickets carry no fee.

4.2 The fee is deducted from each payment before it reaches your Stripe balance (1.1). We never change the fee on a ticket already sold, and a change to the fee is a change to these terms, made only under section 15.

4.3 Whenever you refund a ticket, in full or in part, and for any reason — a cancellation, a postponement, a move, or a refund you choose to give under your own policy — our fee on that ticket comes back to you with it, in full or in the same proportion. We keep no fee on a ticket whose money went back to the buyer.

Section 5. Chargebacks and disputes

We say this here, plainly, rather than in small print: if a buyer asks their bank or card issuer to reverse a payment for one of your tickets, that dispute is yours. It is decided between the buyer’s bank and Stripe, on the evidence submitted for the payment. You do not have a Stripe dashboard, so you cannot answer a dispute at Stripe yourself: write your account of the sale on the order itself, from your workspace on the platform, and press submit — it reaches Stripe at once, through our system, exactly as you wrote it. Where you need to send a document instead, such as a screenshot, a signed policy or correspondence you cannot paste as text, or where the order cannot take your submission, send it to us through the link in our notice of the dispute, by the date that notice gives, which is three days before Stripe’s own deadline, and we submit it to Stripe for you by hand, as you gave it. Either way, we do not write your case, we cannot influence the decision, and we promise no outcome. If nothing reaches Stripe by its own deadline, the dispute is decided without your evidence. Whatever the decision, its financial result is yours (1.4).

Stripe does not tell you directly when a dispute is opened on one of your payments, so we tell you, with a link to the order where you answer it.

While a dispute is open, the payment cannot also be refunded through the platform.

Section 6. The prices you show, and our embed

Every price the platform shows a buyer is the total the buyer pays, including VAT and our fee. Wherever you advertise a ticket, you show that same total, never a lower price with charges added later.

If you place our ticket button or RSVP card on a website of your own, when we offer one, it shows the final price including everything, and you must not print a different or pre-fee price around it. A misleading price on your page is a breach on your page: the button cannot prevent it, and only you can.

That button stores nothing on your visitor’s device — no cookie and no other storage — until the visitor acts on it, so that using it does not on its own require your visitors’ consent under the ePrivacy rules. If that ever changes, it is a change to these terms under section 15.

Section 7. Data: who can see what

What you can see. Everything that you, your team, your guests and your buyers put into the platform for your events, and everything the platform records about them — your events, guest lists, participations, orders, tickets, admission records and messages — within your own workspace. Nothing that belongs to any other organiser.

What we can see. The same data, because we run the platform. We use it only as section 2 allows, and our staff open it only as far as support or security requires.

What other organisers can see. Nothing of yours. Every record belongs to one workspace, and access across workspaces is refused by the platform itself, not merely hidden on screen. The same holds for any service of our own that is offered on the platform (section 12).

What we give to others. We do not sell your guests’ or buyers’ data, we do not give it to anyone for their own marketing, and we build no profile of any person across organisers. We give it only to the sub-processors on our published list, to Stripe for your payments, and to an authority where the law requires it. We give no one, including you, data drawn from other organisers, whether individually or in aggregate.

After our contract ends, section 10 says what you can still reach.

Section 8. When we may restrict, suspend or end our service

8.1 The grounds. We may stop an event from being sold or unpublish it, or end our service to you entirely, only on one of these grounds, stated here in advance:

• you fail or refuse the verification that Stripe or we require for the kind of event you sell: Stripe verifies you before you can take payments, and we may ask for proof of your identity and, if you have one, your enterprise number before a paid event goes on sale;
• we receive a notice that an event of yours is fraudulent or that its sale is unlawful, and having checked it we find it substantiated;
• you break these terms in a way that harms buyers, other organisers or the platform, including by selling what 3.4 forbids, by not paying a refund you owe under 3.2, or by not paying an amount you owe under 1.6 that you have not contested, or contested and had answered by us, within 14 days of our demand or, where you contested it, of our answer;
• the law, a court or an authority requires it.

8.2 Your payouts. Stripe pays out your money on the timing 1.2 sets, and we take what you owe only as 1.5 and 1.6 say. Restricting an event or our service does not, by itself, stop the money you are owed from being paid out to you. Stripe may restrict your account on its own terms (1.3).

8.3 Our reasons, in writing. Whenever we stop an event from being sold or unpublish it, we give you, before or at the moment it takes effect, a written statement of the specific facts and of the ground in 8.1 we relied on, including what a notice said about you, unless the law forbids us to tell you.

8.4 Ending our service entirely. We give you at least 30 days’ notice, with our reasons in writing. We may end it sooner only where you have seriously failed to perform these terms, or where force majeure prevents us from continuing, and we then give you our reasons in writing without undue delay.

8.5 You can challenge it. Reply to our statement, or use the complaint route in section 14, and we look at the facts again. If we lift the measure, we restore your access, including to your data, without undue delay.

8.6 Tickets already sold remain your sales. Restricting, suspending or ending our service does not cancel them, and what you owe those buyers under 3.2 continues.

Section 9. Ending these terms yourself

9.1 You can end these terms at any time, without giving a reason and without paying anything, by telling us at the address in section 19. It takes effect when we receive it. It ends your future sales on the platform; it does not cancel tickets already sold, and what you owe those buyers under 3.2 continues.

9.2 Your right to withdraw. Because you accepted these terms online as a consumer, you may also withdraw from them within 14 days of the day you accepted them, without giving any reason. To withdraw, tell us clearly, by e-mail to the address in section 19 or with the withdrawal function on the platform. You may use the model form below, but you do not have to. It is enough to send your message before the 14 days end. Accepting version 1.1 of these terms starts a new period of 14 days, from the day you accept it, in which you may withdraw in the same way.

If you withdraw, you pay us nothing for the platform itself. If, during those 14 days, you asked us to start providing the service — which you do by putting a paid event on sale — and then withdraw, the fees on tickets already sold are the proportion of the service already provided, and are the only amount we keep. Tickets already sold remain your sales, as in 9.1.

• Model withdrawal form. To Pilarres EOOD, Legis Center, office 3-8B, 152 6-ti Septemvri Street, 4000 Plovdiv, Bulgaria, info@bicyr.com:
• I hereby give notice that I withdraw from my contract for the provision of the following service: the Bicyr Cangor organiser terms.
• Accepted on: ____
• Name: ____
• Address: ____
• Signature (only if this form is sent on paper): ____
• Date: ____

9.3 Ending these terms, or withdrawing under 9.2, does not end what you owe under 1.4 for sales already made. Held money is still paid out under 1.2, less what 1.5 sets off.

Section 10. Your data when you leave: the exit guarantee

At any time, while these terms run and after they end, you can export what you put into the platform and what your events generated, yourself, without asking us. Today that is, for each event, your guest list and its participation records, in CSV, XLSX, JSON or PDF.

Your orders, tickets and admission records cannot yet be exported by you directly. Until they can, we send them to you on request, free of charge, in an open format.

When our contract ends, you choose whether we return your data to you and then delete it. We keep only what the law requires us to keep, such as accounting records, and we delete nothing you have not yet had the chance to export. After the end we have no access to your data for any purpose of our own, beyond the records the law makes us keep.

Section 11. How your events are shown, and where else they appear

Ranking. The platform has no directory, search or listing that ranks your events against other organisers’ events. Each event is reached through its own address, which you share. Nobody can pay us for more prominence. If we introduce a ranking, we will describe here, before it takes effect, its main parameters and why they matter more than others, including whether any payment affects it.

Other channels. We do not market your events or tickets through any other channel, affiliate programme or reseller.

Nothing else at checkout. We offer your buyers nothing else at checkout — no insurance and no extras, from us or anyone else.

You are free to sell elsewhere. You may sell the same event through other channels, on other conditions and at other prices. We do not restrict that.

Section 12. Our own services on the platform

Pilarres plans to offer services of its own through the platform — audiovisual, catering and print — from 2027, as a vendor on the same footing as any other. It does not offer them today.

When it does, they will get no advantage over anyone else: no better placement or ranking, no data another vendor could not have, and no different fee or access to features. Our service lines use the platform as ordinary workspaces and cannot see yours. What you pay us does not depend on whether you use them. If we ever treat our own services differently, that is a change to these terms under section 15, and we will describe the treatment and our reasons for it here first.

Section 13. Your content and your intellectual property

What you put into the platform — event descriptions, images, names and logos — stays yours. You give us only the permission we need to store it, to show it to the people you share it with, and to include it in tickets and confirmations, for as long as it is on the platform and in the records the law requires us to keep. We claim no other right to it.

You confirm that you are entitled to give us that permission. If we are told that content of yours is unlawful, we deal with it under section 8.

Section 14. Complaints and mediation

If you have a complaint about us — how we applied these terms, a technical problem that affects you, or anything we did or failed to do — write to us at the address in section 19. It costs nothing. We read every complaint, treat like cases alike, answer in writing within a reasonable time, and tell you what we did about it.

If you live in Belgium and your complaint is not resolved, you may take it to the Consumentenombudsdienst / Service de Médiation pour le Consommateur, North Gate II, Boulevard du Roi Albert II 8 bte 1, 1000 Brussels. If you live elsewhere in the EU, you may use the out-of-court body of your own country.

Nothing here stops you from going to court at any time.

Section 15. Changes to these terms

15.1 We change these terms only by publishing a new version at a new address. The version you accepted stays published at its own address.

15.2 We tell you about a proposed change by e-mail at least 15 days before it takes effect, and longer where you need more time to adapt your events or your systems to it. The e-mail itself names the versions before and after, sets out each change in plain words, gives the date it takes effect and your right to end these terms before then, and gives the address of the new version.

15.3 We change these terms only for one of these reasons: a change in the law or a decision of a court or authority; to protect the platform, buyers or you against fraud or a security risk; to describe a new feature of the platform or a change to one; or a change to our fee. A change for any other reason applies to you only if you accept it; if you do not, the version you accepted continues until you or we end it under section 9 or 8.4.

15.4 If a change is to your disadvantage, you may end these terms free of charge under section 9 before it applies to you, and it does not apply to you until the notice period has run.

15.5 No change reaches back. A change never affects tickets already sold or fees already charged, unless the law requires it or it only benefits you.

15.6 Once a change has taken effect, you accept the new version before you put a new paid event on sale, or a new ticket type on an event already on sale. Until you do, what was already on sale when we offered you the change keeps selling as before, under the version you accepted. Tickets already sold are not affected.

Section 16. Responsibility

We are responsible for providing the platform with reasonable skill and care, and for what we promise in these terms. We are not responsible for your event, for what you promise your buyers, or for Stripe’s decisions about your account (1.3).

Nothing in these terms limits our liability for fraud, for intentional or gross fault, for a failure to perform one of our main obligations under these terms except in a case of force majeure, or for death or personal injury, and nothing in them takes away a right the law gives you as a consumer.

Neither of us is responsible for failing to perform an obligation for as long as force majeure prevents it.

Where the platform runs. The public part of the platform -- event pages, ticket sales, RSVP and sign-in -- runs on a single infrastructure provider. If that provider has an outage across its whole service, new sales, RSVPs, sign-in and public pages stop until it recovers. The door does not stop: tickets already issued keep scanning, and what has already been sold stays recorded and is paid out as these terms say. We publish the platform's status on a page hosted away from that provider. We promise no availability figure beyond the service levels we publish for each journey. [COUNSEL REVIEW: single-vendor-public-path -- SESSION_DRAFTED 29 Oct 2026 (bicyr/cangor#2018), unreviewed: the tenant-facing statement of 2.2.6 "The One Vendor on the Public Path"; counsel settles this wording before the owner publishes]

Section 17. Law and courts

Belgian law governs these terms. If you live in another country, you keep the protection of the rules of that country that cannot be set aside by agreement. You may bring proceedings against us in the courts of the place where you live or in the courts of Bulgaria, where we are established. We may bring proceedings against you only in the courts of the country where you live.

Section 18. Languages

These terms are published in English, French, Dutch and German, and each version is equally valid. Where they differ, the meaning more favourable to you applies. The French, Dutch and German versions have not yet been reviewed by a native legal speaker.

Section 19. Who we are and how to reach us

Pilarres EOOD, a single-member limited liability company registered in Bulgaria under UIC 208702712, VAT number BG208702712, registered office Legis Center, office 3-8B, 152 6-ti Septemvri Street, 4000 Plovdiv, Bulgaria. E-mail info@bicyr.com. Telephone +32 485 02 94 23.

Section 20. Moving from version 1.0 to this version

20.1 Your express acceptance. This version applies to you only once you accept it expressly, on the platform. Using the platform, or letting the notice period run, is not acceptance. You may refuse it, and you may end these terms free of charge under section 9, before or after it takes effect. If you do not accept it, your events that were already on sale when we offered you this version keep selling on your existing Stripe account under 1.0; to put a new paid event on sale, or a new ticket type on an existing event, you accept this version first (15.6).

20.2 If you do not accept it, 1.0 continues until you or we end it under section 9 or 8.4. Tickets sold under 1.0 remain governed by it.

20.3 Nothing reaches back. Sections 1.2, 1.5 and 1.6 (the payout hold, set-off and our demand) apply only to tickets sold on or after the day you accept this version, on a Stripe account created under it. 1.7 applies only to such an account.

20.4 A new Stripe account. If you joined the platform under version 1.0, your Stripe account was created on the footing that Stripe, not us, carries its negative balance, and Stripe does not let that be changed. So when you accept this version, you connect a new Stripe account through the platform, and your sales from then on are paid into it. Your old account is not closed by the move, and its balance is paid out to you as before.