Mistake number twelve in the "Early-Stage Mistakes" series: I did not understand the platform's policies before using my account.
A Simple Request from Online Clients
Let me tell you about something that happened to us in early April 2026. It was one of the hardest experiences our company has been through, and we are still living with its effects today.
Some clients needed to publish their mobile apps on Google Play, and they asked us to upload them to our company's developer account to speed up the review and publishing process.
We did not know these clients personally; everything happened online. Most importantly, we did not know that their original accounts had policy violations.
I agreed in good faith, without realising that moving apps over from other accounts could expose our own account to the consequences of the violations attached to them.
Closed for Good, and Banned
The result was the permanent closure of the company's developer account, and a ban on creating a new one.
The worst part: that account had existed since 2017, which makes it older than the company itself. It also held our own apps, and they were hit by the decision too.
We tried everything to prove our good faith and sent every piece of evidence and explanation showing we had no part in those violations, but the decision stood.
An account we built and protected for years, lost because of one decision whose consequences we did not study properly.
What I Learned
- It is not about code. Nor is it just a technical detail; the decision was legal and commercial before it was technical.
- Secure every third-party arrangement. It must be legally protected and comply with the policies of the platform you work through.
- Understand your liability before you agree. Know how any violation or problem on the client's side can come back to you and your company.
The Bottom Line
Being confident in your own work is not enough. You also need to understand and secure every relationship you operate through.
That was mistake number twelve, and one of the most expensive lessons we have learned at Darory.
Have you ever made a good-faith decision that cost you far more than you expected?
Want to Skip These Mistakes?
If you are building a business or a system from scratch and want to avoid these mistakes from day one, talk to us directly.
Message us on WhatsAppLearn more about Alaa Samir, founder of Darory, or send us a message.
The Early-Stage Mistakes Series
- Episode 1: Hiring Before the Work Is Stable: The Most Expensive Mistake of My Early Days
- Episode 2: Polishing One Part While the Whole Project Waits
- Episode 3: "A Technical Fault": The Vague Answer That Almost Cost Us Our Clients
- Episode 4: No Real Rest for the Founder: When Breakdowns Come at the Worst Time
- Episode 5: Taking the Client's Word for It: Why Every Stage Needs a Written Approval
- Episode 6: More Features, Better System? The Mistake of Building Everything the Client Never Needed
- Episode 7: One Post Took Down the Whole Server: Hosting Clients Without an Off-Site Backup
- Episode 9: I Cared About the Code and Forgot the User: Why UI and UX Are Not a Finishing Touch
- Episode 10: The Carpenter's Door Hangs Loose: Why a Software Company's Own Website Must Keep Evolving
- Episode 11: Too Simple to Share? Why the Knowledge You Take for Granted Is Someone Else's Shortcut
- Episode 12: A Developer Account Since 2017, Closed by One Decision: Understand the Platform's Policies Before You Agree