1. Who operates SniperFrame
SniperFrame is a personal, self-hosted household project operated by Leo. Access to its connected accounts and private dashboard is limited to the owner and authorized household participants. This public website describes the project; it is separate from the private dashboard.
2. Google account access
Gmail access requires the account owner’s explicit Google OAuth consent. The personal account requests gmail.readonly. The dedicated family account requests gmail.readonly and gmail.send. Read access is used to retrieve selected messages, metadata and supported attachments. Send access is used for configured reminders and explicitly requested previews sent only to approved household recipients. SniperFrame does not require Google Calendar access: events are stored in its internal calendar.
3. Information processed
Depending on enabled features, data includes sender and recipient addresses, message identifiers, subjects, dates, message bodies, supported image/PDF attachments and extracted text. Derived records include summaries, actions, source links, event details, participant associations and reminder delivery status. Appointment messages may contain sensitive health information. Household settings also contain member names, birthdays and display preferences. Selected iCloud photos are downloaded separately through owner-authorized access.
4. Why this information is used
Information is used to show useful mail summaries, identify clearly dated activities, organize household plans, display selected photos and provide approved appointment reminders. Sender filters limit the messages processed; they are not proof of sender authenticity. Uncertain dates, participants or unreadable medical content require review rather than an invented appointment.
5. AI processing and service providers
Automatic family-mail review sends selected message content, relevant household/appointment context and supported attachment images or extracted PDF text to OpenAI through Codex using the operator’s account. This can include names, email addresses and health-related content when present in the selected source. OpenAI processes that content under the terms and data controls applicable to that account. Local storage does not mean all processing stays on the household server. Human-assisted personal-mail review may also involve the operator’s AI assistant. Google provides Gmail authorization, reading and delivery; Apple supplies selected photos; NWS/NOAA provides weather. The public web host handles website requests.
6. Storage, access and security
OAuth tokens, message records, attachments, household settings and calendar data are stored in private runtime directories on the operator-controlled server, outside the public website and source distribution. File permissions, display pairing, request validation and configured recipient restrictions limit access. Household display access is shared, rather than a separate login for each person. The current private dashboard uses local-network HTTP; trusted TLS and broader access controls remain planned improvements. These measures do not guarantee protection against every threat.
7. Sharing and use limits
Private household data is not published on this website or sold by SniperFrame. Data is disclosed to the processing providers described above as needed for configured functions, and reminder content is shared with approved recipients. The operator does not use Gmail data for advertising, sale or training generalized AI models. Provider-side handling is governed by the applicable provider account settings and terms; this policy does not promise zero provider retention or exclusion from model training independently of those settings.
8. Retention and deletion
There is currently no automatic retention or deletion schedule for imported messages, derived notes, attachments, downloaded photos or review records. They remain on the private server until the operator removes them. Revoking Google access stops future authorized API access; it does not remove existing local copies. Participating household members can ask the operator to disconnect an account or remove their local data, including derived records. Any operator-held backup copies must be considered separately; provider-side retention follows the provider’s rules.
9. Your choices and contact
You may decline authorization or revoke SniperFrame’s access in your Google Account’s third-party connections settings. Contact Leo directly through your established household contact channel, or use the support email displayed on the Google consent screen, to request access, correction, deletion or disconnection. Please do not submit private messages, medical information or tokens through public channels. This service is not open to public registration; a parent or guardian manages information about children in the household.
10. Public website and changes
The published website uses no analytics scripts, advertising trackers, forms or application cookies. Its hosting server may record request information such as IP address, time, requested URL and user agent in access logs; configuration and retention are controlled by the site operator. Links to other websites follow those providers’ policies. Material changes to the project’s data practices will be reflected here with an updated date.
Manage Google account connections ↗
11. Optional Google Maps travel estimates
When the operator enables travel estimates, SniperFrame sends the fixed home origin, an operator-confirmed destination, departure time and driving options to Google Maps Platform. It does not send the event title, patient identity, source email or attachment. A destination may itself reveal sensitive information. The API key remains on the server. Request counters persist locally; route responses are not stored on disk. Opening a Google Maps link shares its origin and destination with Google and the browser. This feature is optional and can be disabled by the operator.