Privacy Policy
Last updated: 5 November 2026
This policy covers the magica-app.com website, forum included. The Magica app has its
own, on the app privacy policy page.
1. Who processes your data
Dimitri Giani
Largo Riviera 7, 56128 Pisa, Italy
VAT number: IT02381200506
Email: hello@magica-app.com
2. In short
The site does not profile you. There are no analytics tools, no advertising, no social
buttons following you from site to site, no remarketing. You won’t find a cookie banner: the
only cookies the site sets are technical ones.
Two things do involve your data, and you choose both: registering on the forum and
commenting on an article. They are explained in sections 5 and 6.
3. Data collected while you browse
Like any website, the server records in its technical logs your IP address, the date and
time of the request, the page requested, your browser and operating system, and the site you
came from, if any.
This keeps the site running, helps diagnose faults and spot abuse. We don’t use it to build
profiles. It is kept for 24 months.
4. Cookies
The site uses technical cookies only:
| Cookie | What it does | Duration |
|---|---|---|
pll_language | remembers the language you picked | 1 year |
wordpress_logged_in_*, wp-settings-* | keep your session alive when you sign in to the forum | session or 1 year |
comment_author_* | refill your name and email when you comment again, if you asked for it | 1 year |
No profiling cookies, no advertising cookies. Technical cookies need no consent under
the law, which is why there is no banner to dismiss.
You can delete or block them in your browser. If you do, the site carries on working but you
will have to sign in to the forum on every visit.
5. Registration and forum
The forum is the part of the site where we collect the most, and it only happens if you
choose to register.
When you register we ask for a username and an email address, and you choose a
password. We do not know your password: it is stored only in its hashed, non-reversible
form. The email address is used to confirm your registration, to recover your password and
to write to you when needed: it does not appear in public posts.
When you post on the forum we keep the content of your posts, the date, the topic you
posted in and — worth knowing — the IP address you posted from, which the forum software
records alongside every contribution for moderation and abuse prevention. Your IP address is
not visible to other users: only the site’s administration sees it.
What you write on the forum is public. Your username, your posts, your signature and
anything you put in your profile can be read by anyone visiting the site, registered or not,
and may be indexed by search engines. Bear that in mind: avoid posting data you don’t want
made public, whether yours or someone else’s.
You can ask for your account to be deleted at any time by writing to
hello@magica-app.com. On request we can also delete the posts you wrote, or detach them from
your username and leave the discussion readable: tell us which you prefer.
6. Article comments
If you comment on a blog article we collect the name you give, your email address,
your website if you enter one, the content of the comment and your IP address.
Your name, the comment and the website are public; your email address is not. If you tick
the box when commenting, your browser stores those details in a cookie so you don’t have to
type them again.
The avatars next to comments, where enabled, are provided by Gravatar, by Automattic:
to fetch them the site transmits a hashed version of your email address and your IP address
to Gravatar.
7. Contact forms
When you write through a form on the site we collect your name, email address and
message. They reach us by email and we use them only to reply to you.
8. Sending email
The emails the site sends — registration confirmations, password recovery, forum
notifications, copies of form submissions — are delivered through Titan Email, which handles the recipient’s address and the message content only
for as long as delivery takes.
9. Resources loaded from third parties
Some parts of the site are served by third parties:
| Service | What it provides | What it receives |
|---|---|---|
| Google Fonts (fonts.googleapis.com, fonts.gstatic.com) | the site’s typefaces | your IP address and the technical data of the request |
| jsDelivr (cdn.jsdelivr.net) | libraries for image galleries | your IP address and the technical data of the request |
| Google reCAPTCHA (google.com, gstatic.com) — contact pages only | protects the contact form from spam | your IP address, technical data about your browser and how you interact with the page; Google may set its own security cookie |
| Chatbase (chatbase.co) | the support chat at the bottom of the page | your IP address and the technical data of the request and, if you write in the chat, the messages you send |
Google Fonts and jsDelivr set no cookies, but to deliver the file they do receive your IP address. In the chat, avoid writing personal data your request doesn’t need.
10. Legal basis for processing
| Processing | Legal basis |
|---|---|
| Server technical logs and technical cookies | legitimate interest in running and protecting the site (Art. 6.1.f) |
| Forum account and published posts | performance of the service you asked for by registering (Art. 6.1.b) |
| IP address recorded with posts | legitimate interest in moderating and securing the forum (Art. 6.1.f) |
| Article comments | consent, given by submitting the comment (Art. 6.1.a) |
| Contact forms | responding to your request (Art. 6.1.b) |
| Contact form protection (reCAPTCHA) | legitimate interest in protecting the site from spam and abuse (Art. 6.1.f) |
| Support chat | responding to your request (Art. 6.1.b) |
11. How long we keep data
| Data | Retention |
|---|---|
| Forum account | until you ask for it to be deleted |
| Forum posts and comments | for as long as they stay published; when your account is deleted you decide whether to remove them or detach them from your name |
| IP address attached to posts and comments | alongside the post it belongs to |
| Server technical logs | 24 months |
| Messages received through forms | for as long as needed to handle the request and the related dispute period |
| Messages sent in the support chat | about 30 days, after which Chatbase deletes them automatically |
12. Where data is processed
The site is hosted with Hostinger, on servers in Europe. The services listed in sections
6 and 9 are based in the United States: those transfers rely on the Standard Contractual Clauses approved by the European Commission and/or membership of the EU-U.S. Data Privacy Framework.
13. Your rights
At any time you can request access, rectification, erasure, restriction and
portability of your data, and object to processing based on legitimate interest.
Where processing is based on consent, you can withdraw it at any time.
Write to hello@magica-app.com: we answer within 30 days.
You also have the right to lodge a complaint with the Italian Data Protection Authority,
the Garante per la protezione dei dati personali (www.garanteprivacy.it), or with the
supervisory authority in your own country.
14. No advertising, no analytics
- No analytics or statistics tool, from any provider
- No conversion pixels, no remarketing
- No social widgets, no buttons that follow you from site to site
- No profiling, no selling of data
15. Children
The forum is not aimed at children under 16 and we do not knowingly collect their data. If
you believe a child has registered, write to hello@magica-app.com and we will delete the
account.
16. Changes to this policy
We may update this policy. Changes are published on this page, with the date of the last
update shown at the top.
Privacy Policy for the Magica app
This section covers the Magica app for iPhone (with Apple Watch, CarPlay and its widgets) and for Android smartphones (with Android Auto). Both versions handle data in the same way, except where the text says “on iPhone” or “on Android”. How the magica-app.com website handles data is described in the previous section of this document.
1. Data controller
The data controller is Dimitri Giani, Largo Riviera 7, 56128 Pisa (Italy), VAT no. IT02381200506.
For anything concerning your data, write to hello@magica-app.com (support: support@magica-app.com).
2. In short
Magica works without an account: we do not know who you are. We do not collect your name, your email address, or any of the content you create in the app — vehicles, trips, GPS routes, refuellings, expenses, photos and documents stay on your device and are never uploaded to our servers.
We collect which features of the app get used, tied to a random identifier that does not identify you, so we can tell what works and what does not. On iPhone you can turn this off whenever you want; on Android the switch is not available yet (section 6.1). There are no ads and we do not sell your data.
A few things fall outside that promise, described in full further down because you deserve to know them:
- some features need the network to exist at all — voice commands, AI vehicle search, nearby fuel stations, speed cameras, weather, charge points, notifications (sections 6 and 7). When a position reaches our servers, it is sent rounded to roughly one kilometre, used only to answer the request, and not stored;
- maps, addresses and routes are provided by Apple on iPhone and by Google on Android, which receive the coordinates needed to compute them. On Android the trip weather service also receives the precise position (sections 5 and 7);
- purchases: we know that a subscription is active, which product and when (section 9). Payment details are handled by Apple or Google; we never see them;
- app crashes: when Magica crashes we receive a technical report, without your data (sections 6.1 and 7).
If you use the iCloud backup (iPhone) or Google backup (Android), your data is copied into your iCloud storage or your Google account, which are the responsibility of Apple and Google. We have no access to it.
3. Data the app handles on your device
In normal use, the following data is created and kept on the device:
| Category | Content |
|---|---|
| Vehicles | make, model, plate (if you enter it), year, fuel type, technical data, photo |
| Trips | date and time, GPS positions along the route, speed, distance, duration, start and end addresses, tags, notes, driving score |
| Refuellings and charges | date, quantity, price, fuel type, odometer, position of the refuelling, notes |
| Services, deadlines and costs | type of work, date, amount, garage/place, expiry dates, notes |
| Attached documents | photos and PDFs you attach to trips, refuellings, services and vehicles |
| Sport Mode | telemetry of accelerations and track sessions |
| Statistics, goals and badges | values computed from the data above |
| Settings | app preferences, units, currency, notifications, Bluetooth devices recognised for automatic trip start |
This data is yours and stays in the app’s own storage: you can export it (PDF, CSV, GPX on iPhone, backup), transfer it to another device, or delete it at any time, including by uninstalling the app.
Some of it — the GPS positions and your movements in particular — is personal data that describes your habits. That is exactly why the app keeps it local and does not send it to our servers, except in the cases listed in section 6. The map and weather services described in sections 5 and 7 receive the coordinates each request needs.
4. Permissions the app asks for
Magica only asks for permissions that serve a concrete feature. You can deny or revoke any of them at any time in your phone’s settings: the app keeps working, with that feature switched off.
On iPhone:
| Permission | What it is for |
|---|---|
| Location (including in the background) | recording trip routes, the position of a refuelling, where you parked, nearby fuel stations and charge points, speed camera alerts |
| Motion & Fitness | recognising automatically that you are driving, to start and stop a trip |
| Bluetooth | recognising your car stereo or Bluetooth device to start trips automatically, and talking to the Board Magica accessory |
| Local Network | finding your other devices for data transfer and for API Mode over your Wi-Fi |
| Camera | taking the vehicle photo, photographing documents, reading the odometer and the pump display |
| Photos | picking vehicle images and attachments, and saving photos taken in the app to your library |
| Microphone | recording voice commands |
| Notifications | deadline reminders, driving and efficiency alerts, app news |
| Siri & Shortcuts | triggering Magica actions by voice or from iOS Shortcuts |
On Android:
| Permission | What it is for |
|---|---|
| Location (including “Allow all the time”) | recording trip routes, the position of a refuelling, where you parked, nearby fuel stations, charge points and speed cameras |
| Physical activity | recognising automatically that you are driving, to start and stop a trip |
| Nearby devices (Bluetooth) | recognising your car stereo or Bluetooth device to start trips automatically |
| Camera | taking the vehicle photo and photographing documents |
| Microphone | recording voice commands |
| Notifications | trip start and end alerts, deadline and refuelling reminders, badges |
| Unrestricted battery usage | keeping trips recording while the app is closed |
On Android, photos and attachments are chosen with the system picker, which does not give the app access to your gallery. Android also grants the following without asking, because they do not concern personal data: starting up after the phone is switched on, the foreground service that keeps tracking active (with its persistent notification), the high-frequency sensors used by Sport Mode, and the Android Auto screen.
5. Backups, maps and system services (Apple and Google)
On iPhone: iCloud and Apple services
If your iPhone has iCloud enabled, Magica uses it in two ways:
- Backup of the app data. On your request, or automatically if you enable automatic backup, the app creates an archive with the database and the attachments and saves it in the Magica folder of your iCloud Drive.
- Syncing some preferences across your devices, through iCloud’s key-value store.
In both cases the data stays in your iCloud account: the controller has no access whatsoever to that space. Processing there is governed by Apple Inc.’s privacy policy. The same applies to the full iPhone backup handled by iOS, which may include the app’s data.
The app also uses Apple’s services built into iOS to show maps, turn coordinates into addresses (geocoding), search for places and compute routes: in those operations the coordinates are processed by Apple under its own policy.
On Android: backups and Google services
- Manual backup. From the vehicle’s detail screen you can create a backup file and save it wherever you choose (in the phone’s storage, on Google Drive or in another app), or share it. The file contains that vehicle’s data and stays where you put it: the controller does not receive it.
- Android automatic backup. If Google backup is turned on on the phone, Android copies the app’s data — the archive with vehicles, trips and routes, the documents, the photos and the settings, including the statistics identifier described in 6.1 — into your Google account, and restores it when you reinstall the app or move to a new phone. It is handled by Google under its own policy; the controller has no access to it. You can turn it off in Android’s settings, in the Google backup section.
- Maps, addresses and routes. The app uses Google Maps to show maps, Android’s geocoding service to turn the start and end points of trips into addresses, and Google Maps Platform to compute routes and draw the thumbnails of trips and places. These services receive the precise coordinates they need: for a thumbnail, the trip’s track; for a route, the start and end points. Route calculation also starts on its own when a trip begins far from where you had parked, to reconstruct the first stretch.
- Location and driving detection are provided by the phone’s Google Play services, which process them under Google’s policy.
6. When data leaves the device towards our servers
These are all the features that send data to servers operated by the controller (api.magica-app.com, admin.magica-app.com, tracker.dimix.it).
6.1 App usage statistics
To understand which features get used and how to improve the app, Magica collects usage statistics through an analytics service operated directly by the controller (not by a third party).
What is sent:
- a random identifier generated by the app on first install. It does not contain your name, your email address or the device identifier, and it does not link your devices to one another. On iPhone it is replaced by a new one if you uninstall and reinstall the app; on Android, if Google backup is on, it is restored together with the rest of the app’s data (section 5);
- usage events (for example: opening a screen, starting a trip, exporting a report) and the screens visited;
- the length of usage sessions;
- device model, operating system version, app version, language and country as reported by the system settings; on Android also manufacturer, brand and screen size;
- your subscription status and purchases (product, price, currency, transaction identifier, trial or promotional period; on Android also the Google Play purchase token and order number), to measure how subscriptions are doing;
- on Android, crash reports: error message, technical trace of the program and device data.
What is not sent: your vehicles, your trips, your routes, your positions, the amounts you record in the app, or anything you have written.
The statistics are never used to profile you for advertising and are not shared with third parties.
On iPhone you can turn them off at any time in Settings → Share usage statistics, inside the app. With the switch off nothing is sent any more, and no feature of the app changes or becomes limited.
On Android this switch is not available yet: the statistics are sent for as long as the app is installed. You can write to us to object, but the Android app does not show the installation identifier, and without it we cannot find the data that concerns you (section 13).
6.2 Voice commands
When you use a voice command, the audio recording is sent to our servers, and from there:
- the audio is passed to OpenAI to be transcribed into text. The audio is not retained: it is deleted right after transcription;
- the transcribed text is passed to Anthropic to interpret the command.
Only the technical context needed to interpret it correctly travels with the command: vehicle fuel type, units, currency, language, vehicle name, current odometer reading, and the list of available expense and service categories. No data that identifies you is transmitted.
For technical monitoring and service improvement, the transcribed text and the response stay in our logs for a maximum of 30 days, after which they are irreversibly anonymised. Only aggregate metrics remain (processing time, command type, outcome), which cannot be traced back to a person.
The feature is optional: it is enabled only after you have read and accepted the dedicated notice shown in the app, and you can simply not use it without any limitation to the rest of the app.
6.3 AI vehicle search
When you look for your vehicle by describing it, the text you write is sent to our servers and from there to Anthropic, which interprets it to identify make, model and technical data. Nothing else is transmitted. On iPhone the same consent described in 6.2 applies; on Android the search runs when you start it, without a separate consent request.
6.4 Fuel stations and fuel prices
If you use the fuel station map, the prices widget (iPhone) or the fuel station screen on the car’s display, the app sends our servers the approximate position of the area and a search radius, in order to receive the list of stations and prices.
The position is rounded by the app before it leaves, to about one kilometre: what reaches us is an area, not an address. It is used only to answer the request, it is not stored, it is not associated with your identifier, and it is not used to reconstruct your movements.
6.5 Speed camera alerts
If the feature is on, the app periodically sends our servers the approximate position of the area, the radius and the country, to receive the list of speed cameras nearby. The same conditions as 6.4 apply: position rounded to about one kilometre before sending, used only to answer, not stored. On Android speed cameras are shown only on the map: the position is sent when you open or move the map, not periodically.
6.6 Push notifications and Live Activities (iPhone)
To deliver notifications, iOS assigns the app a notification token, which is registered with Google Firebase Cloud Messaging (section 7) and, for the Live Activity of a trip in progress, with our servers. The token identifies the app installation on that device, not you. It is used solely to deliver the notification and is discarded when the activity ends or when you uninstall the app.
On Android, notifications are generated by the phone itself: no token is registered, either with third parties or with our servers.
6.7 App content
The app downloads content from our servers that has nothing to do with your data: the list of makes and models and, on iPhone, news, service announcements and configuration parameters. Those requests carry at most the app’s language. As with any connection to the internet, the server records the requesting IP address in its technical logs.
7. Third-party services
| Service | Data transmitted | Purpose | Location | Policy |
|---|---|---|---|---|
| OpenAI, L.L.C. | audio recording of the voice command | speech-to-text transcription | USA | openai.com/privacy |
| Anthropic PBC | transcribed command text; vehicle search text | interpreting the request | USA | anthropic.com/privacy |
| Google (Firebase Cloud Messaging) — iPhone only | notification token, installation identifier, technical device data, IP address | delivering push notifications | USA/EU | firebase.google.com/support/privacy |
| Google (Firebase Crashlytics) | crash reports: device type, operating system and app version, app state at the time of the crash, installation identifier | diagnosing and fixing malfunctions | USA/EU | firebase.google.com/support/privacy |
| Google (Maps Platform, Google Play services, Google Play) — Android only | precise coordinates for maps, addresses, routes and trip thumbnails; location and driving detection; document scanning; in-app purchases; backup copy of the app’s data, if Google backup is on | making maps, trip detection, scanning, purchases and backup work | USA/EU | policies.google.com/privacy |
| WeatherAPI.com | on iPhone the approximate position (~1 km); on Android the precise position of the trip’s starting point; language | weather forecasts shown in the app and, on iPhone, on the Board Magica accessory | USA | weatherapi.com/privacy.aspx |
| Open Charge Map | approximate position (~1 km) | list of nearby charge points (electric vehicles) | EU/USA | openchargemap.org/site/about/privacy |
| Frankfurter API | currency codes and date | exchange rates for expenses in foreign currency (no personal data) | EU | frankfurter.app |
| Chatbase, Inc. — iPhone only | the messages you type in the support chat | automated user support | USA | chatbase.co/privacy |
| Apple Inc. — iPhone only | coordinates and queries for maps, geocoding and routing; in-app purchases; iCloud backup | making maps, purchases and iCloud work | USA/EU | apple.com/legal/privacy |
Firebase Crashlytics collects a report when the app crashes (on Android also for some errors of the Android Auto screen), and that report contains technical information about the state of the program: it does not contain your vehicles or your trips.
Versions of the Android app up to and including 3.1.0 also contained Google Analytics for Firebase, which automatically collected usage events, device data and Android’s advertising ID. The controller never used that data and has removed the library from later versions: once you update the app, that collection stops.
The support chat (iPhone) is an external service embedded in the app: what you type in that window is processed by Chatbase, Inc. Avoid entering personal data that is not necessary for your support request. On Android, support goes through the support page of the website or by email.
8. Features that stay on your network or your devices
Some features exchange data without going through any server: the communication happens directly between your own devices.
- Data transfer between devices. You can copy Magica’s data from one device to another — between two iPhones, between two Android phones, or between an iPhone and an Android phone — over the local Wi-Fi network. The data travels straight from one device to the other; the transfer only starts after you confirm it on both.
- API / MCP Mode. If you enable it, the app exposes your data as a service on the local network, so that a computer of yours, or an AI assistant you have authorised, can read or modify it. Every client must be paired with a code shown on screen, gets access you can revoke at any moment, and every operation is written to a local audit log. The feature is off until you turn it on, and the service is reachable only from devices connected to the same network as the phone.
- Board Magica accessory (iPhone). If you use the accessory, the app sends it over Bluetooth the texts to display (greeting, data about the trip in progress, weather). The accessory has no internet connection and stores nothing.
9. Purchases and subscriptions
Purchases (subscriptions and one-off purchase) are handled by Apple through the App Store on iPhone and by Google through Google Play on Android. The controller never receives or processes your payment details: it only learns that a subscription is active, which product it is and its transaction identifier (on Android also the Google Play purchase token), used to unlock the features and for the statistics described in 6.1.
10. Legal bases for processing
| Processing | Legal basis (GDPR art. 6) |
|---|---|
| Vehicles, trips, expenses and attachments on the device | performance of the service you requested (art. 6.1.b) — the data stays on your device |
| Voice commands and AI vehicle search | consent (art. 6.1.a), given by enabling the feature; withdrawn by no longer using it. On Android, vehicle search, which does not ask for a separate consent, is based on performance of the service you requested (art. 6.1.b) |
| Fuel stations, speed cameras, weather, charge points | performance of the service you requested (art. 6.1.b): the feature cannot work without a position |
| Maps, addresses and routes (Apple on iPhone, Google on Android) | performance of the service you requested (art. 6.1.b) |
| Push notifications and Live Activities (iPhone) | performance of the service you requested (art. 6.1.b) and your consent to the notification permission |
| Usage statistics | the controller’s legitimate interest in improving and securing the app (art. 6.1.f), with the objection exercisable from the app’s settings on iPhone and by writing to the controller on Android |
| Crash reports (Crashlytics and, on Android, the controller’s analytics service) | the controller’s legitimate interest in keeping the app working correctly (art. 6.1.f) |
| Support (email and chat) | performance of the service and legitimate interest in answering requests |
| Purchases | performance of the contract and legal obligations |
11. Retention periods
- Data in the app: stays on your device until you delete it or uninstall the app. The controller holds no copy of it.
- iCloud or Google account backup: stays in your iCloud storage or your Google account until you delete it, under Apple’s and Google’s rules.
- Voice commands: the audio is not retained; text and response stay in the logs for at most 30 days, then are irreversibly anonymised.
- Usage statistics: individual events are kept for 14 months, then deleted; only aggregate figures remain, referring to no installation.
- Crash reports: according to Google Firebase Crashlytics’ policies (as a rule 90 days for the crash detail); on Android, those received by the controller’s analytics service follow the same periods as the statistics.
- Server technical logs: 30 days.
- Support emails: kept as long as needed to handle the request and for any subsequent dispute period.
12. Transfers outside the European Union
Some of the providers listed in section 7 are based in the United States. Transfers rely on the Standard Contractual Clauses approved by the European Commission and/or on the provider’s certification under the EU-U.S. Data Privacy Framework. You can ask about the safeguards in place by writing to hello@magica-app.com.
13. Your rights
In relation to the data concerning you, at any time you can request: access, rectification, erasure, restriction of processing, portability, and you can object to processing based on legitimate interest. Where processing is based on consent, you can withdraw it at any time, without affecting the lawfulness of processing carried out beforehand.
Write to hello@magica-app.com. We will answer within one month.
Since the app works without an account, to act on a request concerning the usage statistics we need the identifier of your installation: on iPhone the simplest way is to write to us through the support function inside the app, which attaches it to your request. On Android, support does not attach it yet. Without that identifier we are genuinely unable to connect any data to you — which is also the reason we do not collect anything else.
If all you want is to stop being measured, on iPhone there is no need to write: the switch in Settings → Share usage statistics takes effect immediately. On Android the switch is not available yet: you can write to us, as described above.
You also have the right to lodge a complaint with the Italian Garante per la protezione dei dati personali (www.garanteprivacy.it) or with the supervisory authority of the country where you live.
14. Children
Magica is not intended for children under 16 and does not knowingly collect their data. If you believe a child has provided us with data, write to hello@magica-app.com and we will delete it.
15. No advertising and no ad tracking
The app shows no advertising, does not profile you for marketing, and does not pass data to advertising intermediaries. It does not use advertising identifiers: neither the IDFA on iPhone — which is why it does not even ask for permission to track you across other companies’ apps and websites — nor Android’s advertising ID. The exception is versions of the Android app up to and including 3.1.0, which read it through Google Analytics for Firebase (section 7).
16. Changes to this policy
The controller may change this policy at any time, announcing it on this page and, for significant changes, through the app. The date of the last update is shown at the top of this document.