Come Aside Privacy Policy

Last updated: July 12, 2026

Overview

Come Aside is a Catholic companion app for daily readings, journaling, devotional practice, and reminders. The core daily loop is local-first. Account sync, AI reflection suggestions, Scripture Companion suggestions, personalized carrying prayers, and generated review audio artifacts are optional.

Information You Provide

Come Aside may store the following information when you choose to provide it. Some journal, devotion, milestone, and onboarding content may reveal religious practice or beliefs.

• Name and onboarding profile answers.
• Journal reflections, moods, bookmarks, and optional imported journal text.
• Optional voice reflection files stored on the device.
• Optional AI reflection or Scripture Companion requests when you choose a draft, saved entry, transcript text, saved review, or review date range and ask Come Aside to prepare a suggestion.
• Optional personalized carrying-prayer requests when a signed-in Come Aside Plus user asks for a prayer. These requests always include the current carrying note and may include a small amount of relevant journal context selected on the device if the user has chosen journal personalization.
• Optional generated review artifacts, such as spoken reflections and prayer song audio, when you choose to create them from a saved monthly or seasonal review.
• Devotion intentions and check-ins.
• Sacramental milestone dates and notes.
• Reminder and app settings.
• Optional Mass finder area search text stored on the device.
• Email address if you choose to create an account for sync.
• Email address, confirmation status, unsubscribe status, timezone, and send history if you choose to receive the daily email.
• Website visit and daily email engagement information such as page views, referral source, email opens, email clicks, delivery status, bounce status, complaint status, and unsubscribe events.
• Anonymous app product-interaction events, such as app opens, screen views, onboarding completion, saved-entry counts, kept-line counts, review counts, daily-path completion, devotion or Rosary completion counts, paywall results, purchase-success events, and app error signals.

How Information Is Used

Come Aside uses your information to:

• Show your journal and devotion history.
• Choose encouragement through transparent, rule-based personalization from your onboarding answers, current liturgical season, and selected mood.
• Send local reminder notifications if enabled.
• Open Google Maps when you choose to look for nearby Catholic churches, Mass, Confession, or Adoration.
• Prepare optional AI reflection and Scripture Companion suggestions only after you choose the source and ask for a suggestion.
• Compose an optional personalized carrying prayer and choose one passage from Come Aside's approved Scripture catalog when a signed-in Come Aside Plus user asks for that prayer.
• Create optional review artifacts only after you choose a saved monthly or seasonal review and request that artifact.
• Sync your data across devices if account sync is enabled.
• Manage subscription status if you subscribe to Come Aside Plus.
• Send the daily email if you opt in and confirm from your inbox.
• Understand whether the public website and daily email are working, which pages and sources lead to signups, and whether emails are delivered safely.
• Understand whether the app is helping people reach meaningful actions, such as completing onboarding, returning to the daily path, saving a reflection, keeping a line, opening a review, completing a devotion, or starting a subscription.

Come Aside does not use your information for advertising, third-party ad tracking, or hidden background analysis of your journal.

Local Storage

The core app data is stored on your device. If you do not enable account sync, your journal, milestones, devotions, and profile remain local to that device except for operating-system services such as backup that you control through your device settings.

Optional AI Reflection Suggestions

When reflection suggestions are enabled, Come Aside can prepare short, editable suggestions such as titles, summaries, follow-up questions, cleaned text, Scripture Companion passages, review notes, and memory candidates. AI suggestions are requested only when you choose the draft, saved entry, transcript text, saved review, or review date range to use. Suggestions are not saved unless you accept or keep them.

Selected text for an AI request is sent to Come Aside's backend and OpenAI to process that request. Scripture Companion requests also include Come Aside's approved passage catalog so the provider can choose one catalog ID. Come Aside does not send hidden journal history, run background AI analysis, or create a hosted vector store for private journals by default. Local voice recording files, photos, videos, and attachment file paths are not sent as AI source data. If you use text from dictation or a transcript, only the selected text is used for the request you choose.

When cloud suggestions are used, Come Aside keeps lightweight usage metadata so the monthly reflection allowance can be shown and applied. Usage metadata may include the request kind, date, processing location, provider, model, and source identifiers such as entry or review IDs. It does not store raw request text or journal text.

AI suggestions are not a priest, confessor, therapist, spiritual director, or replacement for personal pastoral care. Come Aside applies safety checks before preparing suggestions and may decline to generate a suggestion for some requests.

Optional Personalized Carrying Prayers

Personalized cloud carrying prayers are available in English, Spanish, Portuguese, French, German, and Italian to signed-in Come Aside Plus users. The prayer is generated directly in the app language, with Come Aside's local prayer-and-verse experience as the fallback in every language. The first time an eligible personalized prayer would send private text to the cloud, Come Aside asks the user to choose one of three modes: personalize with the journal, use the current note only, or keep prayer entirely on the device. The choice is saved and can be changed later in Settings > Privacy. Come Aside does not ask again for every prayer unless a future material change to the processor or source scope requires a new choice.

Every personalized request uses the carrying note entered for that prayer. In journal mode, Come Aside may consider eligible journal material on the device and send only the context selected for that request: no more than three relevant excerpts totaling 1,200 characters, up to four relevant kept-memory details, and up to six relevant learned prayer-memory details. The whole journal is not sent to the backend or OpenAI. Journal and memory identifiers, source identifiers, dates, counts, and favorite flags are removed before the provider request. Entries excluded from suggestions, deleted or missing source material, Examen entries, confession-preparation entries, locked journal material that has not been unlocked, voice files, photos, videos, attachment paths, email, location, parish, community, device identifiers, and notification content are not used for journal-informed prayer.

Come Aside sends the bounded request through its backend to OpenAI and disables OpenAI application response storage for the request. Under OpenAI's default API data controls, request and response content may still be retained in abuse-monitoring logs for up to 30 days unless approved retention controls apply. OpenAI states API data is not used to train its models unless the API customer opts in. OpenAI's data-controls documentation is at https://developers.openai.com/api/docs/guides/your-data.

The provider returns an original first-person prayer and one identifier from Come Aside's approved Scripture catalog, not Bible text. Crisis and pastoral-boundary checks run before generation, and those paths use Come Aside's static care experience instead of a personalized response. Provider failure, timeout, missing entitlement, exhausted allowance, disabled personalization, offline use, or a signed-out session returns the local prayer experience.

Come Aside may keep up to 24 short prayer-memory details locally to make later user-requested prayers more relevant. At most six relevant details can be used in one request. These details may sync with the user's account when account sync is enabled, and the user can clear them from Settings > Privacy. An unkept generated prayer is not stored as a journal entry. A prayer is stored as journal content only when the user chooses to keep it.

For entitlement, allowance, idempotency, reliability, and cost control, Come Aside keeps a metadata-only server ledger for up to 13 months. It can contain the signed-in user ID, one-way request and completion fingerprints, status and timestamps, model name, input and output token totals, and a short failure code. It does not contain the carrying note, journal excerpts, prayer-memory text, prompts, generated prayer, Scripture text, source identifiers, or relevance scores. Clearing prayer memory does not restore spent allowance or erase this accounting ledger. Deleting the sync account removes ledger rows tied to that account.

Optional Review Audio Artifacts

When you create a spoken reflection or prayer song from a saved monthly or seasonal review, Come Aside uses the saved review and the details shown in the app before generation. Weekly reviews stay note-only. Song drafts are prepared locally in the app, then the audio request is sent to Come Aside's backend with provider selection handled on the server.

Come Aside may use Google Gemini text-to-speech for spoken reflections and Google/Lyria for prayer song audio. Google credentials stay in Supabase Function secrets and are not included in the app. Generated audio is stored in a private Supabase Storage bucket under your account. Come Aside stores audio metadata such as provider, model, storage path, mime type, duration when available, and an expiring signed playback URL. Backend logs for these requests are metadata-only and do not include lyrics, journal text, or request text.

Prayer songs are for private reflection. They are not liturgical music, not Mass music, and not a replacement for prayer, confession, pastoral care, or spiritual direction.

Sharing To Other Apps

When you choose a personal moment from Apple's Journaling Suggestions picker, Apple shows the picker and Come Aside receives only the moment you select. That moment stays with the reflection you save. You can remove the selected moment before saving the reflection. If the selected moment includes a place, city, workout, movement, or step-count detail, that chosen detail may be saved with the reflection.

When you choose Send to Apple Journal, Come Aside opens the native iOS Share Sheet with a text version of the selected reflection. You choose the destination and approve anything saved outside Come Aside. Come Aside does not read Apple Journal entries, write to Apple Journal in the background, or keep Apple Journal content synced with Come Aside.

