Privacy Policy

DTLA Professional Services, LLC (doing business as "PayXT", and also operating the "IntentXT" software products; collectively "we", "us", or "our") respects your privacy and is committed to protecting the personal and financial information of our users. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you visit our websites (including payxt.app and intentxt.payxt.app), use the PayXT mobile application, use the IntentXT Chrome extension and related dashboards, or otherwise use our services (collectively, the "Services"). Our Services are offered to users in the United States, the European Union / European Economic Area (EU/EEA), the United Kingdom, and other supported regions.

Products covered: This Policy applies to (a) PayXT — invoicing and payment-link software for independent contractors and businesses; and (b) IntentXT — a B2B social intent lead finder delivered as a Chrome extension and web dashboard that helps users monitor public conversations on platforms such as Reddit, LinkedIn, and Facebook, flag leads, and generate AI-assisted reply drafts.

Data controller: For personal data processed in connection with PayXT and IntentXT, the controller is DTLA Professional Services, LLC, 770 S Grand Ave, Los Angeles, CA 90017, USA. Contact: payxt.app/contact, email support-24-7@payxt.app, or phone (213) 444-2224.

Collection

We collect the text of public social media posts and the user's customized company profile data when you use the IntentXT Chrome extension, plus account and lead data needed to run IntentXT and PayXT. We do not collect private messages, social-network passwords, or general browsing history.

IntentXT Chrome extension and dashboard

• Public post text you view or select. On Reddit, LinkedIn, and public Facebook groups, the extension reads the title and text of public posts that match keywords you configure, plus the post URL, platform, optional author display name shown on the page, and a short snippet.
• Company profile data you type. Company name, product description, value proposition, target pain points, and similar settings used to generate AI reply drafts.
• Account and authentication data. Email address, display or legal name, authentication tokens, and account status (including Free, Pro, promotional, or lifetime entitlements) when you sign in with email and password or Google.
• Leads you flag or that scans save. Post title, URL, platform (Reddit, LinkedIn, or Facebook), optional author, snippet, matched keyword, timestamps, and pipeline status you set.
• Monitoring settings you configure. Target keywords, negative keywords, Facebook public group URLs, Auto-Pilot on/off, and related scan preferences.
• Credits and purchases. Plan or entitlement, credit balance and usage events (for example an AI draft), and purchase or redemption identifiers needed to unlock that entitlement.
• Optional destinations you enter. A CRM or Zapier webhook URL, a Slack or Discord alert webhook URL, and a Telegram bot token and chat ID, if you turn those features on.
• Extension telemetry. Extension version, feature usage events, error and diagnostic logs, and security-related signals needed to operate and protect IntentXT. The extension does not include an advertising SDK.

PayXT app, websites, and support

• Account information. Name, email address, phone number, and business details when you create a PayXT or IntentXT account.
• Invoice and transaction data. Invoices you generate, including amounts, taxes, and dates. To facilitate payments you may connect Stripe. We do not store your clients' full credit card numbers on our servers.
• Purchase and license data. If you buy through a marketplace (for example Payhip, AppSumo, Apple, or Google) or redeem a deal or license code, we receive the order email, order identifiers, entitlement type, and redemption timestamps needed to unlock and support the purchase.
• Device, usage, and attribution information. Device identifiers (such as advertising IDs where permitted), IP address, browser or app type, operating system, app or extension version, install and open events, referral and campaign data, and how you interact with our websites and Services.
• Website data. On payxt.app and intentxt.payxt.app we collect standard server logs (IP address, browser type, referring page, and access time) and website analytics via Google Analytics. On intentxt.payxt.app, if you use Talk to Us or signed-in dashboard chat, we collect the messages you send in that chat.
• Support communications. Information you send by contact form, email, or phone. Because California is a two-party consent state, by calling our support lines you consent to the call being answered, recorded, transcribed, and processed by our AI assistant (Sona) for quality and support purposes.

Handling

Post data is sent to our secure backend API to generate AI replies. We process the data above only to operate the features you use.

