How can we help?

Accounts are created in the Android app, with an email address, a display name and a password. There is no separate website signup: the website explains the platform, and the app is where an account lives.

The email on your account is how the platform intends to reach you — about your account, and about anything that needs confirming. Verification itself is not available yet: the platform cannot send email, so there is no message to click and no way to prove the address. Until that is in place the account simply holds the address you registered with, and nothing on the platform claims an address has been proven when it has not.

There is no self-service reset yet, because a reset needs to send you a link and the platform cannot send email. If you are still signed in on a device, stay signed in — the session is not affected by the password. If you are not, write to support and state the address on the account; recovery is handled by a person until the automated flow exists.

Open the earning screen, choose an opportunity and follow the steps on its detail page. Each opportunity states what it asks for and what it pays before you start it.

An opportunity is refused when the requirements on its detail page were not met — the activity was not completed, it was completed outside the window, or the proof the partner checked did not match. The refusal is recorded on the opportunity itself, and a refused opportunity cannot be resubmitted.

A reward is held until the activity behind it is confirmed, and confirmation is the partner’s to give. While it is pending it is visible in your wallet but not spendable and not part of what you can withdraw. This is deliberate: pending money is never counted as earned, so a reward that fails to confirm never has to be taken back out of a balance.

Check the opportunity’s own status first: a completion that is still being verified shows as pending, and one that did not meet the requirements shows as refused with its reason. If the opportunity shows completed and confirmed but nothing arrived, the reward will be in your reward history — a confirmed reward appears there against the activity that produced it.

AK Coin is the platform’s own rewards unit. It records what you have earned on the platform and it can be moved through the payout methods the platform supports. It is not a cryptocurrency, not a security, and not an investment — nothing here appreciates, and holding it earns nothing.

In the wallet in the app, which separates available, pending and withdrawn balances rather than showing one number. The available balance is the part that can be paid out; pending is money still being confirmed.

Because the confirmation has not arrived. Rewards become spendable when the activity is confirmed, and the platform does not advance one on a timer — a pending reward that never confirms is possible, and it is why pending money is never shown as earned.

XP records how much you have taken part: completing opportunities, keeping a daily streak, and other activity the platform awards it for. It moves you up the platform’s levels as it accumulates.

Each level has a threshold of XP, and reaching it moves you up. The levels page lists the thresholds and what each one unlocks.

No. XP is not money and does not convert into any. It is a record of participation, and it is deliberately kept apart from the balance that can be paid out — the two are shown separately everywhere they appear for that reason.

Your invitation link carries your referral code. Opening it on a phone with the app installed hands the code to the app, which carries it into signup; opening it without the app shows the invitation on this website, with the code, so it can be entered in the app when you install it. Either way the code is applied to the new account when it is created.

When the person you invited completes the activity the referral programme treats as qualifying. Joining is not qualifying: an invitation on its own earns nothing, which is the rule the whole programme turns on.

The referral list shows where each invitation stands — invited, pending qualification, qualified, or unqualified — so the first place to look is the row for that person. A referral that is still pending has not qualified yet; an unqualified one did not meet the requirement. A qualified referral whose reward is still being confirmed shows as pending rather than confirmed.

No. An invitation has to be for a different person: a referral attributes one account to another, and an account cannot be its own inviter. The platform checks this when the referral is applied, not only in the interface.

Open the earning screen and claim the day’s reward. Each claim moves the streak forward one day, and the streak is what the platform awards more for.

The streak ends and starts again at the next claim. The days you already claimed are not affected — a streak is a count of consecutive days, not a total, so nothing you have already earned is taken back.

Tickets are earned by taking part — the daily check-in and other platform activity grant them — and each spin spends one. There is a daily limit on how many are granted and a cap on how many can be held at once, so tickets are not something to accumulate indefinitely. The app shows both before you spin.

The prize is chosen by the server from the wheel’s current prize table, with each prize’s odds set by that table, and the result is recorded against the spin. The client never decides a result — it asks and displays the answer.

Either the day’s grant was already made and the daily limit has been reached, or you are at the balance cap and there is no room for another. Both limits come from the platform’s configuration, and both are visible in the app before you try.

Choose a payout method in the app, provide the destination details that method needs, and confirm the request. The method’s own requirements — including the minimum and any fee — are shown before you submit, because they belong to the method rather than to the site.

A submitted request is reviewed and processed, and the balance stays reserved while that happens — reserved is held for the request, not gone. The request’s status in the app is the authority on where it has got to.

Commonly because the destination details are wrong or the method does not accept them, and sometimes because a verification requirement has not been met yet. When a request fails, the reserved amount is released back to the available balance rather than lost.

Each payout method carries its own minimum and, where the platform charges one, its own fee. They are configuration rather than a fixed rule, so the platform shows them on the method itself, before a request is submitted, instead of publishing a number here that could be out of date.

From the download page on this site, which is the only place the platform’s build is published. The page states the current version and its checksum so you can confirm the file you received is the one that was published.

Download it, open it from your notifications or your Downloads folder, and allow the install when Android asks — Android asks once because the app does not come from a store. The download page walks through the same steps with a little more detail.

The download page states the minimum Android version the current build requires, which is the app’s own requirement and is shown there rather than repeated here.

Open Profile → Security → Active sessions and sign out every device except the one you are holding. That removes access that has already been established, and it is the action the platform supports today. Changing the password is not yet available in the app — it depends on the same email capability that verification does — so if you believe the account is being used by somebody else, do the sign-out first and then contact support.

Only from this website. Nobody from the platform will send you an APK by message, and a copy from anywhere else cannot be checked against the checksum published on the download page.