Legal

Acceptable use policy

What you can and cannot do with PayBlah — including the line we will not cross on collections tactics.

1. What this policy is

This Acceptable Use Policy (“Policy”) describes how you may and may not use PayBlah’s website, application, APIs, webhooks, debtor portal, and related services (together, the “Service”).

PayBlah is not a debt-collection agency. It is subscription software that helps a business send overdue-invoice reminders about its own B2B invoices, in that business’s own name. You remain the creditor at every step. We do not buy debt, do not contact people as a third-party collector, and never threaten anyone.

Using the Service means you agree to this Policy together with our Terms of Service Refunds & Cancellation GDPR Data Request. If something here conflicts with a signed commercial agreement that expressly overrides this Policy, that agreement controls for the points it covers.

Plain summary. Use PayBlah to remind business customers about your own overdue invoices, politely and lawfully. Do not use it for consumer debt, harassment, spam, security abuse, or to ignore opt-outs and STOP requests.

2. Who it applies to

This Policy applies to:

  • Account owners, admins, and standard users on a PayBlah workspace
  • Anyone who accesses the Service via API keys, webhooks, or integrations you configure
  • Affiliates, resellers, advisors, or other third parties who use the Service on a customer’s behalf (to the extent they interact with the Service)

If you invite others into your workspace, you are responsible for making sure they follow this Policy.

3. Permitted use

Subject to this Policy and your subscription, you may use the Service to:

  • Send overdue invoice reminders for B2B receivables you are owed — that is, invoices for goods or services supplied by your business (or by a business you are authorized to act for under a written arrangement) to another business, organization, or professional customer
  • Import or sync invoice and contact data from supported accounting systems (Xero, QuickBooks Online, Sage) or spreadsheet/CSV import, so reminders stay accurate
  • Configure reminder sequences, tones (Friendly / Standard / Firm / Final), quiet hours, and related settings that the product exposes
  • Use the debtor portal, payment links (where your plan includes them), activity queue, reports, API, and webhooks for legitimate accounts-receivable operations on your own data
  • Honor payment, reply, dispute, opt-out, and STOP events so chasing stops or adjusts as designed
  • Export your data and manage users, roles, and security settings for your workspace

Reminders are designed to go out in your business’s name, using the fixed template wording you select — not as PayBlah acting as a collector.

3.1 What “B2B” means here

For this Policy, B2B means the person or entity you are contacting is being invoiced in a business, trade, professional, or organizational capacity — not as a private consumer for personal, household, or family purposes. If you are unsure whether a relationship is B2B, do not enroll it until you have confirmed it is appropriate under the laws that apply to you.

4. Prohibited use

You must not use the Service — and must not attempt to use the Service — for any of the following.

4.1 Consumer debt and non-B2B receivables

  • Collecting, chasing, or reminding about consumer debt (personal, household, or family obligations)
  • Using the Service as a consumer debt-collection tool, marketplace for bought debt, or third-party collection operation
  • Importing or enrolling invoices you do not own or are not authorized to pursue as the creditor (or as the creditor’s clearly authorized accounts-receivable operator)

4.2 Harassment, abuse, and pressure tactics

  • Harassing, intimidating, demeaning, or repeatedly contacting people in a way that is designed to distress them
  • Using language that implies formal legal process, financial-record harm, seizure of goods, or other consequences PayBlah templates do not support — and that this product is not built to deliver
  • Contacting people at unreasonable frequency or outside the product’s intended reminder model in order to pressure payment
  • Using the Service to target individuals for personal grievances unrelated to a genuine business invoice you are owed

4.3 Spam and unsolicited bulk messaging

  • Sending bulk commercial messages that are not genuine overdue-invoice reminders for invoices you are owed
  • Using contact lists scraped, purchased, or obtained without a legitimate business relationship and a valid basis to message about a specific invoice
  • Misrepresenting who is sending the message, or concealing the identity of the creditor business

4.4 Ignoring opt-outs, STOP, and suppression

  • Continuing to message a channel after a valid opt-out, unsubscribe, or SMS STOP request has been recorded for that contact and channel
  • Attempting to bypass, clear, or work around the consent register, suppression lists, or pause/stop behavior
  • Re-enrolling a contact on a channel they have opted out of without a lawful, documented basis and product-supported path to do so

4.5 Security abuse and multi-tenant attacks

  • Probing, scanning, or testing the Service for vulnerabilities except under a coordinated responsible-disclosure process to security@payblah.com
  • Attempting to access another customer’s tenant, database, portal tokens, API keys, or data
  • Interfering with the integrity, availability, or isolation of the Service (including denial of service, credential stuffing, or automated abuse)
  • Circumventing rate limits, authentication, authorization, or audit controls
  • Introducing malware, malicious scripts, or harmful content through any upload, API, or integration path

4.6 Reselling and unauthorized commercial redistribution

  • Reselling, sublicensing, white-labeling, or otherwise providing the Service to third parties as your own product without a separate written agreement with PayBlah that expressly permits it
  • Sharing a single subscription across unrelated businesses to avoid plan limits, except where a multi-entity arrangement is expressly agreed in writing

4.7 Unlawful and high-risk misuse

  • Any use that violates applicable law in the territories where you operate or where you contact recipients (including anti-spam, privacy, telecommunications, and unfair commercial practices rules)
  • Fraud, impersonation, or sending invoices you know are false or not owed
  • Using the Service in connection with activities that are illegal where you operate

5. Safety features are not optional upgrades

PayBlah includes safety controls designed to keep reminders respectful and controllable. These capabilities are part of the product on every plan, including trials — they are not sold as paid add-ons:

  • Auto-pause when a payment, reply, or dispute is recorded for an invoice
  • Firm / Final approval settings (ships default-on; you remain responsible for how you configure them)
  • Kill switch to halt sending
  • Email opt-out and SMS STOP / suppression handling where SMS is enabled
  • Consent register and append-only audit trail of sends and key actions
  • Never-chase flags, pauses, and first-run review so you can see what would send before live traffic

You must not attempt to disable these protections by technical workarounds. Where a setting can be adjusted in the product UI, use only those supported controls — and configure them in a way that still honors opt-outs, STOP, and applicable law.

Your responsibility. PayBlah provides tools and defaults. You remain responsible for who you enroll, what invoices you chase, the accuracy of contact details, and compliance with laws that apply to your business and your recipients.

6. Opt-outs, STOP, and contact preferences

Respecting contact preferences is a condition of using the Service.

  • Email: Honor unsubscribe and opt-out signals processed by the Service for reminder email
  • SMS: Where texting is enabled on your plan, STOP and related carrier / regulatory handling must be honored; suppressed numbers must not be re-messaged on that channel through PayBlah
  • Fallback: If a contact opts out of SMS, do not attempt to force texts; the product is designed to fall back to email rather than continue on a blocked channel
  • Records: Do not delete or falsify opt-out history to continue contact

If you believe an opt-out was recorded in error, contact support@payblah.com — do not invent a technical bypass.

7. Accounts, credentials, and fair access

  • Keep login credentials, API keys, and webhook secrets confidential
  • Use roles appropriately; do not share owner credentials broadly inside or outside your organization
  • Notify us promptly if you suspect unauthorized access to your workspace
  • Do not use another customer’s account, or misrepresent your identity to support or in the product
  • Use the Service within plan limits and fair-use expectations described in pricing and product documentation; do not attempt to evade caps by creating duplicate workspaces for the same business without permission

8. Content you send and data you import

You are responsible for:

  • The accuracy of invoice amounts, due dates, and customer identity
  • Having a legitimate basis to process and contact the people and businesses in your data
  • Not uploading unlawful, infringing, or harmful content
  • Not using custom fields, letter content, or free-text areas (where available) to introduce prohibited pressure language or non-invoice marketing spam

Templates in PayBlah are fixed, pre-written wording. Do not treat the Service as a free-form bulk messaging platform for unrelated marketing.

9. Policy response

If we reasonably believe this Policy has been breached, we may take steps that are proportionate to the risk and the facts available to us. Depending on severity, those steps may include:

  • Contacting the account owner for clarification or remediation
  • Requiring removal of prohibited data or cessation of a prohibited campaign
  • Temporarily suspending sending features or the workspace while we review
  • Limiting API access where abuse or risk to the platform is involved
  • Terminating the account for serious or repeated breach

We prefer to resolve issues by conversation where that is safe and practical. Suspension or termination is a platform-integrity measure, not a substitute for your own legal advice about your receivables.

Nothing in this Policy obliges us to monitor all customer activity, and failure to apply a provision in one instance does not waive our ability to apply it later.

10. Changes to this Policy

We may update this Policy as the product and regulatory environment evolve. Material changes will be communicated in a reasonable way (for example, by email to the account owner, an in-app notice, or an update posted on this page with a revised date). Continued use of the Service after the effective date of a change means you accept the updated Policy, except where applicable law requires a different process.

11. Contact

Questions about acceptable use, suspected misuse of your workspace, or help configuring safety settings:

Draft website policies for product readiness — have qualified counsel review before public launch in each territory. This page describes intended product rules and is not legal advice. Territory-specific messaging, privacy, and commercial rules may require local counsel review before you rely on them in production.