1. Scope
This Privacy Policy explains how PayoutChecker handles personal information when you visit our website, create an account, purchase a subscription, contact support, receive communications, or use the reconciliation Service.
2. Our privacy roles
For account, billing, marketing, website and support information, PayoutChecker generally acts as the entity determining the purposes of processing. For transaction/order/financial files uploaded by a restaurant, accounting firm or restaurant group for reconciliation, PayoutChecker generally processes that data on the customer’s instructions and may act as a processor/service provider under applicable law.
3. Information we collect
- Account and business data: name, work email, phone, organization, role, locations and preferences.
- Billing metadata: Stripe customer/subscription/invoice identifiers, payment status, billing address, tax IDs where provided, and limited payment-method metadata such as card brand/last four. Stripe processes full payment credentials.
- Uploaded business data: marketplace statements, POS exports, bank exports, rate cards, payout IDs, order IDs, fees, refunds, adjustments and generated reports.
- Usage/security data: IP address, browser/device, login events, audit logs, error logs and feature interactions.
- Support/communications: emails, messages, files and support notes.
- Marketing/analytics data: campaign/source information and permitted analytics/advertising identifiers when those technologies are enabled.
4. How we use information
- provide payout analysis, matching, reports and dispute documentation;
- authenticate users and isolate organizations;
- process billing and subscription entitlements;
- send transactional report/deadline/billing notifications;
- provide support and improve parser reliability;
- detect fraud, abuse and security incidents;
- comply with legal obligations;
- send marketing where permitted and subject to opt-out choices.
5. Restaurant customer information inside uploads
Some source exports may contain information about restaurant consumers. PayoutChecker is designed to normalize only fields needed for financial reconciliation. Customers should minimize unnecessary names, phone numbers, addresses and free-text notes. PayoutChecker may retain raw source files for a configured period so findings remain auditable, then delete them according to retention settings and contractual requirements.
6. How we disclose information
We may use service providers/subprocessors for cloud hosting/storage, billing, email, SMS, monitoring, support and analytics. Examples may include Stripe, Cloudflare or another S3-compatible storage provider, an email delivery provider, Twilio and analytics/advertising vendors actually enabled by the customer/website configuration. We disclose only information reasonably needed for the service provider’s task and use contractual/security controls where appropriate.
We may also disclose information if required by law, to protect rights/security, in a corporate transaction, or at your direction.
7. Sale/sharing and targeted advertising
We do not sell personal information for money. Some analytics or advertising technologies, if enabled, can be treated as “sharing” or targeted advertising under certain U.S. state privacy laws. Where applicable, PayoutChecker provides privacy choices and honors qualifying opt-out signals such as Global Privacy Control for non-essential advertising/targeting uses.
8. Cookies and similar technologies
We use strictly necessary technologies for authentication, security and preferences. Optional analytics/advertising technologies are governed by the Cookie Policy and your choices. You can reopen privacy choices from the website footer.
9. Retention
We keep information for as long as reasonably necessary to provide the Service, maintain financial/audit records, comply with law, resolve disputes and enforce agreements. Retention periods vary by data type and plan. Cancellation does not necessarily cause immediate deletion. Customers may request deletion subject to legal, security, backup and contractual exceptions.
10. Security
We use administrative, technical and organizational measures designed to protect data, such as encrypted transport, access controls, tenant authorization, audit logging and controlled object storage. No system is completely secure, and we cannot guarantee absolute security.
11. International processing
PayoutChecker may be operated by an entity outside the United States and may use service providers in multiple countries. Where required, we use appropriate contractual or legal mechanisms for cross-border transfers. Hosting region and transfer mechanisms must match the production architecture and enterprise agreements.
12. U.S. state privacy rights
Depending on where you live and whether a law applies to PayoutChecker, you may have rights to request access/knowledge, correction, deletion, portability, or opt out of certain sale/sharing/targeted advertising, and to appeal certain decisions. California law also recognizes Global Privacy Control as an opt-out signal for covered businesses that sell/share personal information.
Submit requests through Privacy Choices or privacy@payoutchecker.com. We may verify identity/authority before fulfilling certain requests.
13. Business customer requests
When PayoutChecker processes restaurant/customer data on behalf of a business customer, individuals should generally contact that restaurant/accounting firm first. We will assist our customer as required by contract/law.
14. Children
PayoutChecker is a business service not directed to children under 13, and accounts are intended for adults authorized to act for businesses.
15. Marketing communications
You can unsubscribe from marketing email using the link in the message. Transactional/service communications may continue while needed to operate your account. SMS opt-out instructions are provided in text messages; STOP requests must be honored.
16. Changes and contact
We may update this policy as the Service changes. Privacy contact: privacy@payoutchecker.com (verify mailbox before launch).
