FIRELINE

Privacy

FIRELINE is free and works without an account. This page says exactly what is stored, why, where, for how long and who can see it. It was written from the code that handles the data, not from a template.

In short

Who is responsible

FIRELINE is run by a private individual in Benahavís (Málaga, Spain): [NOMBRE COMPLETO DEL RESPONSABLE · OPERATOR'S FULL NAME], [DIRECCIÓN POSTAL · POSTAL ADDRESS], Benahavís, Málaga, España, [NIF / NIE]. It is not a company, the app costs nothing and nothing is sold.

For anything to do with your data, write to fireline@acedntl.com. It is the same address the app sends its own mail from.

FIRELINE is not an official emergency service. In an emergency, call 112.

Counting visits

So the operator knows how many people use the app and which screens matter, without cookies and without storing IP addresses.

What is stored
The day, a 32-character code, whether the app is installed on the home screen, the device family (iPhone, Android, desktop or other), whether it was opened inside another app (WhatsApp, Instagram, Telegram…), the language, the screen name, and the names of actions (watch started, alerts on or off, report sent, feedback sent).
How the code is made
It is the start of the SHA-256 of a secret key, the date, your IP address and your browser's user-agent string. The IP and the user-agent are used to work it out and then dropped: neither is written to the database. Because the date goes into the calculation, your phone's code changes every day and cannot be followed from one day to the next.
Where
In FIRELINE's own database (the stat_visitors, stat_pages and stat_events tables).
Who sees it
Only the operator, on the admin screen. It goes nowhere else.
Legal basis
Legitimate interest (GDPR art. 6(1)(f)): knowing whether the tool is useful to anyone. No cookie is set for this.

Reports from residents

Anyone can send a report without an account and without waiting for approval. That means the app has to be able to tell a neighbour apart from a flood of messages.

Who sent it
An account, if you are signed in. Otherwise the phone itself: the first time you send something, the app leaves a cookie (fireline_reporter) holding a random identifier. It contains no name and nothing about you; it exists so you can see and recognise your own reports.
What the report stores
The exact position you sent it from and its accuracy in metres, the compass direction you were facing and its accuracy, the type of what you saw, the time you sent it, the capture time read from the photo or video, and the place you chose.
A summary of your network
A keyed hash of your IP address (32 characters), never the address itself. It is used for two things only: limiting one network to 6 reports an hour, and stopping one person from posing as the two neighbours an unconfirmed alert needs.
What other people see
Your position rounded to about 250 m, and the distance rounded to 100 m. The operator and moderators see the exact position.
“I see it too”
A confirmation stores the same things: your exact position, its accuracy, the compass direction and the hash of your network.
Legal basis
Your consent (GDPR art. 6(1)(a)): you send the report, and the app asks for location permission first.

Photos and videos

Before anything is uploaded, your own phone prepares the file. Photos are re-encoded through a canvas, which removes all metadata, GPS included. Videos are re-compressed on the phone with none of the original's metadata copied across; where the phone cannot do that, the original is sent with the location strings in the movie header zeroed out.

The capture time does travel with the report, because whether the alert is any use depends on it: it is read from the photo's EXIF or the movie header, never from the file's date. Anything not taken in the last 15 minutes is flagged as such, and anything older than 72 hours is refused.

Photos and videos are public as soon as you send them. There is no approval step: anyone with the link can see them, with no account. A moderator can reject a report, which hides its media. Think about what is in the frame: faces, number plates and people's windows are published too.

The files are kept in Cloudflare's object storage (R2).

Alerts on your phone

No account. What is stored is the minimum needed to deliver the alert.

The subscription
The delivery address your browser gives (at Apple, Google, Mozilla or Microsoft), its two keys, your language, and the first 200 characters of your browser's user-agent string.
Places you follow
Up to 6 public community places. Only their identifier, which is already public.
Areas you follow
Up to 3, and of each one only the centre of a 0.05° square (about 5 km). Your exact point is never sent: the app works out the square's centre on the phone and sends only that centre.
Deliveries
Which alert went to which subscription, the outcome and the HTTP status the push service returned. It is used to retry and to switch off dead subscriptions.
What Apple, Google, Mozilla or Microsoft see
The delivery address and the fact that a message is being sent, with its time. The text is end-to-end encrypted (RFC 8291, aes128gcm): the push service cannot read it, only your phone can.
How to delete it
Turning alerts off in the app deletes the subscription and everything it follows, there and then.
Legal basis
Your consent: the browser asks and you give it.

Your home pin

The pin you place lives in your browser's local storage (fireline_pin), together with the last saved answer so you can still read it with no signal. It is not uploaded to any account.

To work out your exposure, the coordinates travel inside the body of a request to /api/assess. They are used for that one calculation and nothing else: they are not written to the database, not cached and not logged. The answer comes back marked “no-store, private”. If the calculation fails, only the error's name is logged, never the request body.

When your pin is far from every community place, the weather is fetched from Open-Meteo using coordinates rounded to 0.05° (about 5 km), never the pin.

Map tiles are served through FIRELINE's own server, so the IGN never sees which area you look at.

The fireline_view cookie holds only “pin” or “place”, so the server knows which screen to open with. It never carries coordinates.

Accounts (optional)

They are only needed for moderation and for saving your own locations. Nothing most people use requires one.

What is stored
Your email address, the name and picture Google returns if you sign in with Google, when the account was created and your role. If you sign in with Google, the tokens Google returns are stored too.
The sign-in code
The 6-digit code is stored alongside your email until you use it or until it expires, after 10 minutes.
The session
This is where an IP address is stored: the sign-in library (Better Auth) writes the IP address and the user-agent string of the device that signed in, and the session lasts up to 60 days. It is the only place in FIRELINE where an IP address is written down.
Saved locations
The label you give them, the exact point and your alert preferences.
Legal basis
Performance of the service you asked for (GDPR art. 6(1)(b)) and legitimate interest in account security.

Feedback and address search

The feedback form
Stores your message, the category, the screen you were on, the language, an email address if you choose to type one, and a keyed hash of your IP to limit sending to 5 an hour. No location is attached.
Searching for an address
What you type travels in the request body, never in the URL, and FIRELINE's server queries CartoCiudad (IGN) with it. So your address never appears in access logs and your IP never reaches the IGN. The search is not stored.

What FIRELINE does not store

How long things are kept

The things you ask for are deleted at once: turning alerts off deletes the subscription and its follows, unfollowing a place deletes that follow, deleting a saved location deletes it — and the button at the end of this page deletes everything you have sent.

Everything else is cleared by a nightly clean-up (03:17 UTC): index calculations and written explanations older than 14 days (the newest for each place is always kept), copies of what each source returned older than 3 days, satellite detections older than 30 days, road incidents older than 7, and run logs older than 14. What the authorities said, and neighbours' reports, are never touched by it.

If you want something deleted sooner than that, use the button below or write, and it is done.

Cookies and what sits in your browser expire on their own, on the timescales in the table below. You can clear them yourself at any time in your browser settings.

Cloudflare keeps its own request logs according to its own retention, not FIRELINE's.

Who processes what

Companies that process data on FIRELINE's behalf, and sources FIRELINE reads without telling them anything about you.

Cloudflare, Inc.
Hosting for the app, storage for photos and videos (R2), the cache, the database connection (Hyperdrive) and the sending of sign-in emails. Every request passes through Cloudflare, so it sees your IP address in transit, and request logging on the server is switched on.
[PROVEEDOR DE LA BASE DE DATOS · DATABASE PROVIDER]
The managed PostgreSQL database that holds everything described on this page.
Apple, Google, Mozilla, Microsoft
Delivery of alerts to your phone, and nothing else. The text is encrypted and they cannot read it.
Resend
An alternative sender for the sign-in code when it is configured. It receives your email address and the message.
Anthropic
The written explanation for a public community place is drafted by a model from fire, weather and official-notice data. No personal data is sent to it, and never a private pin: private-pin screens always use the template text.
Open-Meteo
Receives coordinates rounded to about 5 km from FIRELINE's server when your pin is far from every community place. It never receives your pin or your IP address.
CartoCiudad (IGN)
Receives the text you type when searching for an address, from FIRELINE's server. Never your IP address.
Sources that receive nothing about you
IGN (base map, terrain and orthophoto, served through FIRELINE's own server), NASA FIRMS, EUMETSAT LSA SAF, EMA · Plan INFOCA (Junta de Andalucía), AEMET, Copernicus EMS, EFFIS and the DGT. FIRELINE polls them from its own server, on a fixed schedule, for the whole region. Your phone never calls them directly.

Your rights

You have the right to see your data, to correct it, to have it deleted, to object to its processing, to have it restricted, and to receive it in a portable format. Write to fireline@acedntl.com and you will get an answer.

Because without an account there is nothing that says who you are, deleting a specific report means telling us enough to find it: roughly when and from where you sent it. If you would rather not write, clearing the site's cookies in your browser cuts the link to that identifier, though a report already sent stays until you ask for it to be deleted.

For a device, the app itself is fastest: turning alerts off deletes its subscription and its follows there and then.

If you think this has been handled badly, you can complain to the Spanish data protection authority, the Agencia Española de Protección de Datos (www.aepd.es).

Cookies

Four cookies, none for advertising and none that track you across sites. That is why there is no consent banner.

fireline_reporter · 1 year
Remembers that this phone has sent reports, so you can see and recognise your own without an account, and so the waiting time between reports applies. It is a random identifier. HttpOnly, Secure, SameSite=Lax.
fireline_locale · 1 year
The language you chose. It holds only “es” or “en”. SameSite=Lax.
fireline_view · 1 year
Whether the app opens on your pin or on a community place. It holds only “pin” or “place”, never coordinates. SameSite=Lax.
__Secure-fireline.session_token · up to 60 days
Keeps you signed in. It exists only if you have signed in. HttpOnly, Secure.
Also, in your browser's storage
The pin you placed (fireline_pin), the last saved answer for reading with no signal (fireline_snapshot), the places and areas you follow (fireline_push_places, fireline_push_areas), your night-watch settings (fireline_watch_prefs), what you have ticked on the preparation list (fireline_prepare_done), and whether you have dismissed the install or language prompts. All of that stays on your phone; it is sent nowhere and it goes when you clear the site's data.

Changes to this page

When what the app does with data changes, this page changes and so does the date at the top. There are no archived earlier versions: what you read here is what the code does today.

Delete what I have sent

This deletes your reports, their photos and videos, and your confirmations. With an account it also deletes your saved locations and alerts. It cannot be undone.

FIRELINE is not an official emergency service. In an emergency, call 112.

Last reviewed: 19 September 2026.