Frequently Asked Questions

You sign in without a password — either with a passkey (recommended, e.g. your device's fingerprint or face recognition) or with a one-time link sent to your e-mail. There is no traditional login password. Note: opening the link from the e-mail first shows a confirmation page — you are only signed in once you click its button. This keeps mail scanners from accidentally using up the one-time link.

A passkey is a device-based sign-in key (e.g. via fingerprint, face recognition, or your device's PIN) that makes passwords unnecessary and is much harder to misuse. You can store several passkeys — for example on your phone and laptop as mutual backups — and rename or revoke them anytime in the control center.

Use the e-mail one-time-link sign-in on the login page instead. The link is valid for 15 minutes and can only be used once. After signing in, you can immediately set up a new passkey in the control center.

After filling out the registration form, you'll receive an e-mail with a confirmation link (valid for 24 hours). Your account only becomes active once you click that link, and you'll be signed in automatically. You can then optionally set up a passkey right away. Opening the link first shows a confirmation page; your account is only activated once you click its button.

Level 0 applies right after registration, before you've confirmed your e-mail — signing in isn't possible yet. Level 1 is granted automatically once confirmed, letting you take part in events, ride shares, and accommodations. Level 2 is granted once your address data has been reviewed by an Administrator or Moderator and your legal age confirmed, letting you create your own events, taxis, and BnBs. Level 3 (trustworthy) can only be granted manually by an Administrator or Moderator and shows a seal on your public profile.

Request an address review in the control center under "Personal Data". You'll receive an 8-digit code, which you tell an Administrator or Moderator in person. During the review, your ID card also confirms you're of legal age. You're then automatically upgraded to Level 2.

Level 3 can't be reached on your own — it's granted manually, exclusively by an Administrator or Moderator. It shows an additional seal on your public profile.

A ban is imposed by an Administrator or Moderator and blocks the use of every feature on the site. Signing in and the control center remain usable only for GDPR self-service — data export, correction, and account deletion. A permanent ban additionally deletes the account outright.

The control center is your personal area with several tabs — Account, Personal Data, Messages, Bookmarks, Contacts, Participation, My Entries, Tickets, Inquiries, and GDPR. From there you manage your profile, address data, and passkeys, plus every event, taxi, and BnB you're part of or created.

All lists show 50 entries per page. Use the page numbers, “Previous” and “Next” below the list to switch pages; the line underneath shows the range being displayed, e.g. “51–100 of 412”. Wherever there are search fields or filters (calendar, management lists, participant lists), they always work across all entries, not just the current page. Histories, logs and the event archive (with its own search and country filter) are loaded page by page from the server.

The bookmark list lets you save events, taxis, and BnBs you're interested in, so you can quickly find them again in the control center later — whether or not you're already participating.

On another member's public profile, you can use the "Add to contacts" button to add them to your private contact list, and later remove them again via "Remove from contacts". Your contact list is in the control center's "Contacts" tab — every entry links to the public profile. The list is visible only to you; the added member is never notified and never learns about it. It is capped at 500 contacts.

The data password has nothing to do with signing in. It only encrypts the address data you store in the control center. If you forget it, any existing address data cannot be recovered — resetting it deletes that data permanently.

In the control center under "Personal Data" you can create a one-time, time-limited share for an Administrator, a Moderator, or an event's organizer. You'll receive a randomly generated 8-digit code, which you tell the recipient in person only — never over the same channel as the address data itself. The code is valid for 15 minutes and can only be redeemed once. You can find who currently holds these ranks on the Team page in the navigation.

Request a review in the control center under "Personal Data". You'll also receive an 8-digit code here, which you tell any Administrator or Moderator in person. That person checks both your address and your legal age against your ID card at the same time — you're then automatically upgraded to Level 2. You can find who currently holds these ranks on the Team page in the navigation.

Any member of the Administration or Moderation — both ranks may review address data. The full, current list, each linked to their public profile, is on the Team page in the navigation.

A ticket goes to the staff (Administrators and Moderators) — for bug reports, criticism, suggestions, or reporting a rule-breaking event, taxi, BnB, or user. An inquiry is instead a private message directly to the creator of an event, taxi, or BnB, e.g. for questions — staff has no access to it.

In the control center under "GDPR" you can download all data stored about your account as a JSON file with one click (Art. 15 GDPR) — including participations (with your answers to the participation options), bookmarks, feedback, your own listings, the role and address-access log and the Telegram log. Your address is only included if you enter your data password, because only you can decrypt it.

In the control center under "GDPR" you can permanently delete your account — you'll need to type your username to confirm. If you own events with moderators, you must pick a successor first (or let the system choose one at random); your own taxis and BnBs are simply removed. Deletion happens immediately and cannot be undone.

In the control center under "Account", click "Link with Telegram". A page with two buttons opens: "Open in the Telegram app" and, if the app is not installed, "Open in the browser instead". Tap one of them — our Telegram bot opens and completes the link (the link is valid for 15 minutes and works once). Afterwards you can choose whether your Telegram account is shown on your public profile. Which notifications you receive is set in the "Notifications" section — once Telegram is linked, it replaces e-mail there. If your account is banned, the bot stops working for your linked Telegram account as well.

Nothing is preset: in the control center under "Account" → "Notifications" you switch on what you want to be told about — My participations (accepted/rejected, feedback decisions), entries you take part in or bookmarked (important changes such as date, place, address, plus cancellation, reactivation, removal), My own entries (status changes, changes by others, moderator roles, transfers), New events, New articles, replies to your tickets and — for team members — new review tasks. What you do not switch on you do not get, and whoever caused a change is never notified about it. Messages come in your language and contain only what is necessary. If your Telegram account is linked (and reachable) they come **only** via Telegram, otherwise by e-mail — never twice. Sign-in, confirmation and security mails (login link, e-mail change, data password) always reach you by e-mail. Replies from the team to your tickets additionally show as an unread marker in the control center.

In the control center under "Account" you can upload a profile picture (JPG, PNG, GIF or WebP up to 2 MB, cropped to a square; animated GIFs become a still image), change your display name and enter a new e-mail address. The new address only takes effect after you open the confirmation link sent to it (valid 24 hours); the previous address receives a security notice.

In the control center under "Account" you find your sign-in history for the last 30 days (time, coarse device class, outcome) and your registered passkeys, which you can also remove there. "Stay signed in" keeps you signed in for up to 30 days; without it the session ends after one hour of inactivity. The e-mail sign-in link is valid for 15 minutes and can be used once.

Your display name, profile picture, any team rank, your badges and approved feedback about you. Your date of birth is only shown if you explicitly consented in the control center (withdrawable any time), and your Telegram username only if you made it visible yourself. Your e-mail address and postal address are never public.

In the control center under "Account", "My QR code" shows a QR code of your public profile that you can view or save as PNG. Organizers, appointed moderators and Administrators can choose "Scan QR code" on the manage page of their event, taxi or BnB — the camera reads the code and all lists on the page then show only that person; confirmation is always manual, nothing changes automatically and no camera image leaves the device.

After an event you can write feedback that the organizer approves; for taxis and BnBs the driver or host decides on feedback about them, and approved entries appear on their profile. Approved feedback is public with your display name; rejected feedback stays hidden. Administrators can delete abusive entries.

Your account including address data, passkeys, sign-in history, own listings, participations, bookmarks, contacts and own tickets is deleted; your data disappears from logs and backups within 30 days. Published content you authored deliberately remains — articles, approved experience reports and archive entries — together with the display name shown there; on request we replace the name with "Deleted account" and keep only the text (an informal message is enough). Frozen display names in change logs and your messages in other people's threads (shown as "Deleted account") also remain; in tickets that reported you only a placeholder replaces your name.

From Level 1 you can request participation on the event's detail page. Depending on the organizer's settings, your request is either reviewed manually or approved automatically. Some events additionally require a reviewed address before you can join. You can withdraw your participation at any time as long as it hasn't been rejected. If the organizer allows it, you can also take part without an account (see “How do I take part without an account?”). A clear notice at the very top of the page tells you whether registration has not started yet or has already ended, and whether you need an account for it.

If the organizer allows it, a visitor who is not signed in sees a “Teilnahme” box on the event page with the link “Ohne Konto teilnehmen” (take part without an account). Enter your display name and e-mail address, answer the event’s participation questions (bringing guests is not possible without an account), confirm your age and the privacy policy and submit the form. We send you a confirmation link (valid for 24 hours); only when you confirm it is your participation requested — depending on the event the organizer then reviews it or it is approved at once, and there may be a waitlist. Disposable addresses do not work. If the address already belongs to an account, please sign in instead. Without an account you cannot see on the event page whether you are already in; that is what your personal link is for.

After you confirm, you get an e-mail with your personal link. On that page you see the status (requested, approved, waitlist, rejected), your number, your stored details and your answers. You can change your answers as long as the participation has not been rejected and end the participation with “Teilnahme zurückziehen” (withdraw) — that deletes your data at once. Do not pass the link on: whoever knows it can manage your participation. E-mails about your participation (approval, rejection, moving up, cancellation, important changes) are sent automatically, without any settings and never via Telegram.

Open the event page and choose “Link zur eigenen Teilnahme erneut senden” (send the link again). Enter the e-mail address you signed up with: the answer is always the same (“if you take part, an e-mail is on its way”) so nobody can find out who takes part. If you do take part, you get a new link and the old one stops working. The e-mails about your participation also point to that page. Only a few requests per hour are possible.

Only your display name, e-mail address, language and answers are stored — no password and no sign-in. Only the organizer, the moderators they appointed and the administration can see them on the management page (the e-mail address only that group; it is not in the CSV). You never appear in the public participant list, but the participant count includes you. An unconfirmed request disappears after 24 hours. If you withdraw or the organizer removes you, your data is deleted at once; otherwise at the latest when the event is archived (30 days after it ends) — only your name stays in the archive. If you register later with the same address, the participation is assigned to your new account.

Organizers can decide that registration happens exclusively on their own website. Our event page is then purely informational and shows a link to that external website — opening in a new tab — instead of a join button. Please register over there in that case. You can still bookmark the event and send an inquiry to the organizer as usual.

If an event has a participant limit and the organizer allows a waitlist, you can still send a request when the limit is full: your request stays pending until a place becomes free. Without a waitlist, no further requests are possible once the limit is reached. For the event, the organizer decides what happens when a place becomes free: either the oldest pending request moves up automatically (you are notified if you switched that notification on), or the organizer or their moderators approve every request by hand. Accepted guests count towards the limit; a request with guests only moves up when there are enough free places for you and your guests.

When creating an event, the organizer can define additional questions (free text, single or multiple choice) that you answer when joining. You can change your answers at any time as long as your participation has not been rejected. A multiple-choice option can also have places of its own (e.g. for a shared meal), see "What do limited places on an option mean?".

For a multiple-choice option the organizer can set a number of places of its own, independent of the event's limit — for example for a shared meal. Anyone who ticks at least one box makes a request for that option; every ticked guest makes another. Requests only arise once your participation is accepted. As with the event itself, the organizer (or their moderators) unlocks every request per option — only then is the place confirmed. They can also reject a request per option — every organizer decides that subjectively, and it stays even if you tick the option again. There is no e-mail for this: where you (and each of your guests) stand — requested, waitlist, unlocked or rejected — is shown in the "Your participation" box on the event page. The options hang on your participation in the event: if it is rejected or you withdraw it, your places on the options go too. If the option is full, your request goes on that option's waitlist; whether waiting requests move up automatically when a place frees up or are unlocked by hand as well is decided by the organizer for the event. On the participation form you see how many places are unlocked and where you stand. A confirmed place is not taken away if the number of places is lowered later.

Only if the organizer has allowed it for this event — you can then state on the participation form how many additional people you're bringing, and must confirm that you're authorized to submit information on their behalf. Guests aren't recorded by name, only as "Guest 1", "Guest 2", and so on, and they count toward the event's participant limit. Once your participation has been approved, you can only decrease your guest count, never increase it.

Some organizers show participant numbers — a fixed, sequential number in the order you registered, shown to you on the event page once your participation is approved. If you brought guests along, each guest gets their own number, also shown there. The number is permanent and never reassigned — if someone withdraws, a gap appears where their number was, which is normal.

Some organizers turn on a public participant list. When active, the event page shows your display name for every approved registration, linked to your public profile — nothing else. You can hide yourself from that list at any time without affecting your participation; the control center's "Participation" tab has the toggle. People who take part without an account never appear in this list.

The organizer can optionally set a registration start. It is shown on the event page; before it nobody can register, after it registering is possible until a registration deadline, if one is set. The organizer can change or remove it at any time. A clear notice at the very top of the page shows the registration start as long as it has not been reached.

The organizer can optionally set a registration deadline. It is shown on the event page; after it, nobody can newly register. Requests already made or approved stay in place, you can still change your answers and withdraw — but after the deadline you cannot register again. The organizer can still approve or reject open requests afterwards. A clear notice at the very top of the page shows that the registration deadline has passed.

From Level 2 you can create your own event via the corresponding page. The form is split into four tabs: Basic settings (names, place, dates, preview image, description), Participation (limit, waitlist, guests and more), Detail boxes and Participation options. Required fields are marked with *; if something is wrong, the affected tab opens automatically. New events are saved as a draft first, visible only to you, appointed moderators and the administration. When everything is finished, you submit the event for review on its management page; only then does an Administrator, Moderator or Event-Manager review it, and it becomes publicly visible once approved.

Every new entry starts as a draft that only you, appointed moderators and the administration can see; the team is not notified while you are still working. On the management page you click "Submit for review" - the entry is then "in review" and the team is told. Until a decision is made you can turn the submission back into a draft with "Withdraw". Once the team approves it, it is publicly visible. If the team deactivates it later, it becomes a draft again: you rework it and submit it again. If you reactivate a cancelled entry that was never approved, it also comes back as a draft.

A cancelled event stays around for 7 days, during which you as the organizer can reactivate it. Only after that is it permanently deleted. A direct deletion is immediate and irreversible.

As the organizer, you can start a transfer to another person (Level 2+) from the management page. They have 7 days to accept or decline it in their control center; you can also cancel the request yourself in the meantime. Once accepted, responsibility switches immediately, with no re-approval needed.

As the organizer, you can appoint other people (Level 2+) as moderators from the management page. They can manage participation and edit the event's content, but cannot appoint further moderators or cancel, reactivate, or transfer the event — that stays yours alone.

The management page is available to the organizer, appointed moderators, and the Administration. Moderation and Event Management see the page read-only and can approve, deactivate and review feedback there. Whoever may edit sees every request and can approve, reject, waitlist or remove any participation — at any time, also afterwards; someone who was removed can sign up again. Lists are sorted by registration time, oldest request first. You will also find one shared search field for all lists, the participation-option evaluation, the attendance list, the QR code scanner, the CSV export and a preview that shows the event exactly as a visitor who is not signed in sees it — regardless of its current status.

With automatic acceptance every request is accepted immediately. Since the event then has no fixed size, a participant limit and a waitlist are not possible in that case. With "address required" only people whose address has been confirmed by the moderation can sign up; after acceptance they share their confirmed address with the organizers via an 8-digit code. Only the fact that the address was checked is stored, never the address itself. Both options apply to future requests only — existing participations stay unchanged.

When creating or editing, add a participation option marked "only for organisers (invisible to participants)", e.g. "Attended the meal" or "Paid" — just examples. Participants never see it and cannot tick it. On the management page under "Internal lists" you tick it per person and per guest, separately and at any time. By default all approved participants and their guests appear; alternatively restrict the list to the people of another option (e.g. only those who signed up for the meal, with limited places only confirmed places). In addition you can mark attendance at the event itself for every accepted person and every guest slot. Everything is reversible and visible only to your organizing team.

On the management page, above the participant list, you find the “Add person” form: enter a name (at most 100 characters, plain text), untick “Attended” if needed, done — no account required. The person shows up marked “Added on site” in the participant and the attendance list, gets a participant number (if numbers are on) and counts against the participant limit. Overbooking is allowed: you only get a note that the limit is exceeded; online registrations then stay closed or go to the waitlist and move up when you remove someone again. On options with a place limit and on internal lists you can use “Put a person on this list” below the table — either a person added on site or a name without any participation, e.g. for a sleeping place. Only you and your team see the names (management page and CSV), never the public; the public “x of y” count includes them. The creator, appointed moderators and the administration can add and remove; moderation and event management see the entries read-only. This works after the event ended and after the registration deadline too, as long as the event is neither cancelled nor archived. When an event is archived only the name stays in the archive count, without any link to an account.

When creating or editing your event, tick “Teilnahme ohne Konto erlauben” (allow participation without an account) in the “Teilnahme” tab. Visitors can then take part with a display name and a confirmed e-mail address and answer the participation questions — without guests. The option cannot be combined with the address check or with “external registration only”. You see these people only on the management page, marked “Ohne Konto” with their e-mail address (only you, appointed moderators and the administration); the CSV only has an “Ohne Konto” column, never the address. Approve, reject, waitlist, attendance and remove work as for accounts; removing deletes the data at once. Taxis and BnBs do not offer this.

Participants show their QR code from the control center ("My QR code"). On the management page, "Scan QR code" opens the camera; afterwards all lists on the page (participants, attendance, guests, participation options, internal lists) show only that person, the page jumps to the list and highlights the rows. The name appears in the search field above the lists; "Reset filter" shows everyone again. Without a camera you can type a name or a number there, or paste a profile link in the scan window. The filter stays after every action (e.g. marking attendance). The scan never changes anything automatically — you confirm approval, attendance and other status changes yourself with the button in that row. The camera image is not transmitted; only the public profile identifier is evaluated. The scanner is available on the management pages of events, taxis and BnBs.

Yes, the management pages of events, taxis and BnBs offer a CSV download: name, status, request timestamps and all answers to participation options. For events, the address check (if required), attendance and all internal lists are added. It only contains data you can see on the management page anyway. Please treat the file confidentially and delete it as soon as you no longer need it. People without an account have “Ja” in the “Ohne Konto” column; their e-mail address is never included.

Yes. On the management page, "Export as template" downloads a JSON file (content, settings, detail boxes and participation options). When creating a new event, open "Load from template", choose the file and enter the new start: end, registration start and registration deadline are set with the same distance to the start. The form is only prefilled, nothing is saved until you submit it as usual. The preview image is not part of the template. The file never contains participants, moderators, walk-ins, answers or feedback. Values that could not be taken over are listed above the form. Files from a newer version of the site are rejected.

Only accepted participants can give feedback — after the event has ended and until it is archived (30 days after the end). It is not public at first: the organizer, moderators and the team approve or reject it on the management page. Approved feedback appears with the display name on the event page and stays visible in the archive as well.

The calendar shows all approved events that are currently taking place or lie in the future. Past events move to the public archive 30 days after they end so that their feedback stays visible. On archiving, the participant list becomes a snapshot without links to accounts: only the display names of accepted participations remain, open and rejected requests are deleted. Taxis and BnBs have no archive — they are deleted 7 days after the event ends.

On the detail page of a published event, the last tile is "Add to calendar" — available to every visitor, even without an account. It downloads a calendar file (.ics) that you can open or import in Google Calendar, Apple Calendar, Outlook, Thunderbird or your phone's calendar. The entry contains the event's start, end and location plus two reminders: 1 day and 2 hours before. Your calendar converts the times to your local time zone automatically. If you download the file again later, for example after the event was changed, your calendar usually updates the existing entry instead of adding a second one.

Furry Taxi listings are ride-shares always bound to one specific event — either heading to it or away from it. Only people already approved to participate in that event can request a seat.

From Level 2 you can offer a ride to an already-approved event via the taxi creation page. It is saved as a draft first; you submit it for review on its management page, and it only becomes publicly visible once approved.

You must already be an approved participant of the bound event. Only then can you request a seat on the taxi's detail page; the driver approves or rejects your request manually.

Once your participation in a ride has been accepted, the last tile on its detail page is "Add to calendar". For privacy reasons it is only visible to accepted passengers, the driver, the ride's moderators and administrators. The tile downloads a calendar file (.ics) with the departure time, place, vehicle and two reminders (1 day and 2 hours before); the entry ends at departure plus travel time, or one hour later if no travel time was given. The license plate is never part of the file. Your calendar converts the times to your local time zone automatically.

Some drivers show participant numbers — a fixed, sequential number in the order you requested a seat, shown to you on the taxi page once your participation is approved. The number is permanent and never reassigned — if someone withdraws, a gap appears where their number was, which is normal.

Some drivers turn on a public participant list. When active, the taxi page shows your display name for every approved request, linked to your public profile — nothing else. You can hide yourself from that list at any time without affecting your participation.

The driver can optionally set a registration start. It is shown on the taxi page; before it nobody can request a seat, after it requests are possible until a registration deadline, if one is set. A clear notice at the very top of the page shows the registration start as long as it has not been reached.

The driver can optionally set a registration deadline. It is shown on the taxi page; after it, nobody can newly request a seat. Requests already made or approved stay in place, you can still change your answers and withdraw — but after the deadline you cannot request again. The driver can still approve or reject open requests afterwards. A clear notice at the very top of the page shows that the registration deadline has passed.

Your license plate is never shown publicly. It's visible only to you, already-approved passengers, and Taxi-Manager/Moderator staff. Only the make, model, and color are shown publicly.

As the driver, you can appoint other people (Level 2+) as moderators from the management page. They can manage passengers and edit the ride's details, but cannot appoint further moderators or cancel, reactivate, or transfer the ride — that stays yours alone.

The management page is available to the driver, appointed moderators, and the Administration. Moderation and Taxi Management see the page read-only and can approve, deactivate and lock rides there. Whoever may edit sees every seat request and can approve, reject, waitlist or remove any of them — at any time, also afterwards; someone who was removed can request again. The list is sorted by request time, oldest first. You will also find the participation-option evaluation, the QR code scanner to quickly find a person, and the CSV export of the passengers.

You set the number of seats when creating the ride (at least 1). Only accepted passengers count towards that limit. Once it is reached and you have allowed a waitlist, further requests are marked as waiting; without a waitlist no further requests are possible. You can change decisions at any time and move people up from the waitlist. Moving up never happens automatically for rides: you decide every request yourself.

Yes, on the management page with the “Add person” form: just enter the name. The person appears marked “Added on site” in the list, gets a number and counts against the seats. Overbooking is allowed, you only get a note; online requests then stay closed or waiting. The name is visible only to you and your team (management page and CSV); the public seat count includes the person. You can remove them at any time.

Yes. On the management page, "Export as template" downloads a JSON file. When creating a new taxi, open "Load from template", choose the file and the event the ride is for: departure and registration times are set relative to the start of that event. The licence plate and the preview image are never part of the template and have to be entered again. Nothing is saved until you submit the prefilled form as usual.

The driver as well as the Administration can cancel. A cancelled ride is not a deleted one: it remains for 7 days, during which the driver can reactivate it; after that it is deleted for good. Passengers are informed about cancellation and reactivation. If the linked event is cancelled, its rides are hidden and become visible again when the event is reactivated; after the event has ended, a ride is deleted after 7 days.

Administration, Moderation and Taxi Management can lock a ride, for example after rule violations. A locked ride is no longer publicly visible, and only these ranks can lift the lock again — the driver cannot. You are informed about locking and unlocking. Changes to an already approved ride need no new approval; the team is informed about the change instead and can review it.

On the management page you can start a transfer to another person of level 2 or higher. They have 7 days to accept or decline it in the control center; until then you can withdraw the request yourself. If the target person accepts, responsibility changes immediately without a new approval. Whoever takes over an already approved ride receives the "Driver" flag if needed, plus the "Verified driver" badge.

Furry BnB listings are temporary lodging offers bound to one specific event, with their own availability window instead of a departure time.

From Level 2 you can offer a place to stay for an already-approved event via the BnB creation page. It is saved as a draft first too; you submit it for review on its management page, and it only becomes publicly visible once approved.

You must already be an approved participant of the bound event. Only then can you request a place on the BnB's detail page; the host decides whether to approve or reject it.

Once your participation in a stay has been accepted, the last tile on its detail page is "Add to calendar". For privacy reasons it is only visible to accepted guests, the host, the stay's moderators and administrators. The tile downloads a calendar file (.ics) with the period from "Available from" to "Available until", the place and two reminders (1 day and 2 hours before). The exact address is only included if you may see it on the detail page as well. Your calendar converts the times to your local time zone automatically.

Some hosts show participant numbers — a fixed, sequential number in the order you requested a place, shown to you on the BnB page once your participation is approved. The number is permanent and never reassigned — if someone withdraws, a gap appears where their number was, which is normal.

Some hosts turn on a public participant list. When active, the BnB page shows your display name for every approved request, linked to your public profile — nothing else. You can hide yourself from that list at any time without affecting your participation.

The host can optionally set a registration start. It is shown on the BnB page; before it nobody can request a place, after it requests are possible until a registration deadline, if one is set. A clear notice at the very top of the page shows the registration start as long as it has not been reached.

The host can optionally set a registration deadline. It is shown on the BnB page; after it, nobody can newly request a place. Requests already made or approved stay in place, you can still change your answers and withdraw — but after the deadline you cannot request again. The host can still approve or reject open requests afterwards. A clear notice at the very top of the page shows that the registration deadline has passed.

Only a roughly rounded location (accurate to about 1.1 km) and the distance to the event are shown publicly. The exact address and coordinates are visible only to you, already-approved guests, and BnB-Manager/Moderator staff.

As the host, you can appoint other people (Level 2+) as moderators from the management page. They can manage requests and edit the listing's details, but cannot appoint further moderators or cancel, reactivate, or transfer the BnB — that stays yours alone.

The management page is available to the host, appointed moderators, and the Administration. Moderation and BnB Management see the page read-only and can approve, deactivate and lock stays there. Whoever may edit sees every request and can approve, reject, waitlist or remove any of them — at any time, also afterwards; someone who was removed can request again. The list is sorted by request time, oldest first. You will also find the participation-option evaluation, the QR code scanner to quickly find a person, and the CSV export of the guests.

You set the number of places when creating the stay. Only accepted guests count towards that limit. Once it is reached and you have allowed a waitlist, further requests are marked as waiting; without a waitlist no further requests are possible. You can change decisions at any time and move people up from the waitlist. Moving up never happens automatically for stays: you decide every request yourself.

Yes, on the management page with the “Add person” form: just enter the name. The person appears marked “Added on site” in the list, gets a number and counts against the places. Overbooking is allowed, you only get a note; online requests then stay closed or waiting. The name is visible only to you and your team (management page and CSV); the public place count includes the person. You can remove them at any time.

Yes. On the management page, "Export as template" downloads a JSON file. When creating a new BnB, open "Load from template", choose the file and the event the lodging is for: availability and registration times are set relative to the start of that event. Street, house number, postal code, exact position and the preview image are never part of the template and have to be entered again. Nothing is saved until you submit the prefilled form as usual.

The host as well as the Administration can cancel. A cancelled stay is not a deleted one: it remains for 7 days, during which the host can reactivate it; after that it is deleted for good. Guests are informed about cancellation and reactivation. If the linked event is cancelled, its stays are hidden and become visible again when the event is reactivated; after the event has ended, a stay is deleted after 7 days.

Administration, Moderation and BnB Management can lock a stay, for example after rule violations. A locked stay is no longer publicly visible, and only these ranks can lift the lock again — the host cannot. You are informed about locking and unlocking. Changes to an already approved stay need no new approval; the team is informed about the change instead and can review it.

On the management page you can start a transfer to another person of level 2 or higher. They have 7 days to accept or decline it in the control center; until then you can withdraw the request yourself. If the target person accepts, responsibility changes immediately without a new approval. Whoever takes over an already approved stay receives the "Host" flag if needed, plus the "Verified host" badge.

Use the contact form on the contact page (name, e-mail address, subject, message up to 5,000 characters). It also works without an account and forwards your message by e-mail to the administration; the reply goes to the address you entered. The message is not stored in a database; only whether it was delivered or discarded is logged (with the sender's domain and a shortened IP address, 30 days). Advertising, offers and other unsolicited commercial messages are not wanted and are discarded automatically. To prevent abuse there is also a hidden field, a minimum fill time and a request limit — anyone submitting the form too quickly is turned away.

The contact form is open to everyone, even without an account (or when you are banned). You create a ticket signed in, in the control center, when you want to report bugs, give criticism or suggestions, or report something that breaks the rules; only administration and moderation read it, and you see the history there. An inquiry goes exclusively to the creator of an event, taxi or BnB — for example for questions — and stays private between the two of you.

On the partner page, signed-in users find a section for applying: partner name, target address (http or https only) and an image with a 5:2 aspect ratio (exactly 200×80 or 400×160 pixels, or at least 600×240 pixels, at most 2 MB; animated images are allowed). The administration accepts or rejects the application and you are informed by e-mail. Accepted partners appear with their image and a link on the partner page. You can exchange the image or end the partnership at any time; it also ends automatically when you delete your account.

Yes, as soon as the administration has provided one: on the partner page you will find the German-Furs Network banner in several sizes, each with a ready-to-copy HTML snippet and a download link. You only have to paste the code on your own site or download the image.