PayLync.
Home Products Features Pricing Integrations Partners Blog
Sign in Get Started
Home Products Features Pricing Integrations Partners Blog
Sign in Get Started
Privacy & data

Privacy Policy

How PayLync collects, uses, protects, and shares information across our website, applications, integrations, and payment services.

Last updated: August 24, 2026
On this page
1. Products and Services Covered 2. PayLync FieldKit Privacy Disclosure 3. Chrome Extension Privacy Disclosure 4. How the Chrome Extension Collects Information 5. Chrome Extension Data Use 6. Chrome Extension Data Storage and Security 7. How Chrome Extension Information Is Shared 8. Limited Use Disclosure for Chrome Web Store 9. Information We Collect 10. How We Use Information 11. How We Share Information 12. Payment Data Security 13. Human Access to User Data 14. Cookies and Tracking Technologies 15. Analytics 16. Data Retention 17. Account Deletion and Data Requests 18. Your Choices 19. Do Not Sell or Share Personal Information 20. California Privacy Notice 21. Children's Privacy 22. Third-Party Links and Services 23. Changes to This Privacy Policy 24. Contact Us
Questions?

Contact the PayLync team for help.

Contact us ↗

PayLync respects your privacy and is committed to protecting the personal, business, customer, invoice, accounting, and payment-related information handled through our products and services.

This Privacy Policy explains how PayLync.com d/b/a PayLync and, specifically in connection with the PayLync FieldKit mobile application, Blue Olive LLC, collect, use, store, protect, and share information through the applicable products and services.

Google Play Application and Developer Information

This Privacy Policy applies specifically to PayLync FieldKit, a mobile field service management application published on Google Play.

  • Application Name: PayLync FieldKit
  • Android Package Name: com.fieldkit.app
  • Developer / Publisher: Blue Olive LLC
  • Website: PayLync.com
  • Privacy Contact: support@paylync.com

PayLync FieldKit is developed, published, and operated by Blue Olive LLC. This Privacy Policy explains how Blue Olive LLC collects, uses, stores, protects, retains, and shares information when users access or use the PayLync FieldKit mobile application.

For purposes of this Privacy Policy, references to “PayLync,” “PayLync FieldKit,” “we,” “us,” or “our” refer to Blue Olive LLC in connection with the operation of the PayLync FieldKit application and related services.

PayLync FieldKit

PayLync FieldKit is a mobile field service management application developed, published, and operated by Blue Olive LLC under the PayLync brand. This Privacy Policy applies to PayLync FieldKit and explains how information is collected, used, stored, protected, and shared when users access or use the FieldKit application.

By using PayLync, you agree to the practices described in this Privacy Policy.


1. Products and Services Covered

This Privacy Policy applies to PayLync services, including but not limited to:

  • PayLync Website
  • PayLync Merchant Portal
  • PayLync Customer Portal
  • PayLync Standalone Payment Platform
  • PayLync QuickBooks Online Chrome Extension
  • PayLync Xero Chrome Extension
  • PayLync FreshBooks Chrome Extension
  • PayLync QuickBooks Desktop Integration
  • PayLync QuickBooks Online Integration
  • PayLync Sage Accounting Integration
  • PayLync Mobile Application for iOS and Android
  • PayLync FieldKit mobile application for Android and iOS
  • Payment Links, Hosted Payment Pages, Email Invoices, Recurring Invoices, Payment Reminders, Receipts, and Related Services

2. PayLync FieldKit Privacy Disclosure

When you use the PayLync FieldKit mobile application, we may collect or process information necessary to provide field service management, invoicing, payment, scheduling, customer management, and related functionality.

Depending on the features used, this information may include:

Account and Business Information

  • Name
  • Email address
  • Phone number
  • Company or business name
  • User account identifiers
  • User role and permissions
  • Authentication and login information

Customer and Job Information

FieldKit users may enter or manage information relating to their customers and field service activities, including:

  • Customer names
  • Customer email addresses
  • Customer phone numbers
  • Service or job addresses
  • Job descriptions
  • Appointment and scheduling information
  • Technician assignments
  • Job status and service history
  • Quotes and invoices
  • Notes related to jobs or customers

Photos, Documents, and Signatures

Where these features are used, FieldKit may allow users to upload or capture:

  • Job-related photos
  • Service documentation
  • Attachments
  • Customer signatures
  • Other information voluntarily submitted as part of a job or service record

Camera or photo library access is used only when requested by the user for FieldKit functionality.

Location Information

Where location-enabled FieldKit features are used and permission is granted by the user, FieldKit may process device location information to support features such as field service operations, technician location, job routing, navigation, service location verification, or other location-based functionality.

