Yara Hyper Privacy Policy

This Privacy Policy applies to the active Yara Hyper storefront or application, including without limitation the public website, Android and iOS customer applications, customer account creation and sign-in functionality, ordering and checkout workflows, delivery coordination features, push notification features, feedback or rating workflows, customer support channels, and any ancillary pages, APIs, or interfaces made available in connection with those services. References in this policy to the “Service,” “we,” “us,” or “our” shall be construed accordingly and shall refer to Yara Hyper or the relevant operator responsible for the branded service in the applicable deployment context.

Because the underlying product is white-label and multi-tenant in nature, certain integrations, permissions, processors, analytics tools, or operational workflows may vary by client, deployment, platform, country, or enabled feature set. Accordingly, not every disclosure stated herein will apply in identical form to every user at every moment; however, where a feature is made available, used, enabled, or requested, the associated data practices described in this policy are intended to govern the related processing activity unless a more specific in-product disclosure, consent prompt, or jurisdiction-specific notice applies.

Subject to applicable law and the features you elect to use, the Service may collect, receive, infer, or otherwise process categories of information that include, by way of example and not limitation, identity and account data such as name, mobile number, email address, account profile details, login credentials, account status indicators, and customer identifiers; authentication and provider-linked data such as Google account identifiers, Google-supplied name and email attributes, identity tokens, provider identifiers, and email verification state; transactional and commercial data such as cart contents, line items, order history, invoices, ratings, feedback, refund context, delivery instructions, and customer communications; payment-related records such as selected payment method, order totals, gateway-generated order references, payment references, and payment verification signatures; and support or operational records generated in connection with requests, disputes, delivery coordination, or administrative review.

The Service may also process technical and device-level data including browser type, operating system, application version, language, tenant or store selection, session identifiers, guest-session or cart linkage identifiers, notification tokens, service worker state, device or browser metadata submitted for messaging delivery, approximate or precise location inputs where the relevant feature is used, map or place-selection data, usage telemetry, crash and diagnostics data, route or page-view analytics, and similar information reasonably required for the operation, maintenance, measurement, improvement, security, or lawful administration of the Service.

Information processed by the Service may be obtained directly from you, automatically from your browser, device, or application session, from operational interactions within the Service, from payment or delivery flows, or from third-party identity and infrastructure providers used to support the functionality you invoke. For example, if you authenticate through Google Sign-In, the submitted Google identity token is validated by the backend before login is completed and the Service may receive or derive Google-associated profile information necessary to identify you within the Service.

Where no prior customer account exists for the relevant authenticated identity, the Service may provision a customer record using the information returned in connection with the authentication event, including name, email address, provider designation, provider identifier, and verified-email status. Where the user has previously interacted with the Service in a guest capacity, including through a guest cart or temporary session token, that guest state may be associated with the authenticated account so that cart continuity, order continuity, or session continuity can be preserved across devices, sessions, or platforms.

We process the foregoing categories of information for purposes that include establishing and administering customer accounts, authenticating users, enabling Google Sign-In and comparable login flows, associating guest sessions with customer accounts, preserving cart state, displaying localized or tenant-specific storefront content, processing orders, coordinating delivery, handling refunds or disputes, providing customer service, responding to feedback, enabling map and address workflows, sending transactional notifications where the relevant permission has been granted, maintaining product and service integrity, detecting or preventing fraud, abuse, misuse, or unauthorized access, and satisfying internal recordkeeping, tax, audit, accounting, contractual, or legal obligations.

Depending on the jurisdiction and the processing activity in question, the legal basis or equivalent justification for processing may include performance of a contract or pre-contractual request, compliance with legal obligations, the operator’s legitimate interests in maintaining and securing the Service, or the user’s consent where consent is required or technically solicited through a platform permission request, consent dialogue, or equivalent mechanism. Where processing depends upon consent or a platform-level permission, the associated feature may be limited, modified, or unavailable until the relevant authorization is granted; however, paid functionality should not be conditioned on unnecessary access to personal data, and core features unrelated to a particular permission are intended to remain usable without such permission unless the feature itself inherently requires the data in question.

