Cómo funciona
Nothing here is magic, and none of it is hidden from you. This is the whole process, including the parts where you have to do something.
1. You tell us who you are
We verify your business before anything is published. That is not bureaucracy for its own sake: every store requires the developer account to belong to a verified legal entity, and publishing an app for somebody we cannot identify is how a platform becomes a vehicle for fraud. You upload your registration document and an identity document for a director. A person reads them, usually within a day.
Those documents are deleted once verification is settled and the retention period runs out. They are never shown to anyone outside the two people whose job it is.
2. Your store accounts, in your name
For each channel, the developer account is registered to your company. We are added as a user on it under a written mandate, with the narrowest rights that let us do the work. We never become the account owner.
This is the single most important thing about how Retoxy works, and it is not a preference. Apple's review guideline 4.2.6 rejects apps submitted on a client's behalf by a service. Google's distribution agreement requires a developer to act on its own behalf. Beyond the rules, an agency account holding a hundred clients' apps is a single point of termination for all of them.
The consequence you should care about: if you leave, you keep the account, the listing, the reviews, the ratings and the users. There is nothing to migrate because nothing was ever ours.
3. The submission wizard
You upload a build and write the listing once. We derive the per-store variants, resize the assets, and run every automated check before anything is submitted: whether the privacy policy is reachable without a login, whether the target API level still meets Play's floor, whether the data-safety form matches what the build actually sends, whether a reviewer can get past your sign-in screen.
Checks that would get you rejected block the submission. Checks that are a judgement call warn you and let you proceed. We do not pretend a warning is a failure, because that teaches people to click past both.
4. Our review, before any store sees it
A Retoxy reviewer reads the app and the listing before it is submitted anywhere. A rejection from a store costs you days and counts against your account; a note from us costs you an hour. Nothing reaches a store without this step — it is enforced in the database, not just in the code.
5. Submission, tracking and rejections
We submit to every channel you chose, each at its own pace. The release tracker shows where each one is. When a store rejects something, you get the store's own wording plus what it means and the steps to fix it, rather than a guideline number and a shrug.
6. Staying published
This is most of the work. We watch the policy pages each store actually enforces and tell you when one changes and whether it affects you. We track every certificate, key and account fee that can expire and remind you before it does, not after. We stage rollouts where the store supports it and halt one automatically if crashes jump. We reply to store reviews in your voice if you want us to.
7. Getting paid
Payments go from your customer to your own account at the payment provider. Our share is split off by the provider at the moment of capture. We are never a party to the money, so there is no balance of yours in our hands — not a policy, a structural fact, and the reason this platform needs no money-transmission licence to operate.
You get a double-entry ledger, tax-invoice records and a full history. Refunds and chargebacks are modelled properly, including the part where the provider keeps its fee on a refund and we absorb it rather than passing it to you.
What you still have to do
- Own a registered business, or register one. We cannot do that for you.
- Pay the stores their own developer fees, on your own accounts.
- Publish a privacy policy that is true of your app.
- Answer the age-rating and data-safety questions honestly — we can tell you what they mean, but only you know what your app does.
- Keep a demo account working for the reviewers, if your app needs a sign-in.
See which channels we cover and what each one's policy says, or read what we hold and what happens if you leave.