Skip to main content

Useful salary data needs rules people can trust.

PayYako is designed to create directional market evidence while limiting the risk that any contributor can be identified.

Collection

Contributors submit job, experience, location, organisation type, monthly gross pay, currency, and benefits. We do not request names, email addresses, phone numbers, or employer names.

Normalization & moderation

Job titles are deterministically matched to a controlled role taxonomy. Currency is converted using the configured reference rate. Confidence rules flag unmatched titles, implausible values, and salary–experience mismatches for human review.

Benchmark calculation

Only approved records enter calculations. Salary views report distribution statistics on monthly gross USD-equivalent pay. Benefits views report the share of approved records in a group that selected each benefit.

Publication threshold

A benchmark is public only after it contains at least five approved records. A benefit is shown only after at least three people report it inside that group. Individual submissions and exact record-level details are never exposed publicly.

Privacy & abuse controls

Raw network addresses are not stored. A one-way keyed hash may be retained for rate limiting. Public writes are validated server-side, and the database does not grant anonymous access to salary submissions.

Important limitations

The dataset is voluntary and may not represent every sector, employer, city, market, or informal work arrangement. Self-reported values can contain errors despite moderation.

Exchange rates, benefits, bonuses, commissions, and role scope can change the meaning of base pay. Benchmarks are evidence for a conversation, not a guaranteed offer or compensation recommendation.

Common questions about our methodology

How is salary data collected?
Contributors voluntarily submit their salary details through an anonymous survey. We collect job title, experience, location, industry, company type, and gross monthly pay. No personally identifiable information is requested.
How are benchmarks calculated?
Only approved and moderated records are included. We compute count, minimum, maximum, average, median, 25th percentile, and 75th percentile for monthly gross USD-equivalent pay.
When are benchmarks published?
A benchmark becomes public only after at least five approved submissions exist in that group. Benefits have an additional threshold: each benefit needs at least three selections inside the group before it appears.
Is my personal data stored?
No personal data is collected. IP addresses are never stored raw — only a one-way hash is retained for rate-limiting. Individual submissions are never exposed publicly.