Tumellano ena e fumaneha ka Sepolish le Senyesemane. Ka tlase ke mofuta oa Senyesemane.
Data Processing Agreement (DPA)
Effective: 13 November 2026
This Data Processing Agreement ("Agreement") under Article 28 GDPR forms part of the Ministry Assistant Terms. It is made between Codivine Sp. z o.o., Czarnochowice 579/10, 32-020 Czarnochowice, KRS 0001146954, NIP 6832143115 ("Processor", "we") and the congregation using the congregation features of the app ("Congregation", "Controller"), represented by the congregation's owner in the app. The Agreement is concluded when a congregation is created in the app and, for congregations that already exist, when they continue to use the congregation features after its effective date. On request sent to fluttercodivine@gmail.com we will send a copy signed by us.
1. Roles of the parties
The Congregation is the controller of the personal data that it and its members enter into the congregation part of the app ("Congregation Data"): it decides what data it enters, why, who has access to it and how long it is kept. We process Congregation Data only on behalf of the Congregation, to provide the service. This Agreement does not cover user account data (email address, name, phone number, subscription, profile photo) — we are its controller and the Privacy Policy describes it. Nor does it cover data a user keeps only on their own device.
2. Nature of the processing
The content of Congregation Data is encrypted on members' devices with the congregation key before it leaves the device. Only members of the congregation hold the key — neither we nor our sub-processors have it, so we cannot read the content of Congregation Data. Our processing is limited to: storing the encrypted data, transmitting it and making it available to members according to the permissions the Congregation grants, operating the congregation's links and web pages that the Congregation turns on, sending notifications, and deleting data. The only data we store without this encryption are the technical metadata needed for permissions and notifications and the territory card photos — Annex 2 lists them. We do not sell Congregation Data and do not use it for advertising, profiling or any purpose other than providing the service.
3. Instructions of the Congregation
We process Congregation Data only on documented instructions from the Congregation, including with regard to transfers to third countries. Instructions are: the Terms and this Agreement, settings and actions taken in the app by persons the Congregation has authorised (e.g. granting permissions, turning on a congregation web page, creating a link, deleting the congregation), and requests sent to us in writing or by email by the congregation's owner or an administrator. If the law requires us to process Congregation Data otherwise, we will inform the Congregation before processing, unless the law prohibits this. We will inform the Congregation without delay if, in our opinion, an instruction infringes data protection law.
4. Obligations of the Congregation
The Congregation is responsible for having a legal basis for processing Congregation Data and for informing the persons concerned. Congregation Data may reveal religious beliefs (Article 9 GDPR) — the Congregation assesses whether it may process it, e.g. under Article 9(2)(d) GDPR, and whether it must carry out a data protection impact assessment. The Congregation enters only the data it needs for its purposes, turns off in the settings any sections that may not be kept in its country, decides who has access and with what permissions, and takes care of the protection of its members' devices and passwords. The Congregation acknowledges that we cannot prevent a member from reading, copying or exporting data the Congregation has given them access to.
5. Confidentiality and security
Only persons who need it to maintain the service have access to the systems where we store Congregation Data, and they are bound by confidentiality. We apply the technical and organisational measures described in Annex 2 and will adapt them to the state of the art and the risk (Article 32 GDPR).
6. Sub-processors
The Congregation gives general authorisation to use the sub-processors listed in Annex 3. We will announce any intended addition or replacement of a sub-processor at least 30 days in advance on this page and in the app. The Congregation may object at fluttercodivine@gmail.com; if we cannot find a solution, the Congregation may stop using the congregation features and delete the congregation. Sub-processors are bound by data protection obligations no less protective than those in this Agreement. We remain liable to the Congregation for our sub-processors as for ourselves.
7. Transfers outside the EEA
The database that stores Congregation Data is located in the European Union (Google Cloud, European region: Belgium and the Netherlands). Some Google services the app uses — file storage, server functions, sign-in and notifications — also operate in the USA. Such transfers rely on the European Commission's adequacy decision (EU–US Data Privacy Framework, in which Google LLC participates) and on the standard contractual clauses concluded with Google. As an additional safeguard, the content of Congregation Data is encrypted on members' devices with a key that neither Google nor we hold. The Congregation instructs us to make such transfers.
8. Data subject rights
Because the content of Congregation Data is encrypted, the Congregation fulfils data subject requests (access, rectification, erasure, restriction, portability) itself in the app — it can view, correct, delete and export the data. If such a request reaches us, we will forward it to the Congregation without undue delay and help where we can, e.g. by removing a person's membership or account.
9. Personal data breaches
We will notify the Congregation of a breach affecting Congregation Data without undue delay and no later than 48 hours after becoming aware of it — in the app and by email to the congregation's owner and administrators. We will provide the information we have that the Congregation needs to notify the supervisory authority and the persons concerned (Articles 33 and 34 GDPR), and supplement it as it becomes available.
10. Assistance
Within the information available to us, we will assist the Congregation in meeting its obligations under Articles 32–36 GDPR, including data protection impact assessments and prior consultation with the supervisory authority.
11. Deletion
When the owner deletes the congregation in the app, we delete all Congregation Data and its files from our database. A congregation without a congregation subscription for 12 months (6 months if it only had a trial) is deleted automatically — the owner and administrators are notified 30 days before. Before deletion the Congregation can export its data from the app. We keep no separate backups of the database. Deleted data may remain in Google's systems for a while under its secure deletion procedures (up to about 6 months), without any access by us. If the law requires us to keep data longer, we will inform the Congregation.
12. Information and audits
We will make available to the Congregation the information necessary to demonstrate compliance with Article 28 GDPR and answer questions sent to fluttercodivine@gmail.com. The Congregation may carry out an audit or have it carried out by an auditor bound by confidentiality — at its own cost, with the date and scope agreed in advance, and without compromising the security of other congregations. Google's infrastructure is audited through Google's certifications and reports (including ISO/IEC 27001 and SOC 2).
13. Term and final provisions
This Agreement applies for as long as we process Congregation Data. For Congregation Data it takes precedence over the Terms and the Privacy Policy. We will announce changes to this Agreement at least 30 days in advance on this page and in the app. This Agreement is governed by Polish law. It is available in Polish and English; both versions are equally binding.
Annex 1. Details of the processing
Subject matter and purpose: storing, transmitting and making available to members of the congregation the data needed to organise the congregation's work (meeting programmes, assignments, meetings for field service, territories, duties, field service reports, communication). Duration: for as long as the congregation features are used and until deletion under section 11 and the retention periods in the Privacy Policy. Categories of data subjects: congregation members (with or without an account in the app), people visited in the ministry and residents of addresses in territories, speakers and representatives of other congregations, people who contact the congregation through its web page. Categories of data (depending on what the Congregation enters): names, contact details, addresses, emergency contacts, dates of birth and baptism, appointments and privileges, service group and family, assignments and attendance, absences, field service reports, territories with addresses and notes, shepherding visits, announcements, surveys and sign-ups, territory card photos. Special categories of data: the data may reveal religious beliefs.
Annex 2. Technical and organisational measures
• End-to-end encryption: the content of Congregation Data is encrypted on the device with AES-256-GCM using the congregation key. The congregation key reaches members encrypted with their public keys (X25519); neither we nor Google know it. • Key rotation: when a member is removed, the congregation gets a new key and the data is re-encrypted. • Congregation links and web pages: the decryption key is in the part of the address that browsers never send to the server; links expire and can be revoked. • Transport: encrypted connections (TLS). • Access control: account sign-in; database security rules admit only members of the congregation and only within their permissions; app verification (Firebase App Check). • Data not end-to-end encrypted: metadata needed for permissions and notifications (which account belongs to which congregation and with what permissions, when and to which group a report was submitted, who signed up for a shift, which accounts conduct a meeting for field service, recipients of substitute requests, the settings of the congregation's web page) and territory card photos. They are stored in Google's infrastructure, encrypted by Google, and available only under the congregation's access rules. • Minimisation and retention: automatic deletion after the periods in the Privacy Policy. • Organisation: access to the service consoles only for persons who maintain the service.
Annex 3. Sub-processors
Google Ireland Limited (Ireland) and Google LLC (USA) — Google Cloud and Firebase: database (EU region), file storage, server functions, sign-in, push notifications, website hosting. Basis for transfers to the USA: EU–US Data Privacy Framework and standard contractual clauses (Firebase Data Processing and Security Terms).