• AI reply drafts (IntentXT). When you request a draft, the selected public post text and your company profile are sent to our backend API. The API sends that prompt to a trusted large language model provider (Google Gemini) to generate the reply drafts you asked for. A successful draft uses one AI credit on your account. We do not use public post text or your company profile to train our own models. You remain responsible for reviewing any draft before you post it.
• Optional intent check (IntentXT). If AI intent pre-filter is on, public post title and text plus the matched keyword are sent to the same API and then to Google Gemini to decide whether the post looks like a B2B lead. That check is used only to sort Inbox versus Filtered.
• Keyword scans (IntentXT). Reddit matching runs in the extension against public Reddit content. LinkedIn and Facebook scans you start are handled by our API: we send the keyword you entered (and, for Facebook, the public group URLs you configured) to Apify so matching public posts can be retrieved, then save new leads to your account.
• Account, credits, and billing. We use your account email and authentication token to sign you in, enforce plan limits, record credit use, and fulfill Stripe, Apple, Google, or marketplace purchases and deal-code redemptions.
• PayXT invoicing. We use account and invoice data to generate checkout links and itemized invoices, and to pass the transaction details you initiate to your connected Stripe account. PayXT subscription status is validated through RevenueCat and the Apple or Google store that billed the purchase.
• Alerts and CRM (IntentXT). Chrome desktop alerts stay on your device. If you configure a Slack or Discord webhook, or Telegram, a short lead alert is sent only to that destination when a match is found. Send to CRM runs only when you choose it, and posts the lead to the webhook URL you configured.
• PayXT marketing measurement. In the PayXT mobile app, AppsFlyer and Meta receive device and usage data described in the cookies section below to measure installs and in-app events, subject to your device tracking choices.

Those prompts are sent to Google Gemini through the Gemini Developer API (a server API key; not Google Cloud Vertex AI), only to generate the draft or classification you requested. We do not use public post text or your company profile to train our own models.

Storage

Company profile data is stored locally on the user's device. Flagged leads are stored securely in our database.

• On your device (IntentXT). Company profile data, keywords, scan preferences, alert and CRM webhook settings, Telegram bot token and chat ID, and a local copy of your leads are stored in the extension's local storage (chrome.storage.local) on your browser profile. We do not sync that profile to Chrome Sync.
• In our database (IntentXT). Flagged leads and leads saved from scans are stored in Google Cloud Firestore, tied to your account user ID, so the extension and dashboard can show the same pipeline. Typical lead fields are title, URL, platform, optional author, timestamps, and status.
• Account and credits. Sign-in records are stored in Firebase Authentication. Entitlement, credit balance, and usage events are stored in Firestore.
• PayXT records. Account details and invoice and transaction records you create are stored in our Google Cloud / Firebase database. Full payment card numbers are processed by Stripe (or by Apple or Google for in-app subscriptions), not stored on our servers.
• AI prompts. Post text and company profile fields are transmitted to our API and then to Google Gemini to produce the draft or classification you requested. We do not keep a separate product archive of every prompt beyond what is needed to return the result, operate the service, and record credit usage.

Sharing

User data is never sold. We do not sell, rent, or trade personal information, lead pipelines, company profiles, or public post text to data brokers or advertisers for their own marketing. Data is only shared with trusted large language model providers, such as Google Gemini, strictly to generate the requested reply drafts (and the optional intent classification you enable), and with the processors listed below solely to run the product you are using.

• Google Gemini (Google AI) — IntentXT public post text and company profile fields you submit for a reply draft or intent check, only to generate that result. Google Privacy Policy.
• Google Cloud / Firebase — hosts our APIs, authentication, and databases for PayXT and IntentXT. Firebase Privacy.
• Apify — the keyword, and for Facebook the public group URLs you configured, when you run an IntentXT LinkedIn or Facebook scan so public matching posts can be retrieved. We do not send your company profile or CRM settings to Apify. Apify Privacy Policy.
• Stripe — payment and transaction details you initiate in PayXT, and payment details if you buy IntentXT Pro on our site. We do not store full card numbers. Stripe Privacy Policy.
• Payhip and similar marketplaces (including AppSumo) — order email and entitlement data if you purchase through that marketplace, so we can unlock your plan. Payhip Privacy Policy.
• RevenueCat — PayXT in-app subscription status across iOS and Android. RevenueCat Privacy Policy.
• Apple and Google — PayXT in-app purchases and subscriptions billed by those stores, under their store terms.
• AppsFlyer and Meta — device and usage data from the PayXT mobile app to measure installs and in-app events, as described in the cookies section below. IntentXT extension lead contents are not sent to these partners.
• Google Analytics — website usage on payxt.app and intentxt.payxt.app (page views and similar analytics). Extension lead contents are not sent to these tags. Google Privacy Policy.
• Tawk.to — chat messages you send via IntentXT Talk to Us or signed-in dashboard support chat. Tawk.to Privacy Policy.
• Webhook destinations you configure (IntentXT) — data is shared only with the HTTPS webhook URL you enter, and only when you use that feature. Send to CRM posts platform, title, URL, author if available, matched keyword, snippet, and date found. Slack or Discord alerts post a short lead alert to the webhook you configure. Telegram receives a short lead alert only if you enter a bot token and chat ID.
• Legal obligations — if we are required to disclose information to comply with applicable law, governmental requests, a judicial proceeding, court order, or legal process.

