Keep the shelf fresh.
Send a specific factual correction, a current public source or a reproducible product change. Promotional swaps and paid placement are not accepted.
hello@frupy.com
Include the Frupy page, the exact statement that changed, a current public source and the date you observed it.
What makes a useful correction
Useful messages are concrete. A platform changed its access model, removed a feature, added a visible verification step, rebranded, changed its remote focus or now handles geographic filters differently. Screenshots may help describe an interface change, but include a public URL whenever possible.
For platform representatives
Use a verifiable company email and link to the official material that supports the correction. Frupy may update factual language after independent confirmation. A correction does not guarantee Fresh Ten inclusion, removal of a supported limitation or favorable placement.
For candidates
Personal experience can surface a useful question, but do not send identity documents, banking information, private recruiter conversations or another person’s personal data. Describe the product behavior, date and location context. Frupy does not investigate individual employment disputes or authenticate hiring outcomes.
When a job looks suspicious
Contact the real employer through a route you found independently, report the listing to the host board and use the consumer-protection or law-enforcement channels available in your country. Frupy cannot recover funds, identify anonymous actors or provide legal advice.
What may not receive a response
Generic guest posts, paid ranking requests, link exchanges and requests to remove a factual trade-off are not corrections. Specific current facts receive priority because they help every reader make a better decision.
How factual updates are handled
A submitted source is checked against the current product and the exact Frupy statement. Small factual corrections may be applied directly. A change to Fresh Ten membership requires a broader review because it affects the collection’s balance of use cases, not only one sentence. Frupy may retain a supported limitation even when a platform disagrees with the editorial interpretation.
Product facts and personal experience are handled differently. A current official page can establish a feature or access model. A public user story can suggest a question about that experience, but cannot establish how every candidate or employer behaves. This distinction protects useful criticism without turning an anecdote into a universal claim.