Privacy · Wages.software
Do not send employee records through this website.
The public site explains an early-access calculation product. It is not an intake portal, payroll system, employee account, or secure document exchange.
This public surface
No forms, advertising trackers, or payroll-data fields.
The pages on wages.software are rendered as ordinary documents. They do not offer a login, employee wage-calculation form, upload control, employee lookup, card field, or lead-capture form. The separate taxable-basis explorer illustrates subtraction only and accepts no employee records. The contact action opens email, where a visitor should describe the shape of a problem without attaching staff records. The site sets no marketing cookie and embeds no third-party advertising script. Basic short-lived service logs may include the normal request facts needed to operate and protect a web service.
Email is not the place for Social Security numbers, bank instructions, tax forms, addresses, wage histories, or identifiable employee examples. An early conversation can use a synthetic case or an abstracted historical pattern. If a later evaluation requires protected material, the collection purpose, access, transfer method, retention period, deletion process, and responsible operator must be agreed before any data moves.
Future product data
Calculation inputs, rules, and audit evidence require separate lifecycles.
A calculation may need opaque staff references, earning and deduction lines, filing attributes, and authority elections. The minimum useful record should avoid duplicating identity details already held by an employer system. Signed rules and their provenance need longer retention because they explain historical results. Audit evidence should identify the authorized actor and decision without turning logs into a second payroll database.
Bank instructions, tax forms, and address changes are particularly sensitive. Existing modules validate and mask shapes but do not establish a complete storage product. Encryption, key ownership, access review, field-level display rules, deletion, and incident procedures must exist before any branded surface is allowed to retain them. No marketing sentence on this page substitutes for those controls.
Wages.software is operated by Stanley Studios as a for-profit software product. It does not sell personal information or use employee information for advertising. This page does not claim a certification or a deployed payroll-data environment. Specific contractual privacy terms, subprocessors, and retention schedules belong to an actual scoped service agreement if and when the product becomes operational for an organization.
Start with invented numbers instead of redacting a real statement.
For a first question, create a new example from a blank page. A fictional reviewer might write gross 80,000 cents, deduction 2,000 cents, two hypothetical authorities and a question about whether the bases stay independent. Those invented values can explain the arithmetic without carrying a worker's history. Copying an actual statement and removing the name is a different operation: dates, amounts, references and the surrounding story may still identify someone. This public guide does not provide a de-identification tool or certify that a redacted document is anonymous.
Keep the example small enough that every included fact has a purpose. If the question is subtraction, a home address adds nothing. If the question is a missing signature, an account number adds nothing. If the question is which rule period applies, a personal explanation for an absence adds nothing. This is a manual choice about what to put in an enquiry, not a promise that Wages filters an attachment after it arrives. The safer evaluation example is one whose unnecessary personal fields were never copied.
A source reference is different from the person's underlying record.
A reviewer can identify a governing document by title, version and effective window without attaching a completed employee form. Those details help someone understand the rule question. They do not establish permission to collect the associated personal material. In a fictional unsigned-table enquiry, say which signature condition is missing and which period the example uses. Do not add actual wage statements to make the request seem more complete. More data can make an early question harder to handle without making the software issue any clearer.
The same distinction applies to screenshots. A crop that shows an error may also show browser tabs, a person's name, account context or an unrelated notification. Describe the displayed wording and page path in ordinary text first. If the question can be answered from a synthetic description, the image is unnecessary. This site offers no document upload control or private case room. It cannot inspect your proposed attachment before your email application sends it, and this guide does not promise an automated redaction or classification service.
A masked response does not establish an entire data lifecycle.
The published employee-validation boundary is deliberately narrow: validation and masking return a decision. A displayed last-four representation is not evidence of a saved instruction, a committed audit chain or a completed account change. A privacy review should ask separately what enters a function, what its return contains and whether any caller persists it. The existing Wages explanation says those payroll surfaces persist nothing. The public page does not turn that limited behavior into a promise that a complete employee self-service product is available.
This also limits what a reviewer can infer from a convincing example. A screenshot of a masked account field does not prove a retention period, access-review procedure or deletion workflow. Those are distinct operational questions. Keep them as questions if the relevant service arrangement is absent. The page's description of computation is useful precisely because it does not require an imagined storage system to make sense. These manual examples introduce no intake, storage or transfer mechanism.
Ask about the boundary without supplying the data behind it.
A useful enquiry might say: our review needs to distinguish a computed change event from an instruction retained by an employer system; which published part describes that distinction? The message identifies the concern without including an employee's election. A second question might ask which statements apply to the public website and which describe an early-access calculation product. Keeping those scopes separate prevents a public-page policy from being treated as a negotiated agreement for processing operational wage records. An email discussion does not establish that agreement.
A prospective evaluator may object that an invented example cannot reproduce every difficult case. That can be true. The appropriate result is to identify the remaining evidence requirement, rather than attach real records to a public contact message. Keep any actual operational material within the process responsible for it while the separate scope is considered. This website is not a transfer channel, a payroll processor or a source of legal advice. Its present value is a clear question and a visible limit on what the public surface accepts.
There is no AI intake or automated attachment review on this public surface. It offers no checkout and does not disburse wages. Do not supply card details, bank instructions or employee material in an attempt to activate a service. The contact link is an enquiry route, and the guide establishes no new account or data-handling agreement.
Where to go next
The rest of this site.
Every page here is its own argument rather than a restatement of the home page. If you would rather ask a person, the address below reaches one.