Terms of Service and Privacy Policy of keepDriving!eu

Administrator: AFYA

Contact: contact form

Last updated: 2026-08-20 (v3)

§1. Creating an account and technical requirements

Creating an account requires providing the personal data necessary for registration and service delivery, and confirming the account (e.g. via an activation link sent to your e-mail address).

An account is non-transferable and may not be shared with third parties. The Administrator may store user data for as long as justified by the purposes of the Service, marketing, security or legal requirements.

§1.1. Technical requirements

Using the Service requires a current web browser supporting modern security standards (TLS 1.3, JavaScript ES2022 and newer). We regularly test:

  • Google Chrome 148+ (preferred — all features work natively),
  • Mozilla Firefox 150+ (full compatibility, including Leaflet maps and the admin panel),
  • Apple Safari on iOS and macOS in current versions (works, including native link sharing).

The Service also works on mobile devices (Android, iOS) — the interface is responsive. The Administrator does not guarantee operation on older browser versions or on unsupported browsers (Internet Explorer, Microsoft Edge Legacy). When using a browser that does not meet the requirements, you may experience rendering errors, form issues or be unable to log in.

§2. Rules of use

The Service is provided “as is”. The Administrator does not guarantee error-free operation. The Service may be modified, expanded or have fees introduced without notice.

It is forbidden to interfere with the Service, circumvent security measures, decompile the code, or copy or use elements of the Service without the Administrator’s written consent.

Attempts to disrupt the Service (spam, attacks, bots, automated mass creation of accounts or content) result in immediate and permanent account blocking and — in extreme cases — notification of the competent law-enforcement authorities.

§3. Plans, fees and sponsored content

The Service may offer both free features and paid subscription plans or one-off services.

§3.1. Adding POIs and events — free of charge

Adding places (POIs: campsites, service stations, attractions, Natura Viva places) and events is free. All entries are equal regardless of whether they are added by a traveller, a venue owner or an event organiser.

The Service is run as a hobby and is supported by the optional “sponsored place” service (§3.1a below) and by displayed ads / affiliate content (§3.2).

§3.1a. Sponsored place — paid promotional service

The Service offers a paid “sponsored place” service for entities wishing to highlight their location on the keepDriving!eu map. The service is provided solely by the Administrator after payment of the chosen time package.

Scope of the “sponsored place” service:

  • Permanent map marker — always visible regardless of the selected POI-type filters. You may provide your own marker icon (scaled to approx. 48×48 px). The preferred format is SVG (perfect scaling); we also accept PNG / JPG / WebP (recommended 1024×1024 px, with transparency). Without an uploaded icon, the marker gets a default graphic.
  • Logo on the place card — separate from the marker icon. We show it on the POI card, in the marker tooltip and as a preview image when sharing the link on social media. You provide it (PNG / JPG / SVG, recommended 1200×1200 px); we prepare the appropriate crops.
  • Place description — text up to 5,000 characters with simple formatting (paragraphs via Enter).
  • Contact details — e-mail address, website and phone number. Outgoing links are tagged automatically (UTM parameters), so you can measure the traffic we send you; optionally we add a label for your campaign.
  • Gallery — up to 10 photos and up to 5 YouTube videos. We host the photos.
  • Amenities (“At this place” section) — you can mark attributes (parking, WC, restaurant, EV charging, Wi-Fi, 5G, beach, shop, clinic, etc.) from the same list as tourist attractions. On the public card we show only the marked items.
  • Validity period — we set the promotion end date. After it expires the marker disappears from the public map. 30 days before expiry we send an automatic reminder to the place owner and the editorial team.
  • Statistics for the Client — you have access to the same POI statistics as owners of regular entries (see §3.1c below): link visits, map openings and conversion actions (e-mail / phone / navigation / website), both the all-time total and the current year. Thanks to UTM parameters you can also analyse this traffic in your own tools (Google Analytics, Matomo, etc.).

A sponsored place is not subject to ratings or comments by Users — the POI card contains no review or star section.

The “sponsored place” service is sold via the online shop — three voucher variants are available: 1 month, 6 months and 1 year (pricing in the shop). For non-standard periods or an individual scope (e.g. a set of several POIs for a chain) we encourage you to contact us in advance via the contact form — we will tailor a package to your needs.

§3.1c. POI statistics — for all entries (not only sponsored)

For every POI (both standard — campsite, station, attraction, “wild” — and sponsored) we provide four simple metrics visible to the owner / co-owner / Administrator in the management panel:

  • Link visits — the number of visits directly to the card’s address (e.g. a share link, a search result, a newsletter link). Measures card exposure from outside the Service.
  • Map openings — the number of clicks on the POI marker on the map inside the Service. Measures interest among people already using the map.
  • Conversion actions — the number of clicks on real contact actions: e-mail, phone, navigation, website link. This is the most important metric — it shows how many people moved from viewing to a real interaction.
  • Likes — the number of users who marked the POI as a favourite.