Location information is used only for legitimate FieldKit functionality and is not sold or used for third-party behavioral advertising.

Payment and Transaction Information

When payment functionality is used, FieldKit may process information associated with invoices and payment transactions, including:

  • Invoice amount
  • Transaction amount
  • Payment status
  • Transaction identifiers
  • Payment method type
  • Limited payment information such as card brand or last four digits, where provided by our payment processing partners

Payment transactions may be processed through third-party payment processors and gateways.

PayLync does not store card security codes (CVV). Full payment credentials are handled in accordance with applicable payment security requirements and the practices of the applicable payment processor.

Device and Technical Information

We may automatically process limited technical information necessary to operate, secure, troubleshoot, and improve FieldKit, including:

  • Device type
  • Operating system
  • Application version
  • IP address
  • Device or application identifiers
  • Error and crash information
  • Diagnostic logs
  • Authentication and security events

How FieldKit Information Is Used

Information collected or processed through FieldKit may be used to:

  • Authenticate users
  • Maintain user and business accounts
  • Create and manage customers
  • Create, schedule, assign, and manage jobs
  • Support field service operations
  • Generate quotes and invoices
  • Process and record payments
  • Maintain transaction history
  • Provide customer support
  • Send service-related notifications
  • Maintain security and prevent fraud
  • Diagnose technical issues
  • Improve application reliability and functionality
  • Comply with applicable legal, tax, accounting, payment, and regulatory obligations

Sharing of FieldKit Information

Information may be shared only as necessary with service providers that support FieldKit functionality, including payment processors, hosting and infrastructure providers, notification providers, analytics or diagnostic providers, and other technology providers used to operate the service.

We do not sell personal information collected through FieldKit and do not use FieldKit user data for third-party behavioral advertising.

FieldKit Data Security

We use reasonable administrative, technical, and organizational safeguards designed to protect information handled through FieldKit, including secure network transmission, authentication and authorization controls, restricted access, and other appropriate security measures.

FieldKit Data Retention and Deletion

We retain FieldKit information only for as long as reasonably necessary to provide the service, maintain business and transaction records, comply with legal requirements, prevent fraud, resolve disputes, and fulfill legitimate business purposes.

Users may request access, correction, or deletion of their personal information or account by contacting:

support@paylync.com

Certain information may be retained where required for legal, tax, accounting, payment processing, fraud prevention, dispute resolution, or regulatory purposes.

3. Chrome Extension Privacy Disclosure

The PayLync Chrome extension enables merchants to access PayLync invoice and payment functionality directly within supported accounting platforms, including QuickBooks Online, Xero, and FreshBooks, depending on the merchant's configuration.

When a merchant uses PayLync on a supported accounting platform, the extension may access information displayed on the current supported page that is necessary to provide the requested PayLync functionality. This may include:

  • Customer name, email address, phone number, and billing information
  • Invoice number, invoice date, due date, line items, tax, discounts, fees, and invoice total
  • Invoice and payment status
  • Transaction identifiers and payment-related information
  • The current supported page URL and page context
  • Merchant account information and extension authentication status
  • PayLync configuration and integration settings

The extension accesses supported page content only for invoice, accounting, and payment functionality.

PayLync does not use the extension to collect unrelated website content, monitor unrelated websites, build a browsing profile, track users across unrelated websites, or collect browsing activity for advertising purposes.

The extension may determine the current website, URL, or page context to identify whether the merchant is using a supported PayLync integration and to provide the appropriate payment or invoice functionality.


4. How the Chrome Extension Collects Information

The PayLync Chrome extension collects or processes information only as reasonably necessary to provide its disclosed payment, invoice, accounting integration, synchronization, authentication, security, and support functionality.

Depending on how the merchant uses the extension, information may be obtained through the following methods:

A. Information from Supported Accounting Pages

When a merchant visits or interacts with a supported accounting platform, such as QuickBooks Online, Xero, or FreshBooks, the PayLync Chrome extension may access limited website content and page information necessary to provide PayLync functionality.

This may include:

  • Customer name, email address, phone number, and billing information
  • Invoice number, invoice date, due date, line items, tax, discounts, fees, and invoice total
  • Invoice and payment status
  • Transaction identifiers and payment-related information
  • Other invoice or customer information displayed on the supported page that is necessary to perform a merchant-requested PayLync action

The extension accesses only the information necessary to identify the relevant customer or invoice, display PayLync payment functionality, initiate merchant-requested actions, and synchronize payment or invoice information.

B. Supported Page URL and Page Context

The extension may access the current domain, URL, page type, or other limited page context to determine whether the merchant is viewing a supported PayLync integration and to provide the appropriate functionality.

This information may be considered limited web browsing activity because it identifies the supported accounting page currently being used.

PayLync does not use the extension to collect browsing history from unrelated websites, monitor browsing activity outside supported PayLync integrations, build browsing profiles, track users across unrelated websites, or use browsing activity for advertising purposes.

C. Information Provided by the Merchant

PayLync may collect information that the merchant voluntarily provides or submits when interacting with the Chrome extension.

This may include information provided when the merchant:

  • Signs in to PayLync
  • Selects an invoice or customer
  • Initiates a payment or other payment action
  • Generates or sends a payment link
  • Configures extension or integration settings
  • Connects supported accounting software
  • Requests synchronization of payment or invoice information
  • Contacts PayLync for support or troubleshooting

D. Information Received from PayLync Services

The extension may receive information from PayLync systems where necessary to provide the requested functionality.

This may include:

  • Merchant account information
  • Merchant account or user identifiers
  • Authentication and session status
  • Accounting software connection status
  • PayLync configuration and integration settings
  • Invoice and customer information
  • Transaction information and payment status
  • Payment or synchronization results

Information received from PayLync services is used only as necessary to provide the extension's disclosed functionality.

E. Authentication and Browser-Stored Information

The extension may process authentication and session information necessary to identify the merchant, maintain an authenticated PayLync session, and provide access to authorized PayLync functionality.

Limited information may also be stored within the user's browser as described in the Chrome Extension Data Storage and Security section of this Privacy Policy.

This may include:

  • Authentication token
  • User email address
  • Accounting software connection status

PayLync does not use this information for advertising, unrelated tracking, or profiling.

F. Technical and Diagnostic Information

PayLync may automatically process limited technical and diagnostic information where necessary to operate, secure, troubleshoot, and maintain the Chrome extension.

This may include:

  • Browser type
  • Extension version
  • Supported page URL or page context
  • Error messages
  • Synchronization errors
  • Diagnostic information
  • Security or authentication events

This information is used to maintain the security, reliability, compatibility, and functionality of the extension and to diagnose technical problems.

Data Collection Limitation

PayLync limits Chrome extension data collection and processing to information reasonably necessary to provide, maintain, secure, troubleshoot, or support the extension's disclosed user-facing payment and accounting functionality.

The PayLync Chrome extension does not collect or use unrelated website content or unrelated browsing activity for advertising, behavioral profiling, retargeting, data brokerage, or tracking users across unrelated websites.


5. Chrome Extension Data Use

Information handled through the PayLync Chrome extension is used only as necessary to:

  • Authenticate and identify the PayLync merchant
  • Determine whether the merchant is viewing a supported accounting page
  • Identify the relevant customer or invoice
  • Display PayLync payment options
  • Initiate merchant-requested payment actions
  • Generate or send payment links
  • Process or facilitate payments
  • Update invoice or payment status
  • Synchronize payment information with supported accounting platforms
  • Display transaction and payment information
  • Maintain merchant configuration and integration settings
  • Troubleshoot errors and provide customer support
  • Maintain the security, performance, and reliability of PayLync's extension functionality
  • Comply with applicable legal, regulatory, payment network, banking, and accounting requirements

PayLync does not use Chrome extension user data for personalized advertising, behavioral advertising, retargeting, data brokerage, unrelated profiling, creditworthiness determinations, or lending decisions.


6. Chrome Extension Data Storage and Security

PayLync processes, transmits, and stores information handled through the Chrome extension only as reasonably necessary to provide, maintain, secure, troubleshoot, and support the extension's disclosed payment, invoice, authentication, and accounting integration functionality.

A. Information Stored in the User's Browser

The PayLync Chrome extension may store limited information locally within the user's browser where necessary for extension functionality.

Locally stored information may include:

  • Authentication token
  • User email address
  • Accounting software connection status
  • Limited session, authentication, or configuration information necessary for the extension to operate

This information is used to maintain the user's authenticated PayLync session, identify the associated PayLync account, determine whether supported accounting software is connected, and provide the appropriate extension functionality.

PayLync does not use locally stored extension information for advertising, behavioral profiling, retargeting, data brokerage, or tracking users across unrelated websites.

B. Browser Local Storage and Cookies

The PayLync Chrome extension may use browser local storage and cookies where necessary to support authentication, session management, account identification, integration status, and other functionality requested by the user.

Cookies or locally stored information accessed by the extension are used only for PayLync's disclosed functionality and are not used to monitor browsing activity on unrelated websites or to create advertising or behavioral profiles.

