Evidence rules
How SalaryPadi reaches a careful answer
Every useful label needs a source, a date and a rule. Where the evidence is incomplete, we say so.
Remote eligibility
“Remote” describes where work happens; it does not identify who may be hired. We classify worldwide, Africa, EMEA, Nigeria, named-country, restricted and unclear eligibility separately. The exact source wording, provenance and verification date remain attached to the classification.
We mark Nigeria eligible automatically only when a source explicitly says Worldwide, Nigeria, Africa, or names Nigeria in an included-country list. EMEA and ambiguous free text remain unclear until reviewed.
Source and vacancy freshness
Each source has a policy record describing its terms, attribution, storage, indexing, structured-data and destination requirements. Imports are idempotent. Jobs store first-seen, last-seen, last-checked and expiry dates. A missing record is not expired until a successful refresh provides enough evidence.
Salary publication
Original currency, pay period and gross/net status are preserved. Public employer-role-country figures require at least three sufficiently similar approved contributions from distinct accounts. Smaller cells are broadened or suppressed; individual salary submissions are never public.
Confidence
Confidence reflects sample size, similarity, freshness and verification. It is not a promise that a company, job or estimate is correct or safe. Ratings are withheld until their separate minimum review threshold is met.
Calculators
Payroll rules are versioned with effective dates and official links. The calculator uses the Nigeria Tax Act 2025 rules effective 1 January 2026 and exposes assumptions rather than hiding them. Currency conversions are labelled estimates with a rate and timestamp.
Data environments
Production requires a dedicated SalaryPadi Supabase project. Local code never falls back to another product’s database. Development fixtures are opt-in, visibly labelled and refused in production. Without credentials, private features fail closed rather than storing sensitive data in the browser.
Technical decisions and phase evidence live in the repository’s product plan. Questions or corrections can be submitted through the trust and safety process.