OremuS privacy policy
OremuS privacy policy
Version 1.6 — 11.11.2026
1 Scope of this information
OremuS processes the data needed to maintain an account, publish intentions, record voluntary support and handle communities, moderation and contact. We do not sell users' data or use prayer history for advertising.
2 Data and legal bases for processing
Account data includes a name, city, email address, securely protected password, registration and login dates, and information about permissions and acceptance of the rules. It is used to provide the service and protect the account (Article 6(1)(b) and (f) GDPR); legal obligations are fulfilled under Article 6(1)(c).
We may store the country entered in the profile or identified from an unambiguously recognised parish. Language and a city name alone are not used to assign a country automatically. Presence statistics use only the most recent presence date of a signed-in account and a consecutive-day counter; no detailed sign-in history is created. These data support account administration and statistics, with account breakdowns accessible to the main administrator.
Intention text, prayer activity, membership and an optionally provided parish may reveal religious beliefs, and intentions may also contain health information. Where consent is the basis, explicit consent to the specific purpose is required (Article 6(1)(a) and Article 9(2)(a)). Consent to publish intentions is separate from consent to support history and from accepting the terms. It is not repeated for every post. Updating the app does not give consent on the user's behalf.
Providing a parish is optional. Its official name and address may be completed from a verified directory. If the name is ambiguous, the user selects the correct entry and may also enter the details manually. Queries to the local directory are not sent to an external search engine.
The reason for deleting an account is optional feedback used to improve the service. It is stored separately, without an account identifier, on the basis of the operator's legitimate interest. Personal or health data should not be entered there. Leaving it blank does not prevent account deletion.
Push notifications use the weekly-summary and Sunday-invitation settings, time zone, a random installation identifier linked to the account, platform, Firebase Cloud Messaging (FCM) token, its SHA-256 hash, permission status and update dates. A weekly record contains the date, aggregate supporter count, optional intention identifier and technical delivery status, without a list of supporters. The choice of emails about Android test versions is stored separately. For account administration and aggregate platform statistics, we retain the last platform, app and system versions reported at sign-in and their report date, without a detailed device history.
The summary uses the supporter count from the past week, while selection of a Sunday invitation may use the number of days of the user's own prayer activity in the current week and the availability of intentions.
3 Visibility and recipients
Public intentions are available to all recipients, while private intentions are available only to people with the appropriate access. Do not include information identifying another person without an appropriate basis for publication. A name and city may appear with a post according to the publication method; account contact details are not a public signature.
The exact form of prayer and private support history are not shown to other users. Aggregate support counts may be displayed. Administrators and moderators receive only the access needed for their duties. Authorised community leaders receive the data necessary to handle membership; sharing additional data for reviewing a request requires a separate user choice. Private content is no longer provided after access is lost.
Data may be received by entities providing necessary hosting and message delivery for the operator, on an appropriate basis and within the scope of the service. We disclose data to public authorities only where there is an appropriate legal basis.
For notifications, Google FCM and, on iOS, Apple APNs receive technical data as described in section 7. The general notification text and app name may reveal a religious context to someone viewing the phone screen; presentation on the lock screen also depends on system settings.
4 Voluntary consent and withdrawal
Users can browse public content without consenting to publication or to recording their own history. Consent can be withdrawn free of charge and without deleting the account by contacting wmsoftwarehouse@gmail.com and specifying the relevant purpose. Account deletion also ends processing based on those consents. Withdrawal does not affect the lawfulness of earlier processing; further retention requires another appropriate basis. Users can independently delete their existing intentions.
Guest support is linked to a random identifier and requires explicit consent. A guest can delete its data on the device without creating an account.
Before push registration, the app explains the feature and offers a separate choice to enable notifications or defer the decision. Notifications also require the device's system notification permission. Weekly summaries and Sunday invitations can be disabled independently in the app's notification settings; both switches are enabled by default, which does not itself grant system permission. Notifications can also be disabled in phone settings. Emails about Android test versions are a separate choice, disabled by default, which can be withdrawn in tester settings. These choices do not change consent to publication or prayer history. Opening this policy or updating the app does not give consent to a new processing purpose.
5 Retention periods
Account data is retained until account deletion or the earlier end of the relevant purpose. Support history is retained until its deletion, consent withdrawal or account deletion. A guest identifier expires after 90 days; linked data is removed during retention reviews.
An intention is archived one year after its first publication. Editing does not restart that period. Archiving does not change the audience or create a right to retain personal data indefinitely. Continued retention needs are reviewed; the author may delete a post or exercise data rights.
Moderation cases, decisions and closed applications are generally deleted after one year, subject to earlier deletion of related data and justified legal obligations. Optional feedback on leaving is deleted after 90 days. Minimal consent evidence and data necessary for accountability or claims are retained only for the necessary period for that purpose; we do not retain the entire prayer history as evidence.
After account deletion, its published intentions are hidden pending an anonymisation assessment. They may remain only after information identifying a person, including links within the text itself, has been removed; the signature “A person known to God” alone is not sufficient.
Copies of administrative notices and their delivery requests in OremuS are deleted after 90 days or earlier with the account.
Push settings, the tester-email choice and the last platform data are retained until account deletion. Weekly notification records and their delivery statuses older than 90 days are removed by retention reviews. Reviews also remove device records without permission or a token whose last update is older than 90 days. Active registrations remain until disabled or the account is deleted. Reviews run every 6 hours regardless of whether sending is enabled; downtime may delay cleanup. Disabling a registration clears the token and its hash but does not mean immediate deletion of provider-held data.
An account-recovery code is valid for 10 minutes. Its encrypted delivery request is removed after sending or expiry; the challenge state and attempt-limiting counters are removed once more than 2 days have passed since issue, or earlier with the linked account. Codes, their hashes and security secrets are not exported.
6 Device storage and security
On the device we store preferences, a draft, basic profile data, a membership list, the full history of the user's own intentions, up to 100 recent prayer-history entries, the latest statistics with their update date, and two sets of the 33 newest intentions: public intentions and those matching the last filter. Duplicates are merged. The second set may include private content available to the account at its last connection. When connection returns, we check access; confirmed loss of membership removes cached previews of other people's private content in that community and pending support relating to it. The author's own history remains available under the rules governing their data.
Account data is separated between users and protected by the device operating system's secure-storage mechanisms. After the first successful online login, the app retains an encrypted profile and session for signing in again offline. The password is not stored in plain text; the unlocking key is derived from the password entered. Signing out removes current access, the active-session key and any unsaved draft, while retaining the protected profile and account cache. Confirmed server revocation removes the data enabling offline login for the active account. Security changes made remotely can be recognised only after connecting to the server. The phone should be protected with a device lock.
Support given offline waits on the device and, after reconnection, is sent once after checking the session, consent and access. It is not sent from another account or after confirmed loss of permissions. Where consent has been given, saving one's own intention adds one brief prayer to personal statistics; its detailed type is not published to others. Local copies can be removed by clearing app data as supported by the operating system; remote account deletion or access changes are recognised on the device at its next connection.
We use access controls, securely protected passwords and communication protection appropriate to the environment. We do not make decisions about users with legal effects solely through automated processing.
For push, the device retains a random OremuS installation identifier and a versioned local choice to enable or defer notifications for the account. The identifier is removed at sign-out; the local choice has no separate expiry and remains after sign-out until app data is cleared. The Firebase SDK manages its own registration data. Sign-out attempts to unregister the device and remove its token and system notifications; without internet, completion on the server or at the provider cannot be confirmed.
Reporting a problem opens a draft in the email app with the app version, platform and system version. The user chooses the description and any image and sends the message themselves. A copy of the selected image, up to 10 MB, is stored in the app cache; it is removed when the attachment is replaced or removed and at sign-out. Copies older than 24 hours are cleaned up when tester or reporting screens are next opened, rather than automatically at a particular time. The original image is unchanged. Copying text or a code to the clipboard requires a user action; the app does not automatically clear clipboard contents.
The attachment copy may retain metadata from the selected file; its contents should be checked before sending.
7 External services and transfers
The support link opens Zrzutka.pl, which is responsible for data relating to visits and payments under its own policy. OremuS does not store card details or pass account, prayer-history or membership information in the link. Email and other voluntarily opened services have separate rules.
Before starting processing that requires transfers outside the EEA, the operator informs users about recipients, countries and appropriate safeguards. A configuration change does not replace a required legal basis.
Push is delivered through Google Firebase Cloud Messaging and, on iOS, Apple Push Notification service (APNs). We transmit the device token, notification and recipient-account identifiers, an optional intention identifier, the opening target and general text in the account language, which may include an aggregate supporter count. We do not attach intention text, a name, email address or list of supporters. Identifiers are pseudonymous, not anonymous. Providers may also process technical service data such as installation identifiers and IP addresses. Communications are encrypted in transit, but OremuS does not provide end-to-end encryption for push notifications.
FCM infrastructure is global; Google and Apple may process data outside the EEA, including in the United States. OremuS deletion periods do not determine retention by Google, Apple or email services; deleting a token does not confirm deletion of all provider-held installation data. Firebase information is available at https://firebase.google.com/support/privacy. Information about the relevant recipients, countries and transfer safeguards, and copies of the appropriate safeguards, can be requested from the operator at the contact address in this policy.
Google describes the Data Privacy Framework (DPF) mechanism and, depending on the circumstances, standard contractual clauses in its processing terms: https://firebase.google.com/terms/data-processing-terms. Apple describes standard contractual clauses for transfers of EEA data in its policy: https://www.apple.com/legal/privacy/en-ww/. These are descriptions of provider mechanisms, not a statement that data remains exclusively in the EEA.
8 User rights
Within the limits of the GDPR, users have rights of access and a copy of data, rectification, erasure, restriction of processing, portability and objection to processing based on legitimate interests. Consent may be withdrawn at any time. Copies of data are provided on request to the operator. Users may lodge a complaint with the President of the Polish Personal Data Protection Office. Requests are sent to wmsoftwarehouse@gmail.com; the operator normally responds within one month, subject to statutory exceptions and possible identity verification.
In the app, users can download a JSON copy of their server-held data after signing in and confirming their password. It also includes their own push switches, minimal device information, weekly notification metadata, tester-email choice and last platform data, without raw push tokens, their hashes, recovery codes or other secrets. The downloaded file should be protected. Account deletion removes the linked settings, device registrations, weeks and delivery statuses, tester choice, platform data and recovery data on the server. It does not immediately erase copies on an offline device, in a mailbox or held by a provider.
9 Changes and contact
The current policy is available in the app. The operator provides notice of material changes before new processing starts; a new purpose requiring consent is enabled only after obtaining it. Continued use does not replace that consent. Questions about data may be sent to wmsoftwarehouse@gmail.com.
This update describes notifications, tester features and data copies. It does not give new consent on the user's behalf or replace the separate choices described above.
10 Data controller
The controller of personal data is Jakub Tomczewski, a natural person running a private project under the WMSoftwareHouse brand. Correspondence address: ul. Marii Konopnickiej 9/4, 74-101 Gryfino, Poland. Email: wmsoftwarehouse@gmail.com.