Plain language, before the fine print.

What we collect

The form collects your email address, approximate number of approaches in the last 30 days, biggest current bottleneck, preferred capture method, current review method, a description of your last concrete review and next action, a one-time offer signal, contact permission, optional interest in a free concierge debrief, and optional source and referral tags in the page link. After submission, we create a random referral code so we can count introductions without putting your email address in the shared URL.

The research page also creates a random identifier for the current browser session. FieldCue stores the first measured source for that session, plus one page-view record for each distinct path and source combination you open. A page view includes the path, source tag, referring website hostname, and the random session identifier. FieldCue does not store your IP address, full referring URL, or browser user-agent string in its research database.

The 60-second interview application stores your email address, recent approach-volume range, current review method, selected review problem, contact permission, page path, source tag, and the random browser-session identifier. An application is treated as a contact lead only; it is not counted as a completed interview, purchase, or revenue.

The first time you change any field in the 60-second application, FieldCue stores one anonymous application-start event with only the random browser-session identifier, page path, source tag, experiment name, and started stage. It contains no field name, email, answer, or selection. If you submit and continue to the written interview, the source tag gains a written suffix so the recruitment path can be grouped without claiming that every stage belongs to the same person.

The structured written participant interview stores your email address, recent approach-volume range, current review method, five written first-person workflow answers, preferred capture method, current reaction to the planned $19 self-serve offer, source tag, page path, random browser-session identifier, and five required confirmations: adult status, membership in the target segment of men practicing cold approach, firsthand experience, exclusion of other people's identifying information, and permission for one verification or clarification email. The form does not request or accept audio, transcripts, names, contact details, or precise locations of people approached.

The first time you change any field in the structured interview and after you locally complete each of its first two steps, FieldCue stores an anonymous progress stage containing only the random browser-session identifier, page path, source tag, experiment name, and stage reached. It does not include the field name, email, answer text, or selection. A start or step reach is product analytics, not a submitted or completed interview.

A written interview is initially stored as submitted and is not counted toward the participant-interview target. The private admin review may store a verification-contacted, verified, or rejected status; verification timestamp; coded recurring-problem, existing-workaround, and repeatable-workflow findings; and researcher evidence notes. Only a qualified, substantive, unique record marked verified is counted as a completed structured participant interview. A stated willingness to pay is research evidence only and is never counted as a purchase or revenue.

The operator-interview response form stores a reply-capable email address, selected operator role, the type of review evidence used most often in that operator's program or community, chosen response format, contact permission, page path, source tag, and the random browser-session identifier. If the operator answers asynchronously, it also stores three selected workflow answers, one written observation, and the response timestamp. An asynchronous response is direct operator evidence but is not counted as a completed interview. Neither response format grants access to members, permission to post, or permission to promote an offer, and neither is a purchase or revenue.

If an operator completes a research interview, the private admin pipeline stores its status and completion timestamp, a coded retention driver, first review failure, workflow verdict, separate member-share permission, and researcher notes. An operator interview remains separate from the participant interview count and cannot satisfy that gate.

The Founder Pack purchase-intent form and the Software Pass purchase-intent form store your email address, the exact offer type, recent approach-volume range, preferred delivery format, selected reason the offer would or would not differ from a tracker or AI chat app, explicit $19 purchase-interest confirmation, contact permission, page path, source tag, and the random browser-session identifier. The two offers are stored and reported separately, so the same email may express one intent for each. Neither form collects payment details. A saved intent is not a purchase, reservation, software entitlement, transaction, or revenue.

The Software Access page can validate a license key against the configured Software Pass license benefit. FieldCue forwards the raw key for that validation but does not store it in the research database, browser storage, or the signed access session. A successful validation stores only a seven-day HttpOnly cookie containing the provider license identifier, masked display key, exact benefit identifier, validation time, recheck time, and optional expiry. Clearing the session deletes that cookie. License validation is an access check, not a purchase or revenue event.

If the future Software Pass checkout is activated, FieldCue can receive signed Polar order-paid and order-refunded events for the exact one-time product. The payment ledger stores the provider, sandbox or production environment, organization and product IDs, provider order ID, order and refund status, order amounts and currencies, and provider event times. It does not copy the customer's email, name, billing address, payment-card data, or license key into the research database. Sandbox orders remain test evidence and never count as purchases or revenue. A signed order is also kept separate from the provider's settled and withdrawable balance.

The cold-approach review guide has an optional anonymous question. If you answer it, we store your selected review problem, optional note, page path, source tag, and the same random session identifier. It does not request your email address.

