Privacy Policy
1. Scope
The Privacy Policy is applicable to personal data of subscribers and visitors of the website operated by Classic Driver (Schweiz) AG, Baarerstrasse 22, 6300 Zug, Schweiz („Classic Driver“).
2. General
Classic Driver complies with all the legal provisions of data protection. All protected personal data collected during registration or generated during the use of our service that are subject to the protections of the Swiss Data Protection Act will be collected, stored and used exclusively for the purpose of contract fulfillment, market research as well as billing purposes to the extent that the subscriber has not given express consent to a use going beyond this, or if the Data Protection Act allows it.
3. Types of Data Being Processed
Classic Driver processes the subscriber’s contact data (e.g., name, address), data about services obtained (e.g., when a certain ad was published and which dealer’s package was booked), payment data, data of advertisements (e.g., texts, pictures), as well as surfing data (e.g., which browser is used by a visitor of the website and which elements of the website he used).
4. Processing of Data by Third Parties and Outside of Switzerland
Classic Driver engages third-party service providers to operate its website and deliver services to subscribers and visitors. These providers may receive and process personal data on behalf of Classic Driver, or as independent controllers in their own right. Personal data may be transferred to and processed in countries outside Switzerland, including countries within the European Economic Area (EEA) and the United States of America. Classic Driver ensures that appropriate contractual safeguards are in place for such transfers in accordance with the Swiss Federal Act on Data Protection (FADP/nDSG).
Each entry below identifies the provider, its role, the data it may receive, and a link to its privacy policy. Providers acting as a Data Processor handle personal data only on Classic Driver's instructions and for no other purpose. Providers acting as an Independent Controller operate under their own privacy policy, which governs how they handle data.
4.1 Hosting and Infrastructure
Nine Internet Solutions AG (Switzerland) — Data Processor
Primary website hosting, database, and web server infrastructure (Drupal CMS, MySQL, Apache Solr). Stores and processes all data held on the Classic Driver platform, including subscriber account data, listing content, uploaded images and files, and server access logs.
Privacy policy: https://nine.ch/privacy-policy/
Cloudflare, Inc. (USA — global edge network) — Data Processor
Content Delivery Network (CDN), DNS management, DDoS protection, and image optimisation. All website traffic is routed through Cloudflare's global network, which automatically serves each visitor from the nearest data centre for the fastest possible experience. Processes visitor IP addresses, HTTP request headers, browser information, and pages visited.
Privacy policy: https://www.cloudflare.com/privacypolicy/
Vercel Inc. (USA) — Data Processor
Hosts the Classic Driver member dashboard at users.classicdriver.com (Next.js application). Processes user account data, authentication tokens, and dashboard interaction data for logged-in members who access this subdomain.
Privacy policy: https://vercel.com/legal/privacy-policy
Amazon Web Services, Inc. (AWS) (EU — Frankfurt, Germany) — Data Processor
Cloud data warehousing via Amazon Redshift, hosted in the AWS EU (Frankfurt) region. Receives pseudonymised browsing and behavioural data routed from the analytics middleware described in Section 5. Classic Driver uses the EU (Frankfurt) region to keep data stored and processed within the European Union.
Privacy policy: https://aws.amazon.com/privacy/
Google LLC (Firebase / Cloud Storage) (USA) — Data Processor
Firebase is used to generate secure authentication tokens for sellers who use listing import or inventory synchronisation features. Google Cloud Storage provides file storage. Both are hosted in Google's US-based infrastructure and process only the seller authentication tokens and associated account identifiers needed for those features.
Privacy policy: https://policies.google.com/privacy
Google LLC (BigQuery) (EU) — Data Processor
Cloud data warehousing hosted in Google's EU region. Receives analytics and behavioural data forwarded via Segment (see Section 5.1). Processes pseudonymous user identifiers and browsing interaction data.
Privacy policy: https://policies.google.com/privacy
4.2 Payment Processing
When subscribers make payments through the Classic Driver website (e.g., for listing fees or service packages), the following payment processors receive personal data necessary to authorise and settle the transaction, including the payer's name, email address, billing address, credit or debit card details (where applicable), and transaction amount.
PayPal (Europe) S.à r.l. et Cie, S.C.A. (Luxembourg) — Independent Controller
When a subscriber selects PayPal as payment method they are redirected to PayPal's own platform to complete the transaction. PayPal acts as an independent controller for that processing under its own privacy policy.
Privacy policy: https://www.paypal.com/webapps/mpp/ua/privacy-full
Worldline / SIX Payment Services AG (Saferpay) (Switzerland) — Data Processor
Credit and debit card payment processing via the Saferpay gateway. Card details, payer name, billing address, and transaction amount are transmitted to Saferpay's secure servers for authorisation. Worldline may also process data as an independent controller to the extent required by applicable payment regulations and fraud prevention obligations. [NEEDS REVIEW — confirm whether a current Data Processing Agreement is in place with Worldline/Saferpay.]
Privacy policy: https://worldline.com/en/compliancy/privacy
4.3 Email and Newsletter Services
Campaign Monitor (CM Group / Marigold) (USA / Australia) — Data Processor
Transactional email delivery and newsletter distribution. Used for system-generated emails (e.g., registration confirmations, account notifications, subscription and billing messages) as well as newsletter campaigns. Receives and processes recipient names and email addresses. Also collects email engagement data on Classic Driver's behalf, including whether an email was opened, which links were clicked, and the approximate location derived from the IP address at time of opening.
Privacy policy: https://www.campaignmonitor.com/policies/
4.4 Link Tracking
Rebrandly (Radiate Capital Ltd.) (Ireland / USA) — Data Processor
URL shortening and click tracking used in email newsletters and selected website content. When a visitor follows a Rebrandly link, Rebrandly records the click on Classic Driver's behalf — helping us understand which content is most useful — and may process technical data such as the visitor's IP address, browser information, and click timestamp to do so.
Privacy policy: https://www.rebrandly.com/privacy-policy
4.5 Advertising
adverserve digital advertising services GmbH (Mediabox) (Austria) — Independent Controller
Display banner advertisement serving on the Classic Driver website. adverserve loads its own JavaScript code on pages where advertisements appear and operates as an independent controller for that advertising. This may include processing the visitor's IP address, browser and device information, pages visited, and advertisement interaction data for ad targeting purposes. Full details are available in adverserve's privacy policy.
Privacy policy: https://www.adverserve.com/en/data-protection/
4.6 Social Media Content Integration
Curator Ltd. (Curator.io) — Independent Controller
Social media content aggregation widget embedded on the Classic Driver website to display curated social media content. When a page containing the widget is loaded, Curator.io's own JavaScript runs in the visitor's browser and connects to Curator.io's servers. Curator.io's own privacy policy governs how they handle the data this generates, which may include the visitor's IP address, browser and device information, and the URL of the page visited. The underlying social media platforms whose content is displayed (e.g., YouTube, Instagram) operate under their own privacy policies.
Privacy policy: https://curator.io/privacy-policy
4.7 Affiliate Shop
Shopify Inc. (Canada — EU data residency) — Data Processor
Provides the e-commerce platform powering the Classic Driver shop at shop.classicdriver.com. This Privacy Policy covers data processing at shop.classicdriver.com. Customer data is stored in Shopify's European infrastructure. When visitors access the shop, Shopify processes browsing data on Classic Driver's behalf, and — in the event of a purchase — the buyer's name, shipping and billing addresses, email address, payment information, and order details. Shopify may also act as an independent controller to the extent it processes data for its own platform purposes (e.g., fraud prevention, platform analytics).
Privacy policy: https://www.shopify.com/legal/privacy
4.8 Security Services
Google LLC (Google reCAPTCHA) (USA) — Independent Controller
Protects website forms (e.g., registration, contact, and enquiry forms) so that genuine visitors can submit them without interruption. To verify a submission is from a real person, Google analyses technical signals such as the visitor's IP address, browser and device information, and interaction patterns. Google processes these signals under its own privacy policy.
Privacy policy: https://policies.google.com/privacy
4.9 System Monitoring
New Relic, Inc. (USA) — Data Processor
Server-side application performance monitoring and error tracking. New Relic monitors server response times, error rates, and application health on Classic Driver's behalf to help keep the website fast and reliable. Only server-side data is processed — no visitor personal data is transmitted to New Relic.
Privacy policy: https://newrelic.com/termsandconditions/services-notices
4.10 Internal Communication
Microsoft Corporation (Microsoft 365) (USA) — Data Processor
Classic Driver uses Microsoft 365 for internal staff email and business communication. Emails sent to or from Classic Driver via staff mailboxes are processed and stored in Microsoft's infrastructure. Microsoft is headquartered in the USA.
Privacy policy: https://privacy.microsoft.com/privacystatement
4.11 Development and Test Hosting
Akamai Technologies, Inc. (Linode / Akamai Cloud) (USA) — Data Processor
Classic Driver's development and test server environments are hosted on Linode (now part of Akamai Technologies). These environments may contain anonymised or pseudonymised copies of platform data used for testing purposes. Linode/Akamai has no independent access to the data stored within these servers.
Privacy policy: https://www.linode.com/legal-privacy/
4.12 Customer Relationship Management
Pipedrive Inc. (USA / Estonia) — Data Processor
Classic Driver uses Pipedrive as a web-based sales CRM to manage business relationships with commercial partners, dealers, and advertisers. Pipedrive may store contact data for business contacts and commercial subscribers. Pipedrive is headquartered in the USA and Estonia.
Privacy policy: https://www.pipedrive.com/en/privacy
4.13 Software Development Tools
Atlassian Inc. (USA / Australia) — Data Processor
Classic Driver uses various Atlassian products (including Jira, Confluence, and Bitbucket) for software development, project management, and documentation. These tools are used exclusively by Classic Driver staff and contractors. Atlassian is headquartered in the USA and Australia.
Privacy policy: https://www.atlassian.com/legal/privacy-policy
5. Analytic and Tracking Tools
Classic Driver uses analytics services to understand how visitors use its website, measure the effectiveness of content and campaigns, and continuously improve the experience for everyone. Where possible, Classic Driver configures these services to minimise the personal data collected — for example, applying IP address anonymisation in Google Analytics. Some of these services operate servers outside Switzerland, including in the United States.
5.1 Segment (Twilio Inc.) (USA) — Data Processor
Analytics data middleware. Segment is the primary data collection layer on the Classic Driver website. It collects browsing and interaction data — including pages visited, user actions (e.g., clicking on listings, submitting enquiry forms, adding items to wishlists), device and browser information, and pseudonymous user identifiers — and routes this data to the downstream analytics destinations listed below (Google Analytics, AWS Redshift, Google BigQuery).
Privacy policy: https://www.twilio.com/en-us/legal/privacy
5.2 Google Analytics (Google LLC) (USA) — Joint Controller
Web analytics service. Receives browsing data via Segment (see 5.1 above) and through direct integration for enhanced e-commerce tracking. Google Analytics processes data about pages visited, interactions with listings (impressions, clicks, purchases), session duration, referral sources, and approximate geolocation derived from the visitor's IP address. Classic Driver applies IP anonymisation so that IP addresses are truncated before storage. As Google also uses aggregated analytics data to improve its own services, Google is considered a joint controller for certain aspects of this processing.
Opt-out: Visitors can prevent Google Analytics from collecting their data by installing the browser add-on available at https://tools.google.com/dlpage/gaoptout.
Privacy policy: https://policies.google.com/privacy
5.3 Google Tag Manager (Google LLC) (USA) — Data Processor
Tag management system that controls the loading and configuration of tracking scripts on the Classic Driver website. Google Tag Manager itself does not set cookies or collect personal data independently; it facilitates the execution of other tracking tools such as Google Analytics. When a page is loaded, the visitor's browser connects to Google Tag Manager's servers, which may process the page URL and basic request metadata.
Privacy policy: https://policies.google.com/privacy
5.4 Analytics Data Destinations
In addition to Google Analytics, browsing and interaction data collected via Segment (see 5.1) is transmitted to the following data warehousing services for internal reporting and analysis:
• Amazon Redshift (AWS) — EU (Frankfurt). See Section 4.1.
• Google BigQuery — EU. See Section 4.1.
Data sent to these warehouses via Segment may include pseudonymous Segment user identifiers and, where a visitor is a logged-in subscriber, associated account identifiers. Classic Driver uses Segment's built-in privacy tooling to fulfil data subject deletion requests under the FADP and GDPR, which propagates deletion through to connected destinations including Redshift and BigQuery.
6. Embedded Video Content
Classic Driver embeds YouTube videos on its website. YouTube is operated by Google LLC (USA). Videos are displayed via the Curator.io widget described in Section 4.6. When a page containing the video widget is loaded, the Curator.io JavaScript connects to YouTube’s servers to retrieve video thumbnails. When a visitor plays a video, an iframe connection to youtube.com is established and YouTube may process the visitor’s IP address, browser and device information, and — if the visitor is logged into a Google or YouTube account at the time — associate the interaction with that account.
Classic Driver uses standard YouTube embeds so that videos played on the site may appear in the visitor’s YouTube viewing history and benefit from personalised recommendations. YouTube may set cookies in the visitor’s browser for personalisation and viewing history purposes. YouTube’s data handling is governed by Google’s privacy policy: https://policies.google.com/privacy
7. Cookies
Classic Driver uses cookies. Cookies are small data files stored in your browser that allow the website to recognise your browser on return visits and remember information between page loads. Classic Driver uses cookies for the following purposes:
• User sessions: to keep you logged in during your visit and maintain your account state (SESS… / SSESS… cookies).
• Preferences: to remember your selected currency and mileage unit (km/miles) between visits (Drupal_visitor_currency, Drupal_visitor_mileage_unit).
• Navigation: to return you to the correct page after logging in (Drupal_visitor_path and related cookies, deleted immediately after use).
• JavaScript detection: a small cookie (has_js) is set to confirm that JavaScript is available in your browser.
Sellers managing listings will also encounter cookies that store UI preferences within the listing editor (e.g., image upload view settings). These are functional only and contain no personal data.
Third-party providers integrated on this website — such as those described in Sections 4 and 5 — may also set their own cookies when their content or scripts are loaded. These cookies are managed directly by each provider; please refer to the respective provider's privacy policy for details on how to control them.
You can delete cookies at any time in your browser settings and prevent new cookies from being stored. However, disabling cookies may impair the functionality of the Classic Driver website, including the ability to stay logged in.
8. Financial Standing
Classic Driver may process data about the financial standing of its subscribers if needed.
9. Data Security and Back-Up
Classic Driver will take the financially reasonable, technically possible and proportional measures to secure data and information that the subscriber transfers to the website (e.g., texts, pictures). Classic Driver, however, accepts no liability of any kind for the security of the subscriber’s data. It is the subscribers’ sole responsibility to store a current back-up copy of the data transferred and store it independently from the website.