Doamne Ajuta Privacy Policy

Last updated: August 31, 2026

This Privacy Policy explains how Doamne Ajuta processes information when you use the Android app, this website, and related support services.

1. Scope

Doamne Ajuta is an independently developed application. This policy describes the current supported Android release and public website; it does not create a different policy for a future merchant or company.

2. Information we process

• Account and profile data: Firebase user ID, email address when supplied, display name, authentication-provider identifiers, email-verification status/date, and a profile-photo URL when supplied by an authentication provider. Normal users cannot upload profile photos in the app.
• Notification and device-registration data: notification choices, locale, platform label, app-generated device identifier, Firebase Cloud Messaging (FCM) token, subscribed notification topics, and registration/update times when push notifications are enabled for a signed-in user.
• Account-linked feature data: event attendance response and update time; optional in-app feedback category and message; and participation records used to show points, badges, streaks, completed activity types, and related dates. These are feature records, not a general Firebase Analytics implementation.
• Purchase-verification data: if an eligible user chooses a subscription purchase or restore flow, product ID, purchase token, transaction ID when available, account ID, entitlement status, platform, and expiry/update information are processed to verify access. Payment-card details are processed by Google Play, not by Doamne Ajuta.
• Deletion-request data: account ID, email when available, optional reason, request status, and timestamps needed for a manual account/data deletion request.
• Administrator content data: authorized administrators may deliberately select JSON content files or event images. Approved content or images are sent to Firebase only when the administrator uses the upload action.

3. How we use information

We use this information to authenticate accounts, operate account-backed content and participation features, deliver selected notifications, verify subscription entitlement where available, process feedback and deletion requests, prevent abuse, and meet legal or security obligations.

4. Authentication

Users can create an email/password account or use available Google Sign-In or Facebook Login. Facebook Login requests the public_profile permission. Authentication providers and Firebase may process credentials and tokens under their own terms. An email, name, or profile-photo URL is stored only when supplied by the authenticated account/provider or entered during registration.

5. Notifications

The supported release uses local notifications and may use FCM push notifications. Local reminder schedules, notification settings, and scheduling state stay on the device. For a signed-in user with an FCM token, the app stores the device registration described in section 2 so that selected announcements, event reminders, or daily messages can be delivered. You can change app notification choices and deny or revoke notification permission in device settings.

6. Security and app integrity

The Android release activates Firebase App Check with Google Play Integrity. This security mechanism may process app/device integrity and recognition signals and technical attestation tokens to help prevent abusive or unauthorized Firebase use. It is configured for monitoring at the time of this policy; that does not mean every Firebase service is enforced. Doamne Ajuta does not receive a general raw device-integrity report from this mechanism.

7. Service providers and limited event measurement

We use Google/Firebase services for authentication, Firestore data, Cloud Functions used by supported account/subscription operations, Cloud Messaging, Storage for administrator-uploaded event media, App Check, and Hosting for this website. The Android release also includes optional Google Sign-In and Facebook Login.

The Android release source includes a limited Meta App Events path when a valid Meta configuration is present. It is limited to selected functional events such as authentication outcome, content sharing, schedule response, and administrator content creation, with allowlisted generic parameters. Its event-sanitization code excludes devotional labels and does not send prayer text, feedback text, email address, Firebase user ID, or an uploaded image through that event call. Meta may still process technical/device data under its own privacy policy. See Services and Data Processors for the provider inventory.

8. Advertising and sale of personal information

The current supported Android release is a no-ads release: its release manifest removes the advertising identifier permission and mobile-ads initialization components, and release ads are disabled by default. We do not serve personalized ads in that release and do not sell personal information. Dormant development dependencies or source paths are not an active advertising data-collection path in the supported release.

9. Data stored on your device

The app stores preferences, language/theme choices, local notification schedules, cached app content, reading/engagement state, and personal prayers or personal calendar events on the device. The current personal-prayer and personal-event paths are local to the device; those features do not upload them. Removing the app or clearing storage can remove local data, which may not be recoverable.

10. Location, media, and sensors

The app does not request device location, camera, microphone, contacts, or general photo/media permissions for normal-user features. An administrator may manually enter or choose a map point for a published event or select an event image for upload; that is administrator-provided event content, not device-location collection from attendees or ordinary users.

11. Retention, sharing, and security

We retain account-backed records while needed to operate the selected feature, maintain security, resolve requests, or meet applicable legal obligations. We share information with the processors above only as needed to provide the service, process a request, or comply with law. No transmission or storage method is completely secure.

12. Your choices and deletion requests

You may update available profile details, choose notification settings, and request deletion in the Profile screen or by emailing contact@doamneajutaapp.ro. An in-app request receives status pending_manual_processing; it does not instantly erase the account. We review and verify requests before manual backend processing. When an authentication provider does not supply an email address, we can use the internal user ID. See Data Deletion for request steps.

13. Children’s privacy

Doamne Ajuta is not directed to children below the age required by applicable local law. We do not knowingly collect personal information from children.

14. Content compilation, verification, and licensing

Doamne Ajuta compiles and maintains calendar, prayer, Lives of Saints, Christian Names, traditions, recipes, and related devotional content through locally maintained datasets, local computational logic, editorial curation, normalization, and application-specific content workflows. Public or open reference material may be consulted to cross-check names, dates, events, historical/contextual facts, and provenance or licensing. Where material is adapted or translated from lawful public-domain or open-license works, applicable provenance and attribution information is maintained. Detailed public information is available on the Content Sources and Attributions page.

15. Prayer corpus works

The following concise bibliography identifies editions represented in the local prayer corpus. It does not identify a digital acquisition source.

• Orthodox Daily Prayers — edition represented in the corpus: 1982.
• Prayers of the Early Church — corpus edition: 1953.
• Prayers of the Middle Ages: Light from a Thousand Years — second printing edition represented: 1954.
• The Little Treasure of Prayers — fourth edition represented in the corpus: 1888.
• Little Folded Hands: Prayers for Children — revised edition represented in the corpus; the local title matter does not state a year.
• Book of Needs of the Holy Orthodox Church — English translation/edition represented in the corpus: 1894.

16. Changes to this policy

We may update this policy when the app, providers, or legal requirements change. We will post the revised policy at this URL and update its date.

17. Contact

For privacy questions or data requests, contact contact@doamneajutaapp.ro.

Related pages: Terms and Conditions, Subscription Terms, Data Deletion, and Support.