This marketing site
This version of the PFFT marketing site has no analytics client, advertising scripts, account sign-in or contact form. It does not write cookies or persistent browser storage. Fonts and artwork are served with the site.
Requests to a website or its current-day endpoint expose technical information to the serving infrastructure, including an IP address, user agent and requested URL.
A Party join link can contain the host’s local-network address and room code. These appear in the URL sent to the website and in the browser’s history, and may appear in infrastructure logs. Share room links only with the people you intend to join. The current-day endpoint serves challenge identifiers; its implementation does not create player accounts or store gameplay submissions.
Playing in the same room
Party hosts a room on your local network. Controller and Daily’s Join Party feature use that connection to send the player name you choose, player/session identifiers, readiness and game actions. Depending on the game, the room exchanges answers, guesses, drawings, selected map pins and scores with the host and other players. Private prompts and submissions are shown or revealed according to the game.
Local Network access is used to discover and connect to the host. The controller saves its chosen player name, player identifier, reconnection token and letter-input preference in the app’s local storage. Use a name you are comfortable showing to everyone in the room. The current Party gameplay implementation does not upload the room’s names, typed answers or drawings to a gameplay cloud service.
Results on your device
Daily keeps challenge history and results in local app storage. Those records can include the day, game and puzzle identifier, submitted answer, result details, success, score and distance from a game-location target. Local preferences and cached game-location names are also stored where the relevant features use them.
Sharing a Daily result creates an image in the app’s cache and opens Apple’s sharing tools. The destination you select receives the content you share and handles it under its own practices. The planned server-day integration is not yet installed in the native apps; this notice does not imply that a production daily-results server exists.
Usage and result information
The current Party, Daily and Controller apps are configured to send usage events to Stactics at api.stactics.io. Each app installation generates and saves a random identifier that persists across launches. The identifier is scoped by app and platform and is sent in the analytics user/device identifier fields. It is not a player name or email address, but it lets the service associate events with an installation.
Events include app activation; Daily challenge starts and completions; Party game starts, round reveals and completions; and controller round participation. They include timestamps, event and round identifiers where relevant, app/platform/device category and build information. Daily completion events include the game, puzzle/day, success and score; Letters includes word length and Where Are You includes distance from the target. Host events also include player and round counts.
The PFFT analytics payload does not include player names, email addresses, room codes, typed answers, drawings or selected map coordinates. It records result measurements such as score and distance. These events support measurement of app use, participation and challenge completion/difficulty.
Stactics ingestion separately stores the request IP address and user agent with events and installation records, and creates a project-scoped fingerprint digest. Its inspected backend can derive approximate country, region, city and network/provider information from IP addresses using server-side lookup data. IP-derived location can be inaccurate and is separate from a game’s map guess or the device’s GPS position.
The native client keeps a bounded local delivery queue and retries when sending fails. PFFT does not offer an analytics opt-out. Removing app data or changing the installation identifier is not an opt-out. Their Apple privacy manifest declares identifiers and product interaction for analytics, with advertising/cross-company tracking marked off. That declaration does not mean no data is collected.
Other services involved
Stactics receives the native usage data described above. The inspected IP lookup runs against server-side databases rather than sending each event IP to a separate lookup API.
Party can use Apple’s reverse-geocoding service to label a game location. That request uses the game target’s coordinates. The inspected code does not request the player’s GPS location for this feature. The current map presentation uses bundled map data. Apple’s sharing tools and any sharing destination process a result when you choose to share it.
No payment or subscription flow is implemented in the inspected PFFT apps or this website. Public store distribution and any future payment handling will need to be reflected here before they are introduced.
Retention and your choices
Local app data stays in the app’s storage until the app, operating system or you remove it. Removing local data does not remove analytics already received by the server. The local analytics identifier is stored in app data and can change when that data is removed.
Local app data, usage events, installation records, aggregates, support messages and infrastructure logs can have different storage lifecycles. Contact Ocintra with questions about stored information or to make a deletion enquiry.
For questions, access or correction requests, deletion enquiries, or a privacy complaint, use Ocintra’s contact page and identify PFFT and the app/platform involved. That page can collect the contact details and message you choose to provide. Do not send passwords or confidential game content. Requests go to Ocintra through this existing contact route.
Ocintra’s contact service stores enquiries in Stactics with submission time, IP address, browser user agent and referring page, and offers a prepared email if submission fails. See Ocintra’s privacy policy for that service’s handling.
Audience and changes
PFFT is intended for adults aged 18 and over. This audience statement does not describe an age-verification feature. The current apps do not offer an analytics opt-out, as described above.
We update this notice when the described practices change. Check the date above for the current version.