haggl.ai Privacy Policy

Effective Date: March 11, 2026
Last Updated: October 28, 2026

1. Introduction

This Privacy Policy explains how MOOJO.ID, INC. ("Moojo," "we," "us," or "our") collects, uses, and protects information when you use haggl.ai ("Service"). haggl.ai is performance marketing for agentic commerce: vendors install a JavaScript embed on their website that enables AI agents acting on behalf of buyers to discover, negotiate, and receive personalized offers in real time.

This policy applies to two distinct groups: Vendors (businesses that install the haggl.ai embed and configure their negotiation settings) and Buyers / AI Agents (end-users or automated agents that interact with the haggl.ai negotiation endpoint on a vendor's site).

haggl.ai is operated by MOOJO.ID, INC., 11140 Rockville Pike, 100-346, Rockville, MD 20852, USA. Privacy contact: privacy@moojo.id.

This policy explains our data practices. Where processing relies on consent, we ask for it separately, and you can withdraw it as described below.

2. Information We Collect

2.1 Vendor Account Data

When a vendor registers for haggl.ai, we collect:

• Account information: Name, business email address, company name, and website URL
• Authentication data: Credentials managed via Firebase Authentication (passwords are hashed; we do not store plaintext passwords)
• Billing information: Stripe processes payment details for vendors billed directly by haggl.ai. Shopify manages billing for the public Shopify app; we receive and store the selected app plan and subscription status to determine access to the Service. We do not store raw payment card data.
• Configuration data: Ideal Customer Profile (ICP) parameters, discount rules, pricing tiers, and negotiation policies the vendor defines in their dashboard
• Embed analytics: Aggregate statistics on agent visits, negotiation sessions, and offer outcomes on the vendor's site

2.2 Buyer / Agent Negotiation Data

When an AI agent or buyer initiates a negotiation via a vendor's haggl.ai-enabled site, we may receive and process:

• Customer profile data: Structured attributes submitted by the agent to establish eligibility for a personalized offer (e.g., company size, industry, usage context). This data is provided voluntarily by the agent on the buyer's behalf.
• Negotiation context: The products or plans under consideration, stated requirements, and any constraints provided during the session
• Offer and outcome data: The personalized offer generated, whether it was accepted or declined, and session metadata (timestamps, session ID)
• Verification evidence: Buyers or their agents may submit supporting claims and email evidence to establish eligibility for an offer. Evidence may include sender information, subject, date, an excerpt, and the original email message for signature verification. Our built-in negotiation service removes original email message fields before storing the negotiation or sending its context to the AI model. Submitted metadata and excerpts, content hashes, and verification results may remain in the negotiation record. Order confirmation emails sent to claim cashback are handled as described in Section 2.7 instead.

2.3 Information We Do Not Collect

We do not collect, request, or process:

• Payment card information or financial account details from buyers (handled by vendors independently)
• Protected health information (PHI)
• Government-issued identifiers (e.g., Social Security numbers, passport numbers)
• Authentication credentials, API keys, or passwords from buyers
• Precise GPS location data
• Full conversation transcripts from external AI assistants

2.4 Shopify App Data

When a merchant installs the haggl.ai Shopify app (“haggl.ai: win the agentic sale”), we process Shopify store and app identifiers, the store name and domain, catalog information such as products, prices, and collections, and the permissions and authorization tokens needed to operate the app. We use this information to connect the store, display eligible products, apply merchant-defined reward rules, and create and check single-use discount codes for Shopify checkout. Stored Shopify access and refresh tokens are encrypted.

The app processes paid-order and refund events to identify eligible merchandise, attribute negotiated discounts, calculate haggl.ai fees and reverse fees for refunded items. Financial records include order and line references, product and variant references, quantities, amounts, currency, discount attribution and timestamps. We do not need buyer names, email addresses, phone numbers or delivery addresses for this calculation. Mandatory Shopify privacy requests can contain customer or order identifiers; we use them to locate relevant records and prepare data exports or remove attributable records. Information and evidence submitted directly by buyers or their agents are processed separately as described in Section 2.2.

2.5 Stripe App Data

When a merchant installs the haggl.ai app on a Stripe account, we process the account ID chosen on Stripe's install screen, the permissions granted and the access and refresh tokens Stripe issues. Stored tokens are encrypted. We import the account's active products and prices to draft the offer brief and keep it in sync. For each accepted deal we create a coupon and a Checkout Session on the merchant's account. We read those sessions' payment status and line items, the first invoice of a subscription deal, and refunds and lost disputes of those purchases, to confirm payment and to calculate and reverse haggl.ai fees. Deal records keep the levers applied, the buyer's stated claims, Stripe object IDs and the deal status, and are deleted 12 months after the negotiation starts. When the merchant chooses webhook fulfillment, we forward each paid session's customer ID, customer email and metadata to the merchant's endpoint, signed with the merchant's secret.

2.6 Agentic Discounts and the haggl ID

On haggl.ai/agentic-discounts, a buyer or their AI agent can search the merchants that run a sales agent on haggl.ai, ask them for offers, and keep those offers together under a haggl ID.

• Discount search: We use the search query (a business, website or product) only to find matching merchants. It is not linked to a haggl ID.
• Offer links: An agent that can only open web pages can follow a merchant's offer link. It opens a negotiation session (Section 2.2) that contains no details about the buyer.
• haggl ID: Created only if the buyer agrees to the consent text shown with it; a buyer can decline and still ask merchants for offers. A haggl ID is a random identifier that the buyer's agent keeps. We store a cryptographic hash of it, not the identifier itself, with the date it was created, the time it was last used to ask a merchant for an offer, and limited evidence of the agreement: the consent version, a hash of the consent text, the date, where the buyer agreed (in their agent's conversation, as relayed by the agent; with the checkbox on our page; or on a confirmation page their agent sent them) and, when an agent relayed the agreement, the buyer's words of agreement as the agent quoted them, with email addresses, phone numbers and links removed. We do not require a name or email address to create a haggl ID. A confirmation page link is valid for 30 minutes; we keep the pending confirmation until a day after it expires. Negotiations the agent opens with the haggl ID are linked to that hash. The hash is a pseudonymous identifier, not an anonymous one. Anyone who has the haggl ID can retrieve its record, offers, codes and cashback claims, including payout links, and delete it, so the buyer should keep it private.
• haggl ID record: From the linked negotiations we compute a record of counts and dates: when the haggl ID was created, the numbers of distinct emails that passed our signature check (told apart by a cryptographic hash of each email) and of distinct domains that signed them, the date of the latest successful check, and the numbers of merchants asked, offers received, offers accepted and distinct paid orders we recorded. For haggl IDs created under the consent of October 16, 2026 (version 2026-10-16.4) or later, the record also counts, for each shopping category of our brand index (such as travel), how many of those emails, and how many distinct businesses that signed them, were in it; purchases in the health category are never counted. The record does not include those domains or email content, does not name the businesses, the merchants asked or what was bought, and includes no offer details. Using the haggl ID authorizes us to share this record with the sales agent of each merchant the buyer's agent asks for an offer, to help assess eligibility and personalize offer terms. When the buyer's agent asks the merchants in a category for bids, we ask up to five of them on the buyer's behalf, and each of their sales agents receives the record. Merchants never receive the haggl ID or its hash. The record, offers and codes are shown back to whoever presents the haggl ID.
• Negotiations behind the record: The record excludes email content, but the negotiation sessions linked to a haggl ID separately keep what the buyer's agent submitted in them, including evidence metadata and excerpts, as described in Section 2.2.
• haggl.ai plugin for AI assistants: If a buyer installs the haggl-agentic-discounts plugin in Claude Code or Cowork, it sends haggl.ai the domain of a Shopify store before the buyer's agent creates a checkout there through Shopify's Shop tools, to learn whether that store's merchant runs a sales agent on haggl.ai. It sends nothing else from the checkout or the conversation. We use the domain as a search query. On the buyer's computer, the plugin keeps hashes of the store domains it already looked up in a session.
• Personalized prices: Offers made in a negotiation are personalized using automated decision-making. Each such offer carries the notices "This price was personalized using automated decision-making." and "THIS PRICE WAS SET BY AN ALGORITHM USING YOUR PERSONAL DATA", and our pages show them next to the price. A cashback rate set by the AI model (Section 2.7) carries the same two notices, together with how to ask a person to review it.
• Asking a brand to join: When a buyer asks a brand that isn't on haggl.ai to join, we add one to that brand's request count and record when the latest request came. We don't record who asked. We count one request per network address per brand per day.
• Abuse limits: We count search, offer-link, haggl ID, confirmation, brand and cashback requests per network address, and cashback claims and rate requests per haggl ID, stored as hashes, to limit abuse. These counts expire after their time window.

