Faurya Data Processing Agreement (DPA)
Last revised: 30 October 2026
Faurya legal operator: Markupx brands PVT LTD
Legal, privacy and data-processing inquiries: founder@markupxbrands.com
Product and account support: team@faurya.com
This Data Processing Agreement (DPA) governs the processing of Customer Personal Data by Markupx brands PVT LTD, operating as Faurya ("Faurya," "we," or "Processor"), on behalf of the business or other entity using Faurya ("Customer," "you," or "Controller," as applicable).
This DPA supplements the Faurya Terms of Service or another agreement between the parties (the Agreement) and applies when Faurya processes Customer Personal Data on the Customer's behalf. It is binding to the extent validly incorporated into or accepted under the Agreement. If Customer acts as a processor for another organization, references to Customer as Controller include that organization's relevant instructions and Customer's authority to appoint Faurya as a subprocessor.
This DPA does not govern Faurya's separate processing of personal information for its own account administration, service billing, website operation or direct support communications in its role as an independent controller. Those activities are described in the Privacy Policy.
1. Definitions and the parties' roles
Customer Personal Data means personal information that Faurya processes on behalf of Customer through the enabled Services, including information from Customer's websites, authorized payment-provider connections, or supported data submissions.
Customer Data includes information provided by, collected for, or imported at Customer's direction and the reports derived from that information, subject to applicable rights of third parties and individuals.
Services means Faurya's website/product analytics, conversion and attribution tools, subscription and revenue analytics, billing integrations, reporting, and supported related services.
Subprocessor means an external entity engaged by Faurya to process Customer Personal Data on Faurya's behalf in providing the Services.
Applicable Data Protection Law means privacy and data-protection laws applicable to the relevant processing, including the EU GDPR, UK GDPR, or California privacy laws where their requirements apply.
Terms such as Controller, Processor, Data Subject, Processing, and Personal Data Breach have the meanings provided by applicable law where relevant.
Customer ordinarily determines why Customer Personal Data is collected and how it is used. Faurya processes that information to provide the Services on Customer's instructions. Each party remains responsible for the duties that applicable law assigns to it.
2. Subject matter, duration and purpose of processing
Faurya processes Customer Personal Data for the purpose of delivering the Services selected and configured by Customer. Depending on the functions enabled, those activities include:
Website and product analytics: receiving website events, pageviews, sessions, referrals, browser/device information, visitor identifiers, goals and conversions.
Revenue and subscription analytics: receiving and organizing customer, plan, product, subscription, invoice, payment, refund, dispute, fee and related billing data; calculating recurring revenue, churn, customer and subscription movements, and other reports.
Authorized integrations: using Customer-provided credentials or access grants to receive provider webhooks, import historical records, and perform necessary follow-up reads to complete or reconcile records.
Attribution: where available and enabled, linking authorized visitor or session identifiers with conversions and billing-related events.
Customer submissions: processing supported API submissions and import files where those features are available.
Service operation: storing, validating, deduplicating, organizing, displaying, exporting, restricting and deleting records as necessary to operate and protect the Services.
Processing continues while the applicable Services are provided and during any lawful return, deletion or retention period after they end. Annex A describes the categories of personal data, individuals and processing operations in more detail.
3. Documented instructions and permitted use
Faurya will process Customer Personal Data only on Customer's documented instructions, which may be expressed through this DPA, the Agreement, account settings, connected integrations, supported API requests, and written instructions. An exception applies where processing is required by applicable law; where legally permitted, Faurya will inform Customer of that requirement beforehand.
Customer authorizes Faurya to access, retrieve, organize, store and analyze information from services Customer chooses to connect, within the permissions actually granted. Some integrations also require Faurya to create, update or remove webhook configurations at a connected provider. Those administrative actions are separate from changing a merchant's financial transactions. Standard analytics synchronization does not itself authorize Faurya to issue charges or refunds or change end-customer subscriptions.
As between Customer and Faurya, Customer and its licensors retain their lawful rights in Customer Data. Faurya receives only the limited rights reasonably necessary to provide, secure and support the contracted Services, follow permitted instructions, and meet legal obligations. This clause does not treat an individual's personal data as property or override rights held by third parties. Faurya retains its intellectual property in its software and service components.
Faurya will not sell Customer Personal Data, use it for independent behavioral advertising, or conduct unrelated cross-customer profiling. Where California's service-provider rules apply, the additional restrictions in Section 18 and Annex E also apply.
If Faurya believes an instruction violates Applicable Data Protection Law, it will inform Customer without undue delay unless prohibited by law and may suspend the affected instruction as reasonably necessary while the issue is addressed.
4. Customer responsibilities
Customer is responsible for:
Having a valid legal basis and providing required notices and obtaining required consent for the personal data it collects or directs Faurya to process, including website tracking where consent is required.
Having authority to connect its payment-provider accounts, authorize access to billing information, configure webhooks and import historical records.
Choosing appropriate account access, permissions, data fields and retention/deletion instructions for its use of the Services.
Avoiding unnecessary or unsupported sensitive data in website events, metadata, notes, API requests, import files or support communications.
Handling requests from its website visitors and end customers in its role as Controller, with assistance from Faurya as described in this DPA.
Customer must not intentionally submit passwords, card security codes, complete payment-card numbers, or other unsupported sensitive information to Faurya unless separately authorized and expressly supported by the relevant service. Faurya does not claim to automatically identify and reject every sensitive field a merchant might submit.
5. Confidentiality
Faurya will ensure that personnel authorized to process Customer Personal Data are bound by appropriate confidentiality obligations or legal duties of confidentiality. Personnel access will be limited to legitimate service, security, incident-response, compliance or Customer-requested support needs, subject to appropriate access restrictions.
6. Security measures
Faurya will implement and maintain technical and organizational safeguards appropriate to the nature of the data, the Services, and the risks to individuals, including safeguards required by applicable data-protection law. Such safeguards address access controls, protection of transmitted and stored information, credential handling, separation of customer accounts, system integrity, incident response, recovery, and management of data deletion.
Annex B sets out the relevant security objectives and obligations without representing that Faurya holds an unverified certification, has completed a particular security audit, or offers an unverified uptime, encryption or backup-recovery guarantee.
Faurya may update its security controls as technology and risks change, provided it does not materially reduce the overall level of protection and continues to meet applicable contractual and legal duties.
7. Subprocessors
Customer grants Faurya general written authorization, through the applicable Agreement and this DPA, to use subprocessors identified in the current Faurya Subprocessors Register for the processing described there.
Faurya uses Amazon Web Services (AWS) to provide infrastructure for its customer-data processing. The disclosed Faurya infrastructure region is US East (Northern Virginia), United States (us-east-1). Faurya's application performs the analytics and billing calculations using that infrastructure. The public register describes the currently disclosed subprocessor arrangements. The register does not, by itself, substitute for any legally required subprocessing agreements or international transfer instruments.
Faurya will:
Apply appropriate written data-protection obligations to its subprocessors, providing the protections required for the relevant processing under applicable law.
Remain responsible to Customer for the performance of its subprocessors' applicable data-protection obligations.
Notify affected customers by email at least 30 days before an intended addition or replacement of a subprocessor.
Allow customers 15 days after that notification to raise a reasoned objection at founder@markupxbrands.com.
Consider objections in good faith and seek a reasonable resolution, which may include an available alternative or cessation of the affected Services under the Agreement where no reasonable resolution is possible.
Updating the public register alone does not replace an advance notice that is legally or contractually required.
A merchant-selected payment platform such as Stripe, Dodo Payments, Paddle, Polar, Creem, Lemon Squeezy or Whop is not automatically a Faurya subprocessor merely because the merchant authorizes Faurya to retrieve data from that platform. Its role depends on the actual relationship and processing activity.
8. Requests from individuals
Taking into account the nature of processing and information available to it, Faurya will provide reasonable technical and organizational assistance to Customer with legally required requests for access, correction, deletion, restriction, portability and objection.
When Faurya receives a request about information controlled by a Customer, Faurya may refer the individual to that Customer and will act on the information according to verified Customer instructions or applicable law. Customer can use supported deletion features within Faurya or contact founder@markupxbrands.com regarding a legal/privacy request.
9. Personal Data Breaches
Faurya will notify Customer without undue delay after becoming aware of a Personal Data Breach affecting Customer Personal Data, as required by applicable law. Information provided will include the nature of the incident and reasonably available details of affected information, likely consequences and remedial measures; additional information may follow as investigation continues.
Faurya will take reasonable steps to investigate, contain and address the incident and assist Customer with applicable legal notification and cooperation duties. Customer remains responsible for decisions and notifications assigned to it as Controller, while Faurya remains responsible for its own statutory and contractual obligations.
10. Compliance assistance
Taking into account the nature of its processing and the information available, Faurya will reasonably assist Customer with applicable obligations relating to security, personal-data-breach notifications, data protection impact assessments, and consultations with supervisory authorities. This assistance is subject to applicable law and the parties' reasonable operational arrangements; no arrangement limits assistance that mandatory law requires.
11. International data transfers
Faurya's disclosed customer-data infrastructure uses the AWS us-east-1 region in the United States. Customer Personal Data may therefore be processed outside the country in which Customer or the relevant individuals are located.
Where applicable law restricts a cross-border transfer of Customer Personal Data, the parties will put an appropriate lawful transfer mechanism and any required safeguards in place. Depending on the circumstances, this may involve an adequacy decision, the relevant EU Standard Contractual Clauses, a UK transfer instrument, or other legally permitted arrangements. A reference to these mechanisms in this DPA does not itself establish that an instrument has been signed or that every transfer is lawful. Faurya will make required transfer documentation available or enter into the applicable instrument as necessary for a covered transfer.
Any validly executed transfer instrument takes precedence over inconsistent provisions of this DPA to the extent required by law. See Annex D for the processing and transfer information relevant to those arrangements.
12. Deletion, data return, disconnection and retention
Self-service deletion. Faurya provides controls within its website through which authorized users can delete supported data. Those controls apply according to the user's permissions, the records affected, and the relevant feature. Customer may also submit a verified request for deletion or return through founder@markupxbrands.com. Faurya will reasonably assist with valid requests that cannot be completed through available controls.
Individual records. Requests to delete an end customer's data may affect related subscription, invoice, payment, attribution and other records. The extent of deletion or restriction is determined by applicable instructions, relevant legal obligations and the functionality available for the affected records. Faurya does not promise that every linked financial record is automatically erased when one customer record is removed.
Payment-provider disconnection. Disconnecting a provider stops future authorized synchronization through that connection. Faurya's stated product behavior is to remove data associated with the disconnected provider from the active service. This does not cancel the merchant's independent provider account or erase records retained by that provider. Some temporary technical or recovery copies may expire under separate controlled retention cycles; records may also need to be protected against re-import if the connection is enabled again.
End of the Services. At the end of the processing services, Faurya will, at Customer's choice where required by applicable law, return or delete the Customer Personal Data processed on Customer's behalf and delete existing copies unless applicable law requires their retention. Where immediate removal from protected backups is impracticable, remaining copies will be restricted from ordinary processing and deleted on an appropriate scheduled cycle, with applicable deletion instructions addressed in any restoration process. Faurya will not keep Customer Personal Data for an unrelated business purpose after the Services end.
Exports. Customer may use export or return functionality made available by the Services and may request assistance where required by applicable law. No particular export format or interface is represented as available unless actually offered; mandatory portability and switching rights remain unaffected.
Technical and historical records. Imported data, staged files, webhook records, worker queues, logs, derived analytics and backups may follow different retention processes. Faurya will limit retention to what is reasonably necessary for the permitted purpose, applicable instructions, security, recovery, or legal requirements, and will delete or restrict such information when those purposes end. No unverified fixed backup-purge or temporary-file deletion deadline is promised in this DPA.
Faurya's own account records. Separate from Customer Personal Data processed under this DPA, Faurya account-administration records retained after account closure may be kept for up to five years where lawful and necessary, with earlier deletion where required. This is not a five-year retention requirement for merchant analytics or billing data and is governed primarily by the Privacy Policy.
Deletion within Faurya does not automatically remove records independently held by the merchant's payment providers or other third parties. Customers should make any desired export request before permanently deleting records where the interface permits that sequence.
13. Audits and demonstration of compliance
Faurya will make available information reasonably necessary to demonstrate compliance with its applicable processor obligations and will allow for and contribute to audits or inspections by Customer, or a qualified auditor appointed by Customer, as required by Applicable Data Protection Law.
The parties will first consider reasonable documentation-based reviews, where sufficient. Any further inspection will be arranged with proportionate notice, confidentiality and security safeguards to protect Faurya's systems and other customers' information, without restricting non-waivable audit rights.
14. Government and legal requests
Faurya will disclose Customer Personal Data to an authority only to the extent required by applicable law or otherwise authorized under documented instructions. Where lawful, Faurya will inform Customer of such a request and reasonably limit disclosure to what is required.
15. Liability and responsibility
Each party is responsible for its own compliance with applicable law and the obligations it has accepted under this DPA. Liability limitations or exclusions in the Agreement apply only to the extent permitted by law and cannot displace mandatory data-protection obligations or applicable international transfer instruments.
16. Agreement status, updates and precedence
This DPA applies as part of a validly accepted or incorporated Agreement. The current revised text is identified by the date shown above. Faurya may update this DPA to reflect changed Services or legal requirements, subject to any applicable notice, contractual amendment or renewed-acceptance requirements. A revised webpage alone does not replace acceptance or execution required by law or an existing agreement.
If these provisions conflict with the Terms regarding Customer Personal Data processed on Customer's behalf, this DPA governs that processing. An applicable executed international transfer instrument prevails as legally required.
This DPA remains applicable while Faurya processes relevant Customer Personal Data, including any lawful restricted retention period after service termination.
17. Governing arrangements and contact
Except where applicable mandatory law or international transfer instruments require otherwise, dispute and governing-law provisions of a validly applicable Agreement govern this DPA. No unconfirmed exclusive court or country is imposed by this document.
Legal, privacy, data-processing, security and contractual notices: founder@markupxbrands.com
Product and account support: team@faurya.com
18. California privacy terms (where applicable)
This section applies only where Customer is a covered Business under the California Consumer Privacy Act, as amended (CCPA), and Faurya acts as the relevant Service Provider or Contractor with respect to Personal Information supplied under the Agreement.
Specific purposes. The Personal Information is disclosed to Faurya solely to provide the functions that Customer enables: website analytics and event measurement; billing, subscription and historical-data synchronization; revenue, conversion and attribution reporting; related integration and webhook management; Customer-directed support; and service security, integrity and troubleshooting.
No sale or sharing. Faurya will not sell or share that Personal Information as those terms are defined by the CCPA, including for cross-context behavioral advertising.
Restrictions on use. Faurya will not retain, use or disclose such Personal Information for purposes outside the specified business relationship or purposes above except as the CCPA and its regulations permit.
Combining information. Faurya will not combine Personal Information from different businesses or its own separate interactions with individuals except to the extent expressly permitted by California law. This does not prohibit an otherwise lawful, merchant-authorized connection of that merchant's visitor and billing records for its own attribution reporting.
Compliance and notification. Faurya will comply with the CCPA obligations applicable to its relevant service-provider or contractor role, provide the legally required level of privacy protection, and notify Customer if it determines that it can no longer meet those obligations.
Verification and remediation. Customer may take reasonable and appropriate steps to verify compliant handling and, following notice, stop or remediate unauthorized use, subject to safeguards that do not unlawfully restrict California rights.
Consumer requests. Faurya will provide required assistance with covered consumer requests and enter into applicable written restrictions with downstream processors handling the covered Personal Information.
This section does not automatically classify Faurya as a California service provider for every processing activity. Faurya may act as a separate controller/business for its own account and website information, as explained in its Privacy Policy. Additional processing particulars are summarized in Annex E.
Annex A — Processing details
| Topic | Details |
|---|---|
| Subject matter | Website/product analytics, visitor conversion and attribution data, connected billing and subscription records, customer-authorized historical imports and reporting. |
| Duration | While Customer uses the relevant enabled Services and during applicable return, deletion or lawful restricted-retention periods. |
| Nature of processing | Receiving, collecting, importing, validating, recording, structuring, storing, organizing, combining, calculating, displaying, querying, exporting, restricting and deleting. |
| Purposes | Providing configured analytics, revenue reporting, subscription metrics, attribution, historical synchronization, customer support and service integrity. |
| Data subjects | Merchant website/application visitors; its customers, purchasers and subscribers; individuals named in authorized financial records; and authorized users whose information is processed on the merchant's behalf. |
| Types of personal data | Visitor/session identifiers; online identifiers, IP-related and browser/device data where collected; website events and conversion activity; customer IDs, names and contact information where present; plan/subscription and billing profile data; invoices, orders, payments, refunds, disputes, amounts, currencies, transaction dates and identifiers; associated attribution information and relevant merchant-provided metadata. |
| Sources | Customer's websites and applications, supported tracking tools, merchant-authorized payment-provider APIs and webhooks, and Customer-submitted API/import records where available. |
| Frequency | Event-driven, periodic, ongoing or one-time historical imports, according to enabled features. |
| Unsupported sensitive data | Customers should not submit card security codes, complete card numbers, authentication passwords, unrelated special-category data or unnecessary sensitive information in metadata, events or import files. The interface is not represented as detecting and automatically rejecting all such fields. |
| Recipients / locations | Faurya personnel with appropriate access and authorized subprocessors, including AWS in the disclosed us-east-1 infrastructure region; see the public Subprocessors Register. |
| Instructions | Agreement and this DPA, relevant account/integration settings, supported API requests, and documented authorized communications. |
The categories above describe types of data that may be processed, not a representation that every merchant supplies all categories or that Faurya stores every available field from a payment provider.
Annex B — Technical and organizational security obligations
Faurya will maintain proportionate safeguards addressing these objectives, taking account of the processing risks and applicable law:
| Safeguard area | Objective |
|---|---|
| Authentication and access controls | Restrict access to Customer Personal Data and administration functions to authorized users and personnel with legitimate operational needs. |
| Confidentiality | Apply appropriate confidentiality duties to personnel and contractual requirements to subprocessors. |
| Transmission and storage | Protect data in transit and at rest using safeguards appropriate to the risks and relevant technologies. |
| Integration credentials | Apply access restrictions and appropriate handling to merchant API credentials and webhook secrets, including revocation when a connection ends. |
| Data isolation and integrity | Apply appropriate safeguards against unauthorized access between customers and unintended alteration of records. |
| Webhook and import integrity | Protect supported integration endpoints against unauthorized submission and improper reuse of events, using applicable provider-supported measures as appropriate. |
| Incident response | Provide processes for assessing, containing, investigating and reporting relevant personal-data incidents. |
| Availability and restoration | Maintain recovery and continuity measures appropriate to the Services and risks. |
| Retention and deletion | Apply access restrictions and deletion/expiry procedures for active data, temporary imports and recovery copies in accordance with Section 12. |
| Review and improvement | Reassess safeguards where appropriate in light of changes in threats, processing and the Services. |
This annex describes contractual safeguard objectives. It does not claim that Faurya holds SOC 2/ISO certifications, has completed any specified independent audit, encrypts every individual system with a particular algorithm, or achieves a fixed uptime/recovery target.
Annex C — Authorized subprocessors
Faurya's maintained public Subprocessors Register identifies its disclosed subprocessors and processing activities. Customers authorize the use of listed subprocessors subject to Section 7 of this DPA and the applicable Agreement.
At the time of this revision, Faurya identifies Amazon Web Services (AWS) as its disclosed cloud infrastructure subprocessor. Faurya's stated infrastructure region is US East (Northern Virginia), United States (us-east-1). Relevant personal-data categories include visitor or session identifiers, merchant customer and billing records, and associated account/technical information processed through the Services, depending on configuration.
Changes to authorized subprocessors are subject to 30 days' advance notice by email and a 15-day objection window as described in Section 7. The register is the source for the currently published list; a change to that webpage alone does not override contract or statutory notice requirements.
Annex D — International transfers
The disclosed hosting location for Customer Personal Data processed through Faurya's AWS infrastructure is the United States (us-east-1). Data may therefore cross national boundaries when merchants or their users are located elsewhere.
Where EU, UK or other applicable law requires specific transfer safeguards, the relevant parties must implement them before carrying out a restricted transfer. Depending on the specific relationship, this may include appropriate standard contractual clauses, an applicable UK addendum/transfer agreement, adequacy, or other lawful mechanism. Faurya will provide or enter into required documentation as applicable; this Annex is not itself an executed standard contractual clause or evidence of a completed transfer assessment.
Applicable transfer documentation may need to specify the relevant data exporter/importer, contact information, roles, data categories, purposes, transfer frequency, onward recipients, retention and technical safeguards. The parties will cooperate as required to complete that information.
Annex E — California service-provider processing details (conditional)
This annex supplements Section 18 only to the extent the CCPA service-provider or contractor requirements apply.
| Topic | Processing arrangement |
|---|---|
| Disclosing business | Customer, where it is a CCPA-covered Business. |
| Recipient role | Faurya as Service Provider or Contractor for the relevant covered processing. |
| Specific business purposes | Authorized website analytics; billing and subscription synchronization; recurring revenue, churn, conversion and attribution reporting; necessary webhook management; Customer support; service integrity and security. |
| Information categories | Visitor/session identifiers, website events, customer and subscription identifiers, customer contact details where present, and authorized billing, payment, invoice, refund, dispute and attribution records. |
| Consumers | Customer's relevant website/application visitors, buyers, subscribers and other individuals represented in the authorized records. |
| Restrictions | No CCPA sale or sharing; no unrelated commercial use, prohibited cross-business combination or unauthorized disclosure. |
| Rights and assistance | Customer oversight, legally required consumer-request assistance and required downstream contractual restrictions under Section 18. |
| Duration | For the relevant Services and subsequent lawful return, deletion or restricted retention as described in Section 12. |
For questions about this DPA, privacy requests or contractual notices, email founder@markupxbrands.com. For service or account support, email team@faurya.com.