Where the extension accesses authentication or session cookies, such access is limited to cookies reasonably necessary to authenticate the user, maintain the PayLync session, connect PayLync functionality with supported accounting platforms, or perform another disclosed user-facing function.

PayLync does not use Chrome extension cookies or browser storage for cross-site advertising tracking.

C. Information Transmitted by the Chrome Extension

When necessary to provide PayLync functionality, information may be transmitted between:

  • The PayLync Chrome extension
  • PayLync systems and services
  • Supported accounting platforms
  • Payment gateways or payment processors configured by the merchant
  • Authorized infrastructure, security, and service providers

Information transmitted by the extension is limited to information reasonably necessary to perform the requested PayLync functionality, including authentication, customer and invoice identification, payment processing, payment status updates, accounting synchronization, troubleshooting, security, and related operations.

Information transmitted between the Chrome extension and PayLync services is transmitted using encrypted connections such as HTTPS/TLS.

D. Security Safeguards

PayLync uses administrative, technical, and organizational safeguards designed to protect information handled through the Chrome extension against unauthorized access, use, disclosure, alteration, misuse, or loss.

These safeguards may include, as appropriate:

  • Encryption of information during transmission
  • Authentication and access controls
  • Restricted access to systems containing user information
  • Security monitoring and fraud prevention measures
  • Technical controls designed to prevent unauthorized access
  • Limiting data collection and processing to information necessary for disclosed functionality

No method of electronic transmission or storage can be guaranteed to be completely secure. PayLync nevertheless maintains safeguards designed to protect information appropriate to the nature of the information being processed.

E. Authentication Information

Authentication tokens, session information, and related credentials may be processed where necessary to authenticate the user and enable authorized PayLync functionality.

PayLync does not use authentication information for advertising, unrelated profiling, or data brokerage.

Authentication information is not intentionally made publicly available and is handled only for authentication, security, account access, and related PayLync functionality.

F. Payment Card and Bank Account Information

The PayLync Chrome extension does not store card verification values or card security codes such as CVV, CVC, or CID.

Where payment information is collected through secure hosted payment fields, tokenization services, payment gateways, processors, acquiring providers, or other authorized payment technologies, PayLync does not store the full payment card number or full bank account number within the Chrome extension.

Payment credentials may instead be transmitted directly to or handled by the merchant's configured payment gateway, processor, tokenization provider, acquiring provider, or other authorized payment service.

PayLync may receive and process limited payment-related information necessary to provide its services, such as:

  • Transaction identifier
  • Payment status
  • Payment amount
  • Payment method or payment type
  • Tokenized payment reference
  • Last four digits of a payment card, where provided by the payment processor
  • Authorization, settlement, refund, or transaction status

PayLync does not publicly disclose financial, payment, or authentication information.

G. Data Retention

Information handled through the Chrome extension is retained only for as long as reasonably necessary to:

  • Provide the extension's disclosed functionality
  • Maintain the user's account or authenticated session
  • Synchronize accounting and payment records
  • Maintain transaction and business records
  • Provide customer support
  • Troubleshoot technical issues
  • Prevent fraud, abuse, or security incidents
  • Satisfy applicable legal, regulatory, accounting, banking, payment network, or compliance requirements

Locally stored extension information is retained only for as long as necessary to support the applicable extension functionality.

Information that is no longer reasonably necessary for the purposes for which it was collected is deleted, anonymized, invalidated, or otherwise handled in accordance with PayLync's applicable retention practices and legal obligations.

H. Data Minimization

PayLync limits the collection, storage, transmission, and retention of Chrome extension user data to information reasonably necessary to provide, maintain, secure, troubleshoot, or support the extension's disclosed user-facing functionality.

Chrome extension information is not stored, accessed, or retained for personalized advertising, behavioral advertising, unrelated tracking, data brokerage, creditworthiness determinations, lending decisions, or other purposes unrelated to PayLync's disclosed functionality.


7. How Chrome Extension Information Is Shared

PayLync does not sell Chrome extension user data or share Chrome extension user data with advertising platforms, data brokers, information resellers, or other third parties for personalized advertising, behavioral advertising, retargeting, unrelated profiling, creditworthiness determinations, or lending purposes.

PayLync shares or transfers information handled through the Chrome extension only when reasonably necessary to provide the extension's disclosed payment and accounting functionality, complete a user-requested transaction, maintain or secure the service, prevent fraud or abuse, comply with applicable law, or otherwise as permitted by applicable Chrome Web Store policies.

Depending on the PayLync features, integrations, and payment services selected or configured by the merchant, Chrome extension information may be shared with the following parties.

A. Supported Accounting Platforms

When a merchant uses PayLync with a supported accounting platform, PayLync may exchange information with that platform as necessary to provide invoice, customer, payment, and accounting synchronization functionality.

Supported Chrome extension integrations may include:

  • Intuit QuickBooks Online
  • Xero
  • FreshBooks

Information exchanged with a connected accounting platform may include:

  • Customer name and contact information
  • Customer or account identifiers
  • Invoice number and invoice information
  • Invoice amount and payment status
  • Transaction references
  • Refund or void information
  • Payment status updates
  • Accounting synchronization information
  • Connection or integration identifiers

Information is shared with a connected accounting platform only where necessary to provide functionality requested or enabled by the merchant.

B. Payment Gateways, Processors, and Financial Service Providers

When a merchant initiates or manages a payment through PayLync, relevant information may be transmitted to the payment gateway, processor, acquiring provider, ACH provider, card network, or other payment service provider configured for the merchant.

Depending on the merchant's configuration, these providers may include:

  • NMI
  • Worldpay
  • CardConnect
  • TRX Services
  • ACH processing providers
  • Acquiring banks
  • Card networks and payment brands

Information shared with these providers may include information reasonably necessary to:

  • Create or tokenize a payment method
  • Authorize a transaction
  • Process or settle a payment
  • Process an ACH transaction
  • Perform a refund or void
  • Verify payment status
  • Manage transaction disputes or payment-related issues
  • Return transaction results to PayLync for accounting synchronization

Depending on the payment integration, information may include customer information, invoice information, transaction amount, transaction identifiers, payment method information, tokenized payment references, billing information, and other information required to complete the merchant-requested payment.

PayLync shares only the information reasonably necessary for the applicable payment service.

C. Fraud Prevention, Security, and Abuse Protection

PayLync may disclose limited Chrome extension information where reasonably necessary to detect, prevent, investigate, or respond to:

  • Fraud
  • Unauthorized transactions
  • Account compromise
  • Malware
  • Phishing
  • Abuse of PayLync services
  • Security incidents
  • Other unlawful or harmful activity

Such disclosures are limited to information reasonably necessary for the applicable security or fraud-prevention purpose.

D. Legal and Regulatory Requirements

PayLync may disclose Chrome extension information where required or permitted by applicable law, including where necessary to:

  • Comply with a subpoena, court order, legal process, or other lawful request
  • Respond to lawful requests from public authorities
  • Comply with banking, payment network, tax, accounting, or regulatory obligations
  • Protect the legal rights, safety, property, or security of PayLync, its merchants, customers, users, or others
  • Investigate or prevent fraud, abuse, unauthorized access, or security incidents

PayLync limits such disclosures to information reasonably necessary to satisfy the applicable legal, regulatory, security, or compliance requirement.

E. Business Transfers

If PayLync is involved in a merger, acquisition, reorganization, financing, sale of assets, or similar business transaction, Chrome extension user data will be handled in accordance with applicable law and applicable Chrome Web Store User Data Policy requirements.

Where required, PayLync will obtain the user's explicit prior consent before Chrome extension user data is transferred as part of a merger, acquisition, or sale of assets.

F. Restrictions on Sharing

PayLync does not transfer Chrome extension user data:

  • For personalized or behavioral advertising
  • For retargeting or cross-site advertising
  • To advertising platforms
  • To data brokers or information resellers
  • For unrelated behavioral profiling
  • To determine creditworthiness
  • For lending decisions
  • For purposes unrelated to the Chrome extension's disclosed payment and accounting functionality

Chrome extension user data is shared only where necessary to provide PayLync's disclosed user-facing functionality, process merchant- requested transactions, maintain or secure the service, prevent fraud or abuse, comply with applicable law, or otherwise as permitted by applicable Chrome Web Store policies.


8. Limited Use Disclosure for Chrome Web Store

PayLync uses information received from Chrome extension permissions only to provide and improve PayLync’s disclosed payment, invoice, accounting connection, and related user-facing features.

PayLync does not use or transfer Chrome extension user data for personalized advertising, retargeting, interest-based advertising, data brokerage, credit-worthiness decisions, or any unrelated purpose.

PayLync only transfers user data when necessary to provide or improve the service, process payments, sync accounting records, comply with law, protect against fraud or abuse, provide customer support with user consent, or support a business transfer such as a merger or acquisition.

The use of information received from Google APIs and Chrome extension permissions will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.


9. Information We Collect

Depending on the PayLync product or service you use, we may collect the following types of information.

