Privacy notice

Who operates the app

Hurrik Reports Hub is operated by Manjit Kumar / Hurrik. Contact phpdeveloper.manjitkumar@gmail.com for support or a privacy question about information handled by this app.

This notice covers the reporting application. A merchant controls its Shopify store and chooses report contents, recipients and destinations. For a request about a purchase or a merchant's customer records, contact that merchant first; we assist with information retained by this app.

Information used for reporting

The app uses shop and authentication identifiers, access credentials and subscription-entitlement results to connect an authorized store and provide its selected features. It stores report definitions, filters, columns, dates, timezones, schedules, delivery settings and operational history.

Shopify authentication can supply an authorized staff user's identifier, name, email, locale and account-role information. The app's offline store-access sessions discard associated staff-profile information that is not needed for reporting. Any staff-session information is distinct from customer report fields. Hosting and delivery systems may process request or delivery metadata while operating the service.

Depending on granted read permissions and selected reports, it reads orders and line items, payment and refund transactions, merchandise returns, Shopify Payments payouts and ledger entries, products, variants, inventory, locations, inventory transfers and customer-summary identifiers, counts and spend.

Fixed customer names, email addresses, phone numbers and postal addresses are not part of the report columns requested by the app. Merchant-selected metafields and custom properties can nevertheless contain personal data. Choose only the fields needed for your reporting purpose.

Completed exports and encrypted source rows are retained so reports can be downloaded and matching retained data can be identified for privacy requests. Optional resource sync keeps a minimal encrypted cache. Reports still request current data from Shopify; the cache is not an unlimited historical archive.

When configured, the app also holds report-recipient addresses, email subject/message settings, destination credentials or OAuth tokens, and snapshot-sharing recipient addresses and access records. Sharing applies to a completed export, not live store access.

How information is used

Information is processed to authenticate store access, verify plan permissions, create and download reports, run merchant-configured schedules, deliver files, operate optional connections and sharing, handle privacy requests and diagnose service failures.

The reporting app requests read access to Shopify resources. It does not initiate customer payments, create refunds or change payout settings. A payout report or ledger comparison does not confirm receipt by a bank.

Recipients and service providers

The app processes information on its hosting infrastructure. Configured email delivery passes the message, recipient details and attachment to the app's email service. A merchant can direct reports to authorized recipients or connect an eligible Google Drive, Google Sheets, Slack, SFTP or FTPS destination. Provider availability depends on configuration and the app plan.

Google connections use file-specific access for app-created or otherwise authorized files; they do not request access to every file in the connected account. Slack file delivery uses the configured bot and channel. Connected providers and recipient accounts retain copies under their own terms and controls.

Contact the privacy address for information about the hosting and email providers used for your deployment and applicable processing locations. Those providers and merchant-selected destinations may process information in different countries. This notice does not promise storage in a single country.

Retention and deletion

Routine cleanup uses a default retention of 30 days for completed encrypted exports and their retained source rows, and 90 days for terminal report and delivery history. The operator can configure export retention from 7 to 90 days and history retention from 30 to 365 days; history cannot be shorter than export retention. Contact support to confirm the configuration for your deployment.

Cleanup runs in bounded background batches. Active work, a failed cleanup or a quarantined record can require further processing; these periods are not a promise that every physical copy disappears at an exact minute. Expired report access is unavailable in the app. Interactive usage and sharing/audit metadata have 90-day cleanup paths.

Optional resource-cache records have a default retention of 90 days since their last update; the operator can configure this from 7 to 365 days. Terminal sync history and fulfilled privacy-request records use the history-retention setting, which defaults to 90 days. Fulfilled requests are timed from fulfillment, not receipt. Pending or prepared privacy requests hold the related cache and sync history; active sync work and still-referenced cache generations also delay eligible cleanup. These safeguards preserve information needed to finish existing work or a privacy request.

Saved reports and settings remain while needed for the installation until deleted or removed through store erasure. A full accessible refresh removes stale cache records, and customer/store erasure removes the store's retained cache.

Uninstall disconnects the app, removes active access credentials, pauses schedules and automatic sync, cancels pending work and revokes sharing. It does not instantly erase every retained report or configuration record. Shopify's store-redaction event removes the remaining store records and files from the active app storage.

Customer-redaction handling removes that store's retained export files, run/delivery history, source rows and resource cache, clears retained request identifiers and revokes shares. Automatic sync is paused. This broader deletion protects data even where a report has grouped or renamed columns.

An independent encrypted recovery journal retains the store domain, erasure type, event identifier and date so a database rollback cannot silently restore previously erased information. It does not retain report rows or customer contact fields. Recovery requires replaying outstanding erasure events before the application can start; the journal must be retained for as long as an older recoverable backup could require it.

Active-service deletion does not recall files already downloaded, attachments in recipient inboxes or copies saved to connected destinations. It is also distinct from retention of operational logs and server backups. Contact support about those copies and a specific deletion request; this notice does not claim that report expiry deletes them automatically.

Encrypted application recovery copies are reviewed for removal after 90 days. Removal follows an exact-file operator review and applicable incident or recovery holds; this is not automatic deletion. This policy is separate from live app data, the independent erasure journal and hosting-provider copies.

Access and security

Authenticated app operations are bound to the store. Application encryption protects stored export files, source-row and resource-cache payloads, access tokens, integration credentials and sharing-recipient lists. It also protects saved report names and configuration, recipient and delivery settings, retained report requests and summaries, connection settings, sync cursors, and nonempty retained staff names and email addresses. Protected fields are authenticated against their store, record and field context; the resource-cache lookup uses keyed identifiers rather than raw customer or order IDs.

Operational store domains, internal record identifiers, statuses, timestamps and counts remain readable for service operation. An online session's operational staff identifier is not covered by the protected staff-name and email fields. These are application-level protections, not a claim that the complete hosting disk, every log or every historical backup is encrypted. Older copies may predate the current protections and have separate access and retention controls; contact support about a specific retained copy.

The app checks permissions and validates requests before report work or downloads. Email and FTPS use verified TLS; SFTP destinations require a trusted host fingerprint.

Snapshot sharing requires an approved recipient to verify an emailed single-use code. Codes expire after 10 minutes and verified browser sessions after 15 minutes. Share expiry is bounded by the retained export and can be revoked. View-only access hides the app's download action but cannot prevent screenshots or other copying.

Cookies used by connection authorization and sharing support authentication and request security. This notice describes safeguards, not a guarantee that any system is immune to security incidents.

Privacy requests and contact

The app handles Shopify customer-data-request, customer-redaction and store-redaction events. Authorized merchants can prepare a JSON response from matching information retained by this app, review it and provide it to the store owner. Preparing a response does not send it or confirm that the request has been fulfilled. It is not a complete export of every customer record held by Shopify.

Email phpdeveloper.manjitkumar@gmail.com with the store domain and the nature of your request. Do not email passwords, access tokens or payment-card details. We may need to confirm that you are authorized to act for the store before discussing its information. Rights available to you depend on applicable law and your relationship with the merchant.

We may update this notice as the app and its processing change. The update date appears above. Contact us if you need an explanation of a change or the current handling of a specific data category.