IntentXT processes public data natively visible via your browser or retrieved via third-party infrastructure (Apify). We are not liable for actions taken by third-party social networks against your account for utilizing automated keyword monitoring tools.

The numbered sections below add detail on cookies, legal bases, retention, your rights, and how to contact us. They do not narrow the statements in Collection, Handling, Storage, and Sharing.

1. Information We Collect

We collect information that you voluntarily provide to us when you register for a Service, express an interest in obtaining information about us or our products, purchase a license or subscription, or otherwise contact us. The personal information that we collect depends on the context of your interactions with us and which product you use.

1.1 Information common to our Services

• Account Information: Name, email address, phone number, and business details when you create an account.
• Communications & Support: We collect personal information when you contact us. Because California is a "two-party consent" state, by calling our support lines, you explicitly consent to your call being answered, recorded, transcribed, and processed by our AI assistant (Sona) for quality and support purposes.
• Device, Usage & Attribution Information: Device identifiers (such as advertising IDs where permitted), IP address, browser or app type, operating system, app/extension version, install/open events, referral and campaign data, and how you interact with our websites and Services. We use this to improve performance, resolve bugs, measure marketing effectiveness, and attribute downloads and in-app or in-product events to advertising campaigns.
• Purchase & License Data: If you buy through third-party marketplaces (for example Payhip, AppSumo, Apple, or Google) or redeem a deal/license code, we may receive order email, order identifiers, entitlement type (including lifetime or promotional access), and redemption timestamps needed to unlock and support your purchase.

1.2 PayXT-specific information

• Financial & Gateway Data: To facilitate payments, you may connect Stripe (and related merchant tools). We do not store your clients' full credit card numbers on our servers. Sensitive payment processing is handled by your connected Stripe merchant account.
• Transaction Data: Information about the invoices generated, including transaction amounts, taxes applied, and dates.

1.3 IntentXT-specific information

When you use IntentXT (Chrome extension, website, or dashboard), we may collect and process:

• Account & authentication data: Email, display/legal name, authentication tokens, and account status (including Free, Pro, promotional, or lifetime entitlements).
• Company profile you provide: Company name, product description, value proposition, target pain points, and similar settings used to generate AI reply drafts.
• Keyword & monitoring configuration: Target keywords, negative keywords, Facebook public group URLs you configure, and related scan preferences (for example Auto-Pilot settings).
• Lead / pipeline data you save: Information about social posts you choose to flag or sync, which may include post title or snippet, post URL, platform (Reddit, LinkedIn, Facebook), timestamps, optional author fields when available, and lead status you set in the dashboard. IntentXT is designed to help you work with publicly available social content that you select; we do not claim to operate those third-party social networks.
• AI drafting inputs/outputs: Content needed to generate short reply drafts (for example your company profile and selected post context). Drafts are generated to assist you; you remain responsible for reviewing and posting any reply.
• Extension / product telemetry: Extension version, feature usage events, error/diagnostic logs, and security-related signals reasonably necessary to operate and protect IntentXT.

Important: IntentXT is not a full CRM. It focuses on social intent capture and reply assistance. Third-party platforms (Reddit, LinkedIn, Facebook, and others) have their own terms and privacy policies; your use of those platforms remains subject to their rules.

2. Cookies, Analytics, and Marketing Measurement

We use cookies, pixels, SDKs, web beacons, local storage, and similar technologies on our websites and in our mobile App / browser extension to operate the Services, understand usage, measure advertising performance, and improve PayXT and IntentXT.

2.1 Website analytics

