IFMachine

Content policy

Effective date: 2026-06-03
Last updated: 2026-06-03

IFMachine is an Android app for playing interactive-fiction games, published by Guppy Interactive LLC ("we", "us"). In addition to the games we suggest directly in the app, IFMachine lets you search the Interactive Fiction Database (IFDB) and download story files written and published by third parties. This policy explains what content is not allowed, how to report content you find objectionable, and what we do when you report it.

The short version: IFMachine is a reader, not a host. The stories you search for and download are created by other people and stored on IFDB and the archives it links to, not on any server we operate. We do not write, rate, or pre-screen that catalogue. But because the app gives you access to it, we provide a way to report objectionable content, we drop reported and reviewed content from IFMachine's own search results and suggestions, and we keep the catalogue behind an age screen. We can't delete files from IFDB or stop a story you've already downloaded from running — what we control is what IFMachine surfaces to you.

1. Scope

The prohibited-content standards in §2 apply to everything IFMachine surfaces — the stories and catalogue metadata (titles, descriptions, author names, cover art) it retrieves from IFDB and third-party archives when you search or download, and the small set of games IFMachine suggests directly. The in-app reporting and moderation procedures in §§4–5 are aimed at the third-party IFDB and Archive content, since that is the open, community-authored material we do not control and cannot review in advance. This policy does not cover files you load from your own device.

2. Prohibited content

The following are not permitted in IFMachine's own search results and suggestions. We do not host the story files and cannot block a story you have already downloaded or imported from running; what we control is what the app surfaces to you, and we will remove or suppress content that, in our judgement, falls into these categories from search and suggestions when we become aware of it:

3. Mature content and the age screen

Interactive fiction is a literary medium, and much of it — including acknowledged classics — deals seriously with violence, death, sexuality, addiction, abuse, and other difficult subjects. The presence of a mature theme does not, by itself, make a story objectionable under this policy. The distinction we draw is between mature subject matter treated as part of a work, and the prohibited content listed in §2.

Because the IFDB catalogue is open and not moderated by us, it can include stories written for adults. To keep that content away from children and from anyone who has not chosen to see it, the IFDB browser — both the search and the suggested-stories list — is kept behind an age screen and hidden by default. The first time you open the browser you enter your year of birth and confirm that you understand the catalogue is unmoderated and may contain mature content; the browser stays locked until you do, and remains unavailable if you are under 18. Your year of birth is stored on your device only and is never transmitted (see the privacy policy §7). Stories already in your library and files you import yourself are not gated.

On top of the age screen, explicit sexual content is hidden by default. IFMachine's IFDB search excludes stories the community has tagged as pornographic, erotic, or otherwise sexually explicit; to include them you have to deliberately turn the filter off under Settings → Content (a switch plus a confirmation — two separate actions). Because IFDB's tags are community-sourced and incomplete, this is best-effort: an untagged explicit story can still slip through, which is exactly why the catalogue also sits behind the age screen and why the reporting and blocklist tools in §§4–5 exist. We do not claim to filter perfectly. We do not permit content that sexualises minors. We cannot screen the unmoderated catalogue before such content is identified; once we do identify it (by report or otherwise) we hide it for the reporter immediately and add it to the non-reversible shipped blocklist as quickly as we can, and once that update is installed it is dropped from search and suggestions and can never be switched back on. The urgent handling in §5 covers the rest.

4. How to report objectionable content

You can report a story two ways:

If the content involves the sexual abuse or exploitation of children, please say so explicitly so we can prioritise it. You can also report such content directly to the National Center for Missing & Exploited Children at report.cybertip.org or, outside the United States, to your local authorities.

5. What we do with a report

When you report a story from inside the app:

When we review a report:

Because interactive fiction legitimately contains mature themes (§3), review of non-CSAE reports involves human judgement; we will not necessarily remove a story simply because it deals with difficult subject matter. We aim to act on reports promptly.

6. Copyright and takedown requests

This policy is about objectionable content. Copyright complaints, DMCA notices, and other takedown requests should instead be sent to legal@guppyinteractive.com. Note that story files are hosted by IFDB and the archives it links to; rights holders may also wish to contact those hosts directly.

7. Changes to this policy

If we change this policy, we'll update the "Last updated" date at the top and publish the new version at this URL.

8. Contact

To report content, or with questions about this policy:

moderation@guppyinteractive.com

Guppy Interactive LLC
10938 Vivaracho Way
San Diego, CA 92124
United States