Hotel enquiries
Ask about the guest journey, Central Kraków context, practical planning, or how the hotel experience might suit your visit.
Contact / A useful first note
Use this form for a hotel stay, room, dining, physical casino venue, accessibility, responsible-play, media, or partnership enquiry. We will reply with current information where a delivery route exists. The site does not promise a response time, availability, booking, venue access, or gambling outcome.
Before you send
Choose one enquiry type, give a general stay or visit period if it helps, and describe the question in plain language. Do not include passport details, identity-document numbers, payment-card details, bank details, gambling budgets, income, medical details, account passwords, or exact dates of birth.
Guest enquiry
The form uses method GET and points to a confirmation page. Client-side validation highlights missing information, but no backend, CRM, analytics service, or storage for the message is configured in this static site.
The contact route is broad enough to be useful, but not so broad that it invites sensitive information or creates a promise the site cannot deliver.
Ask about the guest journey, Central Kraków context, practical planning, or how the hotel experience might suit your visit.
Share a room style, a general period, or a practical preference. Current availability and features are confirmed in reply.
Ask about morning service, dinner, lounge, private-table arrangements, dietary requests, or non-alcoholic choices.
Keep questions to physical, on-site adult entertainment. The website does not create accounts, take wagers, or handle deposits.
Describe practical needs such as step-free routing, a quieter position, communication preferences, or assistance with arrival.
Ask about the venue-level route for a break, cooling-off, or self-exclusion concepts where available. For broader support, use appropriate official Polish services.
Explain the outlet, subject, deadline, and the information you need. The site does not invent named executives, awards, or official partnerships.
Describe the organisation, proposal, audience, and practical next step without sending confidential documents through the form.
Expected response wording is intentionally careful: the guest team will review the note and, where a working delivery route exists, contact you with current information. The site does not promise an exact response time or imply that a booking, room, table, access decision, or venue outcome has been made.
The reply can confirm details that belong to the period you asked about.
Availability, service arrangements, venue access, and city conditions may still need confirmation.
The site does not process payments, create gambling accounts, store a message, or send online wagers.
LunaVera is presented as Central Kraków, Poland. Do not rely on an invented street address, exact walking time, distance, transport promise, or fixed route. Check current local transport and map information when planning travel.
When you enquire, include the way you are approaching the city if that helps: rail, air, road, or another route. The reply can point you towards the current information needed without pretending that a static page knows the conditions of your travel day.
If your arrival changes, update the team through the delivery route available to the site owner. Do not include payment or identity-document information in a follow-up note.

This static project does not publish a telephone number or street address. If the owner supplies a verified email or direct contact route later, it can be added to this page and the privacy policy can be updated to match.
For a stay, room, dining, accessibility, or venue-information question, the form is the only interactive delivery route implemented here.
For immediate health or safety concerns, contact local emergency or public-health services rather than waiting for a hotel reply.
For a gambling concern, read Responsible Play and verify current official Polish support resources.
See the privacy page for the static site's storage, consent, forms, and rights information.
These answers describe the actual static workflow.
You can ask about hotel stays, rooms, dining, the physical casino venue, accessibility, responsible-play support, or media and partnership information.
The static site validates the form and navigates to a confirmation page. The message is prepared for the guest team; no backend storage or delivery claim is made by the website.
No exact response time is promised. The reply wording depends on the delivery route and current information available to the owner.
No. Do not send identity-document numbers, payment-card details, bank details, passwords, medical details, or gambling budgets.
No. LunaVera is described as a physical hotel and on-site venue. The website does not provide online gambling or account creation.
Choose the relevant route, share only what is needed, and keep sensitive information out of the form.
Open the enquiry formA contact form is not a performance and it is not a place to tell the whole story of your life. It is a short handover between what you are trying to plan and the current information someone can confirm.
Say the general period, the kind of room or pace you are considering, and the practical detail that matters most. A note such as “I am looking for a quieter room and a calm evening after walking in Kraków” gives the guest team a route into the question. It does not require a passport number, exact date of birth, payment information, medical history, or a promise that the room will be held.
Keep an adult physical-venue question separate from a request for a booking or outcome. Ask about current entry information, identity-check expectations, general atmosphere, breaks, or venue-level responsible-play support where available. The website does not create player accounts, accept wagers, process deposits, provide odds, or guarantee a table, game, access decision, or result.
Describe the route or adjustment that would help: step-free movement, a quieter position, communication preference, assistance at arrival, or a question about a break. Do not send a diagnosis, medication list, bank detail, identity document, or gambling budget. If the matter is urgent or unsafe, use local emergency or public-health services rather than waiting for a website form.
The current static form validates the note and moves to a simple confirmation state. Production delivery still belongs to the operator's verified route.
It confirms that the browser accepted the required fields and navigated to the success page. It does not prove that a person received the message, that a booking exists, that a room or table is held, or that the venue can provide the requested access. The owner should connect a real delivery route before treating the form as operational.
Keep a copy of the general question if you need it, then wait for the verified route available to the owner. Do not resend sensitive information because a response is not immediate. If an urgent safety, health, or responsible-play concern needs immediate help, contact the appropriate local service instead of relying on this website.
Useful contact respects both the visitor and the person receiving it.
Use a broad period and a practical question. Do not add identity documents, financial details, passwords, medical information, or a gambling budget.
The static form is not an emergency, medical, or crisis route. Use the appropriate local service when waiting for a reply would create risk.
That is the standard for every route on this page.
Choose one route, give the general context, and describe the practical next question. The team can then confirm what is current.
Keep sensitive personal and financial information out of the static form. Use a verified production channel if one is later supplied by the operator.