Privacy should be understandable.
This notice describes the IFM beta as it works today. It is not permission to add new data uses silently.
The short version: discovery is public; your Journey is private; IFM does not sell personal or health data; paid placement, health data, and ad spend do not determine organic rank.
What IFM collects
- Closed-beta waitlist. If you ask to join the beta waitlist, IFM stores the email address you enter, the audience type you choose, an organization or community name for nonresident roles, an optional public website, the consent-policy version, status, and signup and update times. This record is separate from an IFM account and does not create a resident, partner, trainer, gym, business, event, or community profile. It is visible only to authorized IFM administrators and is used to evaluate admission and closely related launch updates—not for health personalization, provider ranking, public counts, sale, or disclosure to listed businesses. A repeat anonymous submission for the same normalized email returns the same generic confirmation but does not alter the existing record; corrections and removal use the support channel below.
- Founding-beta invitations. For a selected waitlist entry, an authorized IFM administrator may create one expiring invitation bound to that exact normalized email and a named beta cohort. IFM stores the invitation identifier, waitlist relationship, cohort, state, expiry, creating administrator, and—only after acceptance—the baseline resident account that accepted it. The application exposes the signed link to the administrator for manual copy; it does not send an invitation email or mark one delivered. The raw signed token is derived when needed and is not stored in the database or audit metadata. Inspecting an invitation shows only a masked email, cohort, and expiry and does not create an account or consume the invitation. Acceptance requires the exact invited Google account, redeems the invitation once, and creates or binds only baseline resident access. Gym, trainer, business, organization, and Official Partner authority remain separate reviewed grants.
- Account identity. When production Google sign-in is configured, IFM receives your verified email, display name, Google subject identifier, and optional profile image. The public domain does not trust private Sites identity headers; private resident, partner, trainer, and administrator actions require their own verified identity and scoped authorization.
- Anonymous beta Quick Tune. After admitted beta access, IFM may set a signed, HTTP-only beta-participant cookie that is separate from the shared access cookie and every IFM or Google account. For an adult who explicitly confirms eligibility for this tune, the profile stores only its status, an optional fitness-rhythm choice, an optional supported five-digit Central Indiana ZIP, the broad county derived from that ZIP using the Census ZCTA relationship file, optional explicit five-level activity preferences, a policy version, revisions, and timestamps. The adult confirmation is checked for the save request but is not stored in the profile. IFM does not collect age range or sex in Quick Tune because the current source-checked guide cannot use those fields narrowly enough; legacy beta-test values are cleared. A person under 18 should enter without the tune. Unsupported ZIPs are rejected and not retained. Fitness rhythm gives a small useful-first boost only to a listing whose published category, tags, or source-checked match reasons explicitly name the relevant format; ZIP sets a broad starting area. For each canonical activity and for one exact current listing, you may separately choose Already into it, Want to try, Would try, Not interested, or Absolutely not. Activities marked Already into it or Want to try receive the strongest default-recommendation priority. Would try needs a practical convenience such as the chosen area, a current special, or a separate exact positive. Not interested strongly deprioritizes matching items behind neutral options; Absolutely not removes them from proactive recommendations until changed. Search and explicit filters keep the full guide available. Activity and exact-item choices are reversible and stay with the short-lived anonymous beta participant unless you separately choose otherwise. In the same browser tab, a 12-hour handoff may carry only the broad area and up to 15 active canonical activity-and-level pairs through the Google redirect. After sign-in, IFM displays those exact choices and offers separate actions to use them in the account or leave the browser tune separate; nothing imports automatically, and any active or explicitly neutral account choice wins. The handoff excludes ZIP, fitness rhythm, exact-listing feedback, adult confirmation, identity, contact data, Journey, and Ignus context. While choices remain anonymous they never change paid or public rank, count as displayed community demand, enter Ignus, create an account, become public, or go to a provider, advertiser, or data buyer. A choice imported by explicit confirmation becomes the same reversible signed-in resident preference described below and follows the same thresholded demand rules.
- Resident preferences, recommendation feedback, and saves. IFM stores your chosen broad area, up to three starting activity interests, weekly target, deals-first choice, and the listing or event identifiers you save. You may explicitly mark each canonical activity as Already into it, Want to try, Would try, Not interested, or Absolutely not. Already into it and Want to try receive positive private weight; Would try needs an unusually useful timing, place, price, save, or direct request; Not interested moves behind neutral options; and Absolutely not is a hard exclusion until you explicitly change it. You may separately apply the same five-way scale to one exact listing or event. The exact choice affects only that place or event: Want to try outranks Would try, Not interested pushes it behind neutral options, and Absolutely not hard-hides it until you change or clear the choice. Current exact Want to try choices may appear in a private action queue ordered by current specials and upcoming dates. The preference alone does not create a Flame, save, booking, registration, provider notification, public demand signal, or commitment. From that queue you may separately add a current event to your private week or open the existing exact provider next-step review; an event add stores a private Journey plan but does not register or notify the organizer, and a provider follow-up or contact request still requires its own confirmation. An option leaves the queue while that exact event or current offer step is already in your private plan, and changing or clearing the exact preference also removes it. It does not rate the business, organizer, or broader activity. Making an activity hub one of your communities saves the same private Want to try preference; it does not join a club, create a public follow, or notify a provider. These settings are visible and reversible. IFM does not infer a preference from a view, no click, missed event, Journey skip, or completion, and it does not ask for a diagnosis to personalize discovery. Your individual choice and identity are never disclosed to a provider. An active Already into it, Want to try, or Would try activity choice may contribute only to a coarse public area-and-activity Opportunity Radar band after at least 10 eligible signed-in residents in that same area made that same positive choice. Exact-place and exact-event tuning never contributes to that radar; the three activity intents remain separate, and exact totals, identities, negative preferences, timestamps, demographics, contact details, Journey, and Ignus context never appear. These bands cannot alter paid, organic, or global rank.
- Flames and grouped community demand. A Flame is a separate, explicit broad-interest choice for one current place, event, or challenge. Your identity and exact choice stay private, but the affirmative signal can contribute to a coarse community-demand band and tune your own IFM recommendations; it does not say whether you already do it, actively want it, or would only consider it, and it does not save, book, register, join, purchase, message a provider, or improve paid or organic rank. A signed-in place or event Flame offers a separate optional five-level exact vote so you can distinguish Already into this, Want to try, Would try, Not interested, and Absolutely not. Only an explicit second tap stores that exact level. Only active Flames and the three explicit positive Taste Map levels from live signed-in resident accounts can contribute to displayed bands. IFM shows no shared or partner-visible demand signal below 10 eligible residents, then only 10+, 25+, 50+, or 100+—never an exact total. A public Local Demand Pulse may show current places, events, or challenges that reach one of those Flame bands; its separate Opportunity Radar may show an area-and-activity band for Already active, Want to try, or Would try. Negative activity preferences never contribute, and the three positive intents are never blended. Higher bands appear first; deterministic public ties avoid revealing a hidden exact-count order. For a current public location, an authorized business teammate with exact-location aggregate-analytics access may see only that same public Flame band and a suggested existing workspace action. The same card may separately repeat current exact-location-kit and non-kit directional public activity governed by Partner distribution and impact; those values are not derived from Flames and stay visibly separate from the demand band. A public Opportunity Radar card can route a visitor to matching local options or a contextual partner response brief only when its activity-and-area pair matches the current server-thresholded public snapshot. The brief can open existing review-gated offer, event, community-answer, or distribution tools for an authorized business, but it never auto-publishes, grants private analytics, reveals a resident, creates contact access, or awards a claim. No business receives the exact count, a resident or preference identifier, timestamp, ZIP, demographic, Journey, Ignus context, save, request, or contact detail, and no band or adjacent public activity may be represented as a lead, booking, contact request, customer, purchase, attendance claim, foot traffic, conversion, or ranking signal. A closed-beta browser without a signed-in resident account may keep its own reversible Flame, but that signal is excluded from displayed demand. Older private recommendation feedback is never silently converted into a Flame. For a signed-in resident, adding a Flame does not silently invent an exact level; it clears only a conflicting exact Not interested or Absolutely not choice. Removing a Flame leaves any separately chosen exact level intact. A later exact Not interested or Absolutely not choice turns the matching place or event Flame off, while Would try and a neutral exact state remain separate from the Flame. A negative or convenience reflection on a completed challenge may directly turn that challenge Flame off without creating a place-or-event feedback record. Account export and closure include these resident-owned Flame records.
- Your Indy Week email choice and delivery safety. Weekly email is off until you preview the public-only scope, confirm the current verified account email, and explicitly opt in. IFM stores the consent and content-scope versions, subscription state, revision, timestamps, and a keyed one-way fingerprint of the current destination rather than duplicating the email in the subscription. The preview and each prepared issue may use only your broad home area, activity and interest choices, deals preference, saved public places and events, and exact feedback on public places and events to select up to three source-current public items. They never use or include private Journey planning or progress, Ignus conversations, resident-approved memory, the private working profile, trainer or provider requests or messages, health information, paid placement, page views, or inactivity. Delivery records retain the exact public manifest, bounded provider status, and safety receipts needed for idempotency, bounce and complaint handling, one-click unsubscribe, and audit; IFM does not add tracking pixels. An unsubscribe, hard bounce, complaint, provider suppression, verified-email change, stale provider-health signal, or founder pause stops or pauses delivery without silently changing the resident's underlying discovery choices.
- Private resident working profile. You may optionally save one current focus, one nonclinical support style, up to three broad availability and motivator choices, and up to four controlled practical constraints such as budget, travel, session length, crowds, equipment, or flexible timing. This structured profile belongs to your account, is private and reversible, and is not Ignus conversation history. Saving it does not grant Ignus access. It is never disclosed to providers or trainers and is not used for diagnosis, medical advice, paid ranking, advertising, or completion inference.
- Return-brief checkpoint. After your signed-in weekly brief is displayed, IFM stores its server-issued timestamp and revision with your private discovery preferences. On your next visit, IFM compares that checkpoint only with source-check timestamps for current public places, offers, and events. It does not create messages, infer interest from page views, or expose your checkpoint to businesses or trainers.
- Resident-controlled Ignus Memory. You may keep up to 12 short, nonclinical facts of no more than 160 characters each under preference, routine, practical-constraint, or motivation categories. You can add a fact directly, or Ignus can propose one with the exact excerpt from your latest message shown for you to compare before separately confirming it; a conversation, click, page view, inactivity, skipped action, or completed action never writes to this ledger automatically. Each entry shows whether you entered it or confirmed an Ignus proposal. Memory access is a separate, default-off permission: you can always view, edit, export, or permanently delete your ledger while access is off. When access is on, the server sends Ignus only each permitted entry's category and exact text—not its identifier, provenance, revision, or timestamps. The ledger is treated as untrusted resident-provided context, is not a medical record or conversation transcript, is never disclosed to providers or trainers, and cannot be used for diagnosis, medical advice, provider ranking, advertising, or promotion selection.
- Private Journey data. IFM stores the short action titles, source, status, schedule if supplied, and timestamps needed to manage your Journey. For an official event you add, IFM also stores the exact public organizer revision you accepted. If the current public facts later change, IFM keeps your saved title and schedule distinct from the newest organizer facts and asks you to review them; it does not silently rewrite your private plan or treat a source-only recheck as a new event revision. The beta rejects clinical-record-style titles and does not provide a free-form health journal.
- Community challenge participation. When a signed-in resident explicitly adds a challenge, IFM stores the public challenge slug, exact template revision, Indianapolis week, private participation status, linked Journey item, and timestamps. Participation is private: IFM does not publish participant, join, progress, completion, streak, count, or leaderboard data.
- Challenge invitations. A signed-in resident may create a link for one friend or a group containing an opaque, high-entropy invitation token that expires after 14 days; one link may be used by more than one recipient. Its public preview reveals only the public challenge—not the inviter's identity, participation, Journey, progress, or completion. IFM does not publish a group roster, member count, shared progress, or inviter receipt. Opening the link alone does not join the challenge or count as a conversion. Each recipient must explicitly add the challenge while signed in, and IFM deduplicates self-referrals and replayed conversions.
- Local actions. IFM stores the listing and offer you chose and whether you started, completed, or stopped pursuing it. For normal provider-site handoffs, providers receive the link visit only; IFM sends them no personal information.
- Provider Offer Connect requests. For a current owner-confirmed offer at a separately enabled, claimed gym, studio, wellness, or health-adjacent organization, you may ask the provider to email you. Before a request exists, IFM shows the exact verified account email, one controlled availability choice, and immutable offer revision that would be shared. The request stores the organization, listing, offer snapshot, availability, consent-policy version, and a keyed one-way fingerprint of that email; it does not duplicate the email in the request record. An eligible scoped partner can view the current email only while the request remains active and the email still matches the fingerprint. The partner may acknowledge, decline, or separately report fulfillment and optional revenue. Provider fulfillment and resident completion stay independent, and revenue is labeled provider-reported rather than audited. IFM redacts contact access after completion, cancellation, decline, expiry, fulfillment, authority loss, capability loss, or an email mismatch.
- In-store Offer Codes. For an exact current owner-confirmed offer at a separately enabled location, you may explicitly issue one private, single-use code. IFM stores the resident-owned code record, exact organization, location and offer snapshot, issue and expiration times, state changes, and any partner-recorded redemption receipt. Raw manual and QR secrets are regenerated from protected server signing material rather than stored as reusable database values. An authorized partner can preview only the location, exact offer, expiration, and code state before separately recording that the IFM code was honored; the preview and receipt exclude your identity, email, Journey, Ignus context, interests, trainer relationships, and health information. You may cancel an unused code and may independently confirm use only after a partner redemption. A partner-recorded redemption is not an IFM-verified visit, purchase, revenue amount, or health outcome. Code activity is private, does not affect organic rank, and remains unavailable in rolling location or exact Activation Kit reports. The only partner-facing code outcome is the separate, thresholded Closed-Period Local Impact Receipt described below.
- Closed-Period Local Impact Receipt. After an exact Indianapolis calendar month closes and its 14-day grace period ends, IFM may freeze and retain one deidentified, immutable aggregate for one exact listing and that month. The receipt is eligible for release only when the same listing-month cell contains at least 10 resident-confirmed redemptions, at least 10 other partner-recorded redemptions, and the coarse band plus the location's known redemption total still leave at least 10 possible confirmed totals. When eligible, it releases one coarse confirmed-use band—not an exact confirmed, other, or total count—and contains no resident or Offer Code identity. IFM does not create or release a live, rolling, organization-wide, Activation Kit, exact-link, offer-revision, or arbitrary-date version of this receipt. The band does not establish or support an inference about a visit, purchase, amount spent, revenue, return on investment, satisfaction, or health outcome. Each read rechecks current organization membership, exact-listing scope, and aggregate-analytics authority; suspension, revocation, authority loss, or capability loss removes current partner access without rewriting the retained deidentified month cell.
- Trainer introductions and plans. If you request an introduction from an eligible trainer organization, IFM stores the organization, listing, exact offer revision, one broad availability choice, an optional controlled non-clinical goal tag, the consent-policy version, and a keyed one-way fingerprint of the verified account email shown in the consent preview. IFM does not duplicate the email in the connection record. An open request expires after 14 days. The trainer inbox can display the current verified account email only while the request or assigned connection remains active, the acting account has a verified trainer-practitioner relationship, and the email still matches that fingerprint. A connected trainer receives only a connection-attributed plans permission; the trainer cannot read Journey history, Ignus messages or context, saves, provider actions, health data, diagnoses, metrics, or notes. Each proposed plan stays inactive until you accept it, and only you can complete it. Revocation archives still-pending proposals. Connection, consent, proposal, expiry, and revocation changes are audited. If a trainer closes an IFM account, each affected relationship owned by another resident receives an actorless, content-free closure receipt; the receipt identifies only the connection, consent grant, or pending proposal and contains no account identity, plan content, or audit metadata.
- Ignus eligibility and context. Ignus stores an adult-attestation timestamp before providing adult general-wellness guidance. Broad area, up to 20 active or recently completed Journey titles, canonical activity likes and dislikes, the private resident working profile, and resident-approved Ignus memories are five separate, default-off permissions. Completed titles age out after 90 days. When activity context is enabled, Ignus receives only the canonical activity and your chosen level—not item feedback, reasons, page behavior, or entity identifiers. When working-profile context is enabled, Ignus receives only the server-sourced structured current focus, support style, availability choices, motivators, and practical constraints currently saved to your account; if no active profile exists, nothing is shared. When memory context is enabled, Ignus receives only the active ledger entries' categories and exact text. Ignus treats all permitted profile and memory context as untrusted resident-provided data, not instructions, and cannot use it for diagnosis, medical advice, paid or organic provider ranking, advertising, promotion selection, or completion inference. Trainer and health-connection records are excluded from this context. IFM records the permission policy version, grant or revocation times, and a content-free audit event. The server checks each permission and revision immediately before model use and reads permitted context from your account rather than trusting browser-supplied context. Your typed messages and Ignus's replies in the open conversation are processed to answer you; neither the working profile nor memory ledger is conversation history, and IFM does not persist beta conversation history.
- Partner claims, logos, offer drafts, and event submissions. If you ask to manage a business page, IFM stores the selected listing or public business name, official website, business category, your asserted relationship to the business, claim status, reviewer messages, verification method, and decision timestamps. A verified partner may also upload an authorized location-scoped business logo, save private versions of public pricing and specials, or submit a location-scoped event with its official source, schedule, registration link, price, eligibility, terms, activity, and sponsorship disclosure. Logo files and other drafts stay private to authorized organization users and IFM reviewers until separately approved. An approved logo may appear on that exact public location page; approved offer versions become public with an owner-confirmed date; approved event revisions become canonical public event pages with their organizer and commercial relationship disclosed. Account closure purges solely owned private logo files while restricted reviewed or published provenance may remain for integrity. Partner withdrawal, stale evidence, or revoked authority removes the affected event from current public resolution and may remove other affected current partner content when required. Do not submit resident, patient, client, health, payment, government-ID, or confidential employment information.
- Partner QuickStart and provider source suggestions. A founder may prepare one expiring, single-purpose claim or correction handoff for an exact organization, one to 25 exact linked locations, one primary location, and a public business email. IFM stores the email, location scope, purpose, status, expiry and decision times, only a one-way token digest rather than the raw reveal-once token, and an independently keyed contact fingerprint used to honor a permanent QuickStart do-not-contact request. A valid rendered handoff may record one content-free first-open receipt; it does not count a person, customer, or conversion. A claim requires the exact invited Google account and still enters separate authority review. An accountless correction stores bounded proposed facts, the official HTTPS source, founder disposition and review note, but never changes the catalog automatically. Permanent contact suppression closes active QuickStart links for that fingerprint and is retained to block future QuickStart invitations; it does not remove the public listing. For an authorized organization, IFM separately derives exact-location setup progress from existing reviewed public facts, current reviewed pricing or an explicit no-special state, public-page availability, and active location Activation Kits. This progress is not resident activity and does not prove that a person viewed a page. After every linked location is activation-ready, an eligible organization-wide partner may optionally suggest another provider using only its public business name, city, and official HTTPS website. IFM stores those public source fields, the referring organization, timestamps, an idempotency value, and a separate choice about whether IFM may name the organization as the referrer. A link or suggestion creates no listing, claim approval, outreach, endorsement, ranking signal, or permission to submit a private email, phone number, resident information, or other confidential contact detail.
- Partner distribution and impact. An authorized partner may create an Activation Kit tied immutably to one published IFM location page, one exact current owner-confirmed offer revision, or one exact current reviewed event revision, and label its intended channel or placement. Opening that link creates a seven-day HTTP-only first-party attribution cookie and a separate high-entropy browser token whose one-way digest—not the raw token—is retained with the link and bounded timestamps. Every offer or event redirect rechecks the exact organization, location, publication, revision, freshness, expiration, and authority; an ineligible target stops resolving and is never silently reassigned to a replacement. IFM may internally connect a later matching action to that server-resolved link while keeping resident and provider facts separate. Common crawlers, link previews, prefetches, and rapid same-browser replays are excluded where detected, but recorded opens and first-party browser-token counts are still not verified people, customers, or foot traffic; a calendar action is not proof of import. Current rolling 7/30/90-day location and exact Activation Kit reports expose only directional public interactions such as recorded opens, listing, offer, and event views, public shares, official-source opens, and calendar actions. Resident-derived saves, private plans, requests, completions, Offer Code activity, provider-reported fulfillment, and optional provider-reported revenue are privacy-protected and unavailable in those overlapping reports regardless of cohort size. The Closed-Period Local Impact Receipt is separate from these reports and cannot be requested as a rolling, organization-wide, exact-link, live, revised, or arbitrary-date value that could reveal a protected remainder by subtraction. Conversion rates are unavailable, and organic activity remains separate rather than being claimed as partner-driven.
- Pass the Torch links. After a resident explicitly marks an eligible completed Local Win “Worth repeating” or “Only if convenient,” the resident may separately confirm creation of one 30-day link. A listing link is bound to the current listing and exact offer revision the resident completed; event and challenge links are bound to their exact current revision. IFM stores the resident-owned link, source and target binding, expiry, one-way token digest, and bounded creation receipt; the raw token is returned only in the share path. The link never contains or reveals the resident's name, contact details, Journey title, completion, exact reflection label, health information, or intended recipient. When an eligible browser opens a current link after common automated-preview checks, IFM may issue a seven-day HTTP-only first-party attribution cookie and retain only a one-way digest of its high-entropy browser token with bounded timestamps. The sender never receives an open or action receipt. IFM retains this attribution internally for bounded integrity and aggregate product evaluation; no Pass the Torch sender, open, or action reporting is exposed to a business in the beta, and it never changes organic rank.
- IFM-operated editorial desks and Source Watch. IFM may use clearly named system desks to compile public articles, briefings, prompts, corrections, and official editorial notes from approved local sources. These desks are service identities, not resident accounts. Source Watch may store canonical public source links, bounded response and content fingerprints, observed and verified dates, source-health exceptions, detected fields, proposed patches, review decisions, and scan-run metadata. A scan observation does not extend verification or publish a change. Editorial and source automation does not receive private Journey, Ignus, contact, trainer, provider-request, completion, or health data. Automated source checks and quality-assurance page opens are excluded from resident-facing engagement signals and business-interest reporting.
- Product events. IFM records a narrow allowlist of content-free or tightly bounded events such as an area guide, community hub, challenge, Pulse briefing, or public directory-search view or share; a bounded Pulse action; a source-ready listing or event open; an explicit event organizer-source or calendar action; search; save or removal; official-offer open; successful sharing of an owner-verification link; a private event-plan confirmation; resident-confirmed follow-through; and bounded Make My Week funnel states. A shared directory search can carry only public search, area, activity, category, current-deal, and sort filters in its URL; Saved, I'd try, and the person's private Taste Map level are never included. Its product event contains no search text, URL, filter, listing, sender, recipient, account, Journey, or preference value. A Quick Tune result view contains no profile answer or entity, and opening one of its starting places contains only that validated current public listing identifier—not fitness rhythm, ZIP, broad area, or adult confirmation. Its first-move and continuation events contain only one action category—Flame, details, next step, share, full directory, or tune—and whether the person started the optional Google-first continuation or dismissed it. A separate hide or restore event contains only the validated current public listing identifier so IFM can measure whether the control improves the shortlist; it contains no tune answer, account, area, activity inference, reason, or recipient. Activation events may identify only the approved entry point, Fit or Choose step, broad option kind for an exact Not for me action, and broad confirmed or shared result kind such as event, provider, or private step. Saving a Taste Map answer records only that one optional answer was saved, and skipping to another activity records only that one prompt was skipped; neither event includes the activity, answer level, prior choice, account value, area, or reason. Opening or saving the separate exact-option tuner records only onboarding, weekly, directory, detail, Flame, or Quick Tune plus one bounded five-way choice or neutral reset; it never records the place, event, resident, reason, Journey, or Ignus content. If the person then explicitly asks IFM to show local options, a separate event records only the canonical activity and one of the three positive levels—Already active, Want to try, or Would try. Negative and neutral choices never enter that local-action event. Opening a result from that exact activity filter records only the current public listing identifier plus details or next step; saving a private no-match Community Request records a content-free supply-gap event. The Want-to-try queue view contains no item, account, or count; opening a queue row records only whether the destination was a listing or event—not its identifier, title, offer, date, resident, or preference. Flame handoff events record only whether the explicit choice appeared, completed, or was dismissed; they contain no item identifier, item count, account value, or choice. A return-brief action records only whether the resident opened the next-step, Flames, current-openings, or week destination. Opening the private resident inbox records no item or account value; opening one of its cards records only the bounded category decision, next step, Want-to-try, current opening, or Flame—not its title, provider, Journey record, public entity, or recommendation reason. A successful weekly-match, Flamed-pick, or place share records only the canonical current public event, challenge, or provider identifier. A shared detail page may include a fixed public marker indicating that it came from a weekly pick, Flamed pick, or public detail page; IFM may count a validated shared-page view or next-step open. The marker and events contain no sender, recipient, private title, shared URL, Journey content, or preference. Activation events never accept the resident's area, target, deal preference, working profile, exclusions, suggestion title, shared URL, share recipient, or Journey content. Community, challenge, Pulse, and public event events accept only canonical public identifiers—not a participant state, comment, message, Journey title, or Journey record identifier. For a current publicly found offer, IFM may aggregate official-offer opens and verification-link shares by listing to prioritize an invitation for an authorized owner to claim or correct the page. A random browser identifier may be stored locally and attached to public discovery events. When a current exact partner attribution exists, an event may also retain the organization-owned share-link identifier; client requests cannot choose that identifier. Shared URLs, recipients, search text, Journey content, health information, and resident contact details are not accepted in these events. The identifiers are not health profiles, and a business does not receive the identity of the person who acted.
- Taste Map handoff events. IFM records only whether the explicit post-sign-in Taste Map review appeared, completed, or was dismissed. These events contain no activity, preference level, item count, account value, conflict, ZIP, fitness rhythm, Journey, or Ignus context.
- First-week momentum action. The first-week foundation card reuses the content-free return-brief event and records only whether the resident opened the Taste Map, next-step, current-openings, or week destination. It does not record the resident, completed foundation, preference, place, event, Journey item, provider, or first-week score.
- Challenge invitation delivery event. As a narrow exception to challenge-page events that use a canonical public identifier, a successfully delivered private invitation records only the bounded category friend or crew. It does not accept the challenge, sender, recipient, shared URL, roster, participant state, or progress, and a canceled or failed Share or Copy action is not counted.
- Partner QuickStart distribution event. After an authenticated partner successfully shares or copies a current exact-location Activation Kit from QuickStart, IFM records only the validated current public listing identifier. It does not accept the organization, partner identity, link, placement, recipient, resident information, or private business data, and a canceled or failed action is not counted.
- Google Analytics and advertising measurement. IFM uses Google Analytics when pages load to understand traffic, acquisition, product use, and advertising performance. Google receives a sanitized IFM route, page title, origin-only external referrer, broad browser and device information, approximate geography, Google measurement identifiers, bounded feature-event names, canonical public identifiers for viewed or acted-on listings, offers, areas, events, communities, challenges, and editorial content, and limited server-validated action categories. After a person explicitly asks to see local options from a positive Taste Map choice, this can include the canonical activity and Already active, Want to try, or Would try level; it never includes a negative or neutral choice, area, reason, Journey, or Ignus content. Google Signals and advertising personalization are enabled to support cross-device reporting, audience development, remarketing, and campaign optimization where Google makes those capabilities available. Private-link tokens and arbitrary URL query parameters remain excluded. IFM does not send Google passwords, names, email addresses, phone numbers, private messages, Ignus conversations or memory, free-text health information, Journey titles, provider-request contact details, shared URLs or recipients, or payment credentials.
- Device-local handoff. If you save before signing in, the listing or event identifier may stay in this browser so IFM can import it after authentication. In the same tab, IFM may also hold for up to 12 hours the canonical public identifiers for up to 50 active browser-only Flames so it can offer an explicit account import after Google sign-in. That temporary bridge contains no label, profile answer, ZIP, area, Journey, contact detail, or account value. Nothing imports until you choose; existing account choices win. A bounded partner-claim draft containing only public business information may also stay in this browser across sign-in. Each successfully imported or submitted item is cleared from its device copy; a temporary identifier that cannot sync may remain for a later retry.
- Flame learning and public shortlists. While a Flame remains active, canonical activity tags from that current public place or event may give a moderate private lift to other source-matched options. This temporary affinity is derived when your private feed is built, is not saved as a separate interest preference, never overrides an explicit Not for me choice, and never changes public or paid rank. When you explicitly share from Things I'd try, IFM sends no more than three current canonical public pages through your browser's share sheet or clipboard. The shared text includes the public titles and URLs you chose to send, but not your account, Flame status, private collection, Journey, Ignus context, or exact collection size. IFM records only that a shortlist share completed; the product event contains no item identifier, shared text, URL, recipient, or profile value.
How IFM uses it
IFM uses data to authenticate accounts, keep preferences and saves, personalize useful-first results, honor explicit likes, dislikes, and hidden items, display a resident's private Journey, maintain the resident-controlled Ignus Memory ledger, prevent duplicate actions, answer an Ignus request using only the context permissions currently enabled, deliver a resident-requested provider or trainer introduction with the exact approved fields, issue and protect a resident-requested In-store Offer Code for one exact location and offer revision, keep partner redemption separate from resident confirmation, keep provider fulfillment separate from resident completion, enforce plans-only trainer consent, verify and review authority to manage a business page, derive an authorized organization's exact-location QuickStart progress, review optional public-source provider suggestions, moderate partner-submitted public pricing, offers, and location-scoped events, bind partner distribution to one exact current location, offer, or event destination, measure whether that server-resolved attribution accompanied bounded matching activity, prioritize public source rechecks without treating observation as verification, operate source-aware editorial publishing, preserve the exact version a resident acted on, secure and debug the beta, understand whether discovery leads to real follow-through, prioritize owner-verification opportunities using aggregate public-offer signals, and produce aggregate local signals. Actions created before immutable snapshots launched were sealed during the launch migration using the offer record then stored by IFM and are labeled as legacy migrations; IFM does not represent those records as independent proof of the exact page shown at the earlier action time. IFM does not use an individual resident's negative preferences or private health, Journey, Ignus Memory, provider-request, trainer-request, offer-code, revenue, completion, or distribution-performance data for editorial generation, advertising, or paid or public marketplace rank. Current rolling and exact-activation partner reports contain directional public interactions only; private resident outcomes remain unavailable there. The separate Closed-Period Local Impact Receipt retains only one thresholded band for a frozen exact-listing calendar month and is not available in overlapping scopes that could reveal a protected remainder.
When a resident turns on Your Indy Week, IFM uses the separately disclosed public-only scope to prepare no more than three current local items for a Monday-morning issue. IFM skips rather than pads an issue when no item clears current-source checks. Subscription and suppression state are used only to honor the resident's choice, prevent duplicate or unsafe delivery, operate the email, and report aggregate delivery health to the founder; a founder cannot browse individual subscribers or use the control surface to subscribe them.
Who processes it
Google handles Google authentication. Google Analytics processes the traffic, acquisition, advertising, and feature-use data described above. The deployment and D1 database infrastructure process application and account data. When weekly delivery is explicitly enabled and fully configured, Resend processes the verified destination and email payload to deliver Your Indy Week; IFM requires provider tracking to be disabled and processes signed delivery webhooks for bounce, complaint, suppression, and health state. When configured, OpenAI processes Ignus text, speech, or transcription requests with model-response storage disabled by IFM. Official provider and event links lead to independent sites with their own privacy practices.
Security controls
IFM uses HTTPS deployments, HTTP-only signed session cookies for Google accounts, HTTP-only same-site closed-beta, partner, and resident-pass receipts, verified identity assertions, per-resident ownership checks, organization-scoped authorization, bounded inputs, explicit status transitions, and audit events for sensitive changes. Closed-beta invitation links are signed, carried in the browser fragment before inspection, accepted only by the exact invited Google email, and never stored as raw tokens in the database or audit trail. To rate-limit closed-beta password, invitation, waitlist, and Flame abuse without retaining raw network addresses, IFM stores a purpose-separated keyed one-way digest of the ingress address with a bounded attempt count, timing window, and temporary block time; stale rows are deleted seven days after the last attempt. No internet service can promise perfect security; report a suspected issue to dobetter@indyfitnessmag.com.
Sharing and provider handoffs
A challenge invitation shares only an opaque, expiring link to the public challenge. One link may be sent to one friend or a group and used by multiple recipients, but it never reveals the inviter's identity or private state, creates a group roster or progress view, or gives the inviter an open or participation receipt. Merely opening it creates no participation or conversion. A resident-created Pass the Torch link is also opaque and expiring, but it is available only after an explicit eligible Local Win reflection. A listing link remains bound to the current listing and exact completed offer revision; event and challenge links remain bound to their exact current revision. It starts bounded public-action attribution after common automated-preview checks; the sender never sees who opened or acted, and current partner reports expose no Pass the Torch totals or private context. A partner Activation Kit opens the exact current IFM location, offer, or event destination and starts its own bounded matching attribution; it does not transmit identity, Journey, Ignus, health, or contact data to the business, and it stops rather than repointing when the bound version ends. Opening a current provider or organizer link likewise sends no account, Journey, or contact data from IFM to that third party. Your browser opens the official page and that provider or organizer controls any information you choose to enter there. Offer Connect is a separate optional path for a current owner-confirmed offer at an eligible, separately enabled organization: a confirmation shows the exact verified email, availability, and offer revision before the resident requests sharing. Page-management authority alone does not enable the inbox, and no request is created when consent or eligibility is missing. The trainer Handshake remains a distinct exception available only to a separately verified trainer-practitioner relationship and previews the exact email, availability, optional goal tag, and offer revision. Provider and trainer workspaces expose only their bounded consented fields and permitted actions; they do not expose Journey history, Ignus, saves, unrelated provider actions, trainer data outside the relevant connection, health data, metrics, diagnoses, or notes.
Retention, access, and deletion
The beta waitlist is not part of Account & Data because joining it does not create an IFM account. Email dobetter@indyfitnessmag.com from the listed address to correct or remove a waitlist record. IFM retains active entries only while planning and operating the closed beta and removes or suppresses them when they are no longer needed for that purpose or when removal is requested, subject to restricted consent or suppression evidence needed to honor the request.
The anonymous beta-participant cookie and its Quick Tune profile expire no later than 30 days after admission. A Cloudflare task scheduled every six hours deletes expired participant rows and their cascading Quick Tune, activity preferences, exact-listing feedback, and anonymous Flame rows in bounded batches, records how many expired rows remain, writes a content-free run receipt with deletion counts and completion state, and keeps no more than 120 completed receipts or 90 days of receipts; opportunistic cleanup also runs when a participant is opened. In the guide, Retune reopens every editable Quick Tune control, and Erase immediately deletes the participant row—including activity preferences and exact-listing feedback—and expires its cookie independently of Account & Data. A session-only dismissal prevents an error, Escape key, under-18 path, or “enter without saving” choice from immediately reopening the modal. Signing in suppresses the anonymous tune without automatically merging its fitness rhythm, ZIP, area, activity preferences, or exact-listing feedback into the account. A same-tab visitor may separately review and explicitly import the bounded canonical activity-and-level pairs described above, and may separately choose to import current public-item Flames. Existing active or explicitly neutral resident choices are preserved, accepted imports become resident-owned and reversible, and the original anonymous records remain browser-scoped until normal expiration or Erase.
Account & Data shows the categories IFM currently keeps for your signed-in identity. You can download an on-demand JSON copy of eligible account, working-profile, resident-approved Ignus Memory, preference, recommendation-feedback, save, Journey, challenge-participation, challenge-invitation, Pass the Torch link metadata, action, In-store Offer Code wallet, consent, collaboration, claim, and business-submission records. The download is generated for you when requested, is not emailed or stored as an export file by IFM, and excludes authentication subjects, security secrets, raw invitation or pass tokens, browser-token digests, raw or derived offer-code credentials, offer-code request fingerprints and idempotency values, redeemer identities, unsigned or unconfirmed Ignus proposals, proposal tokens, keyed fingerprints, internal deduplication values, unrestricted audit metadata, and another person's contact or Journey data. Ignus conversation history is not included because IFM does not persist it.
You can also review the current impact and close your IFM account. Closure immediately disables IFM access, expires resident-owned Pass the Torch links, ends active contact delivery and trainer sharing, cancels unused In-store Offer Codes, removes their resident association and wallet access, removes the private resident working profile, resident-approved Ignus memories, eligible resident preferences, activity levels, exact recommendation feedback, saves, Journey content, challenge participation and invitations, and Ignus permissions, and clears IFM data stored by this browser. It does not delete or alter your Google account or a closed-beta preview receipt used to reach the site. Signing in again does not restore the closed account's history.
Turning off Your Indy Week immediately stops future IFM queues and retries and records a suppression so an old or replayed request cannot silently turn it back on. A message the email provider already accepted, or whose outcome is ambiguous, cannot always be recalled and may still arrive. Closing the account also stops safely cancellable queued delivery and removes the resident-owned subscription. Restricted, pseudonymous delivery, consent, unsubscribe, bounce, complaint, and provider-integrity receipts may remain only as needed to prove suppression, prevent replay or duplicate delivery, resolve disputes, and protect email-system integrity; they are not used for personalization, ads, public ranking, or a subscriber directory.
IFM retains only the restricted, pseudonymous records still needed for security, fraud prevention, contact suppression, consent and authority history, moderation, disputes, legal obligations, or the integrity of previously published business information and resident-requested handoffs. This can include the durable QuickStart invitation and correction history needed to prove scope and review, a permanent keyed QuickStart contact-suppression fingerprint, a content-free partner-recorded In-store Offer Code redemption receipt after the resident association, code security material, attribution link, and resident confirmation are removed, and—after the 14-day grace period for a closed Indianapolis calendar month—one immutable, deidentified exact-listing Local Impact aggregate containing only the released band rather than resident or code identities or exact totals. Losing current partner access removes the ability to read that retained receipt but does not reopen or revise the frozen month. For supported Google and separately configured owner-only private-beta identities, retained records may also include an irreversible closed-identity guard made from a keyed fingerprint and one-way digest of the high-entropy provider subject. IFM removes the raw provider subject from the closed account; the guard is restricted, is not used for personalization or ranking, and exists only to prevent the erased account from being recreated. Other retained records cannot reactivate the account and have personal display fields removed or restricted. Public listings, approved public offer history, organization records, and accountless business correction or suppression records do not belong to one resident and are not silently removed with an account. Deletion may be paused when the account is the last IFM administrator or verified business authority must first be transferred safely. Email dobetter@indyfitnessmag.com for a correction, a question about the self-service result, or a request the current controls cannot resolve.
Age and wellness boundary
Public discovery, saves, and the self-guided Journey do not require an Ignus age attestation. Anonymous Quick Tune is an adult-only, separate feature: its confirmation is used only to accept that one save request and does not turn on or satisfy Ignus. IFM does not collect an under-18 person's age, sex, fitness rhythm, or ZIP through Quick Tune. Ignus has its own separate adult attestation, is limited to adults 18 and older, and provides general wellness support—not diagnosis, treatment, emergency services, or a clinical record. Do not place medical details in Journey titles, Ignus Memory, or provider requests.
Before indexing or broader release
This notice reflects the publicly reachable, noindex closed-beta gate and the gated application behind it. The operating legal name, final retention schedule, state-specific disclosures, and launch terms still require owner and legal review before search indexing or broader ungated access is enabled. Production Google OAuth and founder-administrator configuration are also still required before exact-email invitations and the founder waitlist dashboard can operate on the public domain.
