Privacy Policy

Last Updated: May 26, 2026

1. Scope

Borrowed Fire is the company I use to publish the apps I build. This Privacy Policy explains how Borrowed Fire LLC handles information for the public products currently listed on borrowedfire.com: Fated Pages, Jurni, and NextCatch.

This policy does not describe unpublished experiments, internal tools, or work-in-progress products unless they are made public and linked to this policy.

2. Information I Process

2.1 Information Stored on Your Device

The apps I publish store information locally so they can work quickly, offline, and without sending more to a server than the feature needs. This may include:

• App settings and preferences
• Cached event, book, or trip data
• Local reminders and notification preferences
• Subscription status cached for offline access
• Jurni trip content stored locally for offline use
• Fated Pages taste choices, saved books, reading signals, and recommendation state

Local app data may still be included in device backups or device-account services controlled by Apple, Google, or your operating system settings. That backup behavior is separate from Borrowed Fire's backend. Deleting an app may not delete every backup copy controlled by your platform account.

2.2 Fated Pages

Fated Pages is a romantasy recommendation product with a public website and iOS app. If you email support or request product updates, I use your email address to respond to that request.

The Fated Pages iOS app requires Sign in with Apple and an active subscription after onboarding. App access after that gate, including Browse, is not available unless the subscription gate is satisfied.

Fated Pages stores reader state on your device, including taste choices, selected trope or preference markers, saved books, shelf state, reading and feedback signals, recommendation runs, onboarding state, and cached subscription state. When you are signed in, the app may send reader-sync payloads to Supabase. Those payloads can include selected options, feedback events, recommendation-run context, reader signals, and catalog version. The current backend stores account/profile rows, book feedback events, calibration events you submit, and subscription entitlement records.

Fated Pages uses Apple for Sign in with Apple and App Store purchases, Supabase for account and app backend features, Apple StoreKit purchase data and RevenueCat where applicable for subscription entitlement checks, and TelemetryDeck for privacy-focused product analytics. Product analytics may include app interaction events and non-payment product parameters such as book slugs, selected markers, plan identifiers, or purchase-flow state.

Browse sends you outside the app to Apple Books or Amazon search pages for books you are interested in. I do not use affiliate links for those Fated Pages book-search links.

The Fated Pages website is hosted on Cloudflare.

2.3 Jurni

Jurni is a trip planner. Trip content can include itineraries, expenses, documents, polls, photos, travel notes, and locations you choose to add. Jurni stores trip data locally on your device and uses sync and sharing services for features that need them.

Jurni uses Sign in with Apple and supporting backend services for account, sync, invite, sharing, and support features. Account-related information may include your Apple-provided user identifier, display name, email address or relay email, and server account identifier.

Passport numbers, Known Traveler Numbers, Global Entry numbers, and travel-wallet identifiers are stored in the app's local device storage and are not sent to my backend. Because they are local app data, Apple may include them in encrypted device backups, iCloud backups, or device-account recovery systems depending on your iOS settings and backup configuration. I do not receive those fields through Jurni's Supabase backend.

Jurni trip content is encrypted before server sync. I cannot read decrypted trip content from the backend. The backend stores encrypted trip payloads and the metadata needed to make sync and sharing work, such as trip identifiers, timestamps, membership, roles, invite state, access-control information, encrypted trip-key grants, and account/profile records.

If you submit a support report, Jurni may store the information you choose to provide, plus limited diagnostics. Support reports are a user-initiated exception to the normal encrypted-trip-content boundary, so do not include sensitive details in a support request unless you want me to review them for support.

2.4 NextCatch

You can browse NextCatch event information without creating an account. Authenticated features, including raid rooms, require limited account and profile data so those features can work.

NextCatch may process:

• Account and authentication data when you sign in
• Trainer profile details for raid features, such as trainer name, trainer code, optional team, and trainer level
• Raid participation and reliability data, including queue state, room participation, checkpoint confirmations, missed invites, removals, timeouts, and feedback you submit
• Push notification tokens and notification preferences
• Subscription entitlement status for NextCatch+
• Raid screenshot verification results when a host chooses to use screenshot verification, such as OCR text, detected boss name, expected boss name, verification status, confidence, detected weather boost, and whether the host accepted verification risk