On payxt.app and intentxt.payxt.app we may use Google Analytics / Google Tag Manager (or similar tags) to analyze website traffic, monitor aggregate user behavior, and understand how our pages are used. Our hosting infrastructure may also collect standard server/log data (IP address, browser type, referring pages, and access times) for security, performance, and diagnostics.

2.2 Mobile attribution and advertising analytics (AppsFlyer & Meta)

In the PayXT mobile App we use third-party measurement and advertising partners to track app marketing performance, installs/downloads, opens, and related in-app conversion events (for example trial starts and subscription-related events), including:

• AppsFlyer: Mobile attribution and analytics to measure which campaigns, ads, and channels drive app installs and key in-app events, and to help us optimize marketing spend and performance reporting.
• Meta (Facebook) SDK / App Events and related Meta advertising technologies (sometimes called Meta Pixel in web contexts): Used to measure and optimize ads on Meta platforms (including Facebook and Instagram), log app events, and support advertising analytics and retargeting where permitted by law and platform settings.

These partners may receive or process device and usage data such as advertising identifiers (IDFA on iOS when authorized; GAID on Android), IP address, device model, OS version, app events, and campaign/attribution parameters. On iOS, certain advertising tracking is subject to Apple’s App Tracking Transparency (ATT) prompt. If you deny tracking permission, we limit or disable advertiser tracking features accordingly (for example Meta Advertiser Tracking), though some limited measurement or aggregated reporting may still occur as allowed by Apple, Google, and applicable law.

For more information about how these partners process data, see their policies:

• AppsFlyer: AppsFlyer Privacy Policy
• Meta: Meta Privacy Policy
• Google Analytics: Google Privacy Policy

2.3 Cookie Policy

This Cookie Policy explains how PayXT, IntentXT, and our partners use cookies and similar technologies on our websites and, where applicable, analogous identifiers in our App or extension.

What are cookies? Cookies are small text files stored on your device when you visit a website. Similar technologies include pixels, tags, local storage, and mobile SDKs that store or access identifiers on your device.

We (and our service providers) may use the following categories:

• Strictly necessary: Required for basic site/app security, load balancing, and core functionality.
• Performance / analytics: Help us understand traffic and usage (for example Google Analytics on the website).
• Advertising / marketing measurement: Help us measure ad campaigns, attribute installs and conversions, and improve marketing performance (for example AppsFlyer and Meta technologies in the App, and any advertising tags we may use on the website).

Your choices:

• Browser cookies: You can usually block or delete cookies in your browser settings. Blocking cookies may affect some website features.
• iOS tracking: Use the system App Tracking Transparency prompt and Settings → Privacy & Security → Tracking to control cross-app tracking.
• Android advertising ID: You can reset or limit your advertising ID in your device’s Google/ads settings.
• Opt-out resources: Industry tools such as the Digital Advertising Alliance opt-out (where available) and partner-specific controls linked above.

Where required by law (including in the EU/EEA and UK), we treat certain analytics and advertising cookies/identifiers as optional and will obtain consent or honor opt-out/objection rights as applicable before using non-essential cookies or similar technologies.

Our website does not currently alter its practices or respond to browser "Do Not Track" (DNT) signals because no uniform technological standard has been established.

3. How We Use Your Information

We use the information we collect or receive for the following business purposes:

• To facilitate account creation and logon processes for PayXT and IntentXT.
• PayXT: To generate secure checkout links and itemized invoices for your clients, and to securely pass transaction data to your authorized payment gateways (Stripe).
• IntentXT: To provide keyword monitoring, lead flagging/pipeline features, entitlement/license validation, and AI-assisted reply drafts based on settings and content you provide.
• To respond to user inquiries and offer customer support (including via email, phone/SMS, and contact forms).
• To measure marketing performance, attribute downloads/installs and key in-app or in-product events, analyze campaign effectiveness, and improve our advertising (including via AppsFlyer and Meta for the PayXT mobile App).
• To enforce our terms, conditions, and policies for business purposes, legal reasons, and contractual obligations; and to protect the security and integrity of our Services.

4. How We Share Your Information

User data is never sold. The definitive third-party statement is in Sharing above. We only share information with your consent, to comply with laws, to provide you with services, to protect your rights, or to fulfill business obligations. Specifically, we may share data with:

• Payment Processors & Marketplaces: For PayXT, we transmit necessary transaction details to Stripe to process the payments you initiate. For IntentXT purchases sold via third-party marketplaces (e.g., Payhip), those marketplaces process checkout under their own policies; we receive what is needed to fulfill and support your order/entitlement.
• Cloud Infrastructure: We use enterprise-grade cloud service providers (such as Google Cloud/Firebase) to host our databases and execute secure server functions for PayXT and IntentXT.
• AI / Model Providers: For IntentXT reply drafting and related features, we send limited prompts/context to trusted AI providers (Google Gemini / Google AI services) solely to generate the requested draft or intent check. User data is never sold.
• Analytics & Attribution Partners: AppsFlyer and Meta (Facebook/Instagram advertising and measurement tools), as described in Section 2, to measure installs, app events, and marketing performance (primarily for the PayXT mobile App).
• Website Analytics: Google Analytics / Google tags for website usage analysis.
• Subscription Management: For PayXT mobile subscriptions, we use RevenueCat to securely manage, sync, and validate your in-app subscription status across iOS and Android platforms. IntentXT may use Stripe and/or license/deal-code systems for Pro and lifetime entitlements.
• Legal Obligations: If we are legally required to do so in order to comply with applicable law, governmental requests, a judicial proceeding, court order, or legal process.

5. Data Security

We have implemented appropriate technical and organizational security measures designed to protect the security of any personal information we process. Sensitive credentials are transmitted and stored using industry-standard protections. However, despite our safeguards and efforts to secure your information, no electronic transmission over the Internet or information storage technology can be guaranteed to be 100% secure.

6. Third-Party Websites and Services

Our Services may generate links to third-party payment gateways (such as checkout.stripe.com), integrate third-party SDKs and services (including AppsFlyer, Meta, Google, Stripe, RevenueCat, and AI providers), and interact with third-party social platforms (such as Reddit, LinkedIn, and Facebook) when you use IntentXT. We cannot guarantee the safety and privacy of data you provide directly to any third parties. Data collected by third parties is governed by their own privacy policies. We are not responsible for the content or privacy and security practices of those third parties, including social networks you browse or post on.

7. Legal Bases for Processing (EU/EEA and UK)

If you are in the EU/EEA or UK, we process personal data under the EU General Data Protection Regulation (GDPR) and UK GDPR, as applicable, on one or more of the following legal bases:

• Contract: Processing necessary to provide the PayXT or IntentXT service you request (account creation, invoicing features, Stripe Connect onboarding support, subscription/entitlement checks, lead pipeline features, AI draft generation you request).
• Legitimate interests: Improving security, preventing fraud/abuse, diagnosing technical issues, understanding product usage in a privacy-respecting way, and operating our business—balanced against your rights and expectations.
• Consent: Where required for non-essential cookies, certain advertising/measurement technologies (including AppsFlyer and Meta features that rely on tracking permissions), or optional communications. You may withdraw consent at any time without affecting the lawfulness of processing before withdrawal.
• Legal obligation: Where we must retain or disclose information to comply with applicable law, tax, accounting, or regulatory requirements.

8. Your Privacy Rights (including EU/EEA, UK, and California)

Depending on your location, you may have rights regarding your personal information.

8.1 EU/EEA and UK (GDPR / UK GDPR)

If you are in the EU/EEA or UK, you may have the right to:

• Access your personal data and obtain a copy.
• Rectify inaccurate or incomplete personal data.
• Erase personal data (“right to be forgotten”) in certain circumstances.
• Restrict or object to certain processing, including processing based on legitimate interests and processing for direct marketing.
• Data portability (receive data you provided in a structured, commonly used, machine-readable format, where technically feasible).
• Withdraw consent at any time where processing is based on consent.
• Lodge a complaint with your local supervisory authority (for example, your EU Member State data protection authority, or the UK Information Commissioner’s Office).

We will respond to GDPR requests within the timeframes required by law (generally within one month, extendable where permitted).

8.2 California and other US state laws

Depending on your state (e.g., California CCPA/CPRA), you may have the right to:

• Request access and obtain a copy of your personal information.
• Request rectification or erasure of your personal data.
• Restrict the processing of your personal information.
• Opt out of certain “sale” or “sharing” of personal information for cross-context behavioral advertising, including by adjusting device tracking settings or contacting us.

To exercise these rights, contact us using the information in Section 14. We will consider and act upon any request in accordance with applicable data protection laws. We will not discriminate against you for exercising privacy rights.

