Privacy Policy | Riwaq Platform

Riwaq Privacy Policy

Effective date: June 14, 2026 Last updated: September 22, 2026

This Privacy Policy applies to individuals who use the Riwaq mobile app (`io.riwaq.app`) and/or sign in as a community member on a mosque's public Riwaq website. It does not govern mosque operators who administer tenant workspaces through the admin portal; that relationship is covered by the separate Tenant Agreement.

Terms of Use: https://alriwaq.net/terms

Plain-language summary

This summary is for convenience only and is not a substitute for the full policy below.

Haven Software Solutions Inc. collects the information needed to run your account and the features you use — such as email, optional profile details, notification and location preferences, and community carpool listings if you participate. Your mosque's administrators control most published content on their site; Riwaq does not control how tenants use the platform. We use service providers (for example hosting, authentication, push delivery, and email) to operate the service. We use first-party analytics — stored in our own systems, not shared with advertising networks — to understand how features are used and improve the app. We do not sell your data for cross-app advertising. You can manage permissions in your device settings, update your profile in the app, and delete your account when supported. Contact us at hello@alriwaq.net with privacy questions or requests.

1. Scope and relationship to Terms

This Privacy Policy explains how Haven Software Solutions Inc. ("Riwaq", "we", "us") collects, uses, shares, and retains personal data when you use our end-user services.

By creating an account or using the services, you acknowledge this policy and our Terms of Use. If there is a conflict between this policy and mandatory law, mandatory law controls.

2. Data we collect

2.1 Account and profile data

Email address and authentication identifiers.
Optional profile fields you provide (for example display name, phone, address).
Optional birth date used only for age-gated feature eligibility (for example, verifying 18+ eligibility for posting as a carpool driver).

2.2 App usage and preferences

Tenant selection and end-user preferences (for example prayer and notification settings).
Push notification tokens and related delivery metadata.
Optional location data if you enable location-based features (such as geofencing for utility features). For My location (traveler prayer times, spec 40), your device's coordinates are used only on your device to calculate estimated prayer times and are never sent to or stored by Riwaq.
First-party product analytics about how you use core features (for example viewing a special prayer, responding to a nearby-mosque prompt, or restoring a join/invitation link), stored in our own backend to measure usage and improve the app. We do not embed third-party advertising or cross-app tracking SDKs.

2.3 Community carpools data

If your tenant enables community carpools and you participate:

Listing content: role (driver/rider), direction, seats/party size, departure window, optional notes and preference flags.
Coarse pickup data you provide: neighborhood label and/or rounded coordinates/geohash.
Match and message metadata: listing links, status changes, timestamps, in-app message content.
Safety reports: report category and optional narrative details.

We do not position community carpools as a ride-hailing marketplace and do not process in-app fares.

2.4 Technical and device data

Device and app metadata needed for reliability, fraud prevention, security, and troubleshooting.
Session information needed to maintain authenticated app usage.

2.5 Tenant-controlled data

Mosques and community organizations ("Tenants") publish content and may collect additional information through their public sites (for example event registrations or donations handled on tenant pages). That content and those flows are primarily controlled by the Tenant, not by Riwaq. If a Tenant is suspended or removed, you may lose access to Tenant-associated data through the Services.

2.6 Mosque listings, traveler places, and "Report a problem" (spec 40 — draft, see section 13)

Basic public information for mosques not yet on Riwaq — name, address, and coordinates — is sourced from OpenStreetMap contributor data, never from a Tenant's private records. We never copy a prospective mosque's private contact information (for example an outreach email address) into a listing.
Estimated prayer times shown for a listing or a traveler place (a curated city or "My location") are calculated on your device, from that location and your own calculation settings — not fetched from or stored on Riwaq's servers, and not shared with anyone else.
Your calculation-method preferences (method, madhab, high-latitude rule, per-prayer minute offsets) for a listing or place are stored against your own account (or locally on your device as a guest) and are never visible to other members.
If you use "Report a problem with this listing" or "Can't find your mosque?", we store the text you enter, the listing (if any) and, only if you have granted location permission, your coordinates at the time — the same platform feedback inbox used for other in-app feedback (see section 3). Super-admins use these reports to fix or add listing data; they are not shared with any mosque.

3. How we use data

We use personal data to:

Provide account login, profile management, and core app functionality.
Deliver member-facing features across mobile and web.
Send notifications you request or that your tenant sends through supported channels.
Operate community carpools matching, safety moderation, and abuse prevention where enabled.
Enforce product safety rules (for example age-gating for driver listings).
Understand feature usage and improve the product through first-party analytics.
Maintain security, detect misuse, and comply with legal obligations.

