Help & FAQ
How browsing, follows, alerts, notifications, preferences, and account controls work.
Zuletzt aktualisiert: 25. Juli 2026
FOMA helps you keep track of events without watching every feed yourself. Browse first, then save only the alerts you want. These answers describe the product as it works today; event coverage and delivery still depend on the sources and devices involved.
What is FOMA, and what can I follow? Kurz gesagt FOMA matches the event filters you save against incoming event data, then notifies you about the matches you chose.
FOMA currently tracks TV releases, movie releases, sports matches, game releases, motorsport races, esports matches, and rocket launches. You can follow a single thing or build a filter across a whole category.
The catalogue is assembled from specialist third-party event sources. Categories and coverage can grow, but Help describes only the seven categories available now.
Can I browse without an account? Kurz gesagt Yes. Browsing, search, event pages, and alert previews work before sign-up.
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 save an alert. It also lets FOMA carry your alerts and account preferences between signed-in devices.
How do I follow one thing? Kurz gesagt Search for it, open its page, choose Follow, review the alert, and save it.
Simple follows are the quickest path. Search for a team, game, show, person, company, venue, competition, or launch-related entity and choose Follow on its page.
Representative follows 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 saving.
What are templates and Build from scratch? Kurz gesagt Templates start with a useful filter; Build from scratch gives you the category's full filter controls.
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 saving.
Build 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 follow.
Following, templates, and Build from scratch all lead to the same review-and-save flow. None of the examples on this Help page creates an alert.
What can trigger an alert? Kurz gesagt Reminders, newly matching events, and supported changes to events you already match.
- 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.
How do notifications and reminders work? Kurz gesagt Choose one or more reminder times and at least one available channel; push needs separate device permission.
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 today. Email is displayed as a Pro option but is not currently selectable, so do not rely on email delivery.
Saving 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 notification history.
Why do dates change or events go missing? Kurz gesagt Event data comes from external sources, and estimated or announced dates can move, arrive late, or be incomplete.
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.
What do the plans and limits include? Kurz gesagt The app shows your current usage and limits; current price and availability appear before any checkout.
The Free plan currently includes 3 saved alerts and 5 notifications per month. The app shows usage against those limits.
Pro removes the saved-alert and monthly-notification caps. Check the current pricing section and the in-app Billing page for the live price, availability, and checkout terms; this Help page does not invent or freeze a price.
A notification limit counts delivery moments, not devices. Sending the same moment to several registered devices does not multiply that moment's quota cost.
How do language, timezone, interests, and devices work? Kurz gesagt Settings controls account preferences and registered devices; anonymous interest choices stay in that browser.
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.
How do I manage my alerts? Kurz gesagt My alerts lets you edit, pause, resume, test, or delete an alert.
Open My 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 notification history from the app navigation to review sent in-app notifications and their delivery state.
How do I reset, export, or delete my account? Kurz gesagt Reset your password from sign-in or Settings; sign out and delete the account from Settings; account data can be exported as JSON.
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.
How do I send feedback and manage privacy? Kurz gesagt Use the public Feedback page for questions and corrections; use Privacy and Cookie settings for data and analytics choices.
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.