Help & FAQ

The name is short for Fear Of Missing Anything: a play on FOMO, the fear of missing out on whatever everyone else is doing. This is the other half of that: the handful of things you actually care about, and hearing about them before they happen rather than after.

FOMA currently tracks six areas: TV releases, movie releases, sports (including motorsport), game releases, esports matches, and rocket launches. You can set an alert on a single thing, or create one that filters across a whole category.

The catalogue is assembled from specialist third-party event sources. Categories and coverage can grow, but Help describes only the six categories available now.

You can browse categories, search for entities, open event pages, try templates, build filters, and preview matching events without creating an account.

An account is required when you create an alert. It also lets FOMA carry your alerts and account preferences between signed-in devices.

A one-tap alert is the quickest path. Search for a team, game, show, person, company, venue, competition, or launch-related entity and choose Alert me on its page.

Representative alerts include Arsenal matches, new films featuring an actor, releases from a game company, episodes of a show, Formula 1 races, or SpaceX launches. These are examples, not buttons or preselected alerts.

FOMA prepares a filter around that stable entity. You can preview it and change its name, reminder times, channels, and supported triggers before creating it.

A template is a prefilled alert for a common use case. Open one, inspect the filters and current preview, then keep or edit it before creating it.

Create from scratch starts with the advanced builder. It is useful when you want several conditions, such as a platform plus genre plus date window, rather than one simple one-tap alert.

One-tap alerts, templates, and Create from scratch all lead to the same review-and-create flow. None of the examples on this Help page creates an alert.

• Reminders fire at the lead times you selected before an event's resolved date.
• New matching events can notify you when an event first matches the saved alert, including an announcement whose final date is not known yet.
• Tracked changes can notify you when supported fields such as an event date or status change.

New-match and change triggers can be turned on or off per alert. The exact tracked fields depend on the event category. FOMA does not treat every source edit as a user-visible change.

An alert can carry up to five reminder times, from 15 minutes to one month before an event. A rolling date window can limit which longer reminder choices are usable, because a reminder cannot fire before the event enters that alert's window.

Push and in-app delivery are available on Free and Pro. Email delivery is available on Pro.

Creating an alert does not silently grant push permission. FOMA shows its own explanation first, and the browser or device permission prompt appears only after you opt in. In-app notifications remain available in the Inbox.

Push notifications pass through several layers before they reach you: the app, the browser or operating system permission, a delivery service, and finally your device's own notification settings. Any one of them can stop a notification without the others noticing. The fastest way to find out which is Settings → Notifications → Check this device, which runs the same checks the app runs when you turn notifications on and shows a tick or a cross beside each one.

Whatever the cause, your alerts are never lost. Everything FOMA sends you is also in Inbox, so nothing goes missing while a device is being fixed.

Start here, on any device

• Notifications are off on this device. Settings → Notifications shows a Turn on button. Each browser, phone and computer registers separately, so turning them on for your laptop does nothing for your phone.
• You are signed into a different account. Registrations belong to the account that made them. Check the address under Settings → Account.
• You said Not now earlier. FOMA asks once, automatically, after your first alert. After that it stops asking, and Turn on in Settings is how you change your mind.

If your browser is blocking notifications

If you chose Block on the browser prompt (or clicked it away more than once), the browser stops asking and FOMA cannot re-prompt. You have to allow it yourself, and the app cannot do it for you. Settings will say so explicitly rather than offering a button that could not work.

• Chrome, Edge, Brave and Arc (desktop): click the icon at the left of the address bar, set Notifications to Allow, then reload the page.
• Safari (macOS): Safari → Settings → Websites → Notifications, find the FOMA address, set it to Allow.
• Firefox: click the padlock in the address bar → Connection secure → More information → Permissions, then clear the block on Receive Notifications.
• Chrome on Android: tap the icon left of the address bar → Permissions → Notifications → Allow.

Reload the page after changing it. A permission granted in browser settings does not apply to a page that is already open, and FOMA cannot register the device until it does.

If the browser says notifications are allowed and nothing still arrives

This is the case that confuses people most, and it is worth knowing that the app genuinely cannot see it. Your operating system has its own notification switch, separate from the browser's. When it is off, the browser still reports that you granted permission, so every check in the app passes, and nothing is displayed.

• macOS: System Settings → Notifications → find your browser (Chrome, Safari, …) → Allow notifications. Also check Do Not Disturb and any Focus mode.
• Windows: Settings → System → Notifications → find your browser, and check Focus assist.
• Android: Settings → Apps → your browser → Notifications. Check Do Not Disturb, and any battery-saver or Data Saver mode, which can delay or drop background delivery.
• iPhone and iPad: Settings → Notifications → the app → Allow Notifications. Check Focus modes too.

On iPhone and iPad, the site must be installed first