The 30-second recap prototype stores whether a random browser session started or completed the exercise and, if submitted, one selected workflow answer. It also stores the page path and source tag. The prototype does not request microphone access, record or upload audio, transcribe speech, or store the words you say or think during the exercise.

The cold-approach review diagnostic stores four selected answers: current capture method, review frequency, primary review bottleneck, and the workflow you would realistically repeat. It also stores the page path, source tag, and random session identifier. The diagnostic does not request your email address.

FieldCue Alpha can use your microphone to create short voice recaps or create a local playback URL for an audio file you import. Recorded and imported audio, file names, notes, selected outcomes, evidence sentences, and local evidence timestamps are stored in this site's browser storage on the current device so an unfinished field outing can survive a reload. They are not uploaded, transcribed, or stored in FieldCue's server database. Resetting the outing deletes the device-local copy; clearing this site's browser data can also remove it. If you choose “Archive result and start next outing,” the current audio, evidence sentences, file names, outcomes, and timestamps are deleted from the active draft. A separate device-local history keeps at most five structured summaries: completion time, saved-rep count, evidence status, fixed pattern title, fixed next cue, and the internal behavior category. You can delete that archive from the alpha without resetting the active outing. A downloaded report contains the outcomes, behavior labels, evidence sentences, local markers, and coaching result that you chose. It does not embed audio and is saved directly to your device without being uploaded to FieldCue. The private coach-handoff action can place that report and the current outing's local audio files into your device's native share sheet. You choose the recipient and destination; FieldCue does not receive the files.

FieldCue Alpha can cache the public application shell, manifest, icons, and versioned same-origin code and style files so the field interface can reopen offline after one successful online preparation. The offline cache excludes API requests, private dashboard pages, audio, notes, evidence, outcomes, file names, timestamps, coaching results, and participant records. Private outing data remains in this site's separate browser-local IndexedDB storage. Anonymous product signals are not queued or backfilled while offline.

To measure whether the alpha workflow is useful, FieldCue stores only random browser and outing identifiers, whether the session was a sample preview or field session, the furthest stage reached, saved attempt count, whether the session used audio or text, the number of saved attempts that used a local audio marker, whether the result found repeated evidence, whether a local report was exported, whether the user completed the native share chooser or copied the sanitized share text, whether a separate private coach-handoff chooser completed, whether the outing started with a prior local cue, an aggregate transfer status of not tested, held, persisted, or mixed, and the page path and source tag. After synthesis, the user can also submit three optional closed-choice result signals: a 0–10 usefulness score, whether they would run the workflow after the next outing, and the single product gap they most want addressed. Demo answers are labeled separately. The transfer status comes only from the user's per-rep cue checks. The marker count does not include the exact timestamps, and the exported report is not sent to FieldCue. The sanitized share text contains only the fixed pattern title, fixed next cue, and a sample link; it excludes evidence notes and audio. Sample previews are measured separately from field sessions. These anonymous product signals do not contain audio, notes, transcripts, names, phone numbers, the coach-handoff recipient or destination, file names, the cue, the selected behavior, or archived summary content. Result feedback does not collect free text, outcomes, evidence sentences, or the pattern itself.

The research form does not request or accept private conversation recordings, names, phone numbers, photos, or locations of people you met.

Why we use it

We use responses to select relevant interview participants, understand current behavior, compare demand for full recording versus short voice recaps, evaluate pricing, and decide whether the proposed product should be built. Referral codes are used only to measure whether participant introductions produce relevant research responses.

Storage and access

Responses are stored in access-controlled, Cloudflare-backed infrastructure used by OpenAI Sites. Access is restricted to an explicit project-owner email allowlist. We do not sell research responses or use them for third-party advertising.

The anonymous session identifier is kept in browser session storage, which normally ends when that tab or browser session closes. FieldCue uses no third-party analytics SDK. Its hosting providers may still process standard request metadata needed to operate and secure the site.

Field outing content is separate from the anonymous session identifier. It is saved as a temporary draft in IndexedDB for this site on the current device, remains available after a reload, and is accessible to another person who can use the same browser profile. It is not a durable backup. Use “Reset outing” to delete the active draft and “Delete archived history” to remove archived summaries before sharing the device. Clearing this site's browser data removes both. Browser storage limits or private-browsing settings may prevent saving.

Contact and deletion

You may opt out of research contact or ask for your response to be deleted by replying to any FieldCue research message you receive. If you have not received a message yet, use the same community or invitation channel through which you reached this page.

Future product data

If a future version uploads audio for automated analysis, it will receive a separate privacy notice before any server-side audio is collected. The current alpha is deliberately limited to device-local playback and self-selected evidence.