NextCatch raid screenshots are processed locally for OCR. Raw screenshot images are not uploaded by the screenshot-verification flow, but the derived OCR and verification facts listed above may be sent to the backend for trust, correction, and reliability purposes.

Public raid-room browsing uses a limited lobby projection. It may show lobby-card fields such as boss, capacity, participant count, weather boost, host trainer name, host level, host team, and a reliability label. Trainer codes, invite codes, host account IDs, private notes, and lifecycle internals are not part of the public lobby listing. A host trainer code is revealed only through raid-room flows that need it, such as an authorized join or active-room recovery.

NextCatch does not connect to your Pokemon GO account and does not collect your Pokemon GO login credentials.

2.5 Purchases and Subscriptions

Some products may offer optional paid features or subscriptions. Purchases are handled by the platform store where you bought them, such as Apple's App Store or Google Play. Borrowed Fire does not receive your payment card number, billing credentials, or full store account credentials.

RevenueCat may be used to validate subscription status and unlock paid features. Subscription records may include product identifiers, entitlement status, store platform, transaction identifiers, purchase dates, expiration dates, and related validation metadata.

2.6 Analytics and Diagnostics

Some apps use privacy-focused product analytics, such as TelemetryDeck, to understand whether features work and where the product needs attention. These signals are not used for advertising, are not sold, and are not used to track you across other apps or websites.

Crash reports may be provided through Apple's or Google's platform tooling if you have enabled those reports on your device. Some apps also keep local crash breadcrumbs or diagnostic reports on your device so you can choose whether to share them with me for support.

3. Information I Do NOT Collect or Use

I do not collect or use:

• Advertising identifiers for ad tracking
• Personal data for sale to data brokers
• Pokemon GO login credentials
• Payment card numbers or billing credentials
• Fated Pages affiliate-link clicks or affiliate purchase attribution for Apple Books or Amazon book-search links
• Your contacts, messages, or photos except for files or images you explicitly choose to use in an app feature

4. Device Permissions

The apps may request permissions only when a feature needs them:

• Notifications: To send reminders, raid-room updates, or time-sensitive app alerts you enable.
• Calendar: To add events to your calendar at your request. The app writes the event you choose; it does not read your existing calendar data for advertising.
• Camera and Photo Library: To scan or import documents, images, QR codes, or screenshots you choose to use.
• Files: To import documents you select.

You can revoke permissions at any time through your device's Settings app.

5. Third-Party Services

I use third-party services only where they support the product feature, hosting, purchase, sync, analytics, or support flow. Depending on the product and platform, these may include:

• Apple for App Store purchases, Sign in with Apple, device backups, iCloud backup behavior, account recovery behavior, crash reports, and device platform services
• Google for Google sign-in, Google Play purchases, Android push delivery, and Android platform services where available
• Supabase for authentication, database, realtime, storage, support, and sync features
• Cloudflare for website hosting and security
• RevenueCat for subscription entitlement validation
• TelemetryDeck for privacy-focused product analytics

The apps may also link to external websites, such as official event pages, storefronts, app stores, or book retailer links. I am not responsible for the privacy practices of those external sites.

6. Data Security

I use reasonable technical safeguards for the data these products need. For example, local data is protected by your device's security features, network traffic uses encrypted connections, and Jurni trip content is encrypted before sync and sharing.

No system is perfect. Keep your device, Apple ID, Google account, and app store accounts secure.

7. Data Deletion

You can delete local app data by deleting the app from your device. Product-specific deletion controls may also be available inside the app.

• Fated Pages account data, support emails, or product-update request emails can be deleted by contacting me.
• Jurni account and synced data can be deleted through in-app account deletion where available.
• NextCatch account deletion is available in the app or through the account-deletion flow provided on nextcatchapp.com.

8. Children's Privacy

These products are not directed to children under 13. I do not knowingly collect personal information from children under 13. If you believe a child has provided personal information, contact me so I can remove it.

9. Your Rights

Depending on where you live, you may have rights to access, correct, delete, or receive a copy of your personal information. The fastest path is usually the app's own settings or account-deletion flow. You can also contact me.

10. Changes to This Policy

I may update this Privacy Policy from time to time. Changes will be reflected by updating the "Last Updated" date above. Continued use of these products after changes constitutes acceptance of the updated policy.

11. Contact Me

If you have questions about this Privacy Policy, please contact me at:

By using these products, you acknowledge that you have read and understood this Privacy Policy.