2.7 Cashback

haggl.ai pays cashback from its own budget on orders at participating stores. The store is not involved in a claim.

• Your rate: Each participating store has a range of cashback rates. When your agent asks us for your rate at a store before you buy, an AI model (Anthropic) sets it inside that range from how valuable you are likely to be as that store's customer, using what your agent sends with the request. Only if you give a separate permission with that request does it also use your haggl ID's record, which stores signed the emails we verified in your earlier negotiations, and your earlier cashback claims at that store; this can raise or lower your rate, and agreeing to the cashback terms never gives it. Health purchases are never used. The store never sees any of it. The rate holds for one order at that store placed before the time the quote shows; a claim without one gets the store's lowest rate.
• How the rate is set: The AI model estimates how likely you are to become a valuable, lasting customer of the store and picks a rate inside its range. Proven spending in the store's category or at its competitors moves it up; being an existing customer of the store, or having little to show, keeps it at or near the lowest rate. Price sensitivity, urgency or eagerness to buy never raise it. The rate decides your cashback on that order, never the store's price or whether you can buy. If you think it is wrong, email privacy@moojo.id with the quote ID within 30 days: a person at haggl.ai will review it, consider what you tell us, and can raise it within the store's range.
• Claiming: When you ask your agent to claim haggl.ai cashback for an order, and you agree to the cashback terms, your agent sends us the store's order confirmation email exactly as you received it, with your haggl ID. We check the store's digital signature, which also gives us the order date, and an AI model (Anthropic) reads the email's text for the order total, currency and order number.
• What we keep: The store (its name and category, and its main domain: example.com, even when the email came from mail.example.com), the order total, currency and date, the cashback amount and status, the rate quote it used, fingerprints (SHA-256) of the email, of the order number and of your haggl ID, and evidence of your agreement: the terms version, a hash of the terms text, the time, how you agreed, and your words of agreement with email addresses, phone numbers and links removed. We don't keep the email or its content, including the address it came from.
• Rate quotes: For each quote we keep the store, the rate and its time limit, fingerprints (SHA-256) of your haggl ID and of what the rate was based on, the AI model's assessment, which we never show you or the store, evidence of your record permission if you gave it, and a person's review if you asked for one. We don't keep the emails your agent sends with the request.
• Your payout: A link issued by our payout provider, Tremendous, where you choose how to receive it. Tremendous receives the amount, currency and our claim reference, not your name or email unless you give them to Tremendous when you redeem. We don't store the link; your agent gets a new one each time it asks.
• Your claims, rates and haggl ID: Whoever presents the haggl ID can see its cashback rates and claims and get their payout links. Cashback rates and claims are not part of the haggl ID record that merchants' sales agents receive. Deleting the haggl ID deletes its rate quotes that no claim used, and leaves its claims, with the quotes they used, as billing records that can no longer be read with it.
• Billing stores: We keep claim records as financial records for as long as the law requires, and we may share totals per store with that store.
• Hotel cashback: For a limited test, haggl.ai pays cashback on stays at independent and boutique hotels in San Francisco; the hotels are not involved. Your agent may send us signed flight or hotel emails to prove past trips there, the hotel's booking confirmation, and its post-stay email. We check their signatures and an AI model (Anthropic) reads the trip, hotel, dates, total and how the booking was made. We keep those, fingerprints (SHA-256) of the emails and of the addresses they were sent to, your tier and rate, how you came to the offer (the agent's name or campaign tags), and evidence of your agreement; not the emails. To pay you, we keep the email address you give for the payout and send the cashback by bank transfer through Stripe, which emails you a link to give it your bank details directly, or by PayPal; either receives that address, the amount and our reference. We delete the payout address 6 months after the claim, trips and unused quotes 12 months after they were made (or when the haggl ID is deleted), and keep claims as financial records.

