Information we use
X-Medic provides First Aid-kit supply suggestions and private saved recommendations. We collect information you provide in the intake and in support requests. The intake asks about First Aid skill, licensure, ZIP code, number of people, intended use or activity, and an optional container and its dimensions. Do not submit patient records.
Our Consumer Health Data Privacy Notice separately explains health-related categories, recipients, and applicable rights.
Supabase Auth processes your email, verified account and sign-in identifiers, sessions, and authentication events. Google supplies the identity information authorized by you when you choose Google sign-in. Our customer database uses keyed digests of verified email and provider identifiers to connect those identities to your internal account.
You can calculate and shop an unsaved kit without signing in. Completing intake sends your answers to our server to calculate all three tiers without creating account history. Editing answers recalculates unsaved results; it does not overwrite saved recommendations.
Selecting Save this kit after verified sign-in stores permitted intake values and all three recommendation tiers, including supplies, quantities, explanations, supporting evidence, version information, and recalculation links. Unresolved custom hobby or job text is processed for the request, then omitted from saved history; a keyed digest records that exact replay is unavailable. Pending answers remain in the current browser tab for up to one hour and are cleared after saving, sign-out, reset, or account deletion.
We also process network and device information to serve and protect the website. Our application retains short-lived keyed network and request digests for abuse detection, plus quota and duplicate-request records. Hosting, sign-in, email, and bot-check providers may retain the delivery and security metadata needed to operate their services.
Purposes and recipients
The kit builder uses answer choices and fields. It has no chat or speech input and does not send your kit answers to Grok (xAI).
If you previously used optional AI help, X Medic did not save chat transcripts. xAI normally keeps messages and responses for 30 days for security checks; its terms allow longer retention in some cases. See the xAI API security policy and Enterprise Terms, section 4.
The license form collects selected types and optional issuing jurisdictions, authorization kinds and license numbers. These remain self-reported: no verification provider is connected, no licensing source has been queried, and we do not request names in that form. Do not include names or unnecessary personal information in intake fields.
License-form answers follow the same tab-draft and optional saved-kit retention as other intake answers. Checking a license sends its form details to our server, which currently returns unavailable without storing a check record or contacting a verifier. Selecting Save this kit saves the declarations, not a verified license status, in your private run.
Optional Locate me: At the ZIP question, choosing Locate me requests your browser’s location permission. Your browser sends its current coordinates directly to BigDataCloud to suggest a ZIP code. BigDataCloud also receives network/IP data and uses anonymous GPS/IP pairings to improve geolocation. See its Privacy and Cookie Policy. We do not use IP-based location fallback, track your location in the background, or send coordinates through our server.
Coordinates and the geocoder response are transient in your browser, not stored in X Medic drafts, account records or application logs, and not sent to Grok. The suggested ZIP remains editable and is not an intake answer until you accept it with Continue or Save; editing the ZIP yourself also records your manual answer. Only that ZIP follows the intake sharing and retention rules. Your current location may differ from where your kit will be. You can cancel lookup, deny or revoke browser permission, or enter the ZIP manually. Cancellation stops use of a pending result but cannot recall data already sent to BigDataCloud; its policy governs its processing and retention.
We use this information to authenticate accounts; generate, display, save, recalculate, and delete recommendations; answer support requests; prevent abuse and duplicate saves; and maintain, secure, and recover the service. Saved history does not subscribe you to notification or marketing email.
Our operating providers are Supabase (authentication, database, and backups), Vercel (hosting, security, and homepage analytics), Google Workspace (sign-in email and support correspondence), Google (optional sign-in), and Cloudflare Turnstile (bot checks). They receive information necessary for those functions. Cloudflare also uses security signals to improve Turnstile, as described in its Turnstile Privacy Addendum. Product links take you to Amazon or another retailer, which processes your visit and purchases under its own privacy notice. We may disclose information when required by law or necessary to protect people or the service.
F3 administers the shared Google Workspace tenant and hosting accounts used by X Medic. Authorized F3 administrators may access support or privacy correspondence and service information when administering those services.
X Medic does not collect, use, or sell your personal data to train large language models.
We do not sell intake or recommendation information or use it for targeted advertising. Analytics run only on the public homepage, not on intake, authentication, account, history, or recommendation pages. Our analytics configuration does not track your activity across unrelated websites. External sign-in and retailer services can process activity on their own sites. X-Medic does not currently change its behavior in response to a browser's Do Not Track signal. You can disable homepage analytics in this browser by visiting the homepage with analytics off.
Retention and your controls
AI abuse controls use a signed one-hour session cookie, keyed session/network/message digests, random request identifiers, and token and cost accounting, including reasoning-token counts when available—not chat text or account identity. Request records expire 24 hours after settlement, or after the attempt if it remains unsettled, and are removed on the next AI reservation attempt. Global aggregate usage totals, a pending-request identifier and safety-stop state have no automatic reset. Unknown charges stop further AI requests until reconciled. Hosting backups may retain prior security records.
Saved recommendations expire 12 months after creation. You can view or delete them and request account deletion from your account page. Deleting a run hides it immediately; its content and derived records are purged within 24 hours. Account deletion immediately blocks account access and purges recommendation content. Authentication-provider deletion is retried if the provider is unavailable; the account remains blocked.
Abuse events expire after 24 hours. Duplicate-request records expire after 32 days of inactivity; aggregate quota records use short operating windows of up to three months. Account deletion removes these records. Minimal keyed account, identity, and deletion records remain to prevent deleted-account sessions, re-registration, or restored backups from bringing deleted access back. They contain no recommendation content or raw email, but remain linked to the account and are not treated as anonymous information. These minimal records currently have no automatic expiry.
Restricted database backups may retain deleted information for up to seven days. Before restored data becomes accessible, deletion records must be reconciled and checked. We do not retain a hidden copy of deleted recommendations for product use.
Contact the privacy address above to request access, correction, deletion, or other applicable privacy rights, or to appeal a request decision. We may verify your identity. Corrections to saved, immutable recommendations require a new run; you can delete the old run. Any legal restriction on retaining security or deletion records still applies.
Changes
We will post changes here with an updated effective date and prominently identify material changes on the website before they take effect.