A. Account and Business Information

We may collect:

  • Name
  • Email address
  • Phone number
  • Business name
  • Company address
  • Merchant account settings
  • Branding settings
  • Contact information
  • Billing or subscription information

B. Customer and Invoice Information

When you use PayLync to create, send, sync, or collect invoices, we may collect or process:

  • Customer name
  • Customer email address
  • Customer phone number
  • Customer billing and shipping address
  • Invoice number
  • Invoice date and due date
  • Invoice line items
  • Invoice subtotal, tax, discount, surcharge, fee, and total amount
  • Payment status
  • Invoice notes or descriptions
  • Recurring invoice settings
  • Email invoice and payment reminder details

C. Payment and Transaction Information

When a payment is processed through PayLync, we may collect or process:

  • Transaction amount
  • Currency
  • Transaction date and time
  • Payment status
  • Authorization code
  • Transaction ID
  • Gateway transaction reference
  • Refund or void status
  • Card brand
  • Last four digits of the card
  • Card expiration month and year, where applicable
  • Tokenized payment method information
  • Customer profile ID or payment profile ID
  • ACH or bank payment token information, where applicable
  • Surcharge or convenience fee details, where applicable

Depending on the payment gateway and integration type, payment card or ACH details may be entered into a hosted payment page or securely transmitted to the selected payment processor.

PayLync does not store full card numbers, CVV/security codes, or full bank account numbers.


D. Accounting Platform Data

If you connect PayLync with accounting software, we may collect or process data required to provide the integration, such as:

  • Connected company ID
  • Accounting platform account ID
  • OAuth tokens or connection tokens
  • Invoice records
  • Customer records
  • Credit memo or refund details
  • Sync status
  • Error logs related to syncing

Supported or related accounting platforms may include QuickBooks Online, QuickBooks Desktop, Xero, FreshBooks, Sage, and standalone PayLync records, depending on the product configuration.


E. Chrome Extension Data

When you use the PayLync Chrome extension, we may collect or process:

  • Extension authentication status
  • Merchant account ID
  • Supported accounting platform page context
  • Invoice or customer information needed to display PayLync payment options
  • Payment action selected by the user
  • Extension configuration settings
  • Error logs and diagnostic information
  • Browser type and extension version

The extension does not collect unrelated browsing activity or unrelated website content.


F. Mobile App Data

When you use PayLync mobile applications, we may collect:

  • Account profile information
  • Business details
  • Customer records
  • Invoice and estimate data
  • Payment links and transaction information
  • App settings
  • Device type
  • Operating system
  • App version
  • Crash logs or diagnostic information
  • Push notification token, if notifications are enabled

If subscriptions or in-app purchases are offered through Apple App Store or Google Play, payment and subscription management may be handled by Apple or Google according to their own policies.


G. Website and Usage Information

When you visit our website or use our online services, we may automatically collect:

  • IP address
  • Browser type
  • Device type
  • Operating system
  • Referring and exit pages
  • Date and time of visit
  • Pages viewed
  • General usage activity
  • Cookie identifiers
  • Analytics and performance data

We use this information to maintain, secure, improve, and understand the performance of our services.


H. Support and Communication Information

When you contact PayLync, we may collect:

  • Name
  • Email address
  • Phone number
  • Company name
  • Support request details
  • Screenshots or files you choose to provide
  • Technical troubleshooting information

10. How We Use Information

We use collected information to:

  • Create and manage PayLync accounts
  • Provide payment processing services
  • Generate and send invoices
  • Send email invoices and payment links
  • Process credit card, debit card, ACH, and other supported payment methods
  • Support tokenized customer payment profiles
  • Process refunds, voids, credits, and payment adjustments
  • Sync invoices, customers, and payments with accounting platforms
  • Display PayLync features inside QuickBooks Online, Xero, and FreshBooks through the Chrome extension.
  • Provide payment confirmations, reminders, overdue notices, and recurring invoice notifications
  • Manage surcharge, fee, branding, email template, and account settings
  • Provide reports and transaction history
  • Detect, prevent, and investigate fraud, abuse, security incidents, and unauthorized activity
  • Provide customer support
  • Improve product functionality, performance, reliability, and security
  • Comply with applicable laws, payment network rules, tax obligations, and legal requests
  • Enforce PayLync agreements, terms, and policies

11. How We Share Information

PayLync does not sell personal information, customer information, invoice information, or payment information.

We do not share user data with advertising platforms, data brokers, or information resellers.

We may share information only as needed with the following categories of parties.


A. Payment Processors and Payment Gateways