2.8 BigCommerce App Data

When a merchant installs the haggl.ai app for BigCommerce (“haggl.ai: win the agentic sale”), we process the store hash, the BigCommerce user IDs of the store owner and of the user who installed the app, the store owner's email address as BigCommerce reports it, the store name, URL and currency, catalog information such as visible products, prices, variants and categories, and the permissions and access token needed to operate the app. We use this information to create the store's haggl.ai workspace, add the haggl.ai script to the storefront, register webhooks for order and product changes, keep the catalog in sync, and create a single-use coupon on the store for each accepted deal. The stored access token is encrypted. To refuse a replayed request, we keep a hash of each signed app-load request's identifier, with the store hash and the time.

BigCommerce notifies the app when an order is created, its status changes or it is refunded. The app reads the coupon codes on that order. Only for an order that used a haggl.ai deal's code does it read the order and its products, to confirm payment, attribute the deal's discount, count it against the merchant's budget, and calculate haggl.ai fees and reverse them for refunds. Financial records include order and line references, product and variant references, quantities, amounts, currency, discount attribution and timestamps. We do not store buyer names, email addresses, phone numbers or addresses from these orders. Information and evidence submitted directly by buyers or their agents are processed separately as described in Section 2.2.

2.9 Wix App Data

When a merchant installs the haggl.ai app for Wix (“haggl.ai: win the agentic sale”), we process the Wix app instance and site IDs, the site name and URL, and the site owner's email address as Wix reports it. For a site with Wix Stores, we import catalog information such as products, prices, variants and collections. For a site that sells services, we import its Wix Bookings services and, from its business details, the business phone, address, country, language and currency; the business phone is what a buyer's agent receives with a deal. We use this information to create the site's haggl.ai workspace, add the haggl.ai script to the site, keep the catalog or services in sync, and create a single-use coupon on the site for each accepted deal, with a checkout link that applies it. We do not store a Wix access token: the app asks Wix for a short-lived one when it needs it, and Wix stops issuing them once the app is removed.

