Privacy Policy

Inflection Point is an identity, planning and reflection app. This policy explains the app’s information handling and this website’s practices. Contact the developer at nick@nickrae.net with privacy questions.

1. Journal and profile information

The app stores the information you enter, including your character name, visions and anti-visions, reasons, traits, goals, projects, quests, constraints, morning exercises, reflections and progress. Guided-reset records include saved morning responses, daytime pattern checks, evening reviews and links to the goals, projects and quests created from a reviewed plan. These records are part of your local journal. The app also stores settings, reminder preferences and purchase access, and preserves historical preview and usage records. The planned release has no free trial, ongoing free tier or subscription. There is no separate Inflection Point account or app-managed cloud journal sync.

You may choose a profile photo or take an avatar photo using the camera. The planned StoreKit release copies the chosen image into app-owned local storage. Camera access is requested when you choose to take a photo. The app does not automatically pass your saved avatar or chosen profile photo to Image Playground. You may separately choose a personal photo inside Apple’s system sheet. The app does not request your contacts or device location.

2. Optional AI: daily debriefs and avatars

Manual reflection does not send the entry to an AI generator. In the planned native release, an optional daily debrief uses Apple’s on-device Foundation Models framework. Your reflection, selected wins, violated constraints and relevant identity context are processed on your iPhone. The app does not upload that debrief input for generation or fall back to a cloud debrief service. Saving a debrief makes the result part of your local journal.

On-device debriefs require an Apple Intelligence-eligible iPhone, supported language and region, Apple Intelligence enabled and the model downloaded and ready. When the model is unavailable or cannot complete a request, you can use manual Quick Log instead. See Apple’s availability information. This does not mean all Apple Intelligence features run on device, or that every iPhone can generate debriefs.

Optional avatars use Apple’s system Image Playground. The planned native release first asks you to choose the text to share and agree to the explanation. This can include selected active traits, an optional character name and up to two vision descriptions. The app passes that selected text to Apple’s sheet, not to Rork, and does not supply a source photo. You can edit the description or explicitly choose a personal photo in the system sheet. The app receives the image you choose to use and saves it in app-owned local storage.

This app offers Apple’s Illustration, Animation and Sketch styles, without an external-provider style. Apple controls the system generation experience and processing. On iOS 27, Image Playground uses Private Cloud Compute, Apple’s server-based image models; this is separate from the on-device daily debrief. Read Apple’s Intelligence privacy information. Image Playground depends on a supported device, settings, language and region, network access and Apple’s system usage limits. Choosing a photo or taking a camera photo remains an alternative. No offline or unlimited avatar-generation promise is made.

Earlier versions: Expo versions and earlier native betas send AI debrief requests to Rork toolkit services. Those requests include the current reflection, selected wins, selected violated-constraint names, character name, visions and categories/reasons, anti-visions and categories/fear levels, and active traits and anti-traits, rather than every past reflection. Earlier Expo avatar requests include the first two vision descriptions. Earlier native betas also use Rork for avatars, with selected traits and optional character name and vision context. Earlier interfaces and consent controls may differ. These historical online requests are not made local by updating the app.

Rork and its service providers may process submitted context and output. Rork’s general Privacy Policy describes its services, but app-specific toolkit retention, training, human-review and deletion terms have not been confirmed. We do not promise immediate deletion, no retention, no training or no human access. Avoid sending information you do not want processed online. Local reset cannot delete copies already processed by an online provider. These unconfirmed toolkit terms concern historical Rork avatar requests and online debriefs, not a claim about Apple’s system Image Playground processing. Journal content can also leave the device when you export or share it, or through device backups.

3. Purchases and earlier beta services

Apple processes payment and maintains Apple purchase records. The app receives purchase/access information, not your full payment-card details. The planned StoreKit release uses Apple StoreKit directly and keeps a local ownership cache. It does not contact RevenueCat or bundle a third-party purchase analytics SDK.

