Precedent & Fairness in Enforcement Rove is an intentional, safety-forward dating product. It is neither spammy, low-effort, nor duplicative — and yet we continue to face rejections under Guideline 4.3(b). This raises serious concerns about selective enforcement of App Store policy. In the past 60 days, Apple has approved a wide range of new dating apps, including: • Ready: Dating & Relationships – Launched June 3, 2025. Marketed as a native app for “intentional dating,” with a thematic approach directly comparable to Rove. • Meetline – Launched May 15, 2025. A transit-based connection app that limits conversations, just like Rove limits user visibility to avoid overload. • Yuzu – Asian Dating & Friends – A non-swipe app tailored to a specific community — proof that niche dating concepts are not inherently duplicative. • Metya / DateGuard – Two safety-first apps that use community filters and moderation-centric design. These are directionally aligned with Rove’s own innovation in safety and moderation systems. These approvals confirm that Apple is actively supporting innovation in the dating space — especially when apps prioritize safety, intentionality, and community design. Rove deserves to be judged by the same standard. If the guideline is being interpreted inconsistently, then it becomes impossible to innovate without fearing an opaque and biased review process. Selective Enforcement Harms Developers and Innovation As developers and builders, we deserve clarity and consistency — not arbitrary gatekeeping. Apple’s selective enforcement of Guideline 4.3(b) is not just frustrating; it’s damaging. It chills innovation, punishes intentional design, and undermines trust in the App Store as a fair marketplace. Rove is a serious, safety-driven product built from the ground up. Watching Apple greenlight a wave of similar or less-innovative apps — while rejecting ours without clear reasoning — signals that the rules are not applied evenly. We are actively researching internal contacts and press avenues to bring visibility to this issue. Because what’s happening here isn’t just wrong for us — it’s wrong for every indie developer building with integrity.