Wix sends the app the site's order events: an order approved, its payment status changed, or a refund completed. Each order is checked for a haggl.ai deal's code, and only an order that used one is recorded, to confirm payment or a booking, attribute the deal's discount, count it against the merchant's budget, and calculate haggl.ai fees and reverse them for refunds. Financial records include order and line references, product and variant references, quantities, amounts, currency, discount attribution and timestamps. We do not store buyer names, email addresses, phone numbers or addresses from these orders. Information and evidence submitted directly by buyers or their agents are processed separately as described in Section 2.2.

2.10 Agent Visits to Merchant Sites

The haggl.ai embed on a merchant's site counts two kinds of page loads: those made by a browser that an AI agent controls (the browser reports that it is automated, or its user agent names a headless browser or Google-Agent), and those that arrive from an AI assistant (the referring site, or the link's utm_source tag, names ChatGPT, Perplexity, Gemini, Copilot, Claude, Grok or Meta AI). We also count page loads by a browser that an AI provider runs for its users and that signs its requests to haggl.ai with the provider's key (for example ChatGPT's agent). We check each signature against the key the provider publishes and keep only the provider's name. For such a page load, the embed sends haggl.ai only the merchant's vendor ID, the site's host name and which of these it was, or, for a signed request, we read the same from the request the embed already makes, and we add one to that merchant's daily count for that host. We do not store the page address, the referring address, an IP address, a cookie, the signature or any other identifier of the visitor, or a record of the individual page load. Other page loads send nothing. The daily counts are kept as aggregated analytics (Section 5).

3. How We Use Your Information

3.1 Vendors

• Provisioning and operating vendor accounts and dashboards
• Calculating purchase-based haggl.ai fees, processing refunds and fee adjustments, and collecting fees through Stripe for directly billed merchants or Shopify app billing for Shopify merchants
• Executing negotiation logic against vendor-defined ICP and pricing rules
• Providing analytics and reporting on negotiation performance
• Communicating service updates, usage alerts, and support

3.2 Buyers / Agents

• Evaluating submitted customer profile data against the vendor's ICP to determine offer eligibility
• Generating and returning a personalized offer to the agent
• Recording negotiation outcomes for vendor reporting
• Linking negotiations to a haggl ID the buyer opted into, computing its record, and sharing that record with the sales agents of the merchants the buyer's agent asks with it, to help assess eligibility and personalize offer terms (Section 2.6)
• Setting cashback rates by automated decision-making, checking order emails sent to claim cashback, paying cashback through Tremendous, preventing duplicate or fraudulent claims, and billing stores (Section 2.7)

3.3 Service Improvement

