Privacy Policy

As of: 23 October 2026 · Version 2.16

In accordance with Art. 13 and 14 of the General Data Protection Regulation (GDPR), this privacy policy informs you about the processing of personal data when using the web app ViaCamp at via.camp.

1. Controller

Controller within the meaning of the GDPR:

Martin Pfeffer
Flughafenstraße 24
12053 Berlin, Germany
Email: martin@via.camp

A legally mandated data protection officer is not required pursuant to § 38 BDSG (German Federal Data Protection Act). For data protection enquiries, please use the email address given above.

2. Definitions

This privacy policy uses the terms of the GDPR (in particular Art. 4). “Personal data” means any information relating to an identified or identifiable natural person.

3. Hosting and infrastructure

ViaCamp is operated on a dedicated server in a data centre within the European Union (Germany). The infrastructure provider is Hostinger International Ltd., 61 Lordou Vironos Street, Larnaca 6023, Cyprus.

Data is stored in a PostgreSQL database on the same server. No automatic data transfer to the provider takes place beyond what is technically strictly necessary for operating the server. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in operating the service).

4. Server log files

Each time ViaCamp is accessed, the web server (Nginx) automatically collects the following data and stores it in log files:

• IP address of the accessing device
• Date and time of access
• Name and URL of the requested resource
• Amount of data transferred and HTTP status code
• Browser and operating system used (user agent)
• Referrer URL (previously visited page)

Purpose: Ensuring a smooth connection, defending against attacks, analysing errors, rate limiting.
Legal basis: Art. 6(1)(f) GDPR (legitimate interest in the security and functionality of the service).
Storage period: 30 days, after which automatic deletion. This data is not merged with other data sources.

5. Cookies, session and local storage

5.1 Technically necessary cookies

For authentication, ViaCamp uses a server-side signed session cookie (via express-session). Logged-in use is not possible without this cookie.

Both cookies apply to via.camp and its subdomains (app.via.camp, partner.via.camp, help.via.camp, admin.via.camp), so that you stay logged in and keep your language when moving between the app, the operator area, help and administration. Other websites do not receive them. An older session cookie connect.sid, if still present, is taken over on your next visit and deleted.

Legal basis: § 25(2) no. 2 TDDDG (German Telecommunications Digital Services Data Protection Act; strictly technically necessary), Art. 6(1)(b) GDPR (performance of a contract).

5.2 Other cookies

Apart from the technically necessary cookies listed above, ViaCamp sets no cookies — no analytics or advertising cookies either. There is therefore no cookie banner. (Until October 2026, Google Analytics was loaded after consent; this has been discontinued. Any remaining vc-consent entry in your browser no longer has any effect.)

5.3 Local storage (localStorage / sessionStorage)

The following data is stored exclusively locally in your browser and does not leave it:

• Theme selection (light / dark): ap-theme
• Active app tab, filter and heatmap settings
• Location cache (valid for 5 minutes) in sessionStorage, only if you have confirmed the location request

This storage is technically necessary for functionality and not accountable to third parties (§ 25(2) no. 2 TDDDG).

6. Registration and user account

6.1 Registration by email and password

When you register with email and password, we process: email address, chosen password (stored as a salted scrypt hash, never in plain text), display name.

6.2 Login via Google OAuth

Alternatively, you can log in using your Google account. In doing so, you are redirected to Google and authenticated there. After successful login, Google transmits to us: Google user ID, email address, display name, profile picture URL. Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (Google Privacy Policy).

6.3 Login via magic link

For passwordless login, a one-time link is sent to your email address (valid for 15 minutes). The token is stored server-side in the database and deleted after redemption or expiry (at the latest after 30 days).

6.4 Profile information

You can voluntarily store the following in your profile: display name, profile picture (avatar), vehicle type, consumption values, travel preferences. This data is used exclusively to personalise your use and is not passed on to third parties. Legal basis: Art. 6(1)(b) GDPR (performance of a contract).

6.5 Two-factor sign-in (optional)

In your profile you can additionally protect your account with a code from an authenticator app. For this we store a randomly generated secret from which the app calculates the codes – encrypted (AES-256-GCM) and bound to your account –, the time it was switched on, the most recently used time step (so a code cannot be used twice) and ten recovery codes, which are stored only as a non-reversible check value (HMAC-SHA-256) and shown to you only once. We generate the QR code for the setup on our own server; the secret is not transmitted to any third party. Your authenticator app itself processes the data on your device under the terms of its provider.

If two-factor sign-in is on, after your password, sign-in link or Google sign-in your session only remembers for at most ten minutes that the second step is pending; you are signed in only after entering the code. To prevent guessing, failed attempts are counted briefly per account and per IP address in memory.

Legal basis: Art. 6(1)(b) GDPR (providing the user account) and Art. 32 GDPR (security of processing). Retention: until you switch two-factor sign-in off or delete your account; used recovery codes remain marked as used until new codes are generated.

6.6 Deleting your account

You can delete your account yourself at any time in your profile under “Account”. To confirm, you type your account name, plus your password (if set) and, with two-factor sign-in, a code. Deletion cannot be undone.

Deleted immediately: name, email address, profile picture, short bio, password hash, Google link, settings and vehicle data, two-factor data, trips with stops, diary (text and photos) and shared trip links, packing list, checklists (vehicle and season), saved and visited places, achievements, push subscriptions, open sign-in and password links, open claim requests and all sign-in sessions on all devices. Claimed places become free again; details you maintained there as an operator (e.g. prices) stay with the place.

Kept without your name are contributions that serve other campers: reviews, photos, reported places, suggested changes, reports, “helpful” votes and recorded routes for route planning (including the record of your consent to them). They are shown as “Deleted user” and are only linked to an internal number without name or contact details. Guest inquiries you sent to operators remain with the operator as their record. If you want these contributions removed as well, a message to martin@via.camp is enough.

If a paid Featured subscription is still running for one of your places, deletion is possible only after it has been cancelled; invoices are kept because of statutory retention duties. After deletion we send a confirmation to your previous address.

Legal basis: Art. 17 GDPR; for the contributions kept without a name Art. 6(1)(f) GDPR (legitimate interest in complete place information and in route planning for all users), objection under Art. 21 GDPR possible at any time.

7. Map service and routing

7.1 Map tiles (OpenStreetMap)

To display the interactive map, your browser loads map tiles directly from the servers of the OpenStreetMap Foundation (UK). In doing so, your IP address is necessarily transmitted to OSM. An adequacy decision of the EU Commission exists for the United Kingdom (Art. 45 GDPR). OSM Privacy Policy.

7.2 Route calculation

Route calculation takes place primarily on our own Valhalla server (Germany). Your route (waypoints, vehicle profile) is transmitted to our server for calculation, processed there and not stored permanently.

As a fallback if Valhalla fails, the route is sent directly from your browser to the public service router.project-osrm.org (OSRM, Mapbox infrastructure). With this fallback, your IP address is transmitted to the OSRM server. Project OSRM.

7.3 Location request

For certain functions (GPS centring of the map, petrol station search, route start), ViaCamp requests your position via the browser API navigator.geolocation. This only takes place after explicit browser permission. The position is used only on the client side, cached in sessionStorage with a validity of 5 minutes and not transmitted to our server.

7.4 Place search (geocoding)

If you enter a place name in the pitch search (e.g. “Krün”) and there is no direct match in our data, we determine the coordinates of the place via the Nominatim service of the OpenStreetMap Foundation (UK) in order to show you the nearest pitches. The request is made server-side by our server — your IP address is not transmitted to Nominatim, only the search term entered. To spare the service, results are cached in our working memory for up to 7 days. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in a functioning place search). An adequacy decision of the EU Commission exists for the United Kingdom (Art. 45 GDPR).

7.5 Measuring tools (compass, spirit level, ruler, metal detector)

The measuring tools under Profile → Tools use the motion and orientation sensors of your device and, in the ViaCamp app, additionally the magnetometer and the display density. The readings are processed only on your device and are not transmitted to our server. Your browser's localStorage holds only calibration values (the spirit level's zero point, the ruler's scale, the metal detector's sensitivity), the ruler's unit and the chosen compass target (name and coordinates of a saved place); sessionStorage remembers until the tab is closed whether you declined access to the sensors; you can delete them at any time via your browser data. The compass direction to a saved place needs your location and requests it only after your explicit confirmation (see 7.3).

8. POI, weather and petrol station data

8.1 POI (points of interest)

Data on drinking water, toilet, supermarket and other POI locations is obtained server-side by our server via the Overpass API (overpass-api.de, Germany) and a fallback instance (overpass.kumi.systems). Your IP address is not transmitted to Overpass in the process. The results are cached in our PostgreSQL database for 24 hours.

8.2 Weather

Weather data is obtained from OpenWeather Ltd (UK). The request is made exclusively server-side by a time-controlled cron job. Your IP address is not transmitted to OpenWeather. OpenWeather Privacy Policy.

Weather areas on the map: If you switch on the temperature map or precipitation on the map, your browser loads the map tiles from our server (via.camp). Our server fetches the tiles for the relevant map section from OpenWeather and caches them for up to 20 minutes. Only the tile coordinates (zoom level and map section) are sent to OpenWeather, neither your IP address nor any other data about you. We store your setting (layers on or off) in your browser and, if you are signed in, in your user account. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is showing current weather information for trip planning.

8.3 Petrol stations

Petrol station information is loaded via the same server-side Overpass connection and cached for 90 days. Name, brand, opening hours and fuel types come exclusively from OpenStreetMap (ODbL licence).

8.4 Satellite images

If you switch on the satellite view in the app or look at the "From above" section of a site, your browser loads the image tiles from our server (via.camp). Our server fetches them from Esri Inc. (Redlands, USA; ArcGIS Location Platform, "World Imagery" image service and place names) and caches them for up to 24 hours. Only the tile coordinates (zoom level and map section) and our access key are sent to Esri, neither your IP address nor any other data about you. We store your choice between map and satellite only in your browser. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is letting you see what a site looks like from above before you travel. Esri privacy.

9. User-generated content and uploads

9.1 Reviews and photos

You can review pitches and upload photos. This content becomes publicly visible together with your display name. Uploaded photos are stored in /uploads/spots/ on our server. Legal basis: Art. 6(1)(b) GDPR.

Please observe the Terms of Use, in particular regarding third-party rights and prohibited content.

“Helpful” votes: Signed-in users can mark other people’s photos and reviews as helpful. For this we store which account marked which content and when. Only the number is publicly visible; authors see in their statistics how often their content was marked, but not by whom. To protect against manipulation, moderators see the accounts involved in conspicuous patterns (such as many votes from newly created accounts). From the views of a place by signed-in users we calculate how many people have seen a piece of content; this determines the order. Legal basis: Art. 6(1)(b) GDPR (contract of use) and Art. 6(1)(f) GDPR (legitimate interest in a fair order free of manipulation). Storage period: until you withdraw the vote or the content or your account is deleted.

9.2 Profile picture

An optional profile picture is scaled server-side to 256×256 pixels on upload, converted to WebP and stored in /uploads/avatars/. Old avatars are deleted when overwritten.

9.3 Pitch suggestions

You can suggest new pitches or edit existing ones. Suggestions are reviewed by us before publication. In doing so, we process the data you provide (name, coordinates, description, photos) as well as your user ID for attribution.

9.4 Trips and checklists

Trips (routes, pitch lists) and checklists you create are stored in our database and by default are visible only to you. If you share a trip via a public share link, this trip can be accessed without login by anyone who has the link.

10. Transactional emails and contact

10.1 Login emails (magic link)

Magic link emails are sent exclusively transactionally via an external SMTP server. The SMTP provider is currently Namecheap Inc. (USA) — delivery takes place via premium269-4.web-hosting.com from our @celox.io mailbox. When sending, your email address and the one-time token are transmitted to the SMTP server. Legal basis: Art. 6(1)(b) GDPR (performance of a contract).

For the transfer of data to the USA, we rely on the EU-U.S. Data Privacy Framework and standard contractual clauses pursuant to Art. 46 GDPR.

10.2 Manual contact

If you contact us by email, we process the data contained in your message (name, sender address, content) to handle your enquiry. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in responding) or Art. 6(1)(b) GDPR where there is a contractual connection.

10.3 Contact form for operators

On the operator page (partner.via.camp) you can write to us using a contact form. We process the information you enter: name, email address, your message and – optionally – the name of your site, your phone number and the topic. The form is not stored in a database: the information is sent as an email to martin@via.camp (delivery as described in 10.1), and replies go directly to your address. To prevent abuse, your IP address is briefly counted in memory (at most five enquiries per hour) and not stored.

Legal basis: Art. 6(1)(b) GDPR (pre-contractual measures at your request) or (f) (legitimate interest in answering). Retention: the email is deleted once your enquiry has been dealt with and no retention obligation applies; if it leads to an order, the statutory periods apply.