Some earlier Expo versions and native beta builds use RevenueCat to validate and restore purchases and manage access, using an automatically generated app-user identifier and purchase/technical information. Earlier Expo code also attempted to share onboarding/profile fields, including character name, traits count and selected vision/anti-vision categories. Acceptance or retention of those additional fields has not been verified. Removing the SDK does not erase historical provider records. See RevenueCat’s Privacy Policy and Apple’s App Store privacy information.

Earlier Expo versions bundled the Rork toolkit SDK, which could send generation and app-lifecycle events to PostHog when enabled by the build configuration. This audit has not confirmed whether that conditional analytics path was enabled in a distributed beta. The planned StoreKit release does not include that SDK analytics path, advertising identifiers or a third-party crash/session analytics SDK. Apple may collect platform diagnostics under your Apple privacy settings.

4. Reminders, backups and exports

Optional morning, evening and daytime pattern-check reminders use Apple’s local notifications after permission; the app does not send journal text to a remote push-notification service. You can choose pattern-check times and change reminders in the app, or change notification permission in iOS Settings.

Apple device backups may include app data, depending on your settings. That is a platform backup, separate from an app-managed cloud sync or the planned StoreKit release’s local recovery backup. See Apple’s backup information.

Earlier Expo versions provide a partial JSON export containing identity, quests and daily logs; it is not a complete backup of all collections. The earlier native beta already includes journey export during full access. The planned StoreKit release provides complete JSON export, including saved guided-reset progress, reflections and applied-plan links, the rest of the journal and an embedded avatar when present. These journal records are also included in local recovery backups. Export and recovery of existing data remain available without a purchase. Purchase, historical preview/usage and reminder preferences are separate and are not included in that journey export. Native import replaces this device’s journey after confirmation. Copies you export leave app-controlled storage and remain wherever you save or share them.

5. Retention, reset and security

App content is stored in the device’s app sandbox. Native saves use iOS file protection and keep a previous valid local backup. These controls are not an end-to-end encrypted cloud journal or a guarantee of complete security.

Earlier Expo history: the free-tier retention logic can permanently remove daily logs older than its history window. Do not rely on the planned release’s saved-history promise for an earlier installed Expo version, or assume it can recover entries already deleted.

Earlier native beta history: a free-access history window limits visibility while retaining older saved entries.

Planned StoreKit history: lifetime access includes the full saved history, with no free-tier visibility window. The migration reads the legacy journal and retains the original for recovery until Reset all data. An unreadable journal is preserved for recovery rather than silently replaced. Real populated-device upgrade validation remains a release check.

In the planned StoreKit release, Reset all data removes the local journey, including guided-reset responses, reviews and applied-plan records, plus app-owned recovery copies, backups, avatars and local export files. It keeps purchase ownership and historical preview/usage records. Removing a displayed avatar can leave older app-owned image files until reset. Reset does not delete copies exported elsewhere, Apple backups or provider records. Earlier Expo reset behavior differs.

Apple and historical purchase providers retain records under their own practices. No fixed AI-provider retention period or provider-deletion deadline is promised here. Services may process information outside your country.

6. This website and support

This static website is hosted on GitHub Pages. Hosting providers may process request information such as IP addresses for operation and security; see GitHub’s Privacy Statement. The site has no integrated advertising, analytics script, tracking cookie or mailing-list form.

Launch-update and support links open your email app. Clicking does not send an email or automatically subscribe you. If you send a message, the developer receives your address, message and any attachments you choose to include. You can ask to stop launch emails or delete support records under our control. External links and email services have their own practices.

7. Your choices and requests

You can choose manual reflection, edit supported content, control reminders, use the export available in your version and reset local data. Saved daily logs do not have an individual deletion control; available edits depend on the version. Store and share exports privately.

For access, correction, deletion or other rights available under applicable law, contact nick@nickrae.net. We can help with records under our control and appropriate provider requests. We cannot remotely retrieve a journal stored only on your device or guarantee deletion of unidentified provider records. Do not send a journal or recovery file unless you choose to share it.

The app is not designed as a children’s service. Contact us if you believe a child submitted personal information through an online feature. We will update this policy when practices change and provide additional notice where required.