When you choose Export my data, Come Aside opens the native share sheet with a text JSON copy of your profile, journal entries, devotion records, sacramental milestones, and non-sensitive settings. Local voice reflection files and generated review audio files are not included in the text export.

Mass Finder And Maps

Mass finder does not request device location permission. You may optionally type a city, postcode, parish area, or other search area. Come Aside uses that text to build a Google Maps search link, then opens the Google Maps app if it is installed or Google Maps in your browser if it is not.

Come Aside does not receive Google Maps results, store GPS coordinates, sync typed Mass finder place text, or use map searches for tracking. Google Maps handles the search after you leave Come Aside under Google's own terms and privacy policy.

Daily Email

If you opt in through the website or the app, Come Aside stores your email address and basic mailing-list state so it can send the daily email, prevent duplicate sends, and honor unsubscribe requests. Daily emails begin only after you confirm from your inbox. Every daily email includes an unsubscribe link.

The daily email contains the daily reading citations, a public-domain Scripture excerpt from the World English Bible Catholic Edition, one original Come Aside reflection, and one question for your journal. It does not use your journal entries, AI suggestion history, sync data, devotion intentions, milestones, or account profile.

Come Aside uses Supabase to store daily email subscription state and Resend to deliver email.

Website And Email Analytics

When you visit the Come Aside website, Come Aside records limited first-party analytics such as page path, referrer host and path, UTM campaign fields, country and region from hosting headers, language, timezone, device/browser information, viewport size, and anonymous session and daily visitor hashes. Come Aside does not use analytics cookies or store raw IP addresses for website analytics.

When you receive the daily email, Come Aside records subscription events, send history, open and click events when email clients load images or links, delivery events, bounce events, complaint events, and unsubscribe events. Email open numbers are estimates because some email apps load images for privacy and some block images entirely.

Come Aside uses website and daily email analytics to understand whether the website and daily email are working and to improve deliverability. This information is not used for advertising or third-party ad tracking.

App Analytics

When app analytics are enabled, Come Aside sends privacy-safe product-interaction events to PostHog using an anonymous per-install ID. These events help Come Aside understand whether people are opening the app, completing onboarding, reaching the daily path, saving reflections, keeping lines, opening reviews, completing devotions, and seeing subscription screens.

App analytics send counts, booleans, screen names, and event names only. Come Aside does not send journal text, kept-line text, prayer intentions, mood notes, names, email addresses, AI prompt text, generated reflection text, specific devotion content, or specific prayer content to PostHog. App analytics are not used for advertising, retargeting, cross-app tracking, or cross-website tracking.

Account Sync

If you enable account sync, Come Aside uses Supabase to authenticate your email address and store synced app data for your account. Sync is optional. Synced app data may include accepted AI suggestion records, cloud reflection usage metadata, kept memories, personalized prayer memory, generated review artifact metadata, and generated review audio files so your choices can follow your account.

Subscriptions

Come Aside uses RevenueCat to manage subscription status and restore purchases. Payment processing is handled by Apple through the App Store. RevenueCat receives a generated app user ID for this device. When a user signs in, Come Aside associates subscription status with the Supabase user ID so the backend can verify access to personalized carrying prayers. Come Aside does not use the onboarding name as a billing identifier.

Notifications

If you enable reminders, Come Aside schedules local notifications on your device. You can turn these off in the app or in iOS Settings.

Data Deletion

You can remove local app data from the Come Aside Plus gate, from Settings > About > Delete local data, or by deleting the app from your device. This removes local profile, journal, devotion, milestone, reminder, local voice reflection data, local AI suggestion history, kept memories, personalized prayer memory, account session, and generated billing identifier from that device. You can also clear AI suggestion history, kept memories, and personalized prayer memory from Settings > Privacy. Clearing personalized prayer memory does not restore spent allowance or remove the metadata-only accounting ledger. Deleting a saved review removes generated review artifacts tied to that review. If you create a sync account, you can delete the sync account and synced data from Settings > Account & Sync; Come Aside deletes generated review audio objects and carrying-prayer accounting rows tied to that account before or as part of account deletion. If you receive the daily email, you can unsubscribe from any daily email. You may also contact the support address below for help with deletion requests.

Children

Come Aside is not directed to children under 13.

Contact

For privacy questions or deletion requests, contact:

hello@comeaside.app

This is the same support address used for Come Aside help and accessibility questions.

Changes To This Policy

Come Aside may update this policy when the app changes. The published policy will show the latest update date.