Work policy
Prohibited apps
We do not build illegal apps or apps that are incompatible with our way of working. Examples include, but are not limited to, gambling, dating or open chat, misleading or fake-profit content, unlicensed trading or investment, and extremist or illegal apps.
Vague requests are not accepted
We do not accept vague requests such as “build me an app like that one” without clear, implementable requirements covering screens, features, roles and workflows.
The client provides the brand identity
The client provides the brand identity, including the logo, colours, fonts and visual style, as a project requirement. We apply it within the design.
The final requirements document is the reference
We document all requirements and the total cost. Any additional requirement or later change outside the final agreed document requires a new agreement.
Design changes within reasonable limits
We follow an agreed visual system based on the supplied brand identity. Design and branding changes are accepted within reasonable limits.
Milestone-based payments
Work is divided into milestones, with clear payment checkpoints set out in the agreement to protect both parties.
Available payment methods
Available payment methods include PayPal and international transfers through Western Union, Ria, MoneyGram and UPT. Options may be updated when alternatives become available.
Existing projects developed by third parties
We do not continue projects developed by third parties unless the scope is clear and limited, with documentation of the technologies, architecture and databases to avoid wasted time.
Store accounts and publishing ownership
For publishing on Google Play and App Store, the client must provide their store accounts for the final handover and full transfer of ownership. If accounts are unavailable, we may publish temporarily through our accounts, subject to availability. Our accounts remain our property; publishing updates or new versions developed by another party requires a new agreement.
Delivery and responsibility
After testing and verification, the final handover includes the source code, diagrams, documentation and any project-related accounts, where applicable. We are not responsible for misuse after delivery.
Our workflow is fixed
We follow our own workflow across all projects. We do not accept requirements that impose an incompatible process at the beginning, during implementation or at the end of a project.
Paid operational services
The client provides and covers services that require billing, such as Google Maps, SMS/OTP verification, AI services, hosting and cloud storage.
Operations, maintenance and follow-up contracts
We provide maintenance, operations and follow-up contracts for the projects we deliver. Due to the nature of the work and scheduling constraints, we may choose not to sign an operations contract for some projects. This is communicated clearly during implementation. Every delivered project includes our workflow, implementation plan and explanations for each stage.
Policy updates
We update our work policy periodically.