Contact Zakynthos.net

01

Before you write

The fastest way to receive a useful response is to identify what you need and where it appears. For an editorial correction, include the exact page URL and quote the sentence or section. Explain what has changed, when you observed it and which source can confirm the change. A dated public notice, official link, current photograph or first-hand report with enough context is more useful than a general statement that a page is wrong.

For a broken link or technical problem, describe the device, browser and action that led to the issue. Screenshots can help when the problem is visual, but remove booking references, email addresses, telephone numbers or other personal information that is not needed. Do not send passwords, payment-card details, passport information or full booking confirmations.

For privacy requests, clearly state whether you are asking for access, correction, deletion, restriction, objection, portability or withdrawal of consent. We may need reasonable information to verify identity before acting, but we will not ask for excessive documentation. The Privacy Policy explains the scope and limitations of these rights.

02

Editorial corrections and local updates

Local conditions can change faster than a travel website. We welcome reports about beach access, road changes, transport information, public opening arrangements, conservation instructions and businesses that have permanently closed or materially changed. Reports are checked before publication. A first-hand observation is valuable, but a safety-critical change may still require confirmation from the responsible authority.

Businesses may correct objective details such as name, location, contact information, accessibility arrangements or service type. A request to remove a fair editorial limitation, change comparative judgment or guarantee inclusion will be assessed under the Editorial Policy. Payment is not accepted in exchange for correcting an error.

If you own rights in an image or text that you believe is used without permission, identify the exact material, its URL, the basis of your claim and a way to verify your authority. We will investigate promptly. A complete notice helps distinguish a genuine rights concern from an automated or mistaken request.

03

Partnership and contributor enquiries

Zakynthos.net is interested in accurate local knowledge, responsible operators, accommodation information, original photography and destination expertise. A concise proposal should explain the organization or contributor, the relevant page or audience, the proposed value and any commercial expectation. Generic link-exchange and bulk guest-post proposals are unlikely to fit the site.

Tour and accommodation partners should disclose whether information comes from an API, affiliate feed, direct commercial agreement or sponsored placement. Product inventory must remain separable from editorial conclusions. Conservation-sensitive experiences should explain their licensing, wildlife-distance procedures, vessel or group size, cancellation approach and what happens when conditions prevent the advertised route.

Photographers should provide usage terms, credit requirements and confirmation that identifiable people or restricted property are appropriately handled. Writers should disclose material relationships with places they cover and submit original work. We do not accept copied destination descriptions or undisclosed AI-generated factual claims.

04

Bookings, emergencies and response boundaries

Zakynthos.net is not the booking provider for a reservation completed on an external marketplace or operator website. We cannot see confirmation records, change dates, process refunds, resolve a payment dispute or promise that a provider will meet a special request. Use the support details in the confirmation and keep communication inside the booking platform where possible.

Do not wait for an email response in an emergency. In Greece and across the European Union, 112 is the general emergency number. At sea, on a protected beach or near a controlled viewpoint, follow instructions from emergency services, port authorities, rangers and on-site personnel. The website cannot assess real-time weather, medical risk or active access conditions.

We try to review substantive messages, but response time depends on urgency, evidence and workload. Sending repeated copies does not move a request ahead. Spam, abusive messages, deceptive sales contact and submissions containing malicious files may be deleted or blocked. We may retain necessary correspondence to resolve a request, protect the service or meet legal obligations.

05

What happens after submission

Messages sent through the form are delivered to the email address configured by the site operator in WordPress. The form collects the fields shown, basic technical information needed for security and a timestamp. A hidden anti-spam field and short rate limit reduce automated abuse. The submitted content is used to handle the enquiry and related follow-up, not automatically added to a marketing list.

If your message concerns another person, share only what is necessary and confirm that you are entitled to provide it. Sensitive information is rarely needed for an editorial website. Where a request belongs with a public authority or external provider, we may direct you there rather than forwarding personal information without a clear reason.

Use the form below for ordinary contact. If the form does not work, the public site owner should ensure that the WordPress administration email is correct and that outgoing mail is configured reliably. Delivery from WordPress can require a transactional email service; installing a theme does not by itself guarantee mail delivery.

06

Useful details by enquiry type

For a transport or access update, include the location, direction of travel, date, approximate time and whether the information came from a sign, staff member, operator notice or direct observation. Avoid reporting a temporary queue or one delayed departure as a permanent change. If an official page exists, share the direct link rather than a screenshot alone so we can verify later updates.

For accessibility information, describe the practical feature without assuming that it serves every disability. Useful details include step count, surface, gradient, handrails, doorway or vessel boarding method, accessible toilet availability, reserved parking and whether assistance must be arranged. We welcome corrections from disabled travellers and local operators, but the final service commitment must still be confirmed directly before travel.

For conservation concerns, do not put yourself at risk to collect evidence. Record the place, time and activity from a safe and lawful position. Active harm to wildlife, fire, pollution, unsafe boating or entry into a controlled area should be reported to the appropriate local authority or emergency service first. An editorial message can help us improve future guidance, but it is not a real-time enforcement channel.

For a partnership proposal, explain the reader problem your business solves rather than sending a general brochure. State the location, operating season, licensing or professional status where relevant, accessibility information, cancellation policy, sustainability practices and any compensation offered. Clear disclosure at the beginning saves time and protects both the publication and its audience.

For general trip questions, check the Beaches, Towns, Where to Stay, Tours, Things to Do and Guides sections first. We cannot create a private itinerary for every enquiry, confirm tomorrow’s sea state or recommend a provider without enough context. A focused question about information already published is easier to answer and may reveal where a page needs clearer wording for everyone.