Privacy Policy

Last updated: October 26, 2026

This policy explains what FlUck (https://fluck-camera.com), operated by The FlUCK Team, collects and how it is used. We keep it short because we collect little: no accounts, no cookies, no advertising, no analytics and no trackers.

What we collect

Sightings (reports from cameras)

• The vehicle class (for example "marked patrol"), a confidence score, the time, and the precise coordinates reported by the camera.
• The licence plate or unit number of police vehicles. The server rejects plates sent for any other vehicle class, and one-tap phone reports never carry a plate.
• For phones: GPS accuracy and heading.

We store precise coordinates but publish only a delayed (currently 3 minutes) and rounded (about 100 m) location.

Camera registration

• The hacker handle and camera name you choose (both public), the camera type (phone, built unit or webcam), when it registered and when it was last heard from, and a one-way hash of its key (we cannot read the key back).
• Optional live position: only if you switch on sharing (phones: off by default; built units and webcams: on by default, can be turned off), the camera's most recent position is stored, overwritten at each check-in, and shown publicly (rounded) only while the camera is online.

Network information

• To prevent abuse we keep your IP address briefly (for rate limits: about one minute for attempts and up to one hour for registrations), then it is deleted.
• Our web host keeps ordinary server logs (IP address, time, page requested). Those logs are managed by the host under its own policy.

Live tags

A live tag stores the place you tapped (precise until it is deleted a day after it expires), the time, how many people said it was still there or gone, and a keyed hash of your IP address so one visitor can't vote twice. If you tag from a registered camera, the tag is linked to that camera. Tags show on the map only at the usual ~100 m blur and disappear after about 45 minutes.

Photos from cameras (optional)

A camera may attach a small photo of a police vehicle to a sighting so the site owner can check a flagged or unsure report. Photos are never part of the map or downloads. For an unsure detection waiting for a check, the photo may be shown to volunteer reviewers on the review page (without exact location or camera name); it is deleted the moment the detection is decided, and in any case after 7 days or with the sighting. Reviewers' votes are kept with a keyed hash of their IP address, not the address itself.

Camera health

Raspberry Pi cameras may report their temperature, free disk space and load so the owner can notice a failing unit. This is visible only to the owner.

Following by e-mail or browser notification (optional)

If you choose browser notifications we store your browser's push address (a long address from your browser vendor, not your name) and what you follow; the notification itself carries no data. Delete it by turning notifications off in your browser or from the follow dialog.

Following by e-mail (optional)

If you ask to be e-mailed about a plate or an area, we store your e-mail address and what you follow, and send a confirmation link first. We use it only to send those e-mails. Every e-mail has an unsubscribe link, which deletes the address at once. Addresses that are never confirmed are deleted after a week. We do not sell or share it.

Flags and removal requests

When you flag a sighting we keep the sighting number, your reason, and a one-way keyed hash of your IP address (so one visitor counts once), not the address itself. A removal request form keeps what you type, including a contact address if you give one, until the request is dealt with.

Backups

The operator's server keeps a few recent copies of the database (sightings, cameras, followers' e-mail addresses and requests, and a log of the operator's own moderation actions) in a private folder for recovery. Old copies are overwritten automatically.

Nothing else

Otherwise we do not collect your name, phone number or precise device identifiers, and we do not use advertising or analytics services.

Cookies and device storage

We set no cookies. The phone app stores, on your own device, the camera's key, your handle and its offline queue of reports (browser local storage and IndexedDB), because it cannot work without them. The admin page keeps the admin key in session storage until the tab closes. You can clear this at any time in your browser; clearing it logs the phone out of its camera.

Why we use it

To show the map, let you follow a vehicle across cameras, show which cameras are online, prevent abuse and keep the Service running and secure. We do not sell your data.

Third parties

• Map tiles are loaded from the OpenStreetMap Foundation's servers, which therefore see your IP address and the area you view (their policy).
• Our web host stores and serves the site and its database.
• We may disclose information if required by law, court order or valid legal process, or to protect people's safety or the Service.

How long we keep it

Sightings are deleted automatically after a retention period (90 days by default; the operator may change it). Camera records stay until the camera is removed. Deleted data may persist briefly in host backups.

Your choices and rights

• Remove a camera and everything it sent, or correct or remove a vehicle recorded in error: contact us. Depending on where you live (for example the EU/UK or California) you may have rights to access, correct, delete or object to the use of your personal data; contact us and we will help.
• You can stop sharing a camera's position at any time (the phone app's switch, or --no-share-location on a Pi).

Licence plates and public information

Licence plates of police vehicles are shown as they were read. Vehicles are meant to be police vehicles only; if you believe a plate was recorded in error, tell us and we will remove it.

Children

The Service is not directed to anyone under 18, and we do not knowingly collect information from children.

Security

We use HTTPS where available, store camera keys only as hashes, and limit access to the admin tools. No system is perfectly secure; please report problems (see Contact).

Changes

If this policy changes, the date above changes. Continued use means you accept the update.

Contact

Email fluckteam@proton.me.