Terms of Use

The rules both sides agree to. They're written plainly, and the site enforces them.

Version 6 · in effect since 15 October 2026

What changed on 15 October 2026

  • More work on a session: after a report is reviewed, either side can propose more work on the same session, with its own price, report, review and payment. The other side accepts or declines.
  • Unpaid tests: developers can run unpaid (volunteer) tests, and a part can be agreed at $0. Unpaid work doesn't count toward tester tiers.
  • Making a test unpaid later: testers already in are each asked whether to continue for free; anyone who declines keeps their paid deal.
  • Changing your mind: waiting offers, applications, counter-offers, requests to drop a part, call times and finish-early amounts can be changed or withdrawn until the other side answers.
  • Cards: posting a paid test needs a saved card, charged only when a report is accepted. A card can be removed once no paid work still needs it.
Earlier versions
  • Version 5, 14 October 2026: Free during launch: all developer features (several open tests, approving testers, invites, themes, CSV export) are free for now, with no subscription. You still pay only for the reports you accept. When paid plans start, every developer is told in advance, with the date the free period ends. Tests and work already under way carry on. One account can be a developer, a tester, or both; you can't test your own tests.
  • Version 4, 12 October 2026: Free accounts: developers post tests for free and pay only for reports they accept, with one test open at a time. The $3/month subscription adds several open tests, approving testers, themes and transcript search, next rounds and CSV export. Advances: developers can pay part of the agreed price early; it's taken off the final charge. Tips stay extra, on top of the price. Email and texts: choose how you hear about things; texts are only for urgent updates, and only if you add a phone number. Sample work: with both sides' permission, testers can show short excerpts of accepted work on their profile, never from tests under an NDA.
  • Version 3, 11 October 2026: Developer subscription: the first test is free, then posting tests costs $3/month on top of report prices. Cancel any time; it lasts until the end of the month you've paid for. Price offers: testers can offer their own prices before joining; if the developer accepts, the tester joins on those prices. Raising prices: after testers join, prices can go up (never down), and the raise reaches everyone still working on the test. Live calls: testers can propose up to 3 times of their own when the offered ones don't work; the developer confirms one.
  • Version 2, 11 October 2026: Recordings: testers can upload or record test sessions on the site. Only the developer and tester of that session (and admins handling a dispute) can watch them. Transcripts and themes are made by AI models running on our own servers. Recordings and feedback aren't sent to outside AI companies. Editing a test after testers join: prices, formats, session time, the NDA and existing questions can't change, deadlines can only be extended, and joined testers are told about every change. Changes to these terms: you're notified and asked to accept before you post or join another test.
  • Version 1, 9 October 2026: First version.

1. What this platform is

  • Playtest Platform connects people who make apps, websites and games ("developers") with people who try them and give feedback ("testers").
  • Everyone must be at least 18 and give accurate account details. One account per person.

2. Posting a test (developers)

  • A test states its scope up front: what to do, how long a session takes, which feedback formats are required or optional, the price of each, and what counts as an accepted report (the acceptance criteria).
  • Developers post tests for free and pay only for the reports they accept, with one test open at a time. An optional subscription of $3 a month allows several open tests and adds extras (approving testers, themes and transcript search, next rounds, CSV export). It can be cancelled at any time and stays active until the end of the month already paid for. During the launch, all of these extras are free for every developer; before that ends, every developer is told the date it ends, and tests and work already under way carry on.
  • Developers can pay part of the agreed price early (an advance); it's taken off what the report finally costs and isn't refunded if the report is later paid less. Tips are extra, on top of the price.
  • Testers may offer their own prices before joining. If the developer accepts, that tester's deal uses those prices.
  • Posting a paid test needs a saved card; it's charged only when a report is accepted. A card can be removed once no paid work still needs it.
  • A test, or a part of it, can be unpaid (volunteer work, $0). Unpaid work doesn't count toward tester tiers. To make a paid test unpaid after testers join, each tester already in is asked; anyone who declines keeps their paid deal.
  • After a report is reviewed, either side can propose more work on the same session (an extension) with its own price, report, review and payment. It follows the test's current instructions and criteria but keeps its own prices; the other side accepts or declines.
  • Once a tester joins, the scope they agreed to is saved and is what their report is judged against, even if the test is edited later.
  • After testers join, formats, the session time, the NDA and existing questions can't change, prices can only go up (a raise reaches everyone still working on the test), and the deadline can only be moved later. New questions are optional for testers who already joined. Joined testers are notified of every change.

3. Joining and reporting (testers)

  • Joining means you agree to the test's scope, its acceptance criteria and any NDA.
  • Deliver the formats you chose. Honest, critical feedback counts, and so does saying where and why you stopped early.
  • Access keys are personal. Don't share builds, keys or confidential details.
  • Waiting offers, applications, requests to drop a part, proposed call times and finish-early amounts can be changed or withdrawn until the other side answers. Agreed deals change only with both sides' agreement.

4. Reviews and payment

  • Payment is for completing the agreed session and the requested feedback, judged against the acceptance criteria, not for whether the feedback is positive.
  • A developer accepts a report in full, pays part of it (25%, 50% or 75%) or rejects it. Anything less than full must name the criteria that weren't met and give a reason. Acceptance is final.
  • Reports not reviewed within 7 days are accepted in full automatically.
  • Live calls are billed for their real length at the tester's hourly rate (up to the test's maximum, and at most 150% of the booked time). The developer confirms the length within 48 hours, or it's confirmed automatically.
  • Live calls are booked at a time the developer offers, or one the tester proposes and the developer confirms.
  • Testers receive 80% of each report's price and of live call time; the platform keeps 20%. Tips go to the tester in full.
  • The usefulness rating (1-5) affects a tester's reputation, not their pay.

5. Disputes

  • A tester can dispute a rejection or partial payment within 14 days. An admin decides against the agreed criteria, and can read the report, follow-ups and chat.
  • Outcomes: paid in full, paid 50%, or the developer's decision stands. A dispute never lowers a payment.

6. Conduct

  • Be respectful. No harassment, spam, fake or copied reports, or leaking builds.
  • Keep payments on the platform: deals arranged outside it aren't covered by reviews, disputes or payouts.
  • Anyone can report the other side of a test session to the admins. Admins may remove content and suspend accounts that break these rules.

7. Feedback and confidentiality

  • Developers may use the feedback they receive to improve their products. Testers keep no rights over how it's used, but their name isn't published without consent.
  • NDAs set by developers apply between the developer and the tester.

8. Recordings, transcripts and AI

  • Testers can upload or record test sessions on the site, and developers can add recordings of live calls. Only the developer and tester of that session can watch them, plus admins handling a dispute or report.
  • Recordings are transcribed, and feedback is grouped into themes, by AI models running on our own servers. Recordings and feedback aren't sent to outside AI companies or used to train models.
  • Transcripts and themes are made automatically and may contain mistakes; reviews are judged on the report and recordings themselves.
  • With both the tester's and the developer's permission, a tester may show short excerpts of their accepted work (a written answer or a moment of a recording) on their profile. Work from tests under an NDA is never shown, and either side can withdraw permission at any time.

9. The service and changes to these terms

  • The platform is provided as is. We aren't responsible for the products being tested, for builds, or for agreements between users beyond what these terms describe.
  • When these terms change, everyone is notified with a summary of what changed and asked to accept before posting or joining another test. Tests you're already in carry on under the scope you agreed to.