Privacy Policy

Last updated: 19 September 2026

1. Information we collect

The information required depends on the feature you use. You do not need to provide every type of information to use every feature.

• Account and authentication: name, email, Firebase UID, login provider (Email/Password or Google Sign-In), and any profile phone number or photo you choose to add. We do not store passwords in plaintext in the database.
• Blood donor information: name, blood group, phone, age, thana, address, last donation date, donation count, photo/image URL, user ID, approval/status and timestamp.
• Blood requests and health-related information: patient name, blood group, required date, number of bags, haemoglobin/Hb, age, hospital, thana, phone and free-text details. This is collected to provide an emergency community service.
• Marriage biodata: name, marital status, birth year, height, weight, complexion, blood group, permanent and present address, upbringing location, education, phone, details, biodata number, approval/status and timestamp.
• Story ("গল্পঘর") submissions: title, content, category, location, your name, phone, an optional image, a copyright confirmation, submitter UID, status and timestamp. Once approved by an admin, the title, content, image, location and (if provided) your name are published publicly, and view/like counts are recorded.
• Mosque accounts and committee access: committee member lists and donation/income/expense ledgers (maintained by the mosque committee). If you set a PIN to view a specific mosque's ledger, a hash of that PIN and an access grant linked to your UID are stored — the actual PIN is never stored in plain text.
• Complaints, suggestions, comments and reports: name (which may be blank in anonymous mode), phone, upazila, union, category, title, message, comments, support/report activity, user ID, status and timestamp. You may also report a blood donor entry or a marriage biodata post that appears fake or inappropriate — in this case the reporter's UID, the ID of the reported entry, its name and phone number (if any), and the timestamp are stored and visible only to admins.
• Images and media: secure URLs for images that you submit with a complaint or other submission. Images may be sent to Cloudinary's upload service.
• Education, jobs, shops, rentals and directory listings: depending on the listing, name, phone, address/location, education/job details, price/salary, gender, image, social link and description. This may include car rental, courier, salon, farmer, mechanic/craftsman, doctor, lawyer, journalist, tourist-spot and other directory/service listings in the app. Information you voluntarily publish may become a public listing.
• Private chat/messaging: the content and time of messages you send to other users in in-app private chat, typing status, last-seen/online status, and the list of chats you have (chat index). Whether you have blocked, or been blocked by, another user. If you report another user for inappropriate behaviour, the reporter's and reported user's UID/name, the related chat ID, the reason and the timestamp. Based on repeated or serious reports, an admin may temporarily disable a user's ability to send messages (ban).
• Orders and delivery: if you use shopping features, name, phone, delivery address/village/union, user-provided location, cart items, delivery charge, total, order status and timestamp.
• Notifications and device/app information: Firebase Cloud Messaging token, notification title/body, optional image URL, read/last-seen state, app version, device model and Firebase Analytics usage events when those features are enabled.
• Advertising information: Android Advertising ID and advertising-related information if AdMob is enabled. This processing does not apply when advertising is disabled.

2. How we use information

• To create accounts, sign users in, update profiles and protect accounts.
• To provide blood donor/request, hospital, ambulance, education, job, shop, transport, directory, biodata and other community services.
• To receive, moderate and manage complaints, suggestions, comments, support and reports.
• To show a public listing or request when you choose to publish it.
• To publish your approved story ("গল্পঘর") submissions and record view/like counts.
• To send important notifications and service updates.
• To provide private chat/messaging between users, manage blocking/unblocking and user reports, and to temporarily disable messaging (ban) when needed to prevent inappropriate behaviour.
• To understand feature usage, reliability and technical problems when Firebase Analytics is enabled.
• To show and measure ads when AdMob is enabled.
• To prevent abuse, spam, fraud and security incidents and to meet legal obligations.

3. Public content and sensitive information

An anonymous option may still leave an account UID, timestamp or technical metadata in the system. Do not submit passwords, national ID numbers, bank/card information or unnecessary sensitive information in public content.

When submitting biodata or blood donor information, you are now asked to confirm consent — you must tick a box confirming that your name, address and photo will become publicly visible once approved by an admin. Entries that appear fake or inappropriate can be reported from the relevant page.

Chat messages are not public content — they are visible only to you and the person you are chatting with. If you report another user, however, the related chat ID and report details are shown to the admin for moderation.

4. Who we share information with

• Google Firebase: Authentication, Realtime Database, Cloud Messaging, Analytics and related hosting/services.
• Google Sign-In: for authentication when you choose Google login.
• Cloudinary: to store and deliver user-uploaded complaint or media images.
• AdMob/Google Mobile Ads: for advertising and measurement when ads are enabled.
• Notification/account backend: authenticated requests may be sent to `notification-server-steel.vercel.app` to process notifications and account-deletion requests. The server is intended to verify the Firebase ID token before the deletion workflow.
• Legal or safety reasons: valid government requests, court orders, fraud/security investigations or protection of rights.

We do not sell personal information. Third-party providers may process data under their own privacy policies and service terms.

5. Data security

We aim to use HTTPS/TLS-secured connections for data in transit and use Firebase Security Rules and authenticated access where applicable. Internet services, devices, public listings and third-party providers are not completely risk-free, and we cannot guarantee the privacy of information you intentionally publish publicly.

6. Data retention

Information may be retained for as long as needed to operate the account and services, moderate content, resolve disputes, protect security and meet legal requirements. When account deletion is completed, the deletion workflow is used to remove relevant Firebase records. Cloudinary images, notification/backend logs and provider-side backups or logs may follow the provider's systems and legal retention periods. Chat messages, block lists and user reports may be retained for as long as the related chat/account is active and as needed for safety and moderation purposes. Clearing a chat only removes it from your own view — it does not remove it from the other participant's view or from a report record held by the admin.

7. Account and data deletion

You may use Profile → Delete Account in the app or submit a request through the website's Account Deletion page. Re-authentication may be required. The successful deletion workflow is intended to remove the Firebase Authentication account, user profile and in-scope records associated with your UID, including donor/request, complaint, comment, support/report, biodata, tuition and order records, chat messages and conversation history, and block-list entries. Public or third-party copies, legal records, security logs or references held in another user's separate record may not be removed immediately or completely where retention is required. For safety and abuse-prevention purposes, user reports (userReports) filed against you and related moderation information may be retained for a period after account deletion where needed for security or legal reasons.

8. Children

The app is not directed to children. We do not knowingly seek to collect account or personal information from children under 13.

9. Permissions and device access

Notification permission and user-selected photo/media access may be needed for particular features. Where the app does not have GPS location permission, it does not collect the device's precise location itself; locations in listings and orders are generally entered or linked by the user.

10. Your rights and contact

You may request correction or deletion of your profile or listing and may raise privacy questions through the website's Contact page. Do not send passwords, national ID, bank information or unnecessary sensitive data through the contact form.

11. Changes to this policy

We may update this policy when features, providers or legal requirements change. The updated version and date will be published on this page.