Apple only allows web notifications for a site added to the Home Screen. In an ordinary Safari tab there is no permission to grant, and FOMA will show installation instructions instead of a Turn on button. Open the Share menu, choose Add to Home Screen, then open FOMA from the icon and turn notifications on there.

If an ad blocker, privacy extension or private DNS is in the way

Turning notifications on needs FOMA to register a small background script in your browser, and some privacy tools stop that. When they do, Check this device fails on *Our notification service is reachable*, and the fix is to allow this site in whatever is blocking it, or open FOMA in an ordinary window with extensions off. A browser set to block site data does the same thing.

There is one part we do not control. Your browser delivers notifications through its own service (Google's for Chrome, Mozilla's for Firefox, Apple's for Safari) and a corporate network or a strict DNS filter can block that separately. It looks different: Check this device passes every row, and notifications still never arrive. There is no single address to allow, because it differs per browser, so this one is worth taking to whoever manages the network. On a personal device, a different browser is the quicker test.

If you cleared your browsing data

Clearing cookies and site data removes this device's registration, so notifications stop until you turn them on again. You may briefly see the same computer listed twice under Notification locations. The old entry is a registration that no longer exists. FOMA retires it automatically. You can also remove it yourself.

If it works on one device and not another

That is expected. Every browser and device registers on its own, and each appears separately under Notification locations. A phone with notifications working tells you nothing about a laptop that does not. Turn them on once per device you want notified.

Still stuck

Send feedback from Settings and say which device and browser you are using, and which line of Check this device shows a cross. That single detail is usually enough to identify the cause without any back and forth.

Some dates are exact times. Others are day-only or estimated dates supplied by the source. Releases, fixtures, races, and launches can be postponed, cancelled, or corrected after FOMA first sees them.

An event can be missing because a source does not cover it, has not published it yet, or has not been ingested and normalised successfully. Search wording and filters can also exclude an otherwise known event.

Notification delivery also depends on a live registered device, permission, connectivity, quota, and the delivery provider. FOMA is a convenience tool, not the sole source for time-critical decisions.

If a date or event looks wrong, open the feedback dialog from the app footer or Settings, or use the public Feedback page linked from Help. Include enough detail to identify it. An event link is more useful than private account information.

Free includes 3 enabled alerts, 5 push notifications per calendar month, no ordinary event emails, and unlimited in-app notifications. Settings and Billing show your current usage and reset timing.

Pro includes unlimited alerts, 1000 push notifications and 50 emails per Stripe billing period, and unlimited in-app notifications. An account with included Pro access uses a calendar-month allowance instead. Ultimate is coming soon and cannot be purchased. Check Billing for the current price and terms.

Push and email are counted separately. Sending one event notification to several devices costs one push unit. Notifications sent or being sent count toward usage. Quota notices do not. Reaching an external limit does not stop your in-app notifications. If you cancel Pro, choose which alerts to keep in Alerts. Extra alerts pause without being deleted and can return when you upgrade.

Language, country, and timezone

FOMA starts from your device language and timezone. A signed-in choice in Settings follows your account across devices. Country and timezone help choose local dates and sensible reminder times.

Event-type interests

First-run event-type interests order discovery surfaces and choose a useful blank-builder default. They do not create alerts or notifications. Anonymous choices stay in local browser storage. After sign-in, account interests sync across devices.

Registered devices

Settings lists devices registered for push and their receiving state. You can remove a device there. Permission may still need to be changed in that browser or operating system.

Open Alerts to see saved alerts. The switch pauses or resumes an alert without deleting its filters. Edit changes its filters, reminders, channels, or supported triggers. Delete removes it.

An alert detail page can send a test push when a receiving device is registered. Tests are rate-limited and report when no device, permission, or subscription is available.

Signed-in users can open the Inbox from the app navigation to review sent in-app notifications and their delivery state.

Use Forgot password on sign-in, or Change password in Settings, to request a reset link. Sign out also lives in Settings.

A signed-in account can produce a JSON export of its account record, alerts, notifications, registered-device metadata, audit history, onboarding preferences, and submitted feedback. The current web UI does not yet expose the export control. Use Feedback if you need help accessing it.

Delete account is in the Settings danger zone and asks for confirmation. It removes or anonymises personal data as described in the Privacy Policy. Deletion cannot be undone from the app.

Use the public Feedback page linked from Help. In the app, the footer and Settings open the feedback dialog in place. You can report a bug, confusing flow, idea, praise, or event-data correction. Anonymous feedback can include an optional reply address. FOMA does not claim an unconfigured support mailbox here.

Read the Privacy Policy for what FOMA collects and how account deletion works. On this marketing site, open the Cookie Policy and select Cookie settings to grant or withdraw optional analytics consent. The app has its own Cookie settings control for its analytics consent.

Avoid putting passwords, payment details, or other secrets in feedback. For a wrong event, its title and link are normally enough.