We do not use end-user data for cross-app advertising or sell personal data.

4. Legal bases (where applicable)

Depending on your location, we process data under one or more of:

Performance of a contract (providing requested services).
Legitimate interests (service security, abuse prevention, product reliability).
Consent (for optional permissions such as push and location where required).
Compliance with legal obligations.

5. Who can access data

Same-tenant members: can view non-hidden carpool listing fields for events where they have access, when this feature is enabled.
Matched members: may view additional contact details only when explicitly enabled by product behavior and user choices.
Tenant administrators: can view tenant-scoped carpool listings, matches, and reports for moderation and operations.
Riwaq personnel and processors: can access data as needed to operate, secure, and support the service.

We do not sell personal data for cross-app advertising.

6. Service providers and third parties

We use service providers to run core functionality, including:

Supabase — authentication, database, backend infrastructure, and first-party analytics storage.
Expo / Firebase Cloud Messaging (FCM) — push notification delivery on supported devices.
Apple Push Notification service (APNs) — push notification delivery on iOS.
Google Firebase Analytics — app usage analytics in the mobile app, without names, contact details, location or free text (section 13b, draft).
Resend — delivery of transactional and account-related email (for example event ticket confirmations and other service messages).
OpenWeather — optional weather information when enabled in the app.

These providers process data on our behalf under contractual controls and only as needed to provide the services.

Where a tenant links third-party registration, payment, live stream, or map pages, your interactions with those pages are governed by the tenant and the relevant third-party policies.

7. Retention

We retain personal data only as long as needed for the purposes above, including legal, security, and dispute requirements.

After you delete your account, we delete or anonymize end-user profile and preference data within a reasonable period, except where we must retain data for legal compliance, dispute resolution, fraud prevention, or backups.

For community carpools, operational data (listings, matches, messages, reports) may be deleted or anonymized after event relevance windows and safety review periods, unless legal hold or dispute handling requires longer retention.

If a Tenant workspace is suspended or deleted, tenant-scoped data may be removed or retained according to our Terms, legal obligations, and operational needs.

8. Your choices and rights

You can:

Update profile fields in-app.
Disable notification and location permissions in app or device settings.
Withdraw carpool participation by deleting or canceling listings (subject to product constraints).
Delete your account using in-app account deletion controls.

Depending on your jurisdiction, you may also have rights to access, correct, delete, restrict processing of, or object to processing of your personal data, and to lodge a complaint with a supervisory authority. Contact hello@alriwaq.net to submit requests. We may need to verify your identity before responding.

9. Security

We use reasonable technical and organizational safeguards to protect personal data. No method of transmission or storage is perfectly secure, and we cannot guarantee absolute security.

10. Children's data

The service is not directed to children under 13 (or higher minimum age required by local law). If we learn we collected personal data unlawfully from a child, we will take steps to delete it as required.

11. International transfers

Your data may be processed in the United States and other countries where we or our service providers operate, subject to appropriate safeguards required by applicable law.

12. Group trips (draft — counsel review before a production trip)

When a mosque or travel agency runs a group trip, Riwaq stores trip-scoped operational data: traveler names, optional emergency contact and health notes you choose to share, room assignments, bag-tag scans, SOS alerts, and time-boxed live location sharing with organizers — either because you started it, or because you consented at join that organizers may locate you if you are late (you can still decline a later request if you skipped that checkbox). The owner workspace (mosque or agency) is the controller of that trip data; a mosque named as a partner on an agency trip can access the same organizer tools for that trip only. Passport and visa numbers are never entered as data fields. If the trip organizer turns on the optional document-upload feature, scans of travel documents you or your organizer attach are stored privately, visible only to that trip's organizers (not guides) and your own party, never published, and deleted when the trip is archived. Unauthenticated hotel or bus staff who scan a bag tag see only the instruction and room information the operator configured. Family followers see public trip updates, not medical notes or other travelers' rooms. If you pick an unclaimed home mosque after the trip, Riwaq stores that listing choice so we can convert it when the mosque claims a workspace; we do not create a mosque admin account for them. This section is a draft pending counsel review (OQ-L1) and does not authorize a production trip by itself.

13. Mosque listings, traveler places, and map data (draft — counsel review before public launch, spec 40)

Riwaq shows members prayer-time information for mosques across the US and Canada that have not yet joined the platform ("listings"), and for curated traveler locations such as Makkah, Madinah, and other cities, plus "My location" ("places"). This section covers what that means for your data; it does not change how a mosque's own, claimed workspace is governed elsewhere in this policy.

