Frequently asked questions

Send the project enquiry with the goal, audience, scope, timing, and approximate budget. The team reviews fit, then proposes the next step when the enquiry matches the studio services.

No. A description of the problem, user, and intended outcome is enough. Constraints, timing, and budget help us suggest a suitable starting point.

Cost depends on scope, platforms, content volume, integrations, quality target, and schedule. Cup Code provides an estimate after understanding requirements, assumptions, and risk.

Timing varies with scope, dependencies, and decision speed. We divide work into stages with deliverables and review points, then confirm the schedule before delivery starts.

Yes. A prototype tests a defined question, such as core-loop appeal, movement, performance, or player understanding, then ends with a proceed, revise, or redirect decision.

The team selects platforms after reviewing audience, requirements, and budget. Work includes web, mobile, and game platforms suited to the project scope.

This starts with technical and UX assessment plus a review of rights, access, and documentation. We then outline risk and a suitable scope before any commitment.

Yes, under an agreed plan covering response timing, issue handling, security updates, monitoring, and planned improvements.

Priority reflects impact, affected users, function importance, workaround availability, and support plan. The team may adjust priority after reviewing the evidence.

Choose critical for a complete outage of an essential service or confirmed data loss. The form requires impact, timing, and scope. Slowness or a secondary feature issue is not normally critical.

Use the secure tracking link shown after submission. Keep it private because it grants access to ticket details.

No. Voting shows interest, while decisions also reflect impact, fit, effort, risk, and dependencies. The suggestion status shows the latest known decision.

Suggestions are public to read. Posting and selected voting actions require a verified account to protect the community and reduce abuse.

Open a ticket under Data deletion request using the account email and identify the product and request scope. The team verifies identity, then explains what was deleted and any record retained for legal reasons.

Yes. Use Cookie preferences to reject optional analytics and preferences. Necessary storage stays active for sessions, security, and language.

Use the dedicated security report. Include the asset, impact, and safe verification steps. Avoid service disruption, access to other people’s data, or disclosure before remediation.

Yes. Arabic is the primary right-to-left language, and English uses left-to-right layout. The language switcher keeps the current page where a matching version exists.

Use the technical issue form and include page, task, device, assistive technology, and blocked step. The team prioritizes the report based on impact on task completion.