Skip to content
CarCrew
HomeAppContactGet the app
HomeAppContactDownload on the App Store

App privacy

CarCrew App Privacy Policy

This Privacy Policy explains how personal data is processed when you use the CarCrew mobile application for iOS, including optional cloud, sharing, subscription and CrewBonus features.

1. Controller

The controller responsible for processing personal data in the CarCrew app is:

Tim Sessinghaus
Sunderweg 26
58300 Wetter (Ruhr)
Germany

Email: tim@schneider-sessinghaus.de
Phone: +49 152 29450820
Email for privacy, support, the app and the website: info@carcrew.app
Instagram: official_carcrew.app

2. Scope

This Privacy Policy applies to the CarCrew iOS app. It describes which personal data we process, why we process it, the legal bases for processing, the recipients of data and your rights under the General Data Protection Regulation (GDPR).

3. Categories of data processed by the app

The data processed depends on the features you use, the permissions you grant and your subscription plan. It may include:

  • Account data: name or display name, email address, authentication provider, internal user ID and account settings
  • Vehicle data: vehicle name, make, model, model year, registration number if entered, Bluetooth name if entered, odometer readings, technical parameters and cost assumptions such as consumption, insurance, vehicle tax, financing and estimated value
  • Trip data: start and stop times, route coordinates, addresses, distance, duration, speed and route analysis, trip category, cost per trip, and driver information in shared fleets
  • Location data: location during trip recording and, if enabled, an optional precise or approximate last-stop location for authorised fleet members
  • Expense and receipt data: expense details, amounts, categories, dates, receipt images and text recognised using on-device OCR
  • Shared-fleet data: fleet memberships, roles, permissions, invitations, reservations, settlements, outstanding amounts, payment statuses and fleet events
  • Subscription and CrewBonus data: subscription product and status, referral code, inviter and invited-user IDs, referral and reward status, offer identifiers and Apple transaction evidence as described in Section 12
  • Communication data: information that you send to us by email or through support channels
  • Technical data: device and app information, push token, app instance and attestation identifiers, diagnostic data, performance information and optional usage analytics

4. Local storage on your device

Vehicles, trips, expenses, settings and other app data may be stored locally on your device so that CarCrew can function and remain available offline. Local data is subject to the security and backup settings of your device and Apple account.

Purpose: providing the app and offline features.
Legal basis: Art. 6(1)(b) GDPR and, where applicable, Art. 6(1)(f) GDPR based on our legitimate interest in providing a reliable app.

5. Account, sign-in and user management

Depending on the selected sign-in method, CarCrew supports:

  • Anonymous sign-in using a technical user ID
  • Email address and password
  • Sign in with Apple
  • Sign in with Google

Firebase Authentication processes the identifiers and authentication information required for your chosen method. If you use Sign in with Apple or Google, the relevant provider processes the sign-in request and may provide CarCrew with an account identifier, email address, name and other profile information made available under your provider settings. CarCrew does not receive your Apple or Google password.

Purpose: authenticating you, managing your account, providing cloud synchronisation and associating shared data and subscriptions with the correct account.
Legal basis: Art. 6(1)(b) GDPR. The use of Apple or Google as a sign-in provider is your choice.

6. Cloud synchronisation, fleet sharing and settlements

If you use cloud or sharing features, data is processed in Firebase and Cloud Firestore. Depending on your plan and role, this may include:

  • User profile and subscription-tier information
  • Fleet memberships, roles, permissions, invitations and reservations
  • Vehicle, trip, expense, cost and reminder data
  • Driver assignments, monthly totals, member rates, settlement values and payment statuses
  • Fleet events, notifications and records relating to members who leave a fleet

Owners and authorised members can see information according to their role and the permissions configured for the relevant fleet.

Purpose: synchronisation between devices, shared vehicle use, member management, settlements and displaying data to authorised fleet members.
Legal basis: Art. 6(1)(b) GDPR.

7. Location data and encryption

7.1 Trip recording and route analysis

When you record a trip, CarCrew processes location data to calculate the route, distance, time, addresses and trip statistics. Depending on your settings, location access may also be used for automatic trip detection. You can change the app's location permission in iOS at any time. Disabling location access may prevent trip-recording and related features from working.

