Last updated: 4 August 2026
This policy explains how Autocunha Car Rental processes personal data in the Autocunha iOS and Android mobile applications (together, the “Apps”). It covers only features currently present in the Apps' code.
1. Data controller
J M CUNHA - COMERCIO AUTOMOVEIS, LDA., trading as Autocunha Car Rental, tax ID PT 512 061 130, at Canto dos Prestes de Cima, 77, São Roque, 9500-711 Ponta Delgada, Azores, Portugal, is the data controller.
App privacy and support contact: support@autocunha.net.
2. Scope and principles
The Apps allow users to search availability, obtain prices, create and retrieve bookings, select extras and protection, make or prepare payments, receive operational booking updates, add a booking to a calendar and contact branches. No user account is created.
The Apps do not include advertising SDKs, Google Analytics, Firebase Analytics, Meta Pixel, TikTok Pixel, remarketing, session recording or behavioural profiling. Autocunha does not sell personal data.
3. Data processed
| Category | Data | Use |
|---|---|---|
| Search and quote | Branches, dates and times, driver age and any promotional code. | Sent to the Autocunha backend to check availability and calculate prices; not used for behavioural analytics. |
| Identity and contact | Name, email, dialling code and telephone, address, postcode, city, country and date of birth. | Create and manage the booking and rental contract, communicate with the customer and provide support. |
| Driver documents | ID type, number, issuing country and expiry; driving-licence number, issuing country and expiry. | Prepare the booking and rental contract and verify driver requirements. |
| Booking | Locations and dates, vehicle/group, extras, protection, mileage, amounts, deposit, flight number, hotel, notes, references, status and operational history. | Quote, create, retrieve, amend, confirm, cancel and perform the rental. |
| Payment | Amount, currency, mode and status, booking reference, Stripe customer, PaymentIntent, SetupIntent and tokenised payment-method identifiers. | Payments, card authorisations, deposits, refunds, fraud prevention and reconciliation. Full card numbers and CVCs are entered with Stripe and are not stored in Autocunha's internal systems. |
| Notifications | APNs or FCM token, platform, environment, language, email and booking reference/identifier, plus notification title, content and state. On Android, FCM includes a Firebase installation ID and App/SDK/device technical metadata. | Confirmations, cancellations, updates and pick-up/return reminders when notifications are authorised. |
| Technical data | IP address temporarily used for rate limiting, request identifiers, technical error logs, language, app version, preferences and essential technical identifiers. FCM may communicate OS version, manufacturer, model, brand, device form factor and Firebase SDK versions. | Backend communication, security, diagnosis, abuse prevention, notification delivery and App operation. |
4. Data stored on the device
The Apps locally store technical preferences, acknowledgement of the privacy notice, notification state, a dismissed campaign identifier and summaries of saved bookings. iOS keeps at most three bookings in local history; Android lets the user remove saved bookings individually. Pick-up/return instructions, a calendar-event identifier and data required for local reminders may also be cached.
This data remains until replaced, removed through an available feature, cleared in system settings or deleted when the App is uninstalled. Android app backup is disabled in the manifest.
5. Device permissions and resources
| Resource | iOS | Android | Actual use |
|---|---|---|---|
| Internet | Used without a separate prompt. | INTERNET permission. | HTTPS communication with api.autocunha.net, AnyRent through the backend, Stripe and notification services. |
| Push notifications | User authorisation and Apple Push Notification service (APNs). | POST_NOTIFICATIONS and Firebase Cloud Messaging (FCM). | Booking updates and operational reminders; not advertising in the Apps' current behaviour. |
| Location | When In Use. | Approximate or precise location. | Requested only when the user taps SOS during an ongoing booking. A single position creates a Google Maps link in a WhatsApp message. There is no background location, location history or continuous monitoring, and this flow does not send coordinates to Autocunha's backend. |
| Calendar | Write access to events. | No READ_CALENDAR or WRITE_CALENDAR; the external calendar editor is opened. | Pre-fills an event with dates, locations, reference, name and vehicle after user action. Existing calendar entries are not read. iOS locally stores the event identifier. |
| Camera | Camera-based card scanning is available through Stripe PaymentSheet. | No camera permission is declared. | On iOS, access is optional and requested only if the user selects card scanning. Autocunha does not use the camera to photograph documents, vehicles or people, and does not receive or store images from this flow. |
| Device restart | Not applicable. | RECEIVE_BOOT_COMPLETED. | Restores local booking reminders after Android restarts. |
6. Recipients and third-party services
- Autocunha infrastructure (
api.autocunha.net): handles quote, booking, retrieval, payment and notification requests. - JEDEYE LDA / AnyRent: availability and booking system receiving data required for the booking and rental contract.
- Stripe: processes customer and payment data, authentication, card authorisations and fraud prevention. Full card details and CVC are handled directly by Stripe.
- Apple Push Notification service: delivers iOS notifications using a device token and operational notification content.
- Google Firebase Cloud Messaging: delivers Android notifications using an FCM token, per-installation identifier, App/SDK/device technical metadata and operational notification content. Firebase Analytics is not integrated.
- WhatsApp: opened only on user action. A message may include booking information and, for SOS, a current-location link. The user reviews and decides whether to send it.
- Google Maps: used through external branch links and a coordinate link created for SOS. Google receives data when the external service or link is opened.
- Device phone and email apps: opened on user action and thereafter governed by the chosen provider and recipient.
No other analytics, advertising or tracking services were found in the code. Global providers may process data outside the European Economic Area; where applicable, such processing must use the mechanisms and safeguards required by Chapter V of the GDPR.
7. Purposes and legal bases
- Pre-contractual steps and contract performance (GDPR Article 6(1)(b)): search, quotes, bookings, booking retrieval, payments and rental performance.
- Legal obligation (Article 6(1)(c)): tax, accounting, contractual and vehicle-rental obligations.
- Legitimate interests (Article 6(1)(f)): system security, fraud and abuse prevention, support, complaints and legal claims.
- Consent/optional user action (Article 6(1)(a)): notifications, SOS location, calendar and camera-based card scanning. Permission may be refused or withdrawn in device settings without preventing unrelated features.
8. Retention
Data relating to bookings, payments, operational events and technical logs is retained for as long as needed to provide the service and may be kept for up to three years after a booking is completed or cancelled where necessary to manage chargebacks, complaints, audits, penalties, fraud prevention or legal claims.
Certain accounting, tax or contractual documents and data may be retained for longer where required by law or while proceedings are pending. Records held by Stripe, AnyRent or other providers may also be subject to those providers' own legal duties and retention policies.
The active cleanup cron for the mobile backend's operational database removes cancelled bookings after three days and fulfilled bookings fifteen days after return. An additional daily routine deletes Autocunha local-system data older than three years, including operational records and their timeline, technical events, local payment records and local Stripe customer references. Push tokens are retained while needed for associated booking notifications and are covered by the server retention routine. These cleanups do not necessarily delete contractual, accounting or payment records retained by other systems and providers under their respective obligations.
SOS location is processed momentarily in memory to compose the link and is not saved in App history or sent to Autocunha's backend by this flow.
9. Security
The Apps use HTTPS to communicate with the backend; Android blocks cleartext traffic. Stripe and AnyRent secret keys remain on the backend, not in the Apps. Access must be limited to people and providers needing data for the stated purposes, with appropriate technical and organisational measures.
10. User rights
Under the GDPR, users may request access, rectification, erasure, restriction, portability and objection, withdraw consent at any time, and obtain information about processing. A right may be limited where retention is required by law or for legal claims.
Requests: support@autocunha.net. To locate a booking, the email and reference may be required; never send a full card number or CVC.
A complaint may be lodged with the Portuguese National Data Protection Commission (CNPD).
11. Children
The Apps concern vehicle rentals and require the driver to be at least 18. They are not designed to deliberately collect children's data.
12. Changes
This policy will be updated when the Apps, providers or processing change. The App Store and Google Play privacy declarations must remain aligned with this policy and the distributed App versions.