Privacy Policy

PayGhost is a payment collection and follow-up automation platform operated by NoLapse LLC, a limited liability company registered in Arizona, available at payghost.app.

We distinguish between two categories of people who interact with PayGhost:

• Owners — service businesses and contractors who create accounts and use PayGhost to collect payments from their customers.
• Customers — the end customers of those businesses who receive payment requests via SMS.

From Owners (account holders):

• Name, email address, and password (via Supabase Auth)
• Business name, business type, and business contact information
• Stripe Connect account information (handled directly by Stripe — PayGhost does not see full account or banking details)
• Payment request data you enter: customer names, phone numbers, job descriptions, and amounts
• SMS tone and reminder cadence preferences
• Notification preferences and account settings
• IP address and timestamp when consenting to platform terms at account setup

From Customers (via SMS and payment page):

• Phone number (provided by the owner when creating a payment request)
• First name (provided by the owner)
• Payment method information (collected and stored entirely by Stripe — PayGhost never stores card numbers, CVVs, or expiration dates)
• The last 4 digits of a card, received from Stripe after successful authorization
• Inbound SMS replies (including STOP and HELP)
• Payment and interaction history
• IP address and timestamp when interacting with the payment page

We use the information we collect to:

• Deliver the PayGhost service — sending payment requests, automated follow-up reminders, and processing scheduled charges through Stripe
• Send automated SMS messages to customers on behalf of owners
• Authenticate owners and maintain account security
• Process subscription billing for owner accounts via Stripe
• Send operational notifications to owners (payment received, card declined, plan paused, etc.)
• Comply with legal obligations and respond to lawful requests
• Detect and prevent fraud, abuse, and excessive dispute activity
• Improve the PayGhost service

We do not sell personal information. We do not use customer phone numbers for any purpose other than the specific payment request for which they were provided. We do not send marketing messages to customers.

PayGhost sends SMS messages to customers on behalf of owners. These messages are payment-related only: payment request notifications, follow-up reminders, pre-charge notices, and payment confirmations.

Consent: Owners attest at account setup that their customers have provided their phone number in connection with a job or service and have consented to receive payment-related text messages. This attestation is timestamped and stored against the owner account. Owners are solely responsible for ensuring actual customer consent exists before entering a phone number into PayGhost.

Opt-out: Customers may reply STOP at any time to permanently opt out of all PayGhost messages across all accounts. This opt-out is honored immediately. No further automated messages are sent.

Help: Customers may reply HELP to receive the business contact information for the owner who sent the request.

Message frequency:Typically 1–5 messages per payment request depending on the owner's chosen follow-up cadence. Message and data rates may apply.

Customer phone numbers are not shared with third parties for marketing and are not used outside the PayGhost payment collection context.

PayGhost uses Stripe for all payment processing. PayGhost never stores full card numbers, CVVs, or expiration dates. The only card data that may appear in PayGhost is the last 4 digits of a card, received from Stripe after authorization and used solely for display in the owner's dashboard.

PayGhost never holds or has access to customer funds. All money moves directly through Stripe's infrastructure.

Stripe's privacy policy governs how Stripe handles payment data: stripe.com/privacy.

We share information only with the following parties and only as necessary to deliver the service:

• Stripe — for payment processing, Connect account management, and fraud prevention
• Twilio — for SMS delivery (receives recipient phone numbers and message content)
• SendGrid — for email delivery (receives recipient email addresses and email content)
• Supabase — for database and authentication infrastructure
• Inngest — for background job scheduling and automation
• Legal requirements — we may disclose information when required by law, court order, or valid legal process

We do not sell, rent, or trade personal information to any third party for their own marketing or commercial purposes.

Owner account information is retained for the duration of the account and for a reasonable period afterward as required by law. Payment event records, consent records, and audit logs are retained for a minimum of 3 years to satisfy financial recordkeeping and TCPA compliance requirements.

Customer phone numbers and payment history are retained for as long as the associated owner account is active. Owners may request deletion of specific customer records by contacting support@payghost.app. Opt-out records (STOP replies) are retained indefinitely to ensure suppression is honored even after account deletion.

We use industry-standard security measures including encrypted connections (TLS 1.2+), encrypted data storage, row-level security on all database tables, and strict access controls. No system is completely secure. If you believe a security incident has occurred, contact us immediately at support@payghost.app.

Depending on your location, you may have rights to access, correct, or delete your personal information. To exercise these rights, contact us at support@payghost.app. We will respond within 30 days. Note that some information may be retained as required by law even after a deletion request.

We may update this Privacy Policy from time to time. We will notify account holders of material changes by email at least 14 days before changes take effect. The date at the top of this page indicates when it was last updated.

Questions or concerns? Contact us: