Back to GeoQuiz
πŸ’¬ Support center

Get help without the runaround.

Questions about your progress, a subscription, syncing or anything else GeoQuiz-related β€” we handle support by email and try to respond within a couple of working days.

Write to support

Email is the fastest way to reach us. Please include the Apple ID email you bought your subscription with (if relevant) and a short description of the issue.

Specific guidance by issue type

To help us answer faster, include the details below depending on what you’re writing about.

πŸ’³ Billing & subscriptions

Mention whether your purchase came through the Apple App Store and the plan you have (monthly, quarterly or yearly). We can’t issue refunds ourselves β€” they’re handled by Apple, but we can guide you through it.

πŸ”„ Progress & sync

GeoQuiz stores progress on your device. If your XP, streak or Journey progress is missing, include your device model, iOS version and the last action you took before the issue appeared.

πŸ› Bug reports

Describe what you were doing, what you expected and what actually happened. A screenshot or short screen recording helps a lot. Include the app version (Settings → About).

πŸ—ΊοΈ Content corrections

If a country, capital, flag or fact looks wrong, tell us which country and what the correct value should be. We update content regularly.

Before you write

A few small things that usually speed up the conversation:

  • 1
    Describe the issue concisely. One paragraph with what you tried and what went wrong is more useful than a long backstory.
  • 2
    Attach screenshots only when they clarify the issue. A picture of the wrong screen helps; a picture of the home screen rarely does.
  • 3
    Specify your device and iOS version. e.g. “iPhone 13, iOS 18.2”. Some bugs only show up on certain combinations.
  • 4
    Note whether you’re on the free tier or Premium. Some features (ads, all Journey stages) behave differently.

Useful links

Many common questions about data, subscriptions and account removal are already answered in our policy pages: