Who is responsible
The controller for this website is:
Jannes-Oke VossStaufenring 4
89073 Ulm, Germany
jannes-oke.voss@gmail.com
You can use this address for questions about the service or your personal data.
Account, trips & reviews
Google sign-in supplies your account identifier, name, email address, verification status and profile image if provided. Tageweit stores this identity, authentication tokens and session records in its Cloudflare database to recognise you and protect your account. It does not request access to your Gmail, contacts, calendar or Drive. Google handles its sign-in service under its own privacy policy. Google privacy policy.
Account-saved hiking trips contain your route, dates, packing list, notes and any booking references you enter. These records belong to your account and are not public. Imported GPX geometry stays in your browser draft until you save the trip; saving also stores its coordinates, available elevations and overnight points. The operator and hosting provider process these records to provide the service.
When signed in, changes to mixed adventures save automatically in your Google-linked Tageweit account, including activities, travel and personal preparation. This lets you reopen the trip on another device. Older browser copies move online only when you choose to keep an online copy; clearing browser storage can remove device copies. A private backup contains your complete trip and preparation. The separate text brief excludes private notes, assignees, private coordinates and the arrival board. Finder and Library requests contain public search filters and catalogue IDs, not your private itinerary or notes.
For a shared adventure, the organizer can invite signed-in people as editors, contributors or viewers. Members see the agreed itinerary, entered origins and exact shared locations and tracks, plus member names and roles. Owners and editors can save changes and review suggestions; contributors submit proposed changes. Your notes, checklists, packing and booking references remain separate for your account. Invitation tokens are stored as hashes with expiry, role and claim records. Agreed versions and suggestion decisions are retained as trip history. Removing a member or revoking a link blocks future authorized access; it cannot erase previously downloaded copies.
Legacy shared hiking trips use a separate record. Invited signed-in members can read its group name, itinerary, shopping list, chosen member names, proposals, booking reports and accepted history. Only the organizer accepts changes. A read-only link exposes the limited itinerary previewed by the organizer to anyone holding that link, without requiring sign-in. Account details, private-trip notes, shopping text and booking codes are excluded from that link. Removing access or revoking a link blocks future authorized reads; it cannot erase copies already downloaded or captured.
Reviews publish your chosen display name, rating, title, text, optional visit month and publication or edit dates. Your sign-in email is not published with the review. Place editors’ changes retain an internal author reference, notes and previous record versions for editorial accountability.
Account, trip and review processing provides the functions you request (Article 6(1)(b) GDPR). Editorial history serves the legitimate interest in reliable, traceable information (Article 6(1)(f)). Signing in is optional; basic identity is required for account functions. Other trip details are voluntary.
Maps & walking directions
Displayed maps load images directly from the OpenStreetMap Foundation. Its servers receive your IP address, browser and request information, including the requested map area. This supports our legitimate interest in providing usable maps (Article 6(1)(f) GDPR). OpenStreetMap privacy policy.
When you calculate walking directions, Tageweit sends consecutive point coordinates and your walking profile through its server to openrouteservice, operated by HeiGIT in Germany. It sends no account details, point names, trip notes or booking references. This processing fulfils your route request (Article 6(1)(b) GDPR). Calculated paths and their endpoints may remain in a cache separated by account for up to 24 hours. HeiGIT privacy policy.
Viewing or importing a GPX file does not send it to openrouteservice. Converting it into an editable walking route sends only the selected route points when you calculate. External booking and source links open services with their own privacy practices.
Hosting & browser storage
Cloudflare hosts the website, database and route cache. Requests include technical data such as IP address, browser information, requested address and time. Sessions also record IP address and browser information. Security limits and sampled request or error logs support the legitimate interest in secure, reliable operation and abuse prevention (Article 6(1)(f) GDPR). Cloudflare privacy policy.
Required cookies keep you signed in. Your chosen language is saved in local browser storage. A trip draft may be kept in the tab’s session storage while you sign in; only drafts less than one hour old are restored. This storage enables your requested functions (§ 25(2)(2) TDDDG; related personal-data processing under Article 6(1)(b) GDPR). You can clear it through your browser’s site-data settings. Tageweit uses no advertising or third-party analytics scripts.
If you email the operator, your address and message are processed using Gmail to answer your request. The legal basis is the legitimate interest in handling enquiries (Article 6(1)(f) GDPR), or Article 6(1)(b) where the enquiry concerns your use of the service.
Unsent mixed-trip suggestions, including their explanation, save privately online and are visible only to their author until submitted. A separate recovery copy may remain in this tab for up to 24 hours, bound to the signed-in account and trip revision. Legacy hiking drafts and invitation/viewer tokens also use this tab’s session storage. Browser storage can be unavailable or cleared; keep an exported copy of important unsent changes. Tokens are removed from the address bar after successful local storage and sent to the server in an authorization header or invitation claim, not in a query string. Shared-trip history remains until its deletion is arranged with the operator; there is currently no group-history deletion button.
How long data stays
Account records remain while your account is maintained. Saved trips and reviews remain until you delete them or request deletion. Authentication and editorial records are kept while needed to maintain the account, trace changes or resolve a security incident or dispute. Enquiries are kept until resolved and, where necessary, for applicable legal obligations or claims; data no longer needed for these purposes is deleted.
Sessions are valid for 14 days and may renew during use; signing out ends the current session. Session expiry does not delete your account. Route-cache entries last at most 24 hours. Cloudflare’s standard Workers logs are retained for up to seven days, depending on the hosting plan. Database recovery copies may retain deleted data for up to 30 days; separately exported recovery copies are retained while needed for recovery and protected from ordinary use.
International providers
Cloudflare and Google may process data outside the European Economic Area, including in the United States. Their published transfer safeguards include the EU–US Data Privacy Framework for covered recipients and European Commission standard contractual clauses. The OpenStreetMap Foundation is based in the United Kingdom, covered by an EU adequacy decision. Details and copies of the providers’ safeguards are available through these links or by contacting the operator:
Cloudflare data processing terms · Google transfer safeguards · EU adequacy decisions
Your rights
Under the GDPR, subject to its conditions, you may request access, correction, deletion, restriction and data portability. You may object to processing based on legitimate interests for reasons relating to your particular situation. If processing relies on consent, you may withdraw it for the future. Tageweit makes no solely automated decisions with legal or similarly significant effects.
Edit trips in My trips and your reviews on the relevant place page. Device drafts and legacy private hiking trips have a delete control. To delete an account adventure, its history or your account, or exercise other rights, email the controller above. Signing out or disconnecting Google does not delete your Tageweit data.
You may complain to a data protection authority, particularly where you live, work or believe an infringement occurred. The authority for the operator is:
Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-WürttembergHeilbronner Straße 35, 70191 Stuttgart
poststelle@lfdi.bwl.de
Contact and complaints