Mobile Team
Politika privatnosti · Privacy Policy · Poslednja izmena / Last updated: 9. 10. 2026.
Politika privatnosti
Aplikaciju Mobile Team razvija i održava Milan Jovanovic, fizičko lice, za tim volontera na terenu. On je rukovalac podacima o ličnosti opisanim ovde. Kontakt: miland.sm@gmail.com.
Mobile Team služi za dobrovoljnu koordinaciju terenskog tima: ljudi u grupi sami biraju da međusobno dele lokaciju, vide se na mapi, postavljaju upozorenja i šalju SOS grupi, a lider grupe može da nacrta ogradu u kojoj tim treba da se kreće. Niko ne mora da deli lokaciju: svako za sebe uključuje i zaustavlja deljenje.
Koje podatke obrađujemo
- Nalog: mejl adresa, ime koje upišeš, uloga (lider ili član; pešak ili mobilni tim) i grupa kojoj pripadaš. Lozinku čuva Google Firebase Authentication; mi je ne vidimo.
- Kod za prijavu: pri svakoj prijavi šaljemo ti jednokratni kod mejlom, preko servisa Resend. Čuvamo samo njegov otisak (hash) i adresu na koju je poslat.
- Lokacija: samo dok ti uključiš deljenje lokacije. Dok deljenje traje, aplikacija čita lokaciju i kad je u pozadini ili je ekran zaključan (na iPhone-u se tada vidi plava oznaka, na Androidu obaveštenje „Deljenje lokacije“). Članovi tvoje grupe vide tvoju trenutnu poziciju, smer i brzinu kretanja, SOS ako ga uključiš i da li si van ograde. Čuvamo i tragove kretanja, da bi grupa videla pređeni put. Kad zaustaviš deljenje, tvoja poslednja pozicija ostaje sačuvana, ali se ne prikazuje dok ponovo ne podeliš lokaciju. Kad deljenje nije uključeno, aplikacija ne čita lokaciju, osim Mapbox-ove telemetrije, opisane ispod.
- SOS: kad uključiš SOS, članovi grupe ga vide na mapi i svima u grupi stiže obaveštenje na telefon. SOS ne poziva hitne službe; u hitnom slučaju pozovi 112.
- Upozorenja koja postaviš na mapi (vrsta, mesto i vreme) i ograda grupe koju nacrta lider.
- Token za obaveštenja tvog uređaja, da bi lider dobio obaveštenje kad neko zatraži ulazak u grupu ili izađe iz ograde i da bi grupa dobila obaveštenje kad neko uključi SOS.
- Izveštaji o padu aplikacije (Firebase Crashlytics): kad se aplikacija sruši ili naiđe na grešku, šalje opis greške, model uređaja, verziju sistema i aplikacije i nasumični identifikator instalacije. Ne šalje mejl ni ime.
- Provera aplikacije (Firebase App Check): da bi server prepoznao zahteve prave aplikacije sa pravog uređaja, telefon dobija potvrdu od Apple-a (App Attest, DeviceCheck) ili Google-a (Play Integrity) i šalje je Google-u. Potvrda ne sadrži tvoje podatke iz aplikacije. Za sada te provere samo pratimo i ne odbijamo zahteve.
- Mapbox (mapa): aplikacija preuzima mapu od Mapbox-a. Za mobilni tim deo pozicija šaljemo Mapbox servisu Map Matching, da bi se putanja poravnala sa putem. Mapbox-ov deo aplikacije može da prikuplja podatke o korišćenju mape i lokaciji uređaja (telemetrija) za Mapbox-ovu analitiku, prema Mapbox-ovoj politici privatnosti.
- Tehnički zapisi servisa (na primer greške), koje beleži Google Cloud.
Svaki servis vidi IP adresu uređaja, jer bez nje veza ne radi. Podatke ne koristimo za reklame, ne prodajemo ih i ne pravimo profile.
Ko vidi podatke
- Članovi tvoje grupe: tvoje ime, ulogu, poziciju dok deliš lokaciju, tragove kretanja, SOS i upozorenja.
- Lider tvoje grupe vidi i mejl adrese članova grupe.
- Administrator aplikacije vidi naloge i grupe, radi upravljanja nalozima.
Pravni osnov
Ovo je opis prostim rečima, a ne pravni savet.
- Nalog, grupa i prijava: potrebni su da bismo ti pružili aplikaciju koju koristiš.
- Deljenje lokacije, SOS i obaveštenja: tvoj pristanak. Deljenje i SOS uključuješ ti, a dozvole daješ u telefonu. Pristanak povlačiš kad god hoćeš: zaustaviš deljenje, isključiš SOS ili oduzmeš dozvolu. To ne menja zakonitost obrade pre toga.
- Bezbednost i ispravan rad (provera aplikacije, izveštaji o padu, tehnički zapisi): naš legitimni interes da servis radi i da bude zaštićen od zloupotrebe.
- Zapis obrisane grupe: naš legitimni interes da razumemo kako se aplikacija koristi (na primer koliko grupe traju i koliko su velike), da bismo je poboljšali. Na to možeš da uložiš prigovor.
Servisi koje koristimo (obrađivači) i kanali distribucije
- Google Firebase (Authentication, Cloud Firestore, Cloud Functions, Cloud Messaging, Crashlytics, App Check, Hosting): nalozi, čuvanje podataka, obaveštenja, izveštaji o padu, provera aplikacije i ove stranice. Baza (Cloud Firestore) i funkcije (Cloud Functions) su u Evropskoj uniji, a nalozi za prijavu (Authentication) u SAD.
- Resend (Plus Five Five, Inc., SAD): slanje mejlova sa kodom za prijavu. Resend vidi adresu na koju šaljemo kod i sadržaj mejla.
- Mapbox: mapa, Map Matching i telemetrija mape.
- Apple (App Store, TestFlight) i Google (Google Play, Firebase App Distribution): distribucija aplikacije. Za preuzimanje važe i njihova pravila privatnosti.
- Shorebird: isporuka ispravki aplikacije. Ne šaljemo mu lične podatke.
Koliko dugo čuvamo podatke
- Tragovi kretanja: 31 dan, pa se automatski brišu.
- Upozorenja: 7 dana, pa se automatski brišu.
- Poslednja pozicija: dok ne napustiš grupu ili obrišeš nalog, a najduže 31 dan posle poslednjeg deljenja.
- Nalog (mejl, ime, uloge, grupa): dok ne obrišeš nalog.
- Kod za prijavu: briše se kad ga iskoristiš ili zatražiš novi, a najkasnije 7 dana posle slanja.
- Pozivi u grupu: svaki poziv važi 10 minuta ili dok ga neko ne iskoristi. Uz njega čuvamo grupu i interne identifikatore lidera koji ga je napravio i osobe koja ga je iskoristila. Poziv se čuva 7 dana posle isteka, i kad obrišeš nalog, pa se automatski briše.
- Zapis obrisane grupe: kad grupu napusti poslednja osoba u njoj (lider), grupa se zatvara, ali ostaje zapis o njoj: naziv, boja, ograda, poslednji spisak članova i interni identifikator bivšeg lidera. Na tom spisku je samo bivši lider (ime, uloga i uloga na terenu). Zapis se čuva 12 meseci od zatvaranja grupe, i kad bivši lider obriše nalog, pa se automatski briše. Tragovi kretanja i upozorenja iz te grupe brišu se po istim rokovima kao i ostali.
- Izveštaji o padu: 90 dana. Tehnički zapisi: do 30 dana.
- Rezervne kopije baze: najviše 7 dana.
- Podaci za prijavu (Firebase Authentication) posle brisanja naloga: nestaju iz Google-ovih rezervnih kopija najkasnije 180 dana posle brisanja.
- Mejlovi sa kodom: šalje ih Resend, koji svaki poslati mejl (adresu, naslov i tekst sa kodom, koji važi samo 10 minuta) i zapis o njegovoj isporuci čuva 30 dana od slanja. Iz Resend-ovih rezervnih kopija sve to nestaje najkasnije 7 dana kasnije (najviše 37 dana od slanja). Ako mejl ne može da se isporuči ili ga označiš kao neželjenu poštu, Resend tvoju adresu čuva na listi blokiranih adresa dok je ne uklonimo; piši nam ako želiš da je uklonimo. Kopiju poslatih mejlova ne čuvamo u svom sandučetu.
Automatsko brisanje se obično izvrši u roku od jednog dana posle isteka roka.
Kad obrišeš nalog (Grupa → Obriši nalog), brišemo nalog, sesiju, token za obaveštenja, zahteve za pridruživanje, poslednju poziciju, sve tvoje tragove kretanja i upozorenja i tvoje mesto na spisku članova (osim na zapisu obrisane grupe, vidi gore). Lider koji briše nalog prvo bira novog lidera; ako u grupi nema nikog drugog, grupa se zatvara zajedno sa nalogom. Kad napustiš grupu ili te lider ukloni, briše se tvoja poslednja pozicija. Detalji i brisanje bez aplikacije: Brisanje naloga.
Prenos podataka van Evropske unije
Baza (Cloud Firestore) i funkcije su u Evropskoj uniji. Podatke za prijavu (mejl adresu i otisak lozinke) čuva Google-ov servis Firebase Authentication, koji radi samo u SAD. Google, Mapbox i Resend su američke kompanije, pa i ostali deo obrade (na primer slanje obaveštenja i mejlova sa kodom, izveštaji o padu, provera aplikacije i servisi mape) može da se odvija u SAD; Resend poslate mejlove čuva u SAD. Takav prenos se zasniva na primeni standardnih ugovornih klauzula Evropske komisije, koje su deo ugovora tih kompanija o obradi podataka; Google i Resend se oslanjaju i na Okvir za privatnost podataka EU–SAD (EU-U.S. Data Privacy Framework).
Tvoja prava
Imaš pravo na pristup svojim podacima, ispravku, brisanje, ograničenje obrade, prenosivost i prigovor, kao i pravo da povučeš pristanak, u skladu sa Zakonom o zaštiti podataka o ličnosti Republike Srbije i Opštom uredbom o zaštiti podataka (GDPR). Piši nam na miland.sm@gmail.com. Imaš i pravo da podneseš pritužbu Povereniku za informacije od javnog značaja i zaštitu podataka o ličnosti.
Deca
Aplikacija nije namenjena osobama mlađim od 16 godina.
Izmene
Novu verziju ove politike objavićemo na ovoj stranici, sa datumom izmene.
Privacy Policy
Mobile Team is developed and maintained by Milan Jovanovic, an individual, for a volunteer field team. He is the controller of the personal data described here. Contact: miland.sm@gmail.com.
Mobile Team is for the voluntary coordination of a field team: people in a group choose to share their location with each other, see each other on a map, place warnings and send an SOS to the group, and the group's leader can draw a fence the team should stay inside. Nobody has to share their location: each person turns sharing on and off for themselves.
Data we process
- Account: email address, the name you enter, your role (leader or member; on foot or mobile team) and your group. Your password is held by Google Firebase Authentication; we never see it.
- Sign-in code: each sign-in sends you a one-time code by email, through the Resend service. We keep only its hash and the address it was sent to.
- Location: only while you turn on location sharing. While sharing is on, the app reads your location also in the background or with the screen locked (an iPhone shows a blue indicator; Android shows a "Deljenje lokacije" notification). Members of your group see your current position, direction and speed, an SOS if you turn it on, and whether you are outside the fence. We also keep your movement trail so the group can see where you have been. When you stop sharing, your last position stays stored but is not shown until you share again. When sharing is off, the app does not read your location, apart from Mapbox's telemetry, described below.
- SOS: when you turn on SOS, your group's members see it on the map and everyone in the group gets a notification on their phone. SOS does not call emergency services; in an emergency, call 112.
- Warnings you place on the map (type, place, time) and the group's fence drawn by the leader.
- Notification token of your device, so the leader can be notified when someone asks to join the group or leaves the fence, and the group when someone turns on SOS.
- Crash reports (Firebase Crashlytics): when the app crashes or hits an error, it sends a description of the error, the device model, the system and app versions and a random installation id. It does not send your email or name.
- App verification (Firebase App Check): so the server can recognise requests from the genuine app on a genuine device, the phone gets an attestation from Apple (App Attest, DeviceCheck) or Google (Play Integrity) and sends it to Google. The attestation contains none of your data from the app. For now we only monitor these checks and do not reject requests.
- Mapbox (maps): the app loads its map from Mapbox. For mobile teams, some positions are sent to Mapbox Map Matching to align the trail with the road. Mapbox's part of the app may collect map usage and device location data (telemetry) for Mapbox's own analytics, under Mapbox's privacy policy.
- Technical logs of the services (for example errors), recorded by Google Cloud.
Every service sees your device's IP address, since a connection cannot work without it. We do not use the data for advertising, do not sell it and do not build profiles.
Who sees the data
- Members of your group: your name, role, position while you share, movement trail, SOS and warnings.
- Your group's leader also sees the email addresses of the group's members.
- The app's administrator sees accounts and groups, to manage accounts.
Legal basis
This is a plain-language summary, not legal advice.
- Account, group and sign-in: needed to provide the app you use.
- Location sharing, SOS and notifications: your consent. You turn on sharing and SOS yourself and grant the permissions on your phone. You can withdraw consent at any time by stopping sharing, turning SOS off or removing the permission; this does not affect processing before that.
- Security and a working service (App Check, crash reports, technical logs): our legitimate interest in a service that works and is protected from abuse.
- A deleted group's record: our legitimate interest in understanding how the app is used (for example how long groups last and how large they get), to improve it. You can object to this.
Services we use (processors) and distribution channels
- Google Firebase (Authentication, Cloud Firestore, Cloud Functions, Cloud Messaging, Crashlytics, App Check, Hosting): accounts, data storage, notifications, crash reports, app verification and these pages. The database (Cloud Firestore) and functions (Cloud Functions) are in the European Union, and the sign-in accounts (Authentication) in the US.
- Resend (Plus Five Five, Inc., US): sending sign-in code emails. Resend sees the address we send the code to and the email's content.
- Mapbox: maps, Map Matching and map telemetry.
- Apple (App Store, TestFlight) and Google (Google Play, Firebase App Distribution): app distribution. Their own privacy terms apply to downloads.
- Shorebird: delivering app updates. No personal data is sent to it.
Retention
- Movement trails: 31 days, then deleted automatically.
- Warnings: 7 days, then deleted automatically.
- Last position: until you leave the group or delete your account, and at most 31 days after you last shared.
- Account (email, name, roles, group): until you delete the account.
- Sign-in code: deleted when you use it or request a new one, and at the latest 7 days after it was sent.
- Group invites: each invite is valid for 10 minutes or until someone uses it. With it we keep the group and the internal user ids of the leader who created it and of the person who used it. An invite is kept for 7 days after it expires, also when you delete your account, and is then deleted automatically.
- A deleted group's record: when the last person in a group (its leader) leaves, the group is closed but a record of it stays: its name, color, fence, final member list and the former leader's internal user id. Only the former leader is on that list (name, role and field role). The record is kept for 12 months from the group's closing, also when the former leader deletes their account, and is then deleted automatically. Movement trails and warnings recorded in that group are deleted under the same periods as all others.
- Crash reports: 90 days. Technical logs: up to 30 days.
- Database backups: 7 days at most.
- Sign-in data (Firebase Authentication) after an account is deleted: gone from Google's backups within 180 days of the deletion.
- Sign-in code emails: they are sent by Resend, which keeps each sent email (the address, the subject and the text with the code, valid for only 10 minutes) and the record of its delivery for 30 days after it was sent. It is all gone from Resend's backups 7 days later at most (37 days after it was sent at most). If an email cannot be delivered or you mark it as spam, Resend keeps your address on its list of blocked addresses (suppression list) until we remove it; write to us if you want it removed. We keep no copy of sent emails in a mailbox of our own.
Automatic deletion usually happens within a day after a period ends.
When you delete your account (Grupa → Obriši nalog), we delete the account, the session, the notification token, your requests to join, your last position, all your movement trails and warnings, and your place on the member list (except on a deleted group's record, see above). A leader who deletes their account first picks a new leader; if nobody else is in the group, the group is closed together with the account. When you leave a group or the leader removes you, your last position is deleted. Details, and deletion without the app: Account deletion.
Transfers outside the European Union
The database (Cloud Firestore) and functions are in the European Union. Your sign-in data (email address and password hash) is held by Google's Firebase Authentication, which runs only in the US. Google, Mapbox and Resend are US companies, and other parts of the processing (for example sending notifications and sign-in code emails, crash reports, app verification and map services) can also take place in the US; Resend stores the emails it sends in the US. Such transfers rely on the European Commission's standard contractual clauses, which are part of these companies' data processing terms; Google and Resend also rely on the EU-U.S. Data Privacy Framework.
Your rights
You have the right to access, rectify and erase your data, to restrict processing, to data portability and to object, and to withdraw your consent, under the Serbian Law on Personal Data Protection and the GDPR. Write to miland.sm@gmail.com. You may also lodge a complaint with the Commissioner for Information of Public Importance and Personal Data Protection (Serbia) or your local supervisory authority.
Children
The app is not intended for people under 16.
Changes
We will publish any new version of this policy on this page, with its date.