Legal

Privacy Policy

Last updated: November 2026

1. Introduction

Revebe Digital Private Limited ("Revebe", "we", "our", or "us") respects your privacy and is committed to protecting your personal information. This Privacy Policy explains how we collect, use, disclose, and safeguard information when you use our services, including the Revebe Digital ERP System, our website https://revebe.com, our Shopify applications, and our integrations including the WhatsApp Business Platform and the Meta and Google advertising platforms. By using our services, you agree to the collection and use of information in accordance with this policy.

2. Information We Collect

We collect the following categories of information:

Meta Pixel on this website. revebe.com uses the Meta Pixel, a small piece of code provided by Meta Platforms Inc. It reports activity on this site — pages viewed and similar events — to Meta, so that we can measure how our own advertising performs and show relevant ads to people who have already visited us. It does not read what you type into our forms. You can limit it through your browser's cookie settings, through your Meta ad preferences, or with any tracker-blocking extension; this site works normally either way. This is our own advertising measurement and is separate from Section 6, which describes pixels a merchant may choose to enable on their own storefront.

3. WhatsApp Integration (Meta Platform)

Our services may integrate with the WhatsApp Business Platform provided by Meta Platforms Inc. When this integration is used, messages may be sent through the WhatsApp Cloud API, and phone numbers and message content may be processed through Meta infrastructure. Revebe does not access or store WhatsApp conversations beyond what is required to deliver the service, maintain message logs, or comply with legal requirements.

4. Our Shopify Applications

We publish applications on the Shopify App Store. When a merchant installs one, Shopify asks them to approve a specific set of permissions, and we receive an access token limited to those permissions. We describe below exactly what each application reads and stores.

4.1 Syncfeed (product feeds)

Syncfeed generates product feed files so a merchant's catalogue can be advertised on Google, Meta, TikTok, Snapchat and Pinterest. With the merchant's approval it reads, from their Shopify store:

Syncfeed does not read customer records, orders, payment details or any other personal data from a merchant's store. The permissions it requests are limited to product, inventory and pixel data, and it cannot access anything outside them.

We store: the Shopify access token, the merchant's feed configuration, and the generated feed files.

4.2 Revebe Alert for WhatsApp

Revebe Alert sends order notifications to shoppers over WhatsApp. With the merchant's approval it reads order and customer contact details from their Shopify store — including customer name, phone number and order contents — because those are required to send an order message. It stores a record of messages sent, their delivery status and any reply received, so the merchant has a log and so the service can avoid sending duplicates.

4.3 Revebe: Product Reviews & UGC

Revebe Reviews collects product reviews from a merchant's shoppers and shows them on the merchant's store. With the merchant's approval it reads the store's products and orders. Orders are used for two things only: to confirm that a reviewer bought the product (shown as "Verified buyer"), and, where the merchant turns on review request emails, to know whom to ask for a review once an order has been fulfilled.

It stores:

Customer names and email addresses are encrypted in our database. Emails to shoppers are sent from the merchant's own email account and only for these purposes: asking for a review, one reminder, a thank-you discount code, or an invitation to update a review the shopper wrote. They are never used for our own marketing. Every review request email has a one-click unsubscribe link, honoured for all future review emails from that store. A thank-you discount is the same whatever rating a review gives. We do not sell or share this data.

Retention: review request records are deleted 180 days after the email was sent; discount code records 90 days after the code expires; the access record after one year. Reviews stay while the application is installed, because they are the merchant's content. When Shopify asks us to erase a customer, their name, email address and photos are removed from their reviews, which remain as "Anonymous". When a merchant uninstalls the application, all of that store's data is deleted when Shopify sends its shop erasure request, 48 hours after the uninstall.

5. Product Feeds Are Published Deliberately

A product feed exists to be fetched by advertising platforms. Each feed is served from a web address containing a long, randomly generated token, because the platforms that read it (Google Merchant Center, Meta Commerce Manager and others) cannot log in.

This means anyone who has the feed address can read the product data in it: titles, descriptions, prices, stock levels, images and links. This is by design and is how every product feed works. The address is not published or indexed by us, and a merchant can regenerate it at any time from inside the app, which immediately makes the previous address stop working.

Feeds contain product information only. They never contain customer, order or payment data.

6. Advertising Platforms

Where a merchant configures them, our applications send data to the following third parties on that merchant's behalf and under their instruction:

Each of these platforms processes that data under its own privacy policy. Merchants are responsible for disclosing their use of advertising pixels to their own customers, as required in their jurisdiction.

7. Our Mobile Apps

We publish mobile apps on Google Play for the staff of businesses that use Revebe. This section covers the Revebe CRM and Revebe ESS apps; it will also cover our other staff apps as they are published.

7.1 Revebe CRM

Who can use it. Revebe CRM is for staff of a business that uses Revebe CRM. A user signs in with their company code and the account their company created for them. The app does not let anyone create an account.

What the app keeps on the phone: for each company a user adds, the company's name, code and logo, the user's name and email address, and a sign-in token. The token is stored on our servers only in hashed form. This data is excluded from Android backups and from transfers to a new phone, and it is removed when the user signs out of a company or uninstalls the app.

What the app sends to our servers:

Permissions:

What the app does not collect: location, contacts, call logs, SMS or the advertising ID. The app shows no adverts and contains no third-party analytics or tracking.

Third parties: Google Firebase Cloud Messaging delivers the notifications, and Google Play delivers the app and its updates; each processes data under Google's privacy policy. The conversations and customer data in the CRM belong to the business that uses Revebe; we process them on its behalf, as set out in our Data Processing Agreement.

Security: the app connects only over encrypted connections (HTTPS) and trusts only the phone's own certificate authorities. The microphone and file downloads work only on the Revebe CRM's own site.

Deleting your data: signing out of a company in the app revokes its token on our servers. To have your staff account and its data deleted, ask your company's administrator, or follow Section 14 below.

7.2 Revebe ESS

Who can use it. Revebe ESS is the employee self-service app for employees of a business that runs its HR and payroll on Revebe. Only an employee their company has added can sign in, with the company code and their CNIC or email address. The first-time set-up does not create an account: it sets a password for the employee's existing record, after a code we send to the email address on that record.

What the app keeps on the phone: one company per phone: the company's name, code and logo, the employee's name and email address, and a sign-in token. The token is stored on our servers only in hashed form. This data is excluded from Android backups and from transfers to a new phone, and it is removed when the employee signs out or uninstalls the app. Signing in to another company replaces it.

What the app sends to our servers:

What the app shows: the employee's own HR record at their company: profile details (including CNIC and employee number), leave balances and applications, payslips, tax deduction certificates, appraisal letters, loans and repayments, and resignation requests. An employee can see only their own record.

Permissions:

Revebe ESS does not use the microphone.

What the app does not collect: location, contacts, call logs, SMS or the advertising ID. The app shows no adverts and contains no third-party analytics or tracking.

Third parties: Google Firebase Cloud Messaging delivers the notifications, and Google Play delivers the app and its updates; each processes data under Google's privacy policy. The HR and payroll records belong to the employee's company; we process them on its behalf, as set out in our Data Processing Agreement. Revebe ESS does not lend money: a loan request goes to the employee's own employer.

Security: the app connects only over encrypted connections (HTTPS) and trusts only the phone's own certificate authorities. File downloads work only on the Revebe ESS pages of our own site.

Deleting your data: signing out in the app revokes its token on our servers. Your HR record is kept by your company; to have it corrected or deleted, ask your company's HR, or follow Section 14 below.

8. How We Use Your Information

We do not use merchant store data to train models, to build profiles of individuals, or for any purpose other than delivering the service the merchant installed.

9. How We Share Information

We may share information with trusted service providers (hosting, payment processing, analytics, messaging infrastructure), with Meta Platforms when WhatsApp messaging features are used, with the advertising platforms described in Section 6 when a merchant configures them, and where required to comply with laws or protect our rights. We do not sell personal data to third parties.

10. Data Retention

We retain personal information only as long as necessary to provide services, maintain transaction records, comply with legal obligations and resolve disputes. When data is no longer required, it is securely deleted. The periods for each Shopify application are stated in Section 4.

11. Data Security

We implement safeguards including encrypted connections (HTTPS), secure server environments, controlled database access and access authentication. Access tokens are stored on our servers and are never exposed to browsers or third parties. Customer names and email addresses held by our Shopify applications are encrypted at rest, and backups are encrypted before they leave our servers. Access to our servers is limited to named administrators using key-based authentication, and is logged. However, no internet transmission is 100% secure.

12. Your Rights

Depending on your jurisdiction, you may have rights to access, correct, delete or restrict processing of your personal data, withdraw consent, and request data portability. Requests can be sent to info@revebe.com.

13. Uninstalling an Application

When a merchant uninstalls one of our Shopify applications:

We support Shopify's required privacy webhooks — customer data requests, customer redaction and shop redaction — and act on them within the periods Shopify requires. Catalogues previously created in a merchant's own Meta Business are not deleted, because they belong to the merchant and removing them could disrupt advertising they still rely on; a merchant can delete them at any time in Meta Commerce Manager.

14. Data Deletion Requests

Users may request deletion of their personal data by emailing info@revebe.com with their account email, business name and reason for the request. Upon verification, data will be deleted within 7 business days, unless retention is required by law. Instructions are also published in our Data Deletion Policy.

15. Children's Privacy

Our services are not intended for children under 16 years of age. We do not knowingly collect personal data from minors.

16. International Data Transfers

Our services may process data in countries where our infrastructure or partners operate. We ensure reasonable safeguards for international data transfers.

17. Third-Party Services

Our services may contain links to third-party services including Meta / Facebook, the WhatsApp Business Platform, Google, YouTube, TikTok, LinkedIn, Snapchat, Pinterest, Shopify, payment gateways and analytics providers. These third parties have their own privacy policies.

17.1 TikTok and LinkedIn accounts connected to Revebe CRM

When a company connects its TikTok Business Account, or a LinkedIn profile or Company Page, to Revebe CRM, we receive the account's name and identifier, its picture where there is one, and a sign-in token, which we store encrypted. For TikTok we also receive the direct messages and comments that customers send to that account, so that the company's staff can answer them, and figures on the account's videos and followers for the company's own reports. We publish only the posts the company creates. We never see or store the account's password. A company can disconnect an account at any time under Integrations, and can ask for its data to be deleted by writing to info@revebe.com.

17.2 YouTube channels connected to Revebe CRM (YouTube API Services)

Revebe CRM uses YouTube API Services. A company that uses Revebe CRM can connect its own YouTube channel, upload videos and Shorts to it from Social Posting, and see how those videos are doing. By connecting a YouTube channel or using these features you agree to be bound by the YouTube Terms of Service. Google's handling of your information is described in the Google Privacy Policy.

What we access. A channel is connected under CRM → Integrations → YouTube. Google's own page opens, where the person signs in (the password is typed there; we never see or store it), chooses the channel and allows two permissions: "Manage your YouTube videos" (to upload) and "View your YouTube account" (to find the channel and read its videos' figures). With them Revebe CRM reads the channel's ID, name, handle and picture; uploads the videos, thumbnails, titles, descriptions and tags that the company's staff publish through Social Posting; and reads the number of views, likes and comments of those videos. Revebe CRM does not read the channel's other videos, its subscribers, its comments or messages, or any other information in the Google account.

What we store:

How we use and share it. This information is used only to provide these features to the company that connected the channel, and is shown only to that company's own staff who have the right to use YouTube in its CRM. The videos and their details are sent to YouTube (Google) because the company asked for them to be published there. We do not share this information with other companies or other third parties, apart from our hosting provider, which keeps our servers. We do not sell it, use it for advertising, or use it to train artificial intelligence models.

Cookies and device information. The YouTube features set no cookies of their own and store nothing on your device. Revebe CRM uses its usual sign-in and security cookies, which are needed to keep you signed in. During the Google sign-in, a one-time security code is kept on our server, not on your device, for up to 15 minutes. No adverts are shown. The channel's picture is loaded from Google's servers.

Removing Revebe CRM's access. You can remove the access at any time in either of two ways:

Deleting the stored data. When a channel is disconnected in Revebe CRM, we delete at once its tokens, its ID, name, handle, picture and permissions, its posting times, and the YouTube video IDs and links of its posts. When the access is removed in the Google Account instead, or the sign-in ends for another reason, the same data is deleted 7 days after Revebe CRM finds the sign-in no longer works, unless the company connects the channel again in that time; in every case within 30 days. You can also ask us to delete it by writing to info@revebe.com with the channel's name or address; we delete it within 7 days. The posts themselves (text, video file and settings) are the company's own content and stay in its CRM as its records, without the YouTube video ID or link. Videos already uploaded stay on YouTube; you can delete them in YouTube Studio.

Google API Services User Data Policy. Revebe CRM's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Questions or complaints about Revebe CRM's use of YouTube can be sent to info@revebe.com, or by post to the address in Section 19.

17.3 Pinterest accounts connected to Revebe CRM

Revebe CRM uses the Pinterest API. A company that uses Revebe CRM can connect its own Pinterest account, publish Pins to its boards from Social Posting, and see how those Pins are doing. By connecting a Pinterest account or using these features you agree to Pinterest's Terms of Service. Pinterest's handling of your information is described in the Pinterest Privacy Policy.

What we access. An account is connected under CRM → Integrations → Pinterest. Pinterest's own page opens, where the person signs in (the password is typed there; we never see or store it) and gives Revebe CRM access. Revebe CRM asks for these permissions: read the account (user_accounts:read), read and create boards (boards:read, boards:write), and read and create Pins (pins:read, pins:write). With them Revebe CRM reads the account's ID, username, business name, picture and account type, and the names and privacy setting of its boards; makes a new board when the company's staff ask for one; publishes the Pins (photos or video, title, description, destination link and alt text) that the company's staff publish through Social Posting; and reads the impressions, saves, Pin clicks and outbound clicks of those Pins. Revebe CRM does not read the account's other Pins, its followers, its messages, or anything else in the Pinterest account.

What we store:

How we use and share it. This information is used only to provide these features to the company that connected the account, and is shown only to that company's own staff who have the right to use Pinterest in its CRM. The Pins and their details are sent to Pinterest because the company asked for them to be published there. We do not share this information with other companies or other third parties, apart from our hosting provider, which keeps our servers. We do not sell it, use it for advertising, or use it to train artificial intelligence models.

Cookies and device information. The Pinterest features set no cookies of their own and store nothing on your device. Revebe CRM uses its usual sign-in and security cookies, which are needed to keep you signed in. During the Pinterest sign-in, a one-time security code is kept on our server, not on your device, for up to 15 minutes. No adverts are shown. The account's picture is loaded from Pinterest's servers.

Removing Revebe CRM's access. You can remove the access at any time in either of two ways:

Deleting the stored data. When an account is disconnected in Revebe CRM, we delete at once its tokens, its ID, username, name, picture, account type, permissions and boards, its posting times, and the Pin IDs, links and boards of its posts. When the access is removed in Pinterest instead, or the sign-in ends for another reason, the same data is deleted 7 days after Revebe CRM finds the sign-in no longer works, unless the company connects the account again in that time. You can also ask us to delete it by writing to info@revebe.com with the account's name or address; we delete it within 7 days. The posts themselves (text, photos, video and settings) are the company's own content and stay in its CRM as its records, without the Pin ID, link or board. Pins already published stay on Pinterest; you can delete them on Pinterest.

Pinterest Developer Guidelines. Revebe CRM's use of information received from the Pinterest API follows the Pinterest Developer Guidelines.

Questions or complaints about Revebe CRM's use of Pinterest can be sent to info@revebe.com, or by post to the address in Section 19.

18. Changes to This Policy

We may update this policy periodically. Updates will be published on https://revebe.com/privacy.php

19. Contact Information

Revebe Digital Private Limited
18, Umar Commercial, Bahria Town, Lahore, Punjab 53720, Pakistan
Email: info@revebe.com
Phone: +92 328 3281111 · +92 328 3282222
Website: https://revebe.com