Where listing data comes from. A listing's name, address, and coordinates come from OpenStreetMap, a public, collaboratively maintained map database, or from Overture Maps Foundation Places data (spec 40a §2 Q4) — some of which is itself derived from Foursquare Labs, Inc. Data © OpenStreetMap contributors, available under the Open Database License (ODbL); Overture Maps Foundation data is available under the Community Data License Agreement – Permissive, Version 2.0 (CDLA Permissive 2.0), and Foursquare-derived rows within it under the Apache License 2.0 (see `prospects/NOTICE-foursquare.txt`). Attribution naming the source is shown on every public listing page. We do not verify OpenStreetMap or Overture data for accuracy and correct it on a best-effort basis when members report a problem (section 2.6). *(counsel: please confirm this paragraph's wording satisfies ODbL/CDLA/Apache-2.0 attribution requirements before public launch.)*
Estimated, not published. Prayer times shown for a listing or place are calculated on your device from location data, a calculation method, and your own optional adjustments — never confirmed by mosque staff, and never sent to or computed on Riwaq's servers. Every screen that shows an estimated time says so.
"My location" is never sent to Riwaq. When you use "My location," your device's own GPS coordinates are used locally to calculate estimated prayer times for wherever you are; Riwaq does not receive, log, or store those coordinates.
A listing is not a customer. A listing has no admin account, sends no messages or push notifications, and is not part of any mosque's or any member's roster until the mosque claims it. Claiming (section 2.6) starts a mosque's own workspace under this policy's other sections.
Feedback about a listing. "Report a problem" and "Can't find your mosque?" submissions are handled as platform feedback (section 2.6, section 3) — reviewed by Riwaq's team, not shared with any mosque or third party beyond the service providers who help us operate the platform (section 6).

This section is a draft pending counsel review and is written to describe the feature accurately for that review; it is not to be relied on as final legal advice.

13a. Member safety alerts (draft — counsel review before launch, spec 44)

If a mosque turns on safety alerts, a follower of that mosque can ask the mosque's admins for help from the app. When they do, Riwaq stores the alert: its type (threat, medical or other), an optional short note, the time, the member's name and phone number from their profile, and the device location only if the member allowed location for that alert (and, while the alert is open, updated locations from the open app). Riwaq sends a push notification with a loud alert sound to the mosque's admins, and the admins can see that information in the Riwaq app and admin portal. Admins can acknowledge or resolve the alert; the member is notified, and an admin's resolution note is shown to the member. The note, the location and the phone number are not written to analytics or logs. Platform staff see alert counts only, not the content. Alerts are deleted after 12 months and location updates after 30 days, and audit entries record who acknowledged or resolved an alert. Riwaq is not an emergency service: it does not contact police, fire or medical services, and anyone in danger should call their local emergency number first. *(counsel: please confirm retention wording, the lock-screen visibility of the note excerpt in the admin push, and the legal basis before launch.)*

13b. Analytics (draft — counsel review before the first build that ships it, spec 45)

The Riwaq app uses Google's Firebase Analytics to understand how the app is used, so we can fix what is confusing and improve what members use. What is collected: app interactions (for example which screens are opened and which actions, such as following a mosque or opening a share sheet, are taken), screen names, device model and operating system version, app version and language, and an approximate country derived by Google from the connection's IP address. What is not collected: your name, email address or phone number, your location, anything you type (messages, notes, search text), or any account identifier — Riwaq does not give Firebase your Riwaq user id, and the app does not use the advertising identifier (no advertising, no cross-app tracking). The app also records a few non-identifying settings as user properties: your app language, a bucket for how many mosques you follow (0, 1, 2–3, 4 or more), whether a home mosque is chosen, whether you are a mosque admin, and whether the build is a store or test build. Analytics is switched off in development and test builds. Google acts as our processor for this data under Google's Firebase data processing terms. Retention: event data is kept for Firebase's default period of 14 months, then deleted automatically. How to object: you can ask us not to include your device in analytics by writing to the contact address in section 15, and you can reset or limit data collection from your device's privacy settings; we will confirm what we can do while the data cannot be tied to you by name. _counsel review_ — *(counsel: please confirm the processor wording, the 14-month retention statement, the legal basis (legitimate interests) and whether an in-app opt-out toggle is required in any launch region.)*

14. Changes to this policy

We may update this policy from time to time. We will update the "Last updated" date and publish the revised version at https://alriwaq.net/privacy.

Material changes may also be communicated through in-app notices, email, or website notices when required.

15. Contact

Haven Software Solutions Inc. Austin, TX, USA hello@alriwaq.net

For privacy-related requests, email hello@alriwaq.net with the subject line "Privacy request" and enough detail for us to identify your account.