To process payments, PayLync may share necessary transaction, customer, invoice, and payment method information with configured payment processors, acquiring banks, payment gateways, card networks, ACH processors, and related financial service providers.

Depending on the merchant’s configuration, these may include:

  • NMI
  • Worldpay
  • CardConnect
  • TRX Services
  • ACH processing providers
  • Card brands and payment networks
  • Acquiring banks and settlement partners

These parties use the information to authorize, process, settle, refund, void, verify, or dispute payment transactions.


B. Accounting and Business Software Providers

When you connect PayLync with an accounting platform, we may share or sync necessary data with that platform to provide the integration.

This may include:

  • QuickBooks Online
  • QuickBooks Desktop
  • Xero
  • FreshBooks
  • Sage
  • Other accounting platforms you choose to connect

Shared information may include invoices, customers, payment records, transaction status, refund records, and sync-related data.


C. Service Providers

We may share information with trusted service providers who help us operate PayLync, such as:

  • Cloud hosting providers
  • Database and infrastructure providers
  • Email delivery providers
  • SMS or notification providers
  • Analytics and performance monitoring providers
  • Security and fraud prevention providers
  • Customer support tools
  • Error logging and diagnostic tools
  • Subscription and app store providers, where applicable

These service providers are authorized to use information only as necessary to provide services to PayLync.


D. Resellers, Partners, and Authorized Agents

If your PayLync account is created, managed, referred, or supported through an authorized reseller, partner, ISO, agent, or implementation provider, we may share limited account, merchant, setup, support, and transaction-related information as needed to provide service, support, onboarding, billing, or operational assistance.


E. Legal, Compliance, and Security

We may disclose information if required or permitted by law, including to:

  • Comply with subpoenas, court orders, or legal processes
  • Respond to lawful requests from public authorities
  • Protect PayLync, merchants, customers, and users
  • Investigate fraud, abuse, security incidents, or unauthorized access
  • Enforce our agreements and policies
  • Comply with payment network, banking, tax, or regulatory obligations

F. Business Transfers

If PayLync is involved in a merger, acquisition, financing, reorganization, sale of assets, or similar business transaction, information may be transferred as part of that transaction, subject to appropriate confidentiality and privacy protections.


12. Payment Data Security

PayLync uses security measures designed to protect payment and personal information.

These measures may include:

  • HTTPS/TLS encryption for data transmission
  • Encryption or secure protection of sensitive data at rest
  • Tokenization of payment methods where supported
  • Restricted access controls
  • Authentication and authorization controls
  • Activity monitoring and logging
  • Secure integration with payment gateways
  • Internal policies limiting access to sensitive information

PayLync does not store CVV/security codes. PayLync does not store full card numbers or full bank account numbers unless explicitly required and permitted under applicable payment rules, and only in a compliant and secure manner.

No method of transmission or storage is 100% secure. However, we take reasonable steps to protect information from unauthorized access, misuse, loss, disclosure, alteration, or destruction.


13. Human Access to User Data

PayLync personnel do not access user data unless access is necessary for:

  • Providing support requested by the user
  • Troubleshooting an issue with user consent
  • Investigating fraud, abuse, or security incidents
  • Complying with legal obligations
  • Performing internal operations using aggregated or anonymized data

Access is limited to authorized personnel with a business need.


14. Cookies and Tracking Technologies

PayLync may use cookies, local storage, and similar technologies on our website, web applications, and supported integrations to maintain authentication, remember preferences, provide requested functionality, maintain security, and improve service reliability.

As part of the QuickBooks Online integration, the PayLync Chrome extension may store and retrieve a PayLync authentication/session token on supported QuickBooks Online domains. This token is used only to authenticate the merchant with PayLync when the merchant initiates PayLync functionality from within QuickBooks Online.

The extension may read this token and transmit it securely to PayLync systems as authentication for the requested PayLync API operation.

PayLync does not use this authentication token or the Chrome extension's cookies permission to:

  • Track users across unrelated websites
  • Monitor unrelated browsing activity
  • Build advertising or behavioral profiles
  • Provide personalized or interest-based advertising or
  • Sell authentication or browsing information to third parties.

Cookie access by the Chrome extension is limited to supported domains and functionality necessary to provide PayLync's disclosed accounting and payment workflow.

PayLync may also use cookies and similar technologies on its own website and web applications to:

  • Keep users signed in
  • Maintain authentication and security
  • Remember user preferences
  • Maintain application functionality
  • Understand service performance and
  • Diagnose technical or reliability issues.

Users may control general website cookies through their browser settings. Disabling cookies or blocking cookies required for authentication may prevent certain PayLync or Chrome extension functionality from working correctly.


15. Analytics

PayLync may use analytics tools to understand website and product usage, diagnose technical issues, improve performance, and measure service reliability.

Analytics information may include browser type, device type, pages visited, feature usage, IP address, approximate location, session activity, and technical logs.

We do not use analytics data from the Chrome extension for personalized advertising or unrelated tracking.


16. Data Retention

We retain information for as long as necessary to:

  • Provide PayLync services
  • Maintain your account
  • Process payments and settlements
  • Support accounting sync and reporting
  • Resolve disputes
  • Prevent fraud and abuse
  • Comply with legal, tax, accounting, payment network, and regulatory obligations
  • Enforce our agreements

When information is no longer needed, we delete, anonymize, or securely retain it as required by law or legitimate business needs.


17. Account Deletion and Data Requests

You may request access, correction, deletion, or export of your personal information by contacting PayLync.

You may also delete your account through supported PayLync applications where account deletion is available.

After account deletion, PayLync will delete or anonymize associated personal information unless retention is required for legal, tax, payment, security, dispute, fraud prevention, or compliance purposes.

To submit a privacy request, contact us at:

support@paylync.com


18. Your Choices

Depending on your location and applicable law, you may have rights to:

  • Access your personal information
  • Correct inaccurate information
  • Delete your personal information
  • Request a copy of your information
  • Restrict or object to certain processing
  • Withdraw consent where processing is based on consent
  • Opt out of marketing communications
  • Close your account

You may unsubscribe from marketing emails by using the unsubscribe link in the email or by contacting us.

Service-related messages, such as payment receipts, security alerts, invoice notifications, account notices, and legal updates, may still be sent when necessary to provide the service.


19. Do Not Sell or Share Personal Information

PayLync does not sell personal information.

PayLync does not share personal information for cross-context behavioral advertising.

PayLync does not use Chrome extension user data for personalized advertising, retargeting, interest-based advertising, or data brokerage.


20. California Privacy Notice

This section applies to California residents.

Depending on how you use PayLync, we may collect the following categories of personal information:

  • Identifiers, such as name, email address, phone number, IP address, and account identifiers
  • Commercial information, such as invoices, customer records, payment history, and subscription details
  • Internet or electronic network activity, such as website usage, app usage, device information, browser information, and diagnostic logs
  • Financial-related information, such as tokenized payment method details, transaction references, last four digits, card brand, payment status, and gateway references
  • Professional or business information, such as company name, role, merchant account details, and business contact information
  • Customer records provided by merchants, such as customer names, email addresses, phone numbers, invoices, and billing details
  • Geolocation information, limited to approximate location derived from IP address, where applicable
  • Inferences, such as product usage preferences or account settings

We collect and use these categories for the purposes described in this Privacy Policy, including providing PayLync services, processing payments, syncing accounting records, security, support, compliance, and service improvement.

California residents may request access, correction, deletion, or information about how their personal information is used. California residents may also opt out of any sale or sharing of personal information, although PayLync does not sell personal information or share it for cross-context behavioral advertising.

To submit a California privacy request, contact:

support@paylync.com


21. Children's Privacy

PayLync is intended for use by businesses, merchants, and authorized users. PayLync is not directed to children under 13 years of age, and we do not knowingly collect personal information from children under 13.

If we become aware that we have collected personal information from a child under 13 without proper consent, we will take reasonable steps to delete that information.


22. Third-Party Links and Services

PayLync may contain links or integrations with third-party services, including accounting platforms, payment gateways, app stores, and business tools.

This Privacy Policy does not apply to third-party websites, applications, platforms, or services that are not controlled by PayLync. Their privacy practices are governed by their own privacy policies.


23. Changes to This Privacy Policy

We may update this Privacy Policy from time to time.

When we make changes, we will update the Last Updated date above. If changes are material, we may provide additional notice through the website, application, email, or other appropriate means.

Your continued use of PayLync after an updated Privacy Policy becomes effective means you accept the updated policy.


24. Contact Us

For privacy questions, data requests, or security concerns, contact PayLync at:

PayLync
Email: support@paylync.com
Website: https://paylync.com
PayLync.

Connected payments, accounting synchronization, field operations, and partner infrastructure for modern businesses.

Platform
Products Features Pricing Partners
Solutions
Small Business Service Business Payment Partners Commercial Data
Partners
ISOs & Agents Processors Gateways Developers
Company
About Contact Privacy Terms
© 2026 PayLync. All rights reserved. 1701 N Collins Blvd, Richardson, TX 75080 · support@paylync.com · +1 (469) 484-6291