Terms of use

Last updated: November 3, 2026

These terms govern the use of TestTogether, the platform where developers help each other test apps and prepare their release. By creating an account, you accept them. How your data is handled is described in the privacy policy.

This is a translation provided for convenience. If it differs from the French version, the French version prevails.

1. Publisher and purpose

TestTogether is a service published by Facydex, based in Bamako (Mali). Contact: facydex@gmail.com · +223 73 40 20 73.

The platform connects members who test each other's apps on real devices, and partners who help them publish on the stores.

2. Account

You create an account with an email address and a password, or with Google or GitHub. It is personal: you are responsible for what is done with it.
Your address must be confirmed before you apply to a mission or publish a campaign. It is never shown to other members.
Profile information and declared devices must be accurate. One account per person.
Your profile shows your activity on the platform; it does not certify your professional skills.

3. Member roles

The same member can be a tester (carries out missions), a creator (has their apps tested) and a partner (supports or publishes other members' apps, after their profile has been reviewed). Rights are checked on every resource: in particular, you can never apply to your own campaign.

4. Campaigns and tests

The creator describes the version under test, the goal, the scenarios, the number of places, the reward and the deadline. Once a mission is accepted, its version cannot be changed and its reward cannot be lowered.
Tests are carried out only with dummy accounts and data provided by the creator. Apps that require a real payment are excluded from missions.
The creator picks the testers within the number of places. If no report is submitted by the deadline, the place is released.

5. Android builds

Creators can upload APK files (testing) and AAB files (publishing). They guarantee they hold the rights to them and sign them with their own key: TestTogether never asks for a keystore or its password.
Every file is analysed automatically before it is offered. A file showing dangerous behaviour is blocked and reviewed by the team; it is neither offered to testers nor passed on to a partner.
The analysis reduces risks without removing them. Testers install apps at their own risk, on the declared device, and uninstall them after the mission.
For iOS, distribution goes exclusively through TestFlight.

6. Reports and rewards

The report states the real environment, the result of each scenario, the issues found and a conclusion. Screenshots must show no personal data and no credentials.
The reward depends neither on the number of bugs nor on a positive store review. A well-documented test with no issue is approved like any other.
The creator has 72 hours to approve, ask for more information (the tester then has 48 hours to reply) or reject with a reason. Nothing is approved automatically.
A given participation can only be rewarded once.

7. Credits and payments

Credits are used on the platform: test places, campaign opening fees, publishing requests and steps. They are earned through approved missions, offered on sign-up (3 credits) or bought with Mobile Money.
Packs, prices, the cost of each action and the payment methods are set by Facydex and shown before each payment or debit. They may change; they never apply retroactively.
Payments are processed by a Mobile Money aggregator. Credits are added only once the operator has confirmed the payment. TestTogether never asks for your PIN.
Credits cannot be withdrawn, converted into money or transferred between accounts. A confirmed purchase is not refundable, except for a processing error or a debit with no matching credits.
When a campaign opens, its budget is reserved; credits for unfilled places are returned when it closes, while those for reports under review or in dispute stay reserved until a decision is made. A recorded transaction is never deleted: any correction is made through an offsetting entry with a stated reason.

8. Partners and publishing

The “Profile reviewed by TestTogether” badge only means the team has checked the partner's file. It is not an Apple or Google certification.
The terms (publisher shown on the store, rights, duration, fees, revenue, maintenance, access, end of the collaboration) are agreed and accepted by the creator and the partner before any preparation. Any fees are settled directly between them: TestTogether does not collect them and is not a party to their agreement.
A partner who publishes from their own account is the publisher on the store and is responsible for complying with its rules. They can allow TestTogether to upload versions through the official API by inviting its service account in the Play Console, and revoke that access at any time.
A partner's agreement does not guarantee approval by a store. Store statuses are reported by the participants.

9. Prohibited conduct

Uploading malware, an app that collects data without its users' knowledge, or an app you do not hold the rights to.
Copying another member's report, creating multiple accounts, approving as a favour or colluding to obtain credits.
Asking for or sharing passwords, two-factor authentication codes, signing keys or real personal data.
Harassing, insulting or threatening a member; posting a review without a real collaboration.
Getting around store rules or promising approval.

10. Disputes and moderation

A rejected report can be disputed for 7 days; the credits stay locked until the team decides, with at most one settlement. Reports of abuse are reviewed, and every decision is explained and logged. An automatic detection triggers a review, never a direct sanction.

11. Intellectual property

Tested apps remain the property of their creators. By submitting a report, the tester allows the creator to use it to improve and publish their app. The TestTogether brand, interface and platform code belong to Facydex.

12. Liability

Facydex takes care to keep the platform running but cannot guarantee permanent availability. TestTogether is not responsible for apps uploaded by members, for store decisions, or for agreements made between creators and partners.

13. Suspension and closure

In case of a breach, the team can restrict or suspend an account, giving a reason. You can ask for your account to be closed from your profile: your access is revoked and the data that must be kept (credit log, ongoing disputes) is reduced to the strict minimum. Unused credits are not refunded.

14. Changes and governing law

These terms may change; members are notified before a significant change takes effect. They are governed by Malian law. Failing an amicable agreement, the courts of Bamako have jurisdiction. For any question: facydex@gmail.com.

Last updated: November 3, 2026

This is a translation provided for convenience. If it differs from the French version, the French version prevails.

2. Account

You create an account with an email address and a password, or with Google or GitHub. It is personal: you are responsible for what is done with it.

Your address must be confirmed before you apply to a mission or publish a campaign. It is never shown to other members.

Profile information and declared devices must be accurate. One account per person.

Your profile shows your activity on the platform; it does not certify your professional skills.

4. Campaigns and tests

The creator describes the version under test, the goal, the scenarios, the number of places, the reward and the deadline. Once a mission is accepted, its version cannot be changed and its reward cannot be lowered.

Tests are carried out only with dummy accounts and data provided by the creator. Apps that require a real payment are excluded from missions.

The creator picks the testers within the number of places. If no report is submitted by the deadline, the place is released.

5. Android builds

Creators can upload APK files (testing) and AAB files (publishing). They guarantee they hold the rights to them and sign them with their own key: TestTogether never asks for a keystore or its password.

Every file is analysed automatically before it is offered. A file showing dangerous behaviour is blocked and reviewed by the team; it is neither offered to testers nor passed on to a partner.

The analysis reduces risks without removing them. Testers install apps at their own risk, on the declared device, and uninstall them after the mission.

For iOS, distribution goes exclusively through TestFlight.

6. Reports and rewards

The report states the real environment, the result of each scenario, the issues found and a conclusion. Screenshots must show no personal data and no credentials.

The reward depends neither on the number of bugs nor on a positive store review. A well-documented test with no issue is approved like any other.

The creator has 72 hours to approve, ask for more information (the tester then has 48 hours to reply) or reject with a reason. Nothing is approved automatically.

A given participation can only be rewarded once.

7. Credits and payments

Credits are used on the platform: test places, campaign opening fees, publishing requests and steps. They are earned through approved missions, offered on sign-up (3 credits) or bought with Mobile Money.

Packs, prices, the cost of each action and the payment methods are set by Facydex and shown before each payment or debit. They may change; they never apply retroactively.

Payments are processed by a Mobile Money aggregator. Credits are added only once the operator has confirmed the payment. TestTogether never asks for your PIN.

Credits cannot be withdrawn, converted into money or transferred between accounts. A confirmed purchase is not refundable, except for a processing error or a debit with no matching credits.

When a campaign opens, its budget is reserved; credits for unfilled places are returned when it closes, while those for reports under review or in dispute stay reserved until a decision is made. A recorded transaction is never deleted: any correction is made through an offsetting entry with a stated reason.

8. Partners and publishing

The “Profile reviewed by TestTogether” badge only means the team has checked the partner's file. It is not an Apple or Google certification.

The terms (publisher shown on the store, rights, duration, fees, revenue, maintenance, access, end of the collaboration) are agreed and accepted by the creator and the partner before any preparation. Any fees are settled directly between them: TestTogether does not collect them and is not a party to their agreement.

A partner who publishes from their own account is the publisher on the store and is responsible for complying with its rules. They can allow TestTogether to upload versions through the official API by inviting its service account in the Play Console, and revoke that access at any time.

A partner's agreement does not guarantee approval by a store. Store statuses are reported by the participants.

9. Prohibited conduct

Uploading malware, an app that collects data without its users' knowledge, or an app you do not hold the rights to.

Copying another member's report, creating multiple accounts, approving as a favour or colluding to obtain credits.

Asking for or sharing passwords, two-factor authentication codes, signing keys or real personal data.

Harassing, insulting or threatening a member; posting a review without a real collaboration.

Getting around store rules or promising approval.