10.4 Direct approach to campsite operators (B2B)

We occasionally contact operators of campsites whose site is listed in our public directory in order to offer them a highlighted listing on ViaCamp (Featured) and – separately – the creation or modernisation of their website via celox.io. In both cases the controller is Martin Pfeffer (see section 1).

Data processed: business contact name, business email address and phone number, name, location and website of the site, a technical analysis of the publicly accessible website (availability, encrypted connection and validity of the security certificate, display on smartphones, loading time according to Google PageSpeed Insights and Google's Chrome UX Report – only the website address is transmitted to Google for this), and our notes on the course of contact (date and content of messages sent, replies, call notes, status). The contact data originates from publicly accessible sources or from you, if you contacted us.

Sources of contact data: (1) the publicly accessible website of the site – our crawler (identifier “ViaCampBot”, robots.txt is respected) reads the home page, legal notice and contact page and records where each contact was found; whether the domain of an email address can receive mail at all is checked via public DNS (without sending a test email); (2) OpenStreetMap (ODbL); (3) the open data of the Overture Maps Foundation (Places, licences CDLA-Permissive-2.0, Apache-2.0 or CC0; sources include Meta, Microsoft, Foursquare, BrightQuery, AllThePlaces) – from this we only take missing phone numbers, websites and email addresses, and whether a site is reported as closed. Found contacts are only taken over after we have checked them. A contact person is only taken from the legal notice. Suppressed addresses (see objection) are not stored.

Google Places: In individual cases we look up the public details of a site on Google Maps (rating, number of reviews, status, phone, website, opening hours). For this we transmit the name, location and coordinates of the site to Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (Google LLC, USA; EU-US Data Privacy Framework). We only store Google's identifier of the place (place ID), not the details themselves. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in up-to-date and correct operator data).

Legal basis: Art. 6(1)(f) GDPR (legitimate interest in initiating business relationships with companies whose activity is directly related to our offer). Each message is checked individually and sent manually; there is no automated bulk sending. Without a reply we will not email you again.

Replies and delivery failures: Replies to our messages, out-of-office notices and notifications about undeliverable emails are automatically assigned to the respective contact and stored there so that we can respond promptly and take objections and invalid addresses into account immediately (Art. 6(1)(f) GDPR). Messages that cannot be assigned to a contact are not stored. If you tell us in a reply that you do not want any further messages, this is treated as an unsubscription.

AI-assisted analysis: To take over contact details and information about the site (e.g. contact person, season, number of pitches, facilities) from the publicly accessible website of the site, we occasionally have the text of the home page and the legal notice analysed by an AI model. The provider is Anthropic PBC, 548 Market Street, San Francisco, CA 94104, USA. Only this public page text and the name and location of the site are transmitted; guest data is not transmitted. The results are suggestions with a verbatim quote from the website, which we check manually before taking them over. An AI model may also suggest a short personal opening paragraph for a message; this, too, is checked manually before sending. No automated decision within the meaning of Art. 22 GDPR takes place. Anthropic processes the data as a processor under its Data Processing Addendum, which forms part of its Commercial Terms; training its models on this data is contractually excluded there. The transfer to the USA is based on the European Commission's standard contractual clauses included in the Data Processing Addendum (Module Two, Art. 46(2)(c) GDPR). The legal basis is Art. 6(1)(f) GDPR (legitimate interest in maintaining operator data correctly and efficiently).

Objection: You can object to the processing at any time (Art. 21 GDPR) – via the unsubscribe link at the end of every message, by replying “keine Werbung” (“no advertising”) or by writing to martin@via.camp. We will then no longer contact you and will delete your contact data from the outreach database. We only keep a suppression record (email address, date, reason) so that you are not contacted again; this record serves solely to respect your objection.

Storage period: The data is deleted or anonymised as soon as (a) you object (then only the suppression record remains), (b) you decline an offer – after 12 months –, (c) after 24 months without a response or (d) the site is removed from our directory. Found contacts for sites we do not create a contact for are deleted after 12 months. If a contract is concluded, we transfer your contact details, our previous correspondence and our offers to our own customer management system (operated by Martin Pfeffer on the same server in the EU); the statutory retention periods apply there, and the acquisition data at ViaCamp is no longer deleted under periods (b) and (c).

10.5 Embedded images from operator websites

To make pitches easier to identify visually, for some of the listed sites we embed images that we collect automatically via structured data (Open Graph og:image, Twitter Cards twitter:image, schema.org image property of Campground/LodgingBusiness) from the publicly accessible websites of the operators and mirror on our servers. These tags are explicitly intended for external platforms to display the respective preview image when linking.

The source of each image can be viewed in the spot detail modal in the detail view of each image as “Quelle: …” (“Source: …”).

Objection / image removal: If you, as an operator, photographer or rights holder, wish an image displayed by us to be removed, there are two ways:

1. Directly in the app: Open the image in the respective spot detail and click the “Report” button. The image is hidden immediately.
2. By email: Informally to martin@via.camp with reference to the spot in question (URL or spot ID). We will then remove the image manually, as a rule within 48 hours, and in any case without undue delay.

If an operator takes over the spot via our operator verification procedure (spot claim), the images previously embedded from their website are automatically deleted from our servers. The operator can then upload their own images.

Legal basis: Art. 6(1)(f) GDPR (legitimate interest in a meaningful presentation of listed sites on the basis of data/tags publicly provided for precisely this purpose). In the event of a conflict with overriding rights of third parties, removal takes place without undue delay; claims for damages are to be mitigated or avoided by the low-threshold notice-and-takedown procedure.

10.6 Feedback form in the app

You can write to us via “Feedback” in the profile of the app. We process the type of message you choose (e.g. bug, request, wrong place data), your message, optionally an email address for questions and – if you are signed in – the link to your account (name, email address). We store the message in our database and additionally receive a notification by email to martin@via.camp (sent as described in 10.1). Your IP address, browser identifier and the page you are on are not transmitted; to prevent abuse, the IP address is only counted briefly in memory (at most five messages per hour) and not stored.

Technical information (optional): Only if you switch on “Include technical info” – it is off by default – the following is also transmitted: app version and build time, browser and operating system, screen and window size, language, the current page (without access keys and similar parameters in the address) and up to 20 of the most recent error messages from the app in shortened form. Under “What is sent?” you can see exactly what is included before sending. Your location, cookies or session data and your email address are not transmitted; we remove address parameters and email addresses from error messages. Until then the app keeps error messages only in your browser’s memory; they are discarded when you close the page.

Legal basis: Art. 6(1)(f) GDPR (legitimate interest in handling feedback and fixing errors). We transmit the technical information on the basis of your consent given by switching it on (Art. 6(1)(a) GDPR, § 25(1) TDDDG, the German Telecommunications Digital Services Data Protection Act); you can withdraw it at any time with effect for the future by email. Retention: technical information 90 days, the message itself 12 months; they are then deleted automatically.

10.7 Payments via Stripe (Featured)

If operators book “Featured” in the site management, payment is processed by Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland. We transmit to Stripe the name and email address of your account as well as details of the booking (number of the site, chosen period). You enter payment data such as card number or IBAN directly with Stripe; we do not receive it. From Stripe we receive the customer number, subscription and payment status and the end of the term. You manage invoices, payment method and cancellation in Stripe’s customer portal.

Stripe processes payment data to carry out the payment and to fulfil its own legal obligations (such as fraud and money-laundering prevention), in part as an independent controller; this may involve a transfer to Stripe, Inc. in the USA (EU-US Data Privacy Framework, supplemented by standard contractual clauses). Stripe’s privacy notice: stripe.com/privacy.

To track payments, we query Stripe for the status of your invoices (paid, open, due date) and store it with the booking. If a payment remains outstanding, we send payment reminders to your account email address (Terms § 5 (6)); we store when they were sent with the booking.

Legal basis: Art. 6(1)(b) GDPR (contract), for invoices Art. 6(1)(c) GDPR (statutory retention obligation). Storage period: booking and invoice data 10 years (§ 147 AO, § 257 HGB); identifiers of processed payment events 90 days.

11. Push notifications

You can subscribe to push notifications only after giving explicit consent via a browser prompt. Technically, we use the Web Push standard with VAPID keys. Delivery takes place via the respective push service of your browser (Google for Chrome, Mozilla for Firefox, Apple for Safari). The push endpoint and the public key material are linked to your account in our database.

You can revoke the notifications at any time via the browser settings or the unsubscribe button. Legal basis: Art. 6(1)(a) GDPR (consent).

12. Third-party providers and fonts

12.1 Google Fonts

We load the fonts Inter and Fraunces from fonts.googleapis.com and fonts.gstatic.com (Google Ireland Limited, Google LLC, USA). When our pages are accessed, your IP address is transmitted to Google; according to Google, no cookies are set and no log data is stored permanently. Google Fonts Privacy FAQ.

Legal basis: Art. 6(1)(f) GDPR (legitimate interest in uniform typography and fast delivery). You can block the loading via browser settings (e.g. uBlock Origin).

12.2 CDN libraries (unpkg.com)

The following open-source libraries are loaded from unpkg.com (operated by Cloudflare Inc., USA): Leaflet, Leaflet.markercluster. When they are loaded, your IP address is transmitted to unpkg/Cloudflare. Legal basis: Art. 6(1)(f) GDPR (performance and uniform sourcing of the JavaScript modules).

12.3 No other social media integrations

No social media plugins (Facebook, Twitter, Instagram, LinkedIn, TikTok) are loaded. There are no embedded YouTube videos, no external tracking pixels, no advertisements.

13. Audience measurement (Umami, no cookies)

To understand which pages are used, we use Umami — self-hosted open-source software on a server in Frankfurt am Main (analytics.celox.io, infrastructure as described in section 3). No cookies are set, and the data is not passed on to third parties or transferred to third countries.

When a page is accessed, the following is processed:

• the page visited and the referring page (referrer)
• browser, operating system, device type, screen size, language setting
• country (derived from the IP address; Umami does not store the IP address itself)

Visits are grouped by a non-reversible hash value; we cannot identify you personally. We only evaluate the data in aggregated form (e.g. page views per day).

Legal basis: Art. 6(1)(f) GDPR. Our legitimate interest is to improve the service based on actual use. You can object to the processing at any time (section 16), for example by blocking scripts from analytics.celox.io in your browser or with a content blocker — the app then works as before.

14. Data transfers to third countries

Your personal data may be transferred to third countries (outside the EU/EEA) in the case of:

• Google OAuth, Google Fonts → USA (Google LLC)
• unpkg.com libraries → USA (Cloudflare)
• SMTP sending → USA (Namecheap)
• OSRM fallback → globally distributed infrastructure

The basis is the adequacy decision of the EU Commission under the EU-U.S. Data Privacy Framework or standard contractual clauses pursuant to Art. 46(2)(c) GDPR.

15. Storage period

16. Your rights

Under the GDPR you have the following rights:

• Access to your processed data (Art. 15 GDPR)
• Rectification of inaccurate data (Art. 16 GDPR)
• Erasure (“right to be forgotten”, Art. 17 GDPR)
• Restriction of processing (Art. 18 GDPR)
• Data portability in a structured format (Art. 20 GDPR)
• Objection to processing (Art. 21 GDPR) — in particular to processing based on Art. 6(1)(f) GDPR
• Withdrawal of consent given (Art. 7(3) GDPR) — at any time with effect for the future

An informal message to martin@via.camp is sufficient to exercise your rights. Requests are handled free of charge within one month (Art. 12(3) GDPR).

17. Right to lodge a complaint

Without prejudice to any other administrative or judicial remedy, you have the right to lodge a complaint with a supervisory authority (Art. 77 GDPR). The authority responsible for us is:

Berliner Beauftragte für Datenschutz und Informationsfreiheit (Berlin Commissioner for Data Protection and Freedom of Information)
Friedrichstr. 219, 10969 Berlin
Phone: +49 30 13889-0
www.datenschutz-berlin.de

18. Automated decision-making

No decision based solely on automated processing, including profiling (Art. 22 GDPR), takes place.

19. Data security

We use technical and organisational measures in line with the state of the art:

• TLS 1.2/1.3 encryption for all connections (Let’s Encrypt certificates)
• Password storage exclusively as a salted scrypt hash
• Rate limiting to defend against brute-force and DoS attacks
• Prepared statements in the PostgreSQL database against SQL injection
• Role system with privilege separation (free / operator / premium / admin)
• Regular security updates of the server operating system
• Access and access-rights control for the database (firewall, port binding to localhost)

20. Changes to this privacy policy

We reserve the right to adapt this privacy policy to changes in the legal situation or in the event of changes to the service. The current version in each case is available at via.camp/legal/datenschutz.html (binding German version; English translation at via.camp/legal/en/privacy.html). In the event of material changes, we will inform registered users by email or in-app notification.

Haut de page