Last Updated: August 29, 2026
Privacy Policy
This Privacy Policy explains how M2 AI, LLC (“M2 AI,” “we,” “us,” or “our”) collects, uses, processes, stores, and discloses information when you use PayerScore at payerscore.app. PayerScore is a business service that analyzes historical receivables and payment information from a connected QuickBooks® Online company.
1. Information you provide
PayerScore does not currently maintain a separate user-profile or password database. You provide authorization through Intuit when connecting a QuickBooks Online company and provide billing information directly to Stripe when purchasing a subscription. If you contact us, we receive the email address, contact details, and information you include in the communication.
2. QuickBooks connection information
To maintain the connection, PayerScore stores the QuickBooks company or realm identifier, company name, encrypted OAuth access and refresh credentials, token-expiration information, and record timestamps. OAuth credentials are stored separately from the accounting data used to calculate a report and are encrypted before being written to the application database.
3. QuickBooks accounting data
When you request a report or customer detail, PayerScore retrieves the records used by its scoring logic: company information, customers, invoices, invoice and due dates, balances, payment status, linked payments and payment dates, and credit memos. The application calculates settled and open invoices, days early or late, on-time payment percentages, trends, and open receivables from those records.
PayerScore retrieves that accounting data on demand, processes it in application memory, and returns the resulting report to your browser. The checked-in database schema does not contain tables or columns for customer, invoice, payment, credit-memo, balance, or calculated-report records, and the application does not write those accounting records to its database.
4. Logs, errors, analytics, and browser storage
PayerScore does not intentionally serialize complete QuickBooks API responses, OAuth credentials, customer records, invoice payloads, payment histories, or report contents into application logs. Application request logs contain a generated request ID, HTTP method, route pattern, response status, and duration. Error messages are reduced to general provider or status information rather than provider response bodies.
Vercel hosts the application and may process ordinary request metadata such as IP address, browser or user-agent information, timestamps, requested URLs, response status, region, and security events. Requested URLs can include technical identifiers used to open a customer-detail view. PayerScore does not control every provider-level log generated by Vercel and does not represent that provider request metadata is the same as in-memory accounting payloads.
The current application does not include a product analytics SDK, advertising tracker, or separate error-monitoring service. It does not use browser local storage or session storage. It uses a signed, secure, HTTP-only browser cookie that can contain an opaque PayerScore connection identifier, OAuth state, anti-forgery token, demo flag, and session timing information. The cookie does not contain QuickBooks access or refresh tokens, customer names, invoices, balances, or payment histories.
5. Billing information
Stripe hosts subscription Checkout and the customer billing portal and processes payment-card information under Stripe’s own privacy terms. PayerScore does not receive or store full payment-card numbers. PayerScore stores the Stripe customer identifier, subscription identifier, subscription status, and signed-event ordering metadata needed to enforce paid access and avoid applying duplicate or out-of-order billing events.
6. How we use information
We use information to:
- authorize and maintain the QuickBooks connection;
- retrieve receivables data and calculate PayerScores on demand;
- present report and invoice evidence to the connected browser session;
- create and manage subscriptions and paid access;
- secure the service, prevent abuse, and validate requests;
- diagnose errors and maintain reliability;
- respond to support, deletion, billing, and privacy requests; and
- comply with legal obligations and protect rights and safety.
7. No sale, advertising use, or generative-AI processing
M2 AI does not sell QuickBooks data and does not use QuickBooks data for third-party advertising. PayerScore’s score is calculated by deterministic application logic from historical invoice-payment records. The application does not send QuickBooks customer, invoice, payment, credit-memo, or balance data to a generative-AI or large-language-model provider, and it does not use that accounting data to train general-purpose artificial-intelligence models.
8. Service providers
- Intuit / QuickBooks Online provides OAuth authorization and the source accounting records requested by the application.
- Stripe processes subscription payments, hosts Checkout and the billing portal, and sends signed billing-status events.
- Vercel hosts and delivers the application and processes ordinary application and request metadata.
- Supabase hosts the private PostgreSQL database containing encrypted connection credentials and billing-entitlement state.
These providers process information under their own terms and privacy policies. PayerScore does not currently use a separate authentication provider, product analytics provider, advertising provider, or error-monitoring provider.
9. When information may be disclosed
We may disclose information to the service providers above as needed to operate PayerScore; when you direct or consent to disclosure; to comply with law, legal process, or a valid governmental request; to investigate fraud, abuse, or security threats; to protect rights, safety, and the service; or in connection with a merger, financing, acquisition, reorganization, or sale of relevant assets. We do not share QuickBooks data merely for unrelated third-party marketing.
10. Retention
- Connection information and OAuth credentials remain in the PayerScore database while the company is connected and are deleted from the active database when PayerScore completes its Disconnect flow.
- PayerScore billing identifiers and status remain with the connection record until that record is deleted. Stripe may retain transaction and subscription records for legal, tax, fraud-prevention, and operational purposes under its own policies.
- Accounting payloads and calculated reports are not written to the PayerScore database. They remain available in the rendered browser page for the current interaction and are re-read when the report is requested again.
- Hosting and security logs are retained according to the active Vercel account settings and provider policies. PayerScore does not currently impose a separate fixed application-log retention period.
- Support communications may be retained as reasonably needed to respond, document the request, protect the service, and meet legal obligations.
Deleted connection records may remain temporarily in infrastructure backups until those backups rotate under provider settings. A formal application-specific log and backup retention schedule has not yet been established and is a prelaunch operational item.
11. Disconnecting, cancellation, and deletion
When you use PayerScore’s Disconnect control and an active paid subscription exists, the application first requests immediate subscription cancellation from Stripe. If Stripe confirms cancellation, PayerScore deletes the connection record—including encrypted OAuth credentials, company identifier and label, and locally stored Stripe identifiers—from the active database and clears the browser session. If Stripe does not confirm cancellation, PayerScore preserves the connection so you can retry without losing access to billing controls.
Canceling only through Stripe does not delete the QuickBooks connection; it changes paid access after Stripe sends the corresponding event. Revoking PayerScore from inside QuickBooks prevents future authorized reads but does not automatically cancel Stripe billing or delete PayerScore’s local connection record. After an external revocation, use PayerScore’s Disconnect control or contact us to cancel and delete the connection.
PayerScore does not currently maintain a separate user account. To request access, correction, or deletion of information associated with a connection or support communication, contact us at the address below. We may retain limited information when required for legal, security, fraud-prevention, dispute, or billing-record obligations.
12. Privacy choices and rights
Depending on your jurisdiction, you may have rights to request access to, correction of, or deletion of personal information, or to object to certain processing. Those rights vary and may be subject to exceptions. Send a request using the contact below. We may need to verify your identity and authority over the connected business before completing it.
13. Security
PayerScore uses HTTPS, OAuth, secure and HTTP-only session cookies, encrypted OAuth credentials at rest, restricted server-side database access, anti-forgery tokens, trusted-host validation, and signed Stripe webhooks. No online service can guarantee absolute security. You are responsible for safeguarding your devices and connected accounts and should notify us if you suspect unauthorized use.
14. Children
PayerScore is a business service and is not intended for children under 18. We do not knowingly solicit personal information from children.
15. International processing
PayerScore’s application and database are currently configured in United States hosting regions. Intuit, Stripe, Vercel, and Supabase may process information in other locations under their policies. If you use the service from another country, information may be transferred to and processed in the United States.
16. Changes to this Privacy Policy
We may update this Privacy Policy as the service or our practices change. We will update the “Last Updated” date and provide reasonable notice of material changes where appropriate.
17. Contact
M2 AI, LLC
richard@m2ai.tech
Intuit and QuickBooks are registered trademarks of Intuit Inc. PayerScore is an independent product of M2 AI, LLC and is not affiliated with, sponsored by, endorsed by, or approved by Intuit Inc.