How Ifrit Personalizes Wake-Ups Without Collecting Everything
Last updated May 20, 2026
Ifrit's privacy posture is simple: collect the minimum v1 data needed to schedule alarms, verify Ifrit Plus access, and prepare a short personalized wake-up message. Personalization should make the first minute clearer, not build an advertising profile.
What Personalization Uses
Ifrit may use your first name or nickname, alarm schedule, selected persona, briefing preferences, approximate location context for weather, optional Google Calendar summary, subscription entitlement state, and generated audio metadata needed to serve the next alarm.
What Stays Optional
Weather, Google Calendar, news categories, and Words of Affirmation are controlled by app settings. Google Calendar is opt-in and uses a compressed day summary for wake-up context rather than storing full event payloads on the backend.
How AI Processing Fits
Ifrit uses AI services to generate the script and text-to-speech audio for Ifrit Plus. The prompt should contain only what is needed for the wake-up: persona, local context when enabled, selected topics, optional calendar summary, and the alarm's effective daypart/date context.
Reliability Still Comes First
Privacy-aware personalization should never make the alarm fragile. If fresh personalized audio is not ready for the upcoming alarm, Ifrit should ring with the default/fallback sound instead of using stale personal context.