• Aggregated, anonymized analytics to improve negotiation quality and protocol reliability
• We do not create buyer profiles for behavioral advertising. If a buyer opts into a haggl ID, we create and maintain the cross-merchant record described in Section 2.6 to support verification and personalized offers. The buyer can choose whether to use the ID and can delete it at any time

3.4 Legal Bases (EEA and UK)

Where the GDPR or the UK GDPR applies, we rely on:

• Contract: running vendor accounts and billing; making the offers a buyer's agent asks for; cashback quotes priced from what your agent sends; cashback claims and payouts under the cashback terms
• Consent: the haggl ID and its record, and the separate permission to use that record for a cashback rate; analytics cookies where we ask for them. You can withdraw consent at any time (Section 7)
• Legitimate interests: preventing fraud and abuse, such as signature checks and request limits, securing the Service, and aggregated analytics to improve it. You can object to this processing (Section 7)
• Legal obligation: keeping financial records of cashback claims and fees

4. Data Sharing and Recipients

4.1 Sharing Between Vendors and Buyers

Customer profile data submitted by a buyer during a negotiation session is shared with the relevant vendor as part of delivering a personalized offer. Vendors receive this data subject to their own privacy obligations toward their customers.

When a buyer's agent asks with a haggl ID, the merchant's sales agent also receives the haggl ID record described in Section 2.6: counts and dates only, including the per-category counts where the consent covers them, never the signing domains, the businesses' names, the content of an email, the haggl ID or its hash. So does the sales agent of each merchant asked for a bid.

When a merchant connects its ServiceBridge account, each deal handed over by phone is also written to that account as a lead: the deal reference, the job as the merchant's price list names it, the agreed terms, the customer profile the offer was made for and, if the buyer's agent gave one, the postcode. The lead never includes the buyer's name, email address or phone number, or anything else the buyer wrote. We store the ServiceBridge API user ID the merchant gives us, and its password encrypted, until the merchant disconnects it.

For the public Shopify app and the haggl.ai apps for Wix and BigCommerce, the relevant merchant can also view negotiation history, submitted profile information and evidence metadata or excerpts, verification results, and offer outcomes in the embedded haggl.ai dashboard within Shopify admin, the Wix dashboard or the BigCommerce control panel. Original email message fields are not included in that dashboard.

4.2 Service Providers

4.3 No Sale of Personal Information

We do not sell, rent, or trade personal information to third parties for marketing or advertising purposes.

4.4 Legal Requirements

We may disclose information if required by law, regulation, legal process, or governmental request, or to protect the rights, property, or safety of Moojo, our users, or others.

5. Data Retention

• Vendor account data: Retained while the account is in use. Account deletion removes eligible account and workspace records; accounts with connected stores, billing, or unresolved purchases require closure review before deletion is completed. Limited security and accounting records described below may remain
• Negotiation session data: Deleted automatically 12 months after the negotiation starts, or earlier through an applicable account-deletion or privacy-request process. Until then, it is retained for negotiation history, vendor analytics, and dispute resolution. Records needed for billing, refunds, and disputes are kept separately, as described for billing records below
• haggl ID: Your haggl ID expires 12 months after your agent last uses it to ask a merchant for an offer. It cannot be used or renewed after expiry and is then automatically deleted, usually within a day. Reading the record does not count as use, and the buyer can delete the haggl ID earlier at any time. Deleting a haggl ID removes its stored hash and associated record, unlinks its negotiations and deletes its cashback rate quotes that no claim used. It does not itself delete the underlying negotiation sessions or its cashback claims, which remain subject to the separate retention and deletion rules in this policy
• Cashback claims: Kept as financial records for as long as the law requires, including after the haggl ID is deleted. Monthly cashback totals per haggl ID, kept to apply the monthly cap, are deleted after about two months
• Cashback rate quotes: Deleted 12 months after the quote; a quote no claim used is deleted earlier, when its haggl ID is deleted
• Billing records: Records needed to reconcile charges, refunds, and disputes may be retained after account closure. Stripe and Shopify retain their own billing records under their policies
• Aggregated analytics: Anonymized usage statistics may be retained indefinitely for service improvement

