Privacy Policy
This privacy policy applies to the CamperOwl web application. It explains which personal data we process when you use our website and features, for which purposes we do so and on which legal basis.
Last updated: 24 April 2026
1. Controller
Emrah Arican Digital Services
Emrah Arican
Sterchelestr. 14
79379 Müllheim
Germany
Email: service@arican.eu
2. Purposes and legal bases
We process personal data in particular to:
- provide the website and user accounts
- offer trip planning, favourites, vehicle profiles, reminders and export features
- handle premium memberships and payments
- provide optional AI, map, analytics and convenience features
- prevent misuse and ensure system stability and security
Depending on the situation, processing is based in particular on:
- Article 6(1)(b) GDPR for the performance of contractual services
- Article 6(1)(a) GDPR for consent-based optional features
- Article 6(1)(c) GDPR where legal obligations apply
- Article 6(1)(f) GDPR for a secure, stable and efficient service operation
3. Hosting, infrastructure and Supabase
When you access the website, we process technically required connection data such as IP address, timestamps, requested content, browser or device information and status data. This is necessary to deliver the website, analyse incidents and ensure secure operations.
We use Supabase for authentication, database access and application data storage. This includes user accounts, profile data, trips, favourites, reminders, AI histories, share links, error logs and other app data whenever this is required for the relevant feature.
4. User accounts, sign-in and Google sign-in
You can register and sign in with email and password. We also offer optional Google sign-in. During registration we process the data required to create the account, especially the email address, login information and technical session data.
After successful registration we create a profile with an internal user ID, email address and role information. If confirmation or sign-in emails are sent, this is done through Supabase authentication infrastructure.
5. Profile data, trips, favourites, vehicle profiles and reminders
When you use protected features, we process the content you store. Depending on your usage this can include profile information, trips, stops, favourites, vehicle profiles, budget and cost data, reminders and other planning information you enter.
We process this data so we can save your trip planning, display it in your account, synchronise it and let you reopen it later. Reminder features additionally use your trip data to provide time-based notices.
6. Sharing trips, exports and user-generated content
You can share trips via share links. We create a random share token and mark the respective trip as shared. Anyone who knows the link can access the shared content. You can revoke sharing at any time.
We also process your data when you use export features such as PDF or GPX exports. If you submit reviews, hints or other content, we process that content for display, quality assurance and feature improvement.
7. Premium memberships and Stripe
We use Stripe as our payment provider for paid premium memberships. When you book a paid plan or manage a subscription, we process the data required for that purpose, especially internal user IDs, email address, your stored name if applicable, plan information, payment status, Stripe customer and subscription IDs and billing events.
The actual payment is handled directly by Stripe. We receive the status and matching information needed for contract fulfilment, billing, fraud prevention and bookkeeping. We also store billing reference data such as Stripe IDs and email snapshots in our application database for internal assignment.
8. OwlAI and AI-supported features
When you use OwlAI, we process your prompts and the context sent with them, such as trips, stops, favourites, route data, budgets, place information or detail context, if this is required for the requested answer. We also store chat histories and metadata so conversations can be resumed and answers can be traced.
AI responses are generated through external AI providers configured by us. Depending on the current system configuration, OpenAI-compatible and or Anthropic-compatible services may be used. These features are used only to provide the AI assistance you requested.
9. Cookies, local storage, session data and service worker
We use technically necessary storage mechanisms for sign-in and session management, security, feature states and local convenience functions. This includes authentication and session data, local consent storage and technical markers for cache and service-worker clean-up.
The browser may use cookies, local storage, session storage and cache storage for these purposes. Without these mechanisms, essential parts of the website could not be operated securely or reliably.
10. Consent management
For optional features we use a consent-management system with the categories Analytics and Maps. Your choice is stored both in the camperplaner_consent cookie and in local storage so it can be respected during later visits.
Without your consent, the related optional features stay disabled. You can reopen the consent settings at any time via the footer or privacy controls in the website and change or withdraw your selection for the future.
11. Analytics, Rybbit and error monitoring
If you consent to Analytics, we load our Rybbit instance at rybbit.arican.eu. Usage and technical data required for reach measurement, page views and web-usage analysis are processed there. The Rybbit integration remains disabled until you consent.
We also use Sentry/Bugsink-compatible error monitoring to detect runtime errors, server errors, failed resource loads, unhandled rejections and stability issues. Current URL, app version, technical error messages and similar diagnostics may be processed. If you consent to Analytics, additional features such as session replay, console-error capture and performance tracing may also be activated.
12. Maps, places, routing, weather and external media
We use external services for map and place-related features. Interactive maps are provided through Mapbox and remain disabled until you consent to the Maps category. Depending on the feature in use, requests may also be sent to Google Places, WeatherAPI, Wikimedia Commons, Wikidata, Mapillary and open geodata sources such as OpenStreetMap.
This can include IP address, browser or device information, timestamps, coordinates, search queries, requested places or specific resources. This applies not only to the map itself, but also to route calculations through the Mapbox Directions API and free-form place lookups through the Mapbox Geocoding API.
More information about the data sources and licence notes we use can be found on the page Data Sources & Licences.
13. Browser notifications and contact
If you actively use reminder or notice features, we may use browser notifications. Such notifications are only used if you have allowed them in your browser or operating system. We process the underlying trip data and reminder times so the requested notification can be triggered.
If you contact us by email, we process your message, sender data and the information contained in the request so we can handle your enquiry and respond to follow-up questions.
14. Recipients, processors and third-country transfers
We transfer personal data to third parties only to the extent necessary to provide the website, deliver requested features or comply with legal obligations. Recipients may include hosting, authentication, database, analytics, monitoring, payment, map, weather, AI and media services.
Where providers outside the EU or EEA are used, or where they can access data there, third-country transfers may occur. In such cases we seek an adequate level of protection, especially through adequacy decisions or suitable contractual safeguards.
15. Storage period
We store personal data only for as long as this is required for the respective purposes or as long as legal retention obligations apply. Account data, trips, favourites, reminders, AI histories and other user-related content are generally stored while your account exists or while storage is necessary for the relevant feature.
We store consent decisions and technical logs only for as long as this is needed for proof, security, error analysis or stable operations.
16. Your rights
Subject to the statutory requirements, you have the following rights in particular:
- right of access
- right to rectification
- right to erasure
- right to restriction of processing
- right to data portability
- right to object to certain processing activities
- right to withdraw consent with future effect
17. Right to lodge a complaint with a supervisory authority
You have the right to lodge a complaint with a data-protection supervisory authority regarding the processing of your personal data.