9. Account and Data Deletion

You have the right to request the complete deletion of your PayXT and/or IntentXT account and associated personal data. For PayXT, you can delete your account directly within the PayXT mobile app settings, or request deletion via our contact form or data deletion page. For IntentXT, request deletion via payxt.app/contact or email support-24-7@payxt.app, and identify the product and account email. Upon request, we will permanently delete your account and remove associated personal data from our active systems within 30 days, subject to legal and tax retention requirements. Deletion of your account may not automatically delete data already processed by independent third parties (such as AppsFlyer, Meta, Google, Stripe, Apple, RevenueCat, Payhip, or social platforms); you may need to exercise rights directly with those providers where available.

10. Data Retention

We retain personal data only as long as needed for the purposes described in this Policy, including to provide the Services, comply with legal obligations, resolve disputes, and enforce agreements. Typical retention practices include:

• Account data: Kept while your account remains active, then deleted or anonymized within approximately 30 days after account deletion, unless longer retention is required by law.
• PayXT transaction / invoice records: May be retained longer where needed for tax, accounting, fraud prevention, or legal claims.
• IntentXT lead pipeline & configuration: Retained while your account is active so you can use the product; deleted or anonymized with account deletion requests subject to backups and legal holds.
• Analytics and marketing measurement data: Retained according to our analytics partners’ retention settings and our business needs, typically in aggregated or pseudonymized form where practicable.
• Support communications: Retained as needed to handle your request and improve support quality.

11. International Data Transfers

DTLA Professional Services, LLC is based in the United States. If you use PayXT or IntentXT from the EU/EEA, UK, or other regions, your personal data may be transferred to and processed in the United States and other countries where our service providers operate. Those countries may not provide the same level of data protection as your home country.

Where required by GDPR/UK GDPR, we rely on appropriate transfer safeguards, such as the European Commission’s Standard Contractual Clauses (SCCs) and/or the UK International Data Transfer Agreement / Addendum, and additional technical and organizational measures as appropriate. By using the Service from outside the United States, you acknowledge these transfers subject to applicable law and your rights described above.

12. Children

PayXT and IntentXT are business productivity applications intended for adults and business users. They are not directed to children under 16, which is the age boundary we apply for EU/UK GDPR. We do not knowingly collect personal data from children under 13, the US Children's Online Privacy Protection Act (COPPA) threshold, and we do not knowingly collect personal data from children under 16. If you believe a child has provided us personal data, contact us and we will take steps to delete it.

13. App Store, Google Play, and Extension Distribution

PayXT is distributed through the Apple App Store and Google Play. In addition to this Privacy Policy and our Terms of Service, your download and use of the PayXT App may also be subject to the platform provider’s terms:

• Apple Licensed Application End User License Agreement (Standard EULA): If you download PayXT from the Apple App Store, your use of the iOS app is also governed by Apple’s standard Licensed Application End User License Agreement, available at https://www.apple.com/legal/internet-services/itunes/dev/stdeula/.
• Google Play: If you download PayXT from Google Play, your use of the Android app is also subject to the Google Play Terms of Service. Google’s collection and use of information is described in the Google Privacy Policy. PayXT’s own data practices for the Android app are described in this Privacy Policy, which is the privacy policy URL we provide for Google Play’s User Data / Data safety requirements (see also Google Play’s User Data policy).

In-app purchases and subscriptions for PayXT are billed by Apple or Google according to their store rules. Refunds for those subscriptions are handled by Apple or Google, not directly by PayXT, except where required by applicable law.

IntentXT is distributed as a Chrome extension and web product (including via direct download packages and third-party marketplaces such as Payhip). Browser vendors and marketplace operators have their own terms. Purchases and refunds made through a marketplace are subject to that marketplace’s buyer policies in addition to these Terms and this Privacy Policy.

Changes

If our practices change, we will update this page and the “Last Updated” date. If we make material changes to this policy, we will notify you via the email address associated with your account or through a prominent notice inside the Chrome Extension/Dashboard prior to the change taking effect. Continued use of PayXT or IntentXT after the updated date means the updated policy applies. The live policy is always at https://payxt.app/privacy.

14. Contact Us

If you have questions or comments about this Privacy Policy, wish to exercise privacy rights (including GDPR requests), or need help with account/data deletion for PayXT or IntentXT, contact us: