Privacy Policy
Start date: Septemba 27, 2026
1. Who we stay
Ministry Assistant help preachas plan an write down dea field service, keep notes, an — wea one local hui use um — make meeting programs, meetings fo field service, da public preaching schedule, peopo fo take ova an service reports. Da data controller fo da account an cloud features: Codivine Sp. z o.o., email: fluttercodivine@gmail.com. Most of wat you put in neva leave yoa phone. Dis policy explain exactly wat leave um, wen, to who, an fo how long.
2. Wat stay on da device an wat go to da cloud
Eryting you put in — hours, notes, territories, peopo you study wit, goals — firs get written to one database on yoa device. Um ony leave da device wen you turn someting on: • one account (email, name, an if you like one phone numba — need um fo sign in, fo frenz find you, an fo one subscription), • sync between yoa devices (you pick da provider: yoa Ministry Assistant account, Google Drive or iCloud), • one backup copy, • sharing someting wit one fren or sending one link (fo example one invite fo go field service), • joining one local hui. Da "Account (encrypted)" sync option encrypt yoa records on da device wit one key dat come from yoa encryption password. We no can read um. Da plain "Firebase" option no do dat — da app say dat on um.
3. Local hui
One local hui stay end-to-end encrypted. Names, meeting programs, assignments, da schedule of meetings fo field service wit places an online meeting details, meeting broadcast details, da public preaching schedule, lists of da ones who get da ok fo assignments, requests fo take ova, attendance an reports get encrypted on da phone wit one local hui key dat ony da members get. Oua server keep ciphertext an no can read notting. Da server do see technical metadata, cuz witout um da permissions an notifications no work: wat account belong to wat local hui an da permissions; wen one report wen get sent an to wat field service group; who wen sign up fo one cart shift; wat accounts run one meeting fo field service; wat accounts wen get one request fo take ova, who wen accept um an wat date um fo; da speaka's account fo one talk in anodda local hui; da local hui website settings. Da talk numba an title one speaka from anodda local hui pick on da invite page no stay encrypted — dey come from da public list of outlines. Members of da same local hui come frenz in da app by demself (dey see wat frenz see — look section 4). You can turn dis off in da privacy settings; da frenz you wen add yoaself stay. Service reports ony get sent wen you clearly say ok, an you can take back da ok. Dey go to yoa group ovaseah an his helpa, an one group summary go to da secretary. One report neva get sent by itself witout dat ok. Wen one member get taken out, da local hui key get changed so dat person no can read new stuff no moa. Da administrators an da ones wit da right permissions put in da local hui stuff. If you get questions about info in one local hui (fo example one entry on da peopo list), firs talk to da eldas of yoa local hui — we no can see dat stuff.
4. Sharing wit odda peopo
Frenz: one fren see yoa name an profile picha. Yoa las name, phone numba, email, local hui, role an dates each get dea own switch in yoa profile. Territories an peopo who stay interested dat you send to one fren go in dat fren's inbox as one copy. You an da person who get um can delete um, an um disappear by itself afta 30 days if nobody do notting wit um. Links (one local hui assignment, one week's program, one speaka invite, one task, one invite fo go field service, one request fo take ova) can be opened by anybody who get da link — dass wat dey stay fo. Da key fo decrypt stay in da part of da address dat browsers neva send to one server; links expire an you can cancel um anytime. Oua server keep da ansa to one link ("I can" / "I no can"). Da name of one person who join one open invite fo go field service or accept one request fo take ova stay encrypted wit da link key — ony da person who wen invite or ask can read um.
5. Da local hui website
One local hui can make da public preaching schedule, one literature request form, da notice board, one report form an da schedule of meetings fo field service open in one browser — fo peopo who no mo da app or ony fo members who sign in. Wat stay on dat kine page stay encrypted wit da key in da link, so da server no can read um. Anybody wit da link can see da page — dass why names (fo example of da ones on shifts or da conductors) ony show if da local hui turn um on. One local hui administrator can turn off certain pages, make peopo sign in, or turn off da browser access all togedda in da settings. Wen somebody wit no account sign up fo one shift or ask fo literature, da name, phone numba an notes dey put get encrypted in da browser wit da local hui key — ony da coordinator can read um in da app. Da browser rememba on da device wat shifts one request wuz sent fo; dat info no come to us. Analytics on dis website ony run if you say ok an neva get wat stay in da requests or da keys from da links.
6. Peopo who no use da app
Da app let you write down peopo you visit, dea addresses an notes, an local hui members who no mo one account. Dose peopo no stay oua users an neva agree to notting wit us — you (an, in one local hui, da administrators) decide wat fo write down an stay responsible fo um. Dass why: dat kine records stay on yoa device unless you turn on sync or sharing; in one local hui dey stay end-to-end encrypted; dea names ony show on da local hui website if da local hui turn names on; an da settings let you turn off whole sections (fo example addresses wea nobody wuz home, or peopo who stay interested) in countries wea dat kine records no stay allowed. If one of dose peopo ask fo get taken off, delete da record in da app — um disappear from yoa device, from yoa copies in da cloud an, afta da time down below, from oua servers. You can write to us too an we goin help.
7. Permissions
Contacts (if you like) — fo show wat contacts awready use da app. Yoa address book neva leave da phone: ony fingaprints (hashes) of email addresses an phone numbas dat no can turn back get sent, an notting from um get kept. Location (if you like) — fo show wea you stay on da territory map an fo show da territory mo close. Wea you stay no get sent to us. Da pin fo one meeting place or one cart place get set by hand on da map, not from wea you stay. Notifications (if you like) — remindas an local hui notifications. Local hui notifications neva get wat stay in one assignment or any names. Da title an short description also stay on da notification list in yoa account, so none of um get lost. Pichas an files (if you like) — territory card pichas, one person's picha, attachments on da notice board, backups.
8. Service providers
Google / Firebase (Ireland, USA) — sign in, database, file storage, server functions, push notifications, crash reports (Firebase Crashlytics), usage numbas in da app (Firebase Analytics, ony if you say ok — look section 9) an, on dis website, Google Analytics, dat no start till you say ok. RevenueCat (USA) — take care subscriptions. Um get yoa account ID an, fo help you, da name, email address an phone numba from yoa account. Apple an Google — take care da payments fo subscriptions. We neva see yoa card details. OpenStreetMap — map tiles. Wen you open one map, um send yoa IP address an da part of da map you looking at to dea servers. Google Maps (or anodda maps app) — ony wen you tap "Directions" or "Map" da address or point open in dat app. Zoom an odda online meeting services — da link open in dea app or website; we no give dem notting. Email delivery of service messages — technical info, no records from da app.
9. Usage numbas an crash reports in da app
Usage numbas (Firebase Analytics) stay off till you say ok. Da app ask one time; you can change yoa mind anytime in Settings → Privacy → Personal data → Usage statistics. Wen you take back da ok, um stop collecting right away an reset da numbas ID on da device. If you say ok, da app (on phones, tablets an in da browser) send events wit no name about wat features peopo use — fo example "one entry wen get add", "one backup wen get made", "wen sign up fo one shift" — wit general details like wea one entry wen come from, yeah/no flags, round numbas of peopo an how long one service entry. Google also write down da app version, da device model an operating system, da language an da country more or less (from da IP address, dat Google no keep). Da events stay link to one random ID of da app install an, wen you stay signed in, to one ID of yoa account dat no show yoa name, so yoa phone an tablet count as one user. Three groups get add too: yoa role in da preaching (fo example preacha or regula pionea), if you get PRO, an how much access you get in one local hui (none, member, wit permissions, administrator, owna). We neva send wat you put in: no names, addresses, notes, reports, local hui names or any odda local hui info, email addresses or phone numbas. We ony use da numbas fo undastand wat features help an wat need fo get betta. Advertising features an Google signals stay off: no advertising ID get collected an da info no get used fo ads or fo make ads personal. Da numbas stay fo 14 months an den get delete by demself. Legal basis: yoa ok (art. 6(1)(a) an art. 9(2)(a) GDPR). Da processor stay Google Ireland Limited; da info can go to Google LLC in da USA unda da EU–US Data Privacy Framework an standard contractual clauses. Test versions of da app neva send numbas. Crash reports (Firebase Crashlytics, ony on phones an tablets) get sent no matta wat da numbas setting stay, cuz witout um we no can fix da errors dat broke da app. One report get da error an da place in da code wea um wen happen, da app version, da device model, da operating system an one random install ID. Um no stay link to yoa account an no get yoa records. Legal basis: oua legitimate interest in one app dat work an stay safe (art. 6(1)(f) GDPR); you can say no by writing to us. Crash reports stay fo 90 days. Da processor stay Google Ireland Limited, same like up dea.
10. How long da info stay
• Records synced to yoa account: long as da account stay active. Afta one subscription pau dey stay fo one year, wit one warning 30 days befo dey get delete. • Delete markers fo sync: 180 days. • Service reports (also da ones sent through da website) an da group summaries fo da secretary: 2 years from da end of da month dey cova — wen you send one report you saying ok to dis. Afta dat dey get delete by demself. In da app da person who wen write um can delete dea report mo early, but not in da firs 60 days afta dey send um (so nobody can take back one report from da ovaseah da nex day). • Requests from da local hui website (one cart shift, literature) dat da coordinator neva accept: 30 days. • Requests fo take ova: up to 2 days afta da date of da assignment. • Da notification list: 60 days. • Announcements on da local hui notice board: till da date da local hui set fo um expire, or till somebody delete um. • Invite an sharing links: up to 120 days, most of um way shorta; task invites an copies sent to frenz: 30 days. • Deleting da account: eryting up hea get delete — yoa account document wit all da records an keys, both sides of ery friendship, being one member of one local hui, reports, invites, notifications, files. One local hui you wen own go to anodda administrator, or get delete if no mo. • One local hui wit no local hui plan: 12 months afta da plan pau (6 months if um ony had da free time); da owna an administrators get one notification 30 days befo um get delete wit da files. • Local hui cart shifts an sign-ups: 13 months; away times: till da end date dey wen put; literature requests dat wen get handed out: 90 days.
11. Security
Connections stay encrypted wen da info going. Local hui stuff, encrypted sync an backups get encrypted one mo time on da device, wit one key dat come from yoa encryption password. Dat mean we no can get back dat password fo you. Keep da recovery code dat show wen you set da password — witout da password or da code, nobody can read da encrypted info, not even us.
12. Yoa rights
You get da right fo see yoa info, fix um, delete um, limit or say no to how um get used, an get one copy. Most of dis you can do yoaself in da app: edit or delete records, turn off wat you no like share, or delete da account (Settings → account), an dat also take off da info up dea from oua servers. You can write to fluttercodivine@gmail.com too. If you tink we no take care yoa info right, you can complain to da President of da Personal Data Protection Office (Urząd Ochrony Danych Osobowych) in Poland.
13. Changes an contact
Dis policy can get updated. Big changes goin get announced in da app's update notes an on dis page, wit one new start date. Data controller: Codivine Sp. z o.o. Email: fluttercodivine@gmail.com