Loading page...
Loading page...
Privacy
This notice explains the main data flows currently used by the URAPPe application. Last updated 17 July 2026.
Account creation can collect a name, email address, optional phone number, and an encrypted password credential. Service actions may require information needed to process that request, such as an address or booking details.
Data is used to authenticate accounts, operate requested features, protect the application, investigate failures, and respond to support requests. Access is limited by application roles and backend authorization.
When you use MyMeds Pharmacy, URAPPe may process cart and order contents, delivery location, pharmacy allocation, prescription review state, and refill-reminder preferences. Prescription files are stored privately and are available through authorised, audited review access. Where pharmacist notifications are explicitly enabled, an upload alert and the customer contact details needed for verification may also be sent to an authorised pharmacist-controlled business messaging account. The prescription document is not attached to that alert. Do not send prescriptions through ordinary support email.
When you use Puja & Priest Services, URAPPe may process the selected ceremony, requested time, service location, coverage result, booking history, cancellation or rescheduling reason, and a moderated review. Public responses omit exact customer coordinates and internal provider-verification records.
URAPPe asks for browser location only after you choose the location action. The browser may store coordinates reduced to roughly 100-metre precision on your device for up to six hours of nearby matching, and the same-origin URAPPe API receives them to compare against explicitly published service-area centres and coverage radii. Device accuracy can be wider than the stored precision, so an area match is not a provider-location guarantee. You can refresh or clear the saved browser location from the navigation and service-area controls.
Production analytics can record a small allowlist of parameter-free conversion event names. URAPPe does not intentionally attach names, email addresses, phone numbers, referral codes, addresses, order identifiers, or search text to those events. Analytics is disabled on pre-production and is suppressed on pages carrying a referral query parameter.
If you enter a referral code, URAPPe may record the referral relationship, campaign and terms version, qualification status, and promotional-grant history. The code is opaque and is not designed to contain a name, email address, phone number, or user ID. Referral summaries provide aggregate status counts and do not expose the referred customer's identity to the referrer.
URAPPe may use verified phone and email status, account, order, externally paid amount, payment-instrument risk signals, refund, chargeback, location, service-scope, campaign limits, and remaining promotional budget to determine eligibility, prevent duplicate or abusive claims, reconcile the promotional ledger, and handle support or appeals. Promotional credit is redeem-only, nonwithdrawable, and non-transferable.
Only when the server confirms that campaign participation is active and you submit registration, this site creates or reuses a random installation UUID in browser storage and sends it as campaign anti-abuse evidence. It is not derived from your hardware, advertising identifiers, contacts, canvas, installed fonts, browsing history, or third-party fingerprint traits. The server protects the identifier before using it for duplicate-claim and risk checks.
Referral sharing is initiated by you. URAPPe does not require contact-list upload or automatically send invitations from the referral page. You should share only with people who expect to receive your link.
Infrastructure and service providers may process data where needed to operate the application. Referral attribution, campaign acceptance, reward-ledger, fraud-review, order, payment, reversal, and support records may be retained where needed for security, accounting, disputes, programme enforcement, and applicable obligations. The platform does not state a fixed period where one has not been formally adopted.
Contact admin@urappe.com. Verification may be required before an account-data request can be fulfilled.