Purpose: trip recording, route and cost calculation, trip analysis and the display of start, stop and route information.
Legal basis: Art. 6(1)(b) GDPR and, where iOS permission is required, your device-level choice.

7.2 Optional last-stop sharing

If enabled, the most recent vehicle location may be shared with authorised fleet members. You can select precise, approximate or disabled sharing. In approximate mode, coordinates are made less precise before sharing. When sharing is disabled, no new last-stop location is stored and existing shared-location data is deleted where the feature provides for this.

The optional shared last-stop coordinates are end-to-end encrypted by CarCrew. This statement does not apply to all data stored in the cloud: account, vehicle, trip, cost, subscription and CrewBonus data is protected through access controls, transport encryption and the security measures of the relevant service providers, but is not described as end-to-end encrypted.

Purpose: optional convenience and status features for shared vehicles.
Legal basis: Art. 6(1)(b) GDPR and, where applicable, Art. 6(1)(a) GDPR based on your optional choice.

8. Bluetooth, CarPlay and automatic trip detection

CarCrew may use Bluetooth, car audio and CarPlay connection states to start or stop trips automatically or associate a trip with a vehicle. This may involve a stored Bluetooth name and the technical status of a connection. CarCrew does not access the content of your calls, messages or audio.

Purpose: automatic trip detection and vehicle assignment.
Legal basis: Art. 6(1)(b) GDPR.

9. Camera, photos and receipt scanning

If you scan a receipt, the app uses the camera and on-device text recognition to help create an expense. Receipt images and extracted information are stored as part of the relevant expense according to your local and cloud settings. If you add photos to Trip Stories or exports, those photos are selected and shared by you through the destination you choose.

Purpose: recording expenses and creating content selected by the user.
Legal basis: Art. 6(1)(b) GDPR.

10. WeatherKit and weather-based trip analysis

CarCrew may use Apple WeatherKit to request current weather conditions for locations along a recorded trip. For this request, the coordinates required to obtain local weather information are transmitted to Apple. According to Apple, WeatherKit location information is used only to provide weather forecasts, is not associated with personally identifiable information and is not tracked between requests.

CarCrew may derive and store a compact weather summary such as temperature, pressure, humidity and wind values and use it to estimate weather-related consumption effects. If cloud trip upload is enabled, these derived weather values may be synchronised with the associated trip. CarCrew does not store an additional raw location history solely for WeatherKit.

Purpose: weather-based consumption and trip analysis.
Legal basis: Art. 6(1)(b) GDPR.

11. Push notifications

If you enable push notifications, CarCrew processes a device token, device-language information and technical delivery metadata through Firebase Cloud Messaging and the Apple Push Notification service. Notifications may include fleet events, requests, reminders and CrewBonus reward availability. The content sent to the push services is limited to the information required to deliver and display the notification.

Purpose: delivering notifications requested or expected in connection with app features.
Legal basis: Art. 6(1)(b) GDPR, Art. 6(1)(f) GDPR based on our legitimate interest in reliable app operation and, where required, Art. 6(1)(a) GDPR through the iOS permission prompt.

12. Subscriptions, App Store transactions and CrewBonus

12.1 In-app purchases and subscriptions

Subscriptions and offer codes are processed through the Apple App Store. Apple processes payment details. CarCrew receives and verifies information required to provide subscription and referral features, including the product identifier, subscription status and term, App Store environment, offer identifier and Apple-signed transaction and renewal information. This can include transaction IDs and original transaction IDs, but not your complete payment-card details.

Purpose: verifying purchases, providing entitlements, preventing duplicate use and processing subscription changes, renewals, revocations and refunds.
Legal basis: Art. 6(1)(b) GDPR and Art. 6(1)(f) GDPR based on our legitimate interest in preventing misuse and maintaining accurate purchase records.

12.2 CrewBonus referral programme

If you participate in CrewBonus, we process data required to create, assign, verify and document referrals and rewards. This includes:

  • Your personal referral code and referral link
  • Internal IDs of the inviter and invited user
  • The time and source of entering a referral code, such as a link or manual entry
  • A share intent and selected channel, such as opening the share sheet or copying the code or link; this records the action in CarCrew and does not prove that a third party received the invitation
  • Referral status, subscription product, offer identifier, App Store environment and allocated offer-code record
  • Apple-signed transaction identifiers and status information used to verify the invited user's purchase, renewal and the inviter's reward
  • Reward months earned, allocated and redeemed
  • Security and audit events used to prevent self-referrals, reciprocal referrals, multiple use, duplicate transactions and other abuse

