The rules, written before the game starts.

• These rules govern the testing missions entrusted to the platform's independent testers.
• They are explicitly accepted at sign-up through a dedicated checkbox. The accepted version, date and time are recorded and can be produced in case of dispute.
• Any amendment is notified by email with 15 days' notice. It never applies retroactively to an ongoing mission. A tester who refuses the new version may close their account and receive their full vested balance, threshold waived.
• Where these rules conflict with a commercial page of the site, the version most favourable to the tester applies.

The tester is an independent contractor. There is no employment contract, no subordination, no imposed hours and no exclusivity. Testers freely choose which missions they accept and may decline any mission without justification and without any consequence for their account.

Each party remains responsible for their own tax and social obligations in their country of residence. The platform provides an annual summary of amounts paid on request.

1. Real device, single account. A physical Android device they own, one personal Google account, no emulator, no virtual machine, no account created for the occasion, no device shared between testers.
2. Accurate information. The declared Google address must be correct and stay active for the whole mission. Any change must be reported before a mission starts.
3. Daily presence. Genuinely open and use the app every day of the mission, exercising the requested core flow, not just the home screen.
4. Reports. At least three concrete findings per mission: a bug, a usability friction or a suggestion. Empty feedback is not a report.
5. Confidentiality. No distribution, publication, resale or sharing of the app under test or its screenshots, and no direct contact with the developer.
6. Good faith. Never post a public review or rating on the Play Store for an app tested in this context. Feedback stays private.

A mission lasts 14 consecutive days. It starts on the day the tester's opt-in is confirmed in the developer's closed testing track.

• Pay rates, duration, app and the flow to test are displayed before the mission is accepted.
• Daily check-in is automatic; the tester sees their counter in real time and may challenge an uncounted day within 48 hours.
• At the end of the mission the tester leaves the track and uninstalls the app, unless the developer asks otherwise.
• If the app is unusable, fails to launch, or the track is closed by the developer, the mission is interrupted through no fault of the tester: days performed are credited and the continuity bonus is paid pro rata.

Permanently vested — cannot be cancelled, even after account closure, except for proven fraud under Article 9:

• credits for testing days performed and validated;
• bug bonuses already confirmed by the developer.

Conditional — only comes into existence when its condition is met, and is cancelled otherwise:

• the end-of-mission continuity bonus (€0.28 on a Presence mission, €0.70 on a Complete mission): owed only if the mission reached day 14 without interruption;
• referral bonuses: €0.50 per referred tester (max 2 counted per month, vested only once the referred tester completes a mission), and €1.50–€3.50 for bringing in a developer client, vested only after that test is delivered.

The vested balance is cumulative, never expires, and becomes withdrawable from €10. If the account is closed by either party outside of fraud, the vested balance is paid in full even below the threshold.

Abandonment occurs when, before day 14, the tester leaves the testing track, uninstalls the app, misses two days on the same mission, or stays unreachable for more than 72 hours after a reminder.

Abandonment causes real harm to the client developer: the 14-day continuity Google requires is broken and their production access can be delayed by two weeks. The consequences are therefore:

• the continuity bonus for that mission is cancelled;
• referral bonuses still “pending” at that date are cancelled;
• credits for days already performed and validated remain owed and are paid normally;
• the mission is reassigned and a replacement is onboarded the same day, at the platform's cost and not the client's;
• on repeat, the account is suspended for 90 days, then closed on the third occurrence.

Clean exit (a tester's right). Nobody is forced to continue a mission. A tester who gives at least 48 hours' notice that they cannot continue is not treated as having abandoned: they lose that mission's continuity bonus but keep their daily credits, their referral bonuses and full access to the platform. Telling us always costs less than disappearing.

Immediate withdrawal, no penalty. A tester may leave on the spot, without notice and without any loss, any mission involving an app that turns out to be illegal, deceptive, dangerous, in breach of Google's Developer Program Policies, or that asks for personal data unrelated to the test. Please report it: the mission is then cancelled for all testers and the client is dropped.

A day missed because of hospitalisation, an accident, a bereavement, a broken or stolen device, or a prolonged network or power outage is not a breach.

• The tester has 7 days to send simple supporting evidence.
• No sanction is applied and no referral bonus is cancelled.
• The continuity bonus is paid pro rata for days performed.
• The tester keeps priority on following missions.

A falsified justification, however, falls under Article 9.

The bonus is €1 per referral, limited to 2 referrals counted per calendar month per referrer. Beyond the quota the referred tester is welcomed normally: they are never penalised for their referrer's quota.

The bonus is first recorded as “pending”. It vests only if the referrer completed a mission themselves with at least one validated report in the period. An account that only recruits, never testing, has its referral bonuses cancelled and its access closed. This platform pays for testing, not for recruiting.

No sanction is applied without the tester being able to respond, except an immediate precautionary suspension where fraud is suspected.

1. Written notification of the alleged breach, with the evidence observed.
2. 72 hours to reply, provide evidence or contest.
3. Reasoned decision sent in writing, stating the sanction and the amounts concerned.
4. Appeal available within 14 days to someone who did not take the original decision; answered within 14 days.
5. If disagreement persists, consumer mediation or the competent court, with no upfront cost to the tester.

Undisputed vested amounts are paid normally throughout the procedure: a dispute never freezes the vested balance.

• Payment: withdrawal available from €10 of vested balance, paid within 7 business days after an anti-fraud check, downloadable receipt. Any fees are shown before confirmation.
• Data: mission data kept for 24 months, accounting records for the statutory period. Access, rectification, erasure and portability rights exercised by simple email, answered within 30 days.
• Evidence: check-in logs, written exchanges and the timestamp of acceptance of these rules are authoritative between the parties, without prejudice to contrary evidence provided by the tester.
• Severability: if a clause were held invalid, the others would remain applicable.
• Governing law and disputes: to be completed according to the company's country of registration before going live.

This article is accepted when a seller or buyer account is created, separately from the rest of these rules, and the acceptance is timestamped.

• Absolute prohibitions: selling or buying a Google Play developer account; exchanging login credentials; publishing unverifiable figures; selling code you do not own; dealing directly between seller and buyer; paying or collecting outside the signed protocol; transferring an app under an undeclared Google warning. Each prohibition is set out with its reason on the Transparency page and inside the member area.
• Ownership declaration: for every listing, the seller certifies holding the rights to the code, the artwork and the name, or a written licence allowing their transfer. The declaration is timestamped and carried into the transfer protocol.
• Order of operations: a transfer follows nine successive steps — party checks, confidentiality and file, signed protocol, deposit, official transfer request, Google confirmation, delivery of code and access, buyer acceptance, balance. No step may be skipped or brought forward, including by Testeo.
• Payment: 30% on signature of the protocol, 40% on Google's confirmation of the transfer, 30% at the end of acceptance, paid directly from buyer to seller. Above €1,500 an escrow agent — notary or licensed service — is named in the protocol. Testeo never collects the sale price and invoices only its 6% commission, due on completion.
• Failed transfer: if Google's refusal stems from the seller's account, the deposit is refunded in full; if it stems from the buyer's account, the deposit stays with the seller for the work carried out.
• Introduction clause: the commission remains due if a sale completes between two parties introduced by Testeo within twelve months of that introduction, through whatever channel.
• Sanctions: any breach means the listings concerned are withdrawn and the account closed. If a transfer is under way, the file is cancelled and amounts already paid settled under the protocol.