The statistics are indicative and counted with simple protection against inflation — repeated visits from the same device within a short time do not bump the counter. Measurement is anonymous: we do not build a tracking profile or link activity across devices — by design (we are not Google). We keep counters broken down by year, so you see both the all-time total and the current year’s result; we do not overwrite historical data.

§3.1b. Other paid plans — possible in the future

The Administrator does not rule out introducing other paid plans in the future (e.g. advanced analytics for venue owners, dedicated marketing tools, POI features).

If such fees are ever introduced, they will apply to entries added after the new rules come into force. We will inform you of any changes well in advance (by e-mail to logged-in Users and a message on the home page), and existing entries will be treated on the terms agreed when they were added.

§3.2. Sponsored content

The Service may display sponsored content, advertisements or affiliate materials. Their presence does not constitute a recommendation or opinion of the Administrator.

Ads may come from external systems (e.g. Google Ads, partner or affiliate networks).

§3.3. Payment methods

  • Payments may be made via secure payment operators such as PayU, Stripe, Przelewy24, PayPal or BLIK.
  • All transactions use TLS encryption. The Administrator does not store payment card data or CVV codes.
  • Payment data is processed solely by payment operators in accordance with the applicable GDPR rules and PCI DSS security standards.
  • You may receive payment confirmation by e-mail or in your account panel.

§4. Personalised ads and remarketing

The Service may use marketing tools that tailor ads to user interests (advertising cookies, tracking pixels, device identifiers).

The Administrator may cooperate with advertising partners that combine visit data with other sources, in accordance with their own privacy policies.

You may limit ad personalisation through your browser, system or privacy panel settings (e.g. youradchoices.com, Google ad settings).

§5. Copyright and logos

All content, code and layout of the Service are legally protected. Copying or reproducing them without the Administrator’s consent is forbidden.

§5.1. Venue and organiser logos

All logos, proper names, trademarks and trade marks visible in the Service — on the POI card, in an event header or in the social-media link-sharing card — belong to their rightful owners or the entities representing them. We display them solely for information and identification purposes — so that the User can recognise a given place or event on the map and in the shared-link card.

The Administrator claims no rights to these marks, does not use them commercially and does not sell advertising space using them. If you are the owner of a mark and do not agree to its presentation, please contact us via the contact form; the logo will be removed or its presentation changed.

Using, reproducing, modifying or distributing parts of the Service — including visual identity, icons, graphics and other elements protected by copyright or related rights — without the prior written consent of the Administrator or the authorised rights holder is forbidden.

§5.2. User photos

By submitting or posting a photo in the Service, the User declares that they hold full copyright to the material and grants the Administrator — AFYA, based in Wrocław, Poland (VAT no. PL-8842279975) — a non-exclusive, royalty-free, perpetual licence to display, publish, process, crop, scale and manage it within the Service.

Photos documenting data presented in the Service — in particular photos of fuel station price boards — may also be used by the Administrator to improve the Service’s automatic content-recognition mechanisms, including training models that read prices from the boards. Location metadata (GPS) is removed before such use, and the Administrator strives to anonymise any personal data visible in the photos (e.g. faces, licence plates). Photos are not sold or shared with third parties for this purpose.

If the User’s account is deleted, the Administrator retains the right to continue presenting, promoting and using the photo in the Service, provided this does not breach applicable law. If the User does not consent to this, they should remove the photo before closing the account.

The User bears full responsibility for submitted photos, including any infringement of third-party rights. The Administrator may remove content that breaches the law, principles of social conduct or these Terms, but is not liable for Users’ actions or content they introduce into the Service.

§6. Privacy policy

The Administrator processes data in accordance with the GDPR. Data may include IP address, e-mail, system logs, form data and cookie data.

Legal bases for processing: legal obligation, performance of a contract, the Administrator’s legitimate interest or the user’s consent. Data is processed for technical, statistical, marketing and security purposes.

Logging in via Facebook, Google and GitHub. If a user logs in or links their account using an external provider (Facebook, Google or GitHub), the Service obtains from that provider only the user identifier and e-mail address (and, if shared, the first and last name). This data is used solely to authenticate and identify the account in the Service — it is not used for any other purpose or shared with third parties. The User may unlink the connected account at any time in the profile settings.

§7. Cookie policy

The Service uses cookies to maintain sessions, tailor content and analyse traffic. You can control cookies in your browser settings. Restricting cookies may affect how the Service works.

§8. Adding entries: moderation and acceptance criteria

Every new entry (POI, event) undergoes moderation by an administrator or editor of the Service before publication. Moderation is done as a hobby — we try to accept entries within 24 hours, but we do not guarantee a specific response time.

§8.1. Reasons for rejecting an entry

An entry may be rejected when:

  • Wrong category — e.g. a “wild” spot reported as a campsite (or vice versa). Each category has its own characteristics, and the wrong POI type confuses other travellers. After correction the entry can be resubmitted.
  • No contact details — at least one of: phone, e-mail, website is required. Without contact, other Users cannot book a place or verify whether the entry is up to date.
  • Low data quality — empty or vague description, missing coordinates, no photos or logo, internally contradictory information.
  • Not our topic — the Service concerns motorhome travel and vanlife. Ordinary city car parks and classic petrol stations are not eligible; we accept fuel stations only if they offer motorhome service (waste disposal, electricity, drinking water), and car parks only if they clearly allow overnight motorhome stays.

The Administrator is not obliged to send individual explanations for each rejection — moderation is done as a hobby and we do not have capacity for per-entry correspondence. The above criteria are guidance for the User on what to pay attention to when adding.

§8.2. Moderation of reviews and comments

Reviews and comments are moderated as to form, not content: we remove profanity, insults, threats, hate speech, defamation and any content violating the dignity of others — without prior notice. Constructive criticism, even a negative rating, is allowed provided it is in a factual form. A review should describe what was wrong, not contain personal attacks.

§9. Taking over management of an existing place

It happens that a venue (campsite, station, attraction) is already added to the Service by another User — usually a traveller who was there — before the venue owner created an account. The owner may take over management of such a place under the conditions below.

§9.1. Procedure

  1. Create a User account in the Service (if you do not already have one).
  2. Open the place card and click the white flag icon on the POI — this is the official report to moderation.
  3. Write to us via the contact form: send your user ID (visible in the menu after logging in) and explain that you are authorised to manage this place.
  4. The Administrator verifies the request (usually 1–3 days). After successful verification the User receives owner rights to this POI.

§9.2. What speeds up verification

Helpful for faster verification are:

  • a link to the venue’s official website with an e-mail address in the footer / contact section,
  • a copy of a document (e.g. business register, invoice) with a company name matching the POI name,
  • a message sent from the venue’s official e-mail address visible on Google / on invoices.

Without additional information, verification may require further questions or be rejected. The Administrator reserves the right to refuse to grant rights if the request does not credibly confirm owner status.

§10. Limitation of liability

The Service is purely informational and community-based. Most data (addresses, opening hours, prices, descriptions, event dates, contact details) is entered by Users themselves — travellers who visited a place and venue owners. The Administrator moderates what is possible (category, contact, basic quality), but does not individually verify every opening hour, price or event date — that is physically impossible for a hobby-run Service.

§10.1. No warranty

The Administrator makes every effort to ensure published information is reliable, complete and up to date, but does not guarantee its completeness, accuracy, timeliness or conformity with the actual state of venues or events.

Information, materials and data published in the Service may be partial, outdated or contain errors resulting from typos, technical mistakes, legal changes or third-party actions.

§10.2. Exclusion of liability

To the maximum extent permitted by law, the Administrator is not liable for:

  • The quality of services provided by campsites, service stations, event organisers or other operators of venues listed in the Service — these are independent entities over which the Administrator has no influence.
  • Outdated opening hours, prices or seasons (e.g. a campsite changed its pricing between updates).
  • Postponed, cancelled or changed event dates (when the organiser did not report the change; the Service tries to mark a date change or cancellation when it has such information).
  • Permanently closed venues shown as active (please report with the “white flag” — we will withdraw the entry).
  • Travel decisions, bookings, transactions and financial commitments made solely on the basis of content from the Service.
  • Damages, financial losses, inconvenience, lost profits and any other negative consequences resulting from relying on data from the Service — both when planning a trip and during it.

§10.3. Reviews, comments and ratings

All reviews, comments, ratings and reviews published in the Service express solely the individual views of their authors. They do not constitute the position of the Administrator or a recommendation of the Service. They are subjective — the same place may receive 5 stars from one traveller and 2 from another, depending on expectations, season, weather and many other individual factors.

The Administrator does not verify the truthfulness of the experiences described in reviews. Only the form is moderated (no profanity, insults, threats, hate speech, defamation). The Administrator is not liable for:

  • the substantive content of reviews or their truthfulness,
  • damages resulting from relying on Users’ reviews,
  • venue owners’ reactions to reviews published in the Service.

The User bears full responsibility for the reviews, comments and content they post. The Service only verifies whether a review was added by an authorised and logged-in User, but does not guarantee its reliability or truthfulness.

§10.4. Recommendations for the User

Use of the Service is at the User’s own risk. Before travelling to a new place — especially far from home, abroad or in high season — we recommend:

  • calling or writing directly to the venue to confirm it is still operating,
  • making sure there are vacancies and prices are current,
  • for events — confirming with the organiser that the event will take place on the planned date.

The contact numbers and websites in each POI card are provided for exactly this purpose. If in doubt about the timeliness or correctness of information, please contact us via the contact form.

§11. Closing an account and inactive accounts

The User may close their account at any time from the Dashboard → Account → Close account panel. The procedure is voluntary, free and does not require contacting the Administrator.

§11.1. Account-closing procedure

  1. In the account-closing form the User may indicate the ID of another Service user (a so-called successor) to whom their POIs (campsites, stations, attractions, Natura Viva places) and events are to be transferred. Photos, descriptions and logos associated with those places / events pass together with them.
  2. If the User does not indicate a successor, their POIs and events are automatically transferred to the Service administrator’s account — they remain visible to travellers, but the User no longer has access to them.
  3. Promoting a co-owner to owner: if the indicated successor is currently a co-owner of one of the User’s POIs or events, they are automatically moved from the co-owner list to a full owner of that POI / event — while keeping continuity of their existing access.
  4. The User’s co-ownerships in other POIs / events (where they were only a co-owner, not the main owner) are withdrawn: their ID is removed from the co-owner list, and the owner of that POI / event remains unchanged.
  5. After the transfer is completed the User’s account is deleted from the database, and all devices on which they were logged in lose their session.

§11.2. Identity confirmation when closing an account

To prevent an account being closed by an unauthorised person (e.g. after a session hijack), we require identity confirmation with a second factor:

  • if the User has active OTP (a code generated by an Authenticator app) — they enter the current 6-digit code;
  • if the User has an active Passkey (Face ID / fingerprint / Windows Hello / hardware key) — they confirm with the browser’s native biometric prompt;
  • if the User has neither OTP nor Passkey — the account is closed without additional second-factor verification; it is enough to type the confirmation phrase ZAMYKAM KONTO in the form (anti-fat-finger), because since the user did not enable 2FA we have nothing to verify against and do not want to forcibly “block” their way out.

§11.3. Automatic deletion after 2 years of inactivity

Accounts of Users who have not logged in to the Service for over 2 years (730 days) are automatically closed by the Administrator. The procedure is as follows:

  • 30 days before the planned deletion the User receives an informational e-mail with a login link — a single login is enough to stop the counter (it starts again);
  • after 2 years without logging in the account is deleted from the database, and the added POIs / events / photos are transferred to the Service administrator (as with self-service closure without indicating a successor);
  • if, before the planned deletion, the User wants to indicate a specific successor (instead of the default transfer to the administrator), they should log in and go through the §11.1 procedure manually.

§11.4. The admin cannot delete someone else’s account

The Service Administrator cannot delete another User’s account or your data from the admin panel. The Administrator may, however, block an account — e.g. in response to sabotage, spam or a breach of these Terms — which prevents logging in but does not delete data. The decision to permanently close an account always belongs to the User themselves (§11.1) or to the automatic inactivity procedure (§11.3).

§11.5. What happens to reviews and comments

Reviews, ratings and comments, once added to the Service, can be edited or deleted only within the first 24 hours of publication. After that window the content becomes a permanent element of the POI / event profile — it can no longer be edited or deleted on your own, because it forms part of the community-gathered experience (which subsequent travellers are entitled to rely on when choosing a venue). The same rule applies after closing an account — if you care about deleting a particular review, do it within the first day of adding it.

In the public view, reviews and comments are signed with an anonymous identifier generated by the Service (we show neither first name, surname nor e-mail of the Author). This protects Users’ privacy while allowing readers to follow a person’s comment thread within a single POI.

The link between the identifier and a specific User account is stored only within the Service and is not made public or shared with other Users. However, the Administrator retains the technical ability to identify the author of an entry at the request of authorised state authorities (courts, police, prosecutor’s office) — solely to the extent and in the manner required by applicable law.

§12. Final provisions

The Administrator may introduce changes to these Terms and the Privacy Policy. The current version is published in the Service.

In matters not regulated herein, Polish law applies. Disputes are settled by the court competent for the Administrator’s registered office.

The main language of communication, notifications, informational materials and User support in the Service is Polish. Content provided in other languages is auxiliary, and in case of any discrepancy the Polish version prevails.

v.0.0.1.451