A compact referral summary may be stored in your user record. More detailed audit records are stored separately and are not directly accessible or editable by app users. Where a reward becomes available, a server-side event may trigger a push notification to the inviter.

Purpose: operating the referral programme, allocating discounts, verifying eligibility, preventing abuse, handling support enquiries and establishing or defending legal claims.
Legal basis: Art. 6(1)(b) GDPR for participation in CrewBonus and Art. 6(1)(f) GDPR based on our legitimate interests in fraud prevention, programme security, complaint handling and the defence of legal claims.

13. Usage analytics, diagnostics and configuration

13.1 Optional Firebase Analytics

Anonymous usage analytics is disabled by default. It is enabled only if you actively opt in through the app's privacy settings and can be disabled there again at any time. The current analytics implementation records a limited set of predefined events relating to Trip Story templates, such as viewing or selecting a template, creating a story, opening the share sheet or completing a share action, together with a predefined template identifier.

Route coordinates, addresses, photos, vehicle names, trip IDs and free-text content are not included as parameters in these usage events.

Purpose: understanding feature usage and improving the app.
Legal basis: Art. 6(1)(a) GDPR. You may withdraw consent at any time in the app settings without affecting the lawfulness of processing before withdrawal.

13.2 Diagnostics, performance and configuration services

Depending on the app version and active configuration, Firebase Crashlytics, Performance Monitoring, Remote Config and In-App Messaging may process technical app, device, crash, performance, network and configuration information. These services are used to diagnose faults, improve stability, deliver configuration and display relevant in-app information.

Legal basis: Art. 6(1)(f) GDPR based on our legitimate interests in app security, stability, support and reliable operation, subject to any additional consent required by applicable law or device settings.

14. Service providers and recipients

We use the following categories of recipients and processors where required by the features you use:

  • Google and Firebase: authentication, cloud database, server-side functions, app integrity, push delivery, storage, configuration, diagnostics and optional analytics
  • Google Sign-In: authentication with a Google account when selected by the user
  • Apple: Sign in with Apple, App Store and StoreKit, App Store Server Notifications, Apple Push Notification service, Maps, geocoding, WeatherKit and other iOS system services
  • Email providers: processing support and privacy enquiries sent by email

Firebase services used by CarCrew

  1. Firebase Authentication

    Purpose: sign-in, account management and associating cloud data with a user account.

    Data processed: user ID, email address where provided, display name, authentication provider and tokens, together with security-related IP address and user-agent information processed by Firebase.

  2. Cloud Firestore and Realtime Database

    Purpose: cloud synchronisation, shared fleets, invitations, subscriptions, CrewBonus, roles, permissions, vehicles, trips, expenses, notifications and technical state.

    Data processed: app content and metadata described in this Privacy Policy.

  3. Cloud Functions for Firebase

    Purpose: server-side subscription and referral verification, offer-code allocation, audit events, notifications and other app logic.

    Data processed: user and technical identifiers, signed Apple transaction information, referral records, request metadata and the data required for the relevant server-side function.

  4. Firebase Cloud Messaging

    Purpose: technical delivery of push notifications.

    Data processed: device tokens, language information and delivery metadata.

  5. Firebase App Check and Firebase Installations

    Purpose: preventing abuse, verifying app integrity and providing an app-instance identifier for technical processes.

    Data processed: app-attestation tokens, app-instance identifiers, and technical security and integrity signals.

  6. Firebase Analytics

    Purpose: optional usage analysis as described in Section 13.1.

    Data processed: limited predefined event data, template identifiers, device and app information, and technical identifiers when you have opted in.

  7. Firebase Crashlytics and Performance Monitoring

    Purpose: diagnosing crashes, improving stability and identifying performance or network bottlenecks.

    Data processed: crash reports, performance measurements, device and app information, diagnostic data, technical identifiers and network metadata.

  8. Firebase Remote Config and In-App Messaging

    Purpose: configuration management, feature availability and relevant in-app notices.

    Data processed: technical identifiers, configuration requests and information about message delivery and interaction.

  9. Firebase Storage

    Purpose: file storage where a feature in the relevant app version requires it.

    Data processed: files selected or created for that feature and associated technical metadata.