For the public Shopify app, we disconnect access and remove stored Shopify authorization tokens when we process a confirmed uninstall. When Shopify subsequently requests shop-data deletion and the installation is confirmed inactive, we remove stored Shopify authorization tokens, imported catalog, campaign configuration, pending account links, account-link audit records, discount-delivery records, and attributable order and refund records. An app-created workspace that has not been linked to a separate haggl.ai account is also deleted, including its negotiation sessions and usage records. For a workspace linked to a separate haggl.ai account, we preserve that account, workspace, and negotiation history for its independent use of the Service; account closure or a separate privacy request addresses those records, and negotiation sessions are still deleted 12 months after they start. For these separately linked accounts, we keep a restricted relinking record containing the haggl.ai account and workspace identifiers, a hash of the Shopify store identifier, and an installation key derived from the store domain. This record is pseudonymous, not anonymous. We use it to preserve workspace ownership, prevent reassignment to another account, and let the same account reconnect after reinstalling. It remains until an applicable account-closure request is reviewed and completed; deleting an account with this retained link requires contacting support at privacy@moojo.id.

Pending Shopify privacy requests retain encrypted shop, order and request identifiers needed to process the request and retry safely. We clear that replay copy when processing completes. Completed technical receipts retain request hashes, processing status, and timestamps. Prepared customer-data exports are encrypted and restricted to authorized merchant access for delivery; later applicable redaction requests remove them. Limited security records, such as account identifiers and deletion-request timestamps, may remain to prevent a pending request from recreating a deleted account binding. Accounting entries needed for reconciliation may remain after source order and installation identifiers are removed; retained entries may remain associated with the merchant workspace.

For the haggl.ai app for BigCommerce, uninstalling deletes the stored access token, disconnects the store from its workspace and pauses a running budget. BigCommerce removes the storefront script and the webhooks. We keep the workspace, its imported catalog, campaign settings and negotiation history, so that reinstalling reconnects the same workspace; negotiation sessions are still deleted 12 months after they start. To have the workspace and its records deleted sooner, the store owner can email privacy@moojo.id. Accounting entries needed for reconciliation may remain.

For the haggl.ai app for Wix, uninstalling disconnects the site from its workspace and pauses a running budget, and Wix stops giving the app access to the site. We keep the workspace, its imported catalog or services, campaign settings and negotiation history, so that reinstalling reconnects the same workspace; negotiation sessions are still deleted 12 months after they start. To have the workspace and its records deleted sooner, the site owner can email privacy@moojo.id. Accounting entries needed for reconciliation may remain.

6. Data Security

We implement appropriate technical and organizational measures to protect your information, including:

• Encryption in transit (TLS) for all data communications
• Encryption at rest for stored data
• Access controls limiting data access to authorized personnel
• Regular security assessments and monitoring

7. Your Rights and Data Access

Depending on your jurisdiction, you may have the right to access, correct, delete, or restrict processing of your personal data. To exercise these rights:

• Vendors may access and update their account data directly in the haggl.ai dashboard, or contact us at privacy@moojo.id
• Buyers whose data was submitted during a negotiation session may contact us to request deletion of their session data. A buyer can delete their haggl ID at any time on haggl.ai/agentic-discounts or through their agent, which withdraws their consent to its record and to sharing it

If you are in the EEA or the UK, you also have the right to data portability, to withdraw consent at any time (without affecting what we did before), to object to processing based on our legitimate interests, and to lodge a complaint with your data protection authority (in the UK, the Information Commissioner's Office). Cashback rates are set by automated decision-making (Section 2.7): to have a person review yours, email privacy@moojo.id with the quote ID within 30 days.

We will respond to verifiable requests within 30 days.

8. Children's Privacy

The Service is designed for business users and does not target children under 13 years of age. We do not knowingly collect personal information from children under 13. Users between 13 and 18 should have parental or guardian consent before using the Service.

9. International Data Transfers

Your information may be processed in countries outside your residence, including within the European Union and the United States. We ensure appropriate safeguards are in place for any international transfers in compliance with applicable data protection laws.

10. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. We will notify vendors of material changes by email and by updating the "Last Updated" date at the top of this policy. We will publish updates with a revised "Last Updated" date and provide notice of material changes through the Service and, where appropriate, by email. Where changes require fresh consent, we will obtain it before beginning the changed processing.

11. Contact Us

If you have questions about this Privacy Policy or our data practices, please contact us:

This privacy policy covers the haggl.ai negotiation platform operated by MOOJO.ID, INC. and applies to all vendors and buyers using the Service as of the effective date above.