I am Goktug Unver, founder of Croncode LLC. This is a refusal list. It exists so a founder does not spend a week discovering we will not ship their slide. What we do build is on a sibling page: what Croncode builds. How we ship from Istanbul is another: how we ship. The company is in Albuquerque. The product team is in Istanbul. We are not croncodetech.com.

Croncode will not build fake rankings, surveillance toys, clone UIs, or a listing that lies about the binary. A no is part of the studio, not a mood.

What store lies will we refuse?

• Fake #1 badges, invented download counts, bought review theater. Positioning without fiction: ASO playbook.
• A paywall that sells a job the binary cannot finish. Honest paywalls.
• Screenshots from Figma that the build does not match. Design QA.
• A thin MVP that is a website wrapper with no job. Too thin.

Our public jobs stay specific: YourStyle, Numira, Spylie, Luviport. Spylie is fiction. We will not build a real phone-spying product and call it a game.

What data work will we refuse?

1. Analytics that reconstruct a person’s week without a job. Analytics.
2. Personalization that feels like watching. Creep line.
3. Training on user photos or journals by default. Fail-safe AI.
4. No deletion path when you have accounts. Deletion.
5. Client bundle IDs in a personal Apple ID. Account ownership.

Security questions we expect you to ask: before you sign. Co-founder on design and web: Yusufhan Sokur. Team: Ozgur Ismet Ozkan.

When is a clone brief a no?

Feature discipline: feature creep. We are a lean studio, not a 40-person bench. Models.

What commercial shapes will we not pretend to run?

A fixed price with an infinite backlog. A retainer with no demo. A site that claims we are another company. Commercial: fixed price vs retainer. Site enough: Elementor. Identity: not croncodetech.com.

Push that lies about frequency: earn permission. Empty states that fake a feed: empty states.

How should you brief us if you still want a yes?

Send the job, the object, the not-now list, and the accounts. Quote packet. AI: AI brief. Hire path: hire the studio. Custom: custom software. Contact: contact. Home: /en/. Journal: /en/journel/.

Istanbul references should be real conversations, not logo walls: check references. Sprint demos must show a binary: sprint demo.

Why publish refusals in the Journal?

Because a studio that only lists capabilities will agree to anything in a first call. I would rather lose a week of pipeline than ship a listing I will not put my name under. Meet the people: meet the team. If you need a different model, that is fine. If you need us, come with a job.

Android as a badge: wait. Crash theater: ask for method. Support black holes: own an inbox. I will also refuse a brief that needs a biography we do not have. We will not invent a story for a teammate to win a pitch. Public names are enough. If you need a 40-person slide, you need a different company.

If you want a yes, bring a job a stranger can finish and a not-now list you will defend. I will still cut claims. That is the work. A studio that never says no will say yes to a listing I will not put next to YourStyle, Numira, Spylie, or Luviport.

Frequently asked questions

Is this a moral lecture?

It is an operating list. We still charge money. We still ship software. We will not ship a lie to do it.

Will you build Android?

As a scoped second train when the iOS job is real. Not as a store badge.

Will you take a project that is only WordPress?

If the job is a handoff site, yes. If you want us to pretend the site is the app, no.

Do you refuse all AI work?

No. We refuse AI as the product name when there is no object and no fallback.

Who else can say no?

Yusufhan Sokur can stop a visual lie. Engineering can stop an unsafe key. I can stop the contract.