Apple services used by CarCrew

  1. App Store, StoreKit and App Store Server Notifications

    Purpose: processing and verifying subscriptions, offer codes, renewals, revocations, refunds and CrewBonus eligibility.

    Data processed: Apple-signed transaction, subscription, product, offer, environment and status information.

  2. Apple Push Notification service

    Purpose: technical delivery of push notifications.

    Data processed: device tokens, notification content and delivery metadata.

  3. Apple Maps and geocoding services

    Purpose: displaying maps and routes and converting coordinates into addresses.

    Data processed: the locations or coordinates required to provide the selected map and address functions, together with technical service data.

  4. Apple WeatherKit

    Purpose: obtaining local weather conditions for weather-based trip and consumption analysis.

    Data processed: the location needed for the weather request and technical service information as described by Apple.

You can find further information in the Firebase privacy and security information, Google Privacy Policy and Apple Privacy Policy.

15. International data transfers

Depending on the service, personal data may be processed in the European Union, the European Economic Area, the United States or other countries in which a service provider operates. Where required, transfers to countries without an adequacy decision are based on appropriate safeguards such as the European Commission's Standard Contractual Clauses. Google provides additional information about Firebase processing locations and safeguards in its privacy and data-processing documentation.

16. Retention, account deletion and referral records

We retain personal data only for as long as it is required for the relevant purpose or as long as a legal obligation or legitimate need to retain it applies. The following criteria generally apply:

  • Local app data: until you delete it, delete the app and its data, or erase the device, subject to your device backups
  • Account and cloud data: while you use the account or cloud feature and until deletion through the app or upon a valid request, subject to technical processing time and any records that must be retained separately
  • Trip, vehicle, expense and fleet data: until deleted by you, removed as part of account or fleet deletion, or no longer required for the shared-fleet relationship
  • Push tokens: while the relevant device is registered, until removed, invalidated or no longer required
  • Optional analytics consent: stored on the device until changed or the app data is removed; analytics events already processed are retained according to the applicable Firebase settings and provider terms
  • Support enquiries: until the enquiry has been fully resolved and thereafter where needed for follow-up or legal obligations
  • Subscription and CrewBonus records: for as long as required to process subscriptions, referrals and rewards and thereafter where necessary to prevent fraud, handle complaints, demonstrate entitlement or defend legal claims, generally in line with applicable statutory limitation and retention periods

The in-app account-deletion function removes the authentication account and core user, fleet and cloud data covered by that function. Certain transaction mappings, referral, reward, audit and anti-abuse records may be retained separately after account deletion where they remain necessary for the purposes described above. These records primarily use internal identifiers rather than account profile fields and are access-restricted. They are deleted or anonymised when they are no longer required, unless a legal obligation or an ongoing dispute requires continued retention.

To request information or deletion beyond the controls available in the app, contact info@carcrew.app.

17. Your rights

Under the GDPR, you have the following rights in particular:

  • Right of access under Art. 15 GDPR
  • Right to rectification under Art. 16 GDPR
  • Right to erasure under Art. 17 GDPR
  • Right to restriction of processing under Art. 18 GDPR
  • Right to data portability under Art. 20 GDPR
  • Right to object under Art. 21 GDPR
  • Right to withdraw consent under Art. 7(3) GDPR where processing is based on consent

Where processing is based on Art. 6(1)(f) GDPR, you may object on grounds relating to your particular situation. To exercise your rights, email info@carcrew.app.

18. Right to lodge a complaint

You have the right to lodge a complaint with a data protection supervisory authority. In particular, the competent authority is:

State Commissioner for Data Protection and Freedom of Information North Rhine-Westphalia (LDI NRW)
Kavalleriestr. 2–4
40213 Düsseldorf
Germany

19. Changes to this Privacy Policy

We may update this Privacy Policy where necessary, for example if app features, service providers or legal requirements change. The current version is available at https://carcrew.app/privacy-app/.

Last updated: 23 July 2026

CarCrew

Clearer trips. Fairer costs. Better shared driving.

Explore

HomeApp & plansContact

Connect

InstagramXinfo@carcrew.app

Legal

Legal noticePrivacy policyApp privacy

© 2026 CarCrew. All rights reserved.

Made for the road ahead.