StubSafe — Source library
Public documentation snapshot: 2026-09-08
Make a pay stub without handing over your payroll
Create accurate pay stubs on your own device. No account, no upload, no cost.
Make a pay stub without handing over your payroll
Built for: Small employers who run payroll for a handful of people and need a real statement each period · Independent contractors, freelancers and single-member owners recording their own pay or draws · Bookkeepers and payroll preparers handling several small clients who cannot put client data on a stranger's website · Workers rebuilding a pay record an employer never gave them, from records they already hold
StubSafe exists because of this.
You need a pay statement. Maybe you pay two people and want the record kept properly. Maybe you are a contractor and the leasing office asked for something showing what you actually made last month. Maybe you left a job that never handed you a stub, and now you are putting the record back together from your own deposits. It is an ordinary piece of paperwork. It should take ten minutes. Instead you land on a website you have never heard of, typing in a worker's full name, their wage, the last four of an ID number, your company address, your pay dates. Then it wants an account before it will show you anything. You have no way to know where that went, how long it is kept, or who can read it. If you are the bookkeeper, you just moved three clients' payroll details onto a company none of them agreed to. "They probably delete it" is not an answer you can give a client, and it is not an answer you should have to accept for yourself. The other half of it is the arithmetic. Gross, overtime at the right multiplier, deductions that come out before tax versus after, employer contributions that never touch the check, leave balances, and year-to-date figures that have to agree with the last statement you issued. One wrong cell and the document is worse than nothing, because now there is a record with an error in it. So most people end up in a spreadsheet, rebuilding the same formulas every period, checking them twice, and still not feeling sure.
StubSafe exists because of this.
The privacy claim is checkable, not just stated — the full app publishes a build record saying it receives no payroll data, and the Android app declares no network permission at all
StubSafe exists because of this.
Free with no per-document charge and no account requirement; optional support never unlocks a feature or changes what a document looks like
StubSafe exists because of this.
Every tax figure names its publisher, links the official source, and prints the effective and collection dates, on screen and on the PDF
StubSafe exists because of this.
Reference tax data is signature-verified before it is used, and can never replace the app's own calculation logic — an invalid, expired or older update is refused and the version already on the device is kept
StubSafe exists because of this.
Any change to a monitored official source stops publication until a person reviews it; a changed web page never becomes a tax rule automatically
StubSafe exists because of this.
Validation runs before the document exists, so a statement whose deductions exceed gross pay, or a correction that names no prior record, cannot be printed
StubSafe exists because of this.
Genuinely bilingual end to end in the full app — interface, manual, validation, and the generated document, not a translated marketing page
How StubSafe works, start to finish.
StubSafe builds pay statements on the machine in front of you. You open it, fill in the employer, the worker, the pay period, the earnings and the deductions, and it produces a finished PDF. The calculations run where you are sitting, the document is assembled where you are sitting, and the file lands in your downloads folder. There is no payroll account to create, no per-document charge, and nothing to upload before you can see the result. The full app publishes a machine-readable build record stating that it receives no payroll data, so it is a claim you can check rather than a promise you have to take on faith. There are two ways in, and it is worth knowing which is which. The quick builder is a single page: employer and worker, the pay period, regular and overtime hours, other earnings, five standard deduction fields, live totals and a PDF. It is the ten-minute version, and it is the right one when you need one statement now. The full app is where the rest of this page lives — vaults, batch, the six layouts, corrections, the tax adviser, the manual and Spanish. It installs to your home screen and keeps working with no connection once opened. In the full app the form covers the shapes real pay actually takes. Choose the worker type first: a W-2 employee, a contractor, an owner draw, a statutory employee, or a reimbursement-only statement. Then add earnings line by line across seven kinds — regular hours, overtime, bonus, commission, piece rate, reimbursement and other — each with its own rate and hours or units. Deductions carry a category so the document reads correctly: tax, pre-tax, post-tax, garnishment or other, calculated as a fixed amount or a percentage. On top of that you can record employer contributions that do not reduce the check, leave balances, notes, a company logo and year-to-date figures that roll forward from the last statement instead of being retyped. Before anything is generated, the app checks the numbers and tells you what is wrong in plain words. Deductions that exceed gross pay stop the export unless you are deliberately marking the statement voided. A corrected or replacement statement will not generate until it names the record it replaces, so the trail holds. A pay period with no start and end date will not export. A statement can be marked original, corrected, replacement, voided or draft, and drafts and voids are watermarked automatically so nobody mistakes one for a live document. When the numbers pass, you get an exact preview of the finished page before you commit — six document layouts, in Letter, A4 or Legal, with your accent colour and logo. Export it as a PDF, a PNG, a CSV, plain text, or an encrypted file you can reopen later. What you keep is up to you. A private session holds the current form in memory only and leaves nothing behind when you close it. A vault does the opposite: you set a passphrase, and drafts, reusable company and worker profiles, batch queues and local history are held encrypted on the device under it. You can keep several separate named vaults, set how much history to retain, see how much space it is using, and erase the lot in one action. The passphrase never leaves the device and cannot be recovered by anyone, including us — which is the point, and also something to take seriously. For anyone paying more than one person, the batch queue takes up to 50 workers, generates a separate PDF for each, and returns them in a single ZIP alongside one combined payroll CSV. Reusable profiles and an option to carry this period's earnings, deductions, contributions and leave items into the next mean the second pay period is mostly a matter of advancing the dates. There is also an optional adviser that will estimate federal and FICA amounts and give a state figure covering all 50 states and the District of Columbia — and every figure it shows names its publisher, links the official source, and prints the effective date and the date the information was collected, because an estimate you cannot trace is an estimate you should not use. Those figures are recommendations for you to confirm, never a guaranteed withholding calculation. The full app — interface, the 19-topic manual, validation messages and the generated documents — runs in English or Spanish, and keeps working with no signal once it has been opened once.
Everything in the current release.
Each of these is built and working today. Nothing on this list is a roadmap item.
Your payroll never leaves the device
Names, wages, ID digits, logos and finished PDFs are handled where you are sitting. There is no payroll account, no upload step and no copy held anywhere else. The full app publishes a machine-readable record stating it receives no payroll data, so you can verify the claim instead of trusting it. There is no analytics beacon either — the usage counters it keeps are on your device and you can reset them.
The arithmetic is done for you, to the cent
Gross, overtime, each deduction, employer contributions, net pay and year-to-date totals are computed as you type. Amounts are handled in whole cents rather than floating decimals, which avoids the rounding drift that bites spreadsheet formulas over a year of statements. You review the totals rather than rebuilding them.
It refuses to print a document that contradicts itself
Deductions larger than gross pay stop the export unless you are deliberately marking the statement voided. A statement with no pay period start and end will not generate. A correction or replacement must name the record it replaces before it can be produced. The check runs before the PDF exists, so a bad number never becomes a document you have to chase down later.
Every kind of pay a small operation actually runs
In the full app, pick the worker type first — W-2 employee, contractor, owner draw, statutory employee, or reimbursement-only — and the statement is built for that shape. Add earnings across seven kinds, from regular hours and overtime through bonus, commission and piece rate. Deductions carry a category — tax, pre-tax, post-tax, garnishment or other — so the document reads the way a payroll record should.
Six layouts, three paper sizes, your branding
The full app offers six document designs and Letter, A4 or Legal paper. Add your logo, set an accent colour, add notes and your own watermark text, and pick a detailed or compact treatment. What you see in the exact preview is what the PDF will be, so you are not printing to find out.
Corrections, replacements and voids that keep a trail
A statement can be original, corrected, replacement, voided or draft. Drafts and voids are watermarked automatically — the status word is stamped across the page whether or not you set a watermark yourself — and corrections carry a reference to the record they supersede. When someone asks later why there are two statements for one period, the documents answer for themselves.
Pay a whole crew in one pass
Add up to 50 completed statements to a batch queue and generate them together. You get a separate PDF for every worker plus one combined payroll CSV summarising the run, delivered as a single ZIP. Reusable company and worker profiles, and an option to carry this period's earnings, deductions, contributions and leave items into the next, mean the following period is mostly advancing the dates.
A locked vault, or no trace at all
Set a passphrase and your drafts, profiles, history and batch queues are held encrypted on the device, with 310,000 key-strengthening rounds standing between a guessed passphrase and your records. Or choose a private session that keeps the form in memory only and leaves nothing behind. You can keep several separate named vaults, cap how much history each retains, see how much space is in use, and erase the lot in one action.
Tax figures that show their homework
The optional adviser estimates federal and FICA amounts and gives a state figure covering all 50 states and the District of Columbia. Every figure names its publisher, links the official source, and prints the effective date and the date the information was collected — on screen and in the advisory section of the PDF. They are recommendations for you to confirm, and the app says so on the document itself.
A sourced checklist, honest about how far it goes
There is no single stub layout that satisfies every federal, state and local wage-statement rule, and StubSafe says so rather than implying otherwise. It bundles a reviewed federal recordkeeping checklist drawn from the US Department of Labor, detailed wage-statement checklists for California, Colorado and New York, and a caution list of states where a municipality may levy its own tax — each with a direct link to the official source and the date it was reviewed. For any other state you get the common-fields checklist and confirm the specifics yourself.
Works with no signal
Once the full app has been opened once, document creation, encryption, profiles, history, the bundled tax reference data, the built-in manual, both sourced guides and every export keep working with no connection at all. That covers a job site, a plane, a basement office, or a day the internet is simply out. Nothing about producing a pay stub requires being online.
English and Spanish, all the way through
In the full app the interface, the 19-topic manual, validation messages and the generated documents are all available in English and Spanish, and you can switch between them at any time, including offline. Documents can additionally carry French labels. A Spanish-speaking worker gets a statement they can actually read.
The Android app has no way to phone home
The Android app ships without internet access at all — it declares no network permission whatsoever, so the operating system will not permit it to send anything anywhere, which is stronger than a promise in a policy. It also blocks screenshots and screen recording and hides your payroll from the app switcher, and the draft it saves is encrypted with a key held in the device's own hardware-backed key store. It is a focused single-statement builder rather than the whole app.
A manual for every button, offline
The full app's built-in manual runs to 19 topic sections: the quick start and guided tour, batch payroll, vaults, pay periods, the tax adviser, corrections and statuses, exports, history, the optional account, troubleshooting, a button-by-button reference and a plain list of the product's limitations. It is searchable, it works with no connection, and contextual links beside the harder sections open the right topic directly.
Numbers we can stand behind.
Every figure below comes from the product's own release record or test suite, not from a marketing estimate.
Numbers we can stand behind.
States its limits on the document itself: every statement is printed as self-generated and independently unverified
Surfaces and status.
Status as of 2026-09-02. Checked 2026-09-02. https://stubsafe.autosecurelogin.com/ returned HTTP 200 and served a working in-browser quick builder — employer and worker fields, pay period, regular and overtime hours, five deduction fields, live totals, a self-generated notice and a PDF export; the page carries no version string. The full app at https://paystub.autosecurelogin.com/ also returned HTTP 200 and displays Version 5.7.2; its published build record reports version 5.7.2, built 2026-08-05,, and receivesPayrollData false. Privacy, terms, support, the manual, status, the sourced English guide and the sample document each returned HTTP 200 in the same check, and the served manual carried 19 topic sections. The public Google Play listing returned HTTP 404, so the Android app is invite-only rather than publicly available: 5.7.3 (build 16) is recorded in as delivered to the invite-only track on 2026-08-25, while 5.8.1 (build 19) is the current build in the repository at dated 2026-09-01 with no delivery recorded.
Worth more together.
Products on this platform share one sign-in, one support queue, and one engineering standard. These pair naturally with StubSafe.
ShopFit
If you are already selling and now have people to pay, the same owner ends up needing both a storefront that behaves and a pay record that holds up.
Policy Lens
Built on the same habit StubSafe applies to tax figures: an answer that cites its source, and stays quiet when the evidence is not there.
ASL Scan
For the same owner who cares where their payroll data goes and wants to know whether their own site or app is leaking something.
Recent progress.
This product ships often. The most recent verified changes, newest first.
Recent progress.
2026-08-17 a real-device pass on a Pixel 8 confirmed vault creation, the redesigned header, per-field clear controls and automatic state-code capitalisation working on hardware.
Recent progress.
2026-08-22 the purpose-built Android client became the main Android app and the old wrapper tree was retired.
Recent progress.
2026-08-24 to 08-25: version 5.7.3 was signed and delivered to the invite-only Android track — still the most recent Android build recorded as delivered.
Recent progress.
2026-09-01 brought three more builds in one day. 5.7.4 came out of auditing the shipped app itself rather than the source, and fixed three genuine defects that only appeared in the released build: saved drafts came back empty after restarting the app, a deduction entered as "1,300" printed as $0.00 on its own line while the total showed the right figure, and the PDF footer carried a stale version number. Pay period start and end are now required before export, so no statement prints with an empty period. 5.8.0 delivered a full visual refresh with proper light and dark modes, a new brand mark, card-based sections and a net-pay summary on the review screen. 5.8.1 fixed edge-to-edge display on newer Android after Google Play flagged it. Through all of it the screenshot blocking, on-device encryption and no-network posture were left untouched, which the current source confirms. The web app remains on 5.7.2.
Recent progress.
Free. Every feature — document creation, PDF export, profiles, batch, local history, encrypted vaults and the built-in manual — is available with no subscription and no per-document charge. Optional one-time support is published at $5, $10, $20 and $50 on the web, handled by Stripe so StubSafe never sees card details. The Android app contains no in-app purchase at all: its support link simply opens the same support page in your browser. Supporting StubSafe never unlocks a feature, changes access, or alters a generated pay stub.
What does it cost, and what is the catch?
It is free, and every feature is included — batch, vaults, profiles, history, all export formats and the full manual. There is no per-document charge, no trial, and no account required to make a stub. If you want to chip in, there are fixed $5, $10, $20 and $50 options on the web, handled by Stripe so StubSafe never sees your card details. The Android app has no in-app purchase at all; its support link just opens the same page in your browser. Supporting it changes nothing about what you can do or what the document looks like.
There are two web addresses. Which one do I want?
The quick builder at stubsafe.autosecurelogin.com is one page: employer and worker, the pay period, regular and overtime hours, other earnings, five deduction fields, totals and a PDF. Use it when you need one statement now. The full app at paystub.autosecurelogin.com is where vaults, the batch queue, the six layouts, corrections and voids, the tax adviser, the 19-topic manual and Spanish live, and it installs to your home screen and works offline. Both are free and both keep your payroll on your device.
We already use a payroll provider. Why would we want this?
If your provider handles everything you need, keep them — StubSafe does not move money, file returns or run direct deposit. It is for the gaps: a contractor or owner draw the provider does not cover, a correction or replacement you need to issue cleanly, a worker asking for a copy of a period the provider will not reprint, or a client too small to justify a provider at all. Plenty of people use both.
How do I know my payroll data is really staying on my device?
Two ways to check rather than take our word for it. The full app publishes a machine-readable build record that states it receives no payroll data, and you can fetch it yourself. The Android app declares no permissions at all — including no internet permission — which the operating system enforces and which you can see in the app's permission list. The only optional network request the web app makes on its own is a read-only download of a shared tax reference catalogue, and no payroll, name, location or document content goes with it. There is no analytics beacon; the usage counters it keeps are on your device and you can reset them.
Is it ready to use for real payroll today?
The web version is live and in use now — you can open it, make a statement and export a PDF in the next few minutes. The 5.7.2 release it is running passed 54 automated checks and a 19-of-19 release-readiness gate with zero warnings and zero failures, with its workflows exercised in a real browser at desktop, phone and tablet widths in both English and Spanish. The Android app is invite-only for now and there is no iPhone release yet.
What happens to my records if I stop using StubSafe?
Nothing disappears, because nothing was ever held anywhere but your device. Your PDFs are files you already saved. Your vault stays on the machine until you erase it, and you can export an encrypted copy of everything, plus CSV and plain text versions, at any time. There is no account to close, no data to request back, and no way for us to lock you out of your own records.
Can I move what I already have into it?
There is no bulk importer for a competitor's export. What there is: reusable company and worker profiles you set up once, an option to carry this period's earnings, deductions, contributions and leave items into the next, year-to-date figures that roll forward, and an encrypted backup file you can move between devices. Realistically the first statement for each worker takes a few minutes of typing and every one after that is mostly advancing the pay dates.
Can I use a StubSafe stub to prove my income to a lender or landlord?
No, and StubSafe says so on the document itself — every statement is printed as self-generated and independently unverified. It is a recordkeeping tool for accurate documents built from genuine payroll records; it does not verify employment, wages, identity or payment, and it must never be used to misrepresent income or eligibility. A document ID and hash can help you show a statement has not been altered since you made it, but that is a different thing from proof of employment.
How accurate are the tax figures?
They are estimates presented for you to confirm, never a guaranteed withholding calculation. The adviser covers federal and FICA amounts and gives a state figure for all 50 states and DC, and every figure names its publisher, links the official source, and prints the effective date and the date it was collected — on screen and in the advisory section of the PDF. State figures are labelled as estimates unless a maintained official method is implemented, and local tax is always something you confirm rather than something we guess from your location.
Does it tell me what my state requires on a pay stub?
Partly, and it is careful about the difference. It bundles a federal recordkeeping checklist from the US Department of Labor, detailed wage-statement checklists for California, Colorado and New York, and a caution list of states where a municipality may levy its own tax — each with the official link and the date it was reviewed. For any other state you get the common-fields checklist and the source links, and you confirm the specifics. It is an educational checklist, not a compliance certification, and no tool can certify a statement on your behalf.
What if I forget my vault passphrase?
The records in that vault are gone, and there is no reset. The passphrase never leaves your device and is not recoverable by anyone, including us — that is what makes the vault worth having, and it is a real trade-off. Keep the passphrase somewhere safe, and use the encrypted backup export so you have a second copy of your records. If you would rather not have a passphrase at all, a private session keeps the current form in memory only and leaves nothing behind.
Does it work without internet?
Yes, once you have opened the full app once. Document creation, calculations, encryption, profiles, history, the bundled tax reference data, the 19-topic manual, both sourced guides and every export keep working with no connection. That covers a job site, a plane, or a day the office internet is down. The Android app goes further and has no internet access at all.
How does it handle a mistake on a statement I already gave someone?
Mark the new statement as corrected or a replacement and it will not generate until it names the record it supersedes, so the two documents reference each other. You can also mark a statement voided, which stamps VOIDED across the page. Drafts are watermarked the same way, so a working copy is never mistaken for something you issued.
Can I run it for several clients without mixing them up?
Yes. Keep a separate named vault per client, each with its own passphrase, so one client's records are never open while you work on another's. Within a vault, reusable company and worker profiles keep the details straight, and the batch queue generates up to 50 workers at once with a combined payroll CSV for the run.
What should I know before I rely on it?
We would rather you hear this from us than discover it later. As of 2026-09-02:
What should I know before I rely on it?
StubSafe does not verify employment, income, identity, payment or legal compliance. Every document it makes is printed as self-generated and independently unverified, and it must not be used to misrepresent income, employment, taxes, benefits or eligibility.
What should I know before I rely on it?
The tax and compliance figures are estimates for you to confirm against the official sources shown, not a guaranteed withholding calculation, tax advice, or legal advice.
What should I know before I rely on it?
State tax figures are labelled as estimates unless a maintained official state method is implemented, and local tax is always confirmed by you rather than inferred from your location.
What should I know before I rely on it?
The bundled wage-statement checklist is detailed for three states only — California, Colorado and New York — alongside a federal recordkeeping baseline and a caution list of states where a municipality may levy its own tax. For every other state you get the common-fields checklist and the official links, and you confirm the specifics yourself.
What should I know before I rely on it?
The two web addresses are not the same thing. stubsafe.autosecurelogin.com is a quick one-page builder with a single PDF output; vaults, batch, the six layouts, corrections, the tax adviser, the manual and Spanish are in the full app at paystub.autosecurelogin.com.
What should I know before I rely on it?
The Android app is a focused single-statement builder in English, not the whole app: one layout, one saved draft, no vaults, no batch, no tax adviser and no built-in manual. It is invite-only and not listed publicly on Google Play.
What should I know before I rely on it?
The Android build most recently recorded as delivered to invite-only testers is 5.7.3. Versions 5.7.4, 5.8.0 and 5.8.1 were built on 2026-09-01 and their delivery is not recorded.
What should I know before I rely on it?
There is no iPhone or iPad release. The source is kept in step with the other platforms but the project is unsigned, and it is blocked on developer-account renewal, so no Apple build is available to install.
What should I know before I rely on it?
If you lose your vault passphrase, nobody can recover it — including us. That is the design, and it means keeping a copy somewhere safe is on you.
What should I know before I rely on it?
Data lives on your device, so a lost or wiped device means lost records unless you have exported an encrypted backup yourself.
Make a pay stub without handing over your payroll
Prefer email? contact@autosecurelogin.com