The Service uses cookies, local storage, browser storage, service worker storage, session identifiers, push token registration flows, and similar client-side technologies for purposes that include maintaining session continuity, preserving cart contents, remembering store or tenant selection, supporting notification enrollment, enabling reliable frontend delivery, measuring usage, and assisting with security, fraud prevention, and diagnostics. Notification permissions are requested before push messaging is enabled; location permissions are requested only where features such as map-based address selection, delivery assistance, or location-dependent workflows are used; and, on iOS, the application may present the App Tracking Transparency prompt where platform-level authorization is required for enabled measurement, attribution, or similar processing subject to Apple platform rules.

Users may withdraw or modify platform permissions through browser or device settings at any time, although doing so may impair or prevent the continued operation of the feature that depends on the relevant data access. Where possible and reasonably practicable, alternative workflows such as manual address entry or continued browsing without notification enrollment are intended to remain available when a user declines a permission that is not strictly required for the requested core function.

Personal data and related records may be disclosed to, accessed by, or processed through service providers, infrastructure providers, payment processors, analytics and diagnostics providers, mapping or geolocation providers, notification providers, identity providers, delivery or operations personnel, support personnel, affiliated operational entities, and similar processors or sub-processors to the extent reasonably necessary to operate, secure, improve, support, or lawfully administer the Service. To the extent required by applicable law, contract, or platform obligation, third parties granted access to such data are expected to process that data in a manner consistent with applicable confidentiality, security, and privacy obligations and to afford user data protections not materially less protective than those described in this policy for the relevant processing activity.

We do not describe the disclosure of personal and sensitive user data for monetary consideration as part of the ordinary operation of the Service. Data may also be disclosed where required to comply with law, regulation, court order, governmental request, legal process, enforcement request, or audit requirement, or where disclosure is reasonably necessary to establish, exercise, or defend legal claims, investigate fraud or security incidents, protect users, protect the Service, enforce applicable terms, or support a merger, acquisition, restructuring, financing, or asset transfer, subject in each case to applicable law and, where appropriate, notice obligations.

Account data, order history, payment reference data, support records, analytics records, diagnostic records, and related operational data may be retained for so long as reasonably necessary to provide the Service, preserve continuity of customer activity, resolve complaints or disputes, investigate misuse or incidents, support fraud prevention, maintain backup and recovery processes, enforce contractual or platform requirements, and comply with tax, accounting, legal, regulatory, or audit obligations. Because certain records are operationally or legally required, deletion or erasure requests may be fulfilled in part rather than in full where continued retention of specific records is necessary for the foregoing purposes.

Where a user seeks account deletion, privacy review, or deletion of associated personal data, such request may be submitted through the privacy contact identified below or through any account-deletion or support intake flow made available in the relevant app, storefront, or publishing channel. Requests are subject to identity verification, fraud and abuse safeguards, legitimate retention obligations, and the technical state of the relevant tenant or brand deployment. Temporary deactivation or access restriction is not necessarily equivalent to final deletion, and residual copies may remain for backup, legal hold, audit, or security purposes for the period reasonably required by those functions.

We employ administrative, organizational, and technical measures intended to reduce the risk of unauthorized access, destruction, loss, misuse, alteration, or disclosure of information processed in connection with the Service, including safeguards relating to transmission security, credential handling, access limitation, and operational review. Notwithstanding the foregoing, no internet-based service, application environment, mobile platform, storage system, or transmission pathway can be guaranteed to be absolutely secure, uninterrupted, or immune from compromise, and users remain responsible for maintaining the confidentiality of their credentials, controlling access to their devices, and using current software and platform protections.

Privacy-related inquiries concerning Yara Hyper, including questions relating to collection, use, disclosure, consent withdrawal, retention, or deletion review, may be directed to Yara Hyper at hi@razi.pro.

For general customer-service purposes, the support contact details presently displayed for this brand are yarahyperonline@gmail.com · +91 90618 77774. We reserve the right to amend, restate, supplement, or replace this Privacy Policy from time to time in order to reflect operational, legal, technical, contractual, or platform-driven changes, and the effective version will be the version published at the applicable public policy URL as of the stated effective date or later revision date.