Faurya Privacy Policy
Last revised: 30 October 2026
Operated by: Markupx brands PVT LTD
Privacy and legal inquiries: founder@markupxbrands.com
Product and account support: team@faurya.com
Faurya is a website, product, and revenue analytics service operated by Markupx brands PVT LTD (referred to as “Faurya,” “we,” “us,” or “our”). We provide website analytics, billing-data integrations, subscription and revenue reporting, and attribution tools.
This Privacy Policy explains the personal information we handle, why we handle it, how it is protected and retained, and how individuals can exercise applicable privacy rights.
Important distinction: Faurya handles two different kinds of information. We manage information about people who use Faurya itself (such as account holders and support contacts). We also process information about a merchant's visitors and end customers on that merchant's behalf, when the merchant enables Faurya's analytics, payment-provider connections, or import features. These relationships are explained below.
1. Who this policy covers
This policy applies to:
People visiting Faurya's own website.
Faurya account holders, authorized users, and people contacting Faurya.
Information used to administer Faurya subscriptions, support, and service security.
At a general level, the website analytics and billing information that merchants instruct Faurya to process through the service.
If you are a visitor or customer of a business that uses Faurya, that business generally controls the data it collects about you. Please consult the business's privacy notice as well as the explanation in Section 4 of this policy.
2. What information we process
The information depends on the features used and the data provided. We may process the following categories as relevant to providing the service.
2.1 Faurya account and business information
Account identifiers and contact details, such as name and email address.
Organization, site or workspace information, user access roles, and account preferences.
Information about Faurya subscriptions, invoices, payments, and account administration.
Authentication, security, technical and support records associated with use of the service.
2.2 Website and technical information
When people use Faurya or when a merchant enables Faurya analytics on its own website, relevant technical and usage information may include:
Page visits, events, sessions, referrals, and conversion information.
Browser and device characteristics, page addresses, and event times.
IP addresses, approximate location signals, cookies, browser storage or other online identifiers, where the relevant technology is used.
Visitor or session identifiers used to understand activity and, where enabled, associate it with conversions.
IP addresses, cookie identifiers, and pseudonymous identifiers may be personal information under applicable law, even if they do not contain a person's name.
2.3 Merchant-connected customer and billing information
When a merchant connects a supported payment provider, enables webhook synchronization, or provides billing records through supported interfaces, information processed may include:
Customer identifiers and available customer contact or profile information.
Products, plans, prices, subscriptions and subscription status or history.
Orders, invoices, invoice line items, payments, refunds, disputes, and related transaction details.
Financial amounts, currency, transaction dates, payment or provider reference identifiers, and revenue calculations.
Website visitor/session identifiers associated with customer or billing records for merchant-enabled attribution.
Historical billing records provided or retrieved for synchronization and reporting.
The precise information depends on the merchant's configuration, provider permissions, record availability, and enabled features. The ability to access a provider field does not necessarily mean Faurya retrieves or stores it. Merchants should avoid supplying unnecessary sensitive information through metadata, events, imports, or support messages.
2.4 Communications
If you contact our team, we process the contact details, message content, and information you choose to provide so that we can respond and help resolve your request. Please do not send passwords, payment-card security codes, or unnecessary sensitive personal information.
3. Why we process information
We process personal information, as relevant to the relationship and enabled services, to:
Create and administer accounts, authenticate users, and provide requested service features.
Receive and process authorized analytics events, provider data, and merchant-initiated imports.
Calculate and display revenue, subscription, conversion, and attribution reports.
Operate and maintain payment-provider integrations and related webhooks.
Provide support, communicate service-related information, and respond to inquiries.
Maintain service reliability, investigate errors, protect accounts, and prevent misuse.
Administer Faurya's own billing and comply with applicable financial, contractual, and legal obligations.
Where EU or UK data-protection law applies to information we control, the relevant legal basis may be performance of a contract, compliance with a legal obligation, legitimate interests (such as securing and operating the service, subject to applicable balancing requirements), or consent where the activity legally requires consent. Different activities can require different bases. We do not treat consent to non-essential cookies as established merely because someone continues browsing.
For merchant-controlled data, the merchant ordinarily determines the purpose of collection and the appropriate legal basis. Faurya processes that information to provide the merchant's configured services under its instructions and the Data Processing Agreement (DPA).
4. Who controls the information
Faurya as controller: We ordinarily determine the purposes of processing information for our own account administration, website operations, support communications, security, and legal compliance. Individuals may direct requests about this information to our legal/privacy contact.
Faurya as processor: When a merchant uses Faurya to analyze that merchant's website activity, customers, subscriptions, or payments, the merchant ordinarily acts as controller, and Faurya processes personal information on the merchant's behalf. If that merchant is itself acting as a processor, Faurya may be a subprocessor.
If you want to access, correct, or delete information held in a merchant's Faurya workspace about you, contact that merchant first. We assist merchants with relevant requests in accordance with the DPA and applicable law.
5. Cookies, analytics, and tracking
Faurya's own website and Faurya tools installed by merchants are separate contexts. Depending on the features in use, cookies or similar technologies may support authentication, security, user preferences, analytics, or visitor/session recognition.
Where the law requires consent for non-essential cookies or similar technologies, that consent must be obtained before the relevant technology is used. Users may also have controls through their browser or device, although those controls do not necessarily provide every consent choice required by law.
Merchants are responsible for providing the required disclosures and obtaining any necessary consent for analytics or tracking that they deploy on their own sites. Faurya's technical behavior can depend on merchant configuration.
6. Information sharing and subprocessors
We do not sell merchant-controlled customer personal information or use it for Faurya's independent cross-context behavioral advertising.
We may disclose information only as necessary for the activities described in this policy or when permitted or required by law, including to:
Infrastructure providers: Faurya's applications and data processing run on Amazon Web Services (AWS) infrastructure. Our disclosed AWS hosting region is US East (Northern Virginia), United States (
us-east-1).A merchant's selected payment provider: to the extent the merchant has authorized connection, synchronization, or webhook configuration. A merchant-selected provider is not automatically Faurya's subprocessor.
Authorized personnel and professional advisers: where access is reasonably needed for support, operation, security, or legal compliance, subject to applicable safeguards.
Government or legal authorities: where disclosure is required by applicable law or a valid legal process.
Our public Subprocessors page describes the subprocessor arrangements disclosed by Faurya. We update that information as arrangements change in accordance with applicable agreements.
7. Where information is processed
Faurya operates its customer-data processing infrastructure in the AWS us-east-1 region (Northern Virginia, United States). Because this is a U.S. hosting region, personal information processed by Faurya may be held in the United States even where a merchant or visitor is located elsewhere.
If data-protection law restricts an international transfer, an appropriate lawful transfer mechanism is required. The applicable safeguards depend on the transfer, parties, and law involved. Questions about transfer arrangements may be directed to founder@markupxbrands.com; contractual processor and transfer obligations are also addressed in our DPA.
8. Data retention and deletion
Faurya provides self-service options for users to delete their data through the Faurya website, subject to their account permissions and the type of data involved. A deletion request may require Faurya to retain limited information where necessary for legal, accounting, security, or dispute-related purposes and as permitted by applicable law.
The following distinctions are important:
| Category | How retention or deletion works |
|---|---|
| Faurya account information | We keep account information while needed to provide and administer the account. Following account closure, account records that still need to be retained may be kept for up to five years, subject to earlier deletion where applicable law requires it. This is a maximum, not a mandatory five-year wait before deletion. |
| Merchant website, customer, and billing data | Merchant users can use the site's available deletion controls. Processing and deletion of merchant-controlled data follow the merchant's instructions, applicable service functionality, and our DPA. |
| Connected payment providers | Disconnecting a provider stops authorized ongoing access through that connection. Relevant Faurya-held data is handled according to the site's deletion behavior and applicable instructions. Deletion from Faurya does not delete records independently held by the payment provider. |
| Temporary technical records and backups | Temporary imports, technical logs, and backup copies may follow separate retention or expiry cycles. They are retained only for applicable operational, security, recovery, or legal purposes. |
| Faurya's own billing and support records | Retained only as long as reasonably needed for the relevant purpose and applicable legal requirements, which can differ from retention of merchant-controlled analytics data. |
We consider the information's purpose, legal requirements, security and recovery needs, and valid deletion requests when determining the applicable period. We do not promise that every kind of data disappears from every backup at the moment a user clicks Delete.
A merchant may need to update or disconnect a source to prevent deleted records from being imported again. The DPA governs return and deletion of merchant-controlled personal information under the applicable agreement.
9. Your privacy choices and rights
Depending on the law that applies to you and the information involved, you may be entitled to:
Request access to information about you.
Correct inaccurate information.
Request deletion or restriction of processing.
Object to certain processing or withdraw consent when processing is based on consent.
Request portable information, where the law provides that right.
Contact or complain to an applicable data-protection authority.
Faurya account holders: Use the data-deletion controls available on the site for supported self-service deletion. For additional assistance, contact team@faurya.com. For legal/privacy requests, contact founder@markupxbrands.com. We may need to verify your identity or authority before acting on a request.
Customers or visitors of a merchant using Faurya: Contact that merchant to exercise rights concerning the merchant's data. We will reasonably assist the merchant where required.
We respond to valid privacy requests within the time required by applicable law, subject to applicable exceptions.
10. Children's information and sensitive data
Faurya is designed for businesses and their authorized users; it is not designed as a children's service. Merchants should not intentionally supply sensitive information unrelated to the configured analytics and billing functions, including passwords, card security codes, or special-category personal data unless expressly supported and lawfully authorized.
If unsupported sensitive information is identified, we may work with the relevant merchant to restrict or remove it, subject to legal obligations and technical capabilities.
11. Security and incidents
We take measures intended to protect the personal information processed through Faurya against unauthorized access, misuse, alteration, or loss. Such measures are evaluated in light of the nature of the data and processing risks. Our DPA describes contractual safeguards and responsibilities for merchant-controlled information.
No online service can guarantee absolute security. If a security incident affects personal information, we will address notification and cooperation obligations as required by applicable law and, where relevant, our agreements with merchants.
For security and legal inquiries, contact founder@markupxbrands.com.
12. Automated analysis
Faurya generates analytical metrics and reports from the data merchants choose to connect or submit. The existence of analytics or automated calculations does not necessarily mean Faurya makes automated decisions about individuals that have legal or similarly significant effects. Any feature that does involve such decisions must be assessed and disclosed as applicable law requires.
13. Changes to this policy
We may update this policy as our services, integrations, or legal obligations change. We will publish the revised policy and its revision date, and provide any additional notice or obtain consent where required by applicable law. Where a separate agreement or DPA requires contractual amendment or acceptance, posting a revised privacy notice does not replace that process.
14. Contact and related documents
Legal entity: Markupx brands PVT LTD
Privacy, legal, and data-processing inquiries: founder@markupxbrands.com
Product and account support: team@faurya.com
Related documents: