Privacy Policy
Lat update: 18/08/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 of the site’s presentation is 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 |
They set no cookies, but to deliver the file they do receive your IP address.
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) |
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 |
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
Last updated: 6 August 2026
This section covers the Magica app for iPhone, Apple Watch, CarPlay and its
widgets. 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, Pisa 56128 Itala.
P.IVA: IT02381200506, C.F. GNIDTR80C25G702S.
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 only 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. You can turn this off whenever you want. There are no ads, no profiling,
and we do not sell or share data with anyone.
Three 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). Wherever a position is needed, it is sent
rounded to roughly one kilometre, used only to answer the request, and not
stored; - purchases: we know that a subscription is active, which product and when
(section 9). Payment details are handled by Apple; we never see them; - app crashes: when Magica crashes we receive a technical report, without
your data (section 7).
If you enable the iCloud backup, your data is copied into your iCloud
storage, which is Apple’s responsibility. 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, 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, full 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.
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 the iOS Settings: the app keeps working, with
that feature switched off.
| 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 |
| Photos | picking and saving vehicle images and attachments |
| Microphone | recording voice commands |
| Notifications | deadline reminders, driving and efficiency alerts, app news |
| Siri & Shortcuts | triggering Magica actions by voice or from iOS Shortcuts |
5. iCloud and backup (Apple)
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.
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, it stays on
this device, it does not link your devices to one another, and it is replaced
by a new one if you uninstall and reinstall the app; - usage events (for example: opening a screen, starting a trip, exporting a
report) and the screens visited; - the length of usage sessions;
- device model, iOS version, app version, language and country as reported
by the system settings; - your subscription status and purchases (product, price, currency,
transaction identifier, trial or promotional period), to measure how
subscriptions are doing.
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.
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.
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. The same consent
described in 6.2 applies.
6.4 Fuel stations and fuel prices
If you use the fuel station map, or the prices widget, 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.
6.6 Push notifications and Live Activities
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.
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, news and service announcements, configuration
parameters. Those requests only carry 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) | 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, iOS and app version, app state at the time of the crash, installation identifier | diagnosing and fixing malfunctions | USA/EU | firebase.google.com/support/privacy |
| WeatherAPI.com | approximate position (~1 km), language | weather shown in the app and 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. | the messages you type in the support chat | automated user support | USA | chatbase.co/privacy |
| Apple Inc. | 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 only when the app crashes, and that
report contains technical information about the state of the program: it does
not contain your vehicles or your trips.
The support chat 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.
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 (including to Android) 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 your own local network. - Board Magica accessory. 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. The controller never receives or processes your payment
details: from Apple we only learn that a subscription is active, which product
it is and its transaction identifier, 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 |
| Fuel stations, speed cameras, weather, charge points | performance of the service you requested (art. 6.1.b): the feature cannot work without a position |
| Push notifications and Live Activities | 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 directly from the app’s settings |
| Crash reports (Crashlytics) | 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 backup: stays in your iCloud storage until you delete it.
- 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). - 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: the simplest way is to
write to us through the support function inside the app, which attaches it
to your request. 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, there is no need to write: the
switch in Settings → Share usage statistics takes effect immediately.
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 use the IDFA (Apple’s advertising
identifier), does not ask for permission to track you across other companies’
apps and websites, does not profile you for marketing, and does not pass data to
advertising intermediaries.
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.