Acceptable Use Policy

You must be 18 or older and legally able to enter a contract where you live. The person paying is the person we have a transaction with — there are no accounts, so there is nobody else to check. If you are doing payroll for a business, you are the employer in this relationship and the record-keeping duties that come with it stay with you, not with this tool.

If you are entering details about another person — an employee, a contractor, someone you pay — you are confirming that you have the right to hold and use that information for payroll records, and that the figures you enter are the figures you actually pay.

• Internal bookkeeping: an itemized record of one pay period for your own accounts.
• Employer-side records where you pay one or a few people and need the per-period breakdown rather than just the amount that left the account.
• Self-employment records: documenting what you paid yourself or what you earned, between the filings that actually carry legal weight.
• Reconciliation: checking that a payslip you were issued matches what you expected, and keeping your own copy of the arithmetic.
• Tax-season housekeeping — as working papers, never as a filed form.

Most of these are either fraud or the preparation for it, in every jurisdiction we are able to reason about; the last bullet is about keeping the service itself workable. They are prohibited on this service regardless of whether anyone is harmed by a given document.

• Presenting a generated document as someone else’s statement. A pay stub is meaningful because the payer issued it. Sending ours to a lender, landlord, insurer, employer, court or agency as if an employer produced it is misrepresentation, whatever the numbers say.
• Using a document for an eligibility decision. Loan, mortgage and credit applications; rental and tenancy applications; identity or employment verification; proof of funds, of address, or of legal status; benefits and government programs. Those ask for a record from the issuer, which is not a thing this tool can make.
• Inventing or inflating. Entering income you or the person you name did not actually receive; fabricating a stub for someone you do not legitimately pay; altering figures so earnings look higher or deductions look lower.
• Assuming an issuer identity. Using an employer name, address, tax/EIN identifier or logo that is not yours to use, or mimicking a real payroll provider’s document layout so the output reads as theirs.
• Substituting for a required form. A generated stub is not a W-2, W-3, 1099, 941 or any other filing, and does not discharge an employer’s reporting or withholding obligations. See the disclaimer for the authoritative IRS pages.
• Harmful or unlawful purpose generally. Harassing or defrauding a person, evading a legal obligation, or anything else a court would not be surprised by.
• Abuse of the service itself. Working around the controls that decide how a document is delivered, instead of using those controls as they are offered: probing or bypassing the rate limits on document requests, the single-use download-token controls, or the payment step that stands between a request and an unwatermarked file. Scraping the generator or the checkout flow, or using another person’s payment method, is prohibited either way.

Stated as the system works, not as a threat. There are no accounts and drafts are encrypted at rest, so we do not read pay stub contents and do not moderate them in advance. What we can do, and do on notice: revoke a document’s download access (existing links stop working and no new one can be issued for that document), delete the stored data, refuse a refund on a paid order where the purchase itself was the abuse, and respond to lawful requests from the payment provider or a competent authority about a specific transaction. The payment provider is the party with card-level fraud controls and the one that sees the transaction; we see the document.

Report abuse to the published compliance contact, with the order number from the receipt if you have one. Requests that come from a payment provider dispute or a legal process are handled through that channel as well, and where a record is credibly implicated in a report we handle it as described under when deletion is held back in the Privacy Policy — that is the only retention this page implies, and there is no other.

This website is operated by a United States–based independent operator under the Paystubs name, with its operator and hosting located in the United States. This site is offered from the United States and is governed by the laws of the State of Alaska. The single published channel for questions, compliance reports and legal notice is support@paystubs.shop.

A tool that generates a document from what you type cannot verify what you typed. So the honest version of an acceptable-use policy for this product is a line drawn at presentation: your numbers, your records, your responsibility; and never someone else’s verification. Everything above follows from that one line, and if a use case needs the second half of it, the right move is to ask the party that pays you for their own record instead.

The commercial terms (payment, license to the output, refunds, liability, the 3-business-day support response) are in the Terms of Service; what the documents are and are not is in the Disclaimer.

Version 3.0 — last updated September 24, 2026. This is the version currently in force for the acceptable use policy you are reading. We do not keep superseded versions at a separate URL: the change log below is the record of what changed and when.

• Version 1.0 — September 22, 2026: First published version: who may use it, allowed uses, prohibited uses, enforcement.
• Version 2.0 — September 23, 2026: Added the operator identity and contact line, and stated the monitoring boundary in the same words the Privacy Policy uses.
• Version 3.0 — September 24, 2026: Rewrote the service-abuse prohibition so it bars circumventing the controls that decide delivery — the rate limits, the single-use download-token controls, and the payment step where one applies — instead of "obtaining an unwatermarked document without paying", which the free promotion would turn into a rule against using the product. Says plainly that requesting a document through the free route is intended use, not a breach, and updates who we have a transaction with now that no payment is required for it.

A material change to this document gets a new version number and date above, and the date the service terms refer to is the same date.