Privacy

About Coalesce

Coalesce: Grow in Spirit is operated by Shahrour Marketing LLC. For privacy questions, contact Joseph at joseph@blkbrdadvertising.com. This notice describes the Coalesce beta. The on-device sky-location section reflects the optional location feature in build 61.

Account information

When you create an account, Coalesce sends your email and password to Firebase Authentication over an encrypted connection. The app does not persist your password. It stores a session credential in this device’s private Keychain so you can remain signed in.

Your private Profile and birthday

Your Profile shows the email returned by the signed-in account. You may optionally add a name and full birthday, including the year, during signup or later. These fields are stored separately for each account in this device’s protected, non-synchronizing, device-only Keychain; they are not uploaded to Coalesce, included in app analytics, shared with companions or widgets, or requested from Google or Apple. Birthdays are stored as Gregorian calendar dates without a time zone and are not used as age verification. Greetings use only the month and day. Earlier full dates keep their actual year; incomplete month/day entries receive no guessed year and must be completed before enabling a birthday reminder.

A separate birthday-reminder choice starts off. If you enable it and allow notifications, Coalesce schedules one upcoming reminder on your device with a generic message, without your name, birthday, account identifier, scripture or location. February 29 is observed on February 28 in non-leap years. Opening the app renews the next occurrence and reconciles the device time zone; iOS controls delivery. Turning this reminder off, removing the birthday, signing out or changing accounts withdraws app-managed pending and delivered birthday reminders when handled by the app; alerts already seen cannot be recalled.

You can edit or remove these optional fields in Profile. Signing out hides them but keeps them for the same account on this device; the app removes them when its account-deletion request is confirmed. This does not provide cross-device profile synchronization. These features describe build 66 and later where available.

Optional Apple and Google sign-in

Where available, Apple or Google can authenticate you through Firebase instead of an email/password login. Coalesce requests basic identity information only: name, email and the provider’s account identifier, not birthday, contacts or additional Google permissions. Connecting another sign-in method to an existing Coalesce account requires your explicit choice, including consent to associate an Apple private relay identity. Coalesce does not merge accounts merely by matching names or emails; its existing Firebase account identifier remains the app’s identity.

Coalesce keeps its Firebase session credential in protected Keychain storage. Google’s SDK may also cache provider credentials in its own protected storage during authentication. The app calls SDK sign-out when that flow completes or is invalidated; a process interruption before cleanup can leave SDK-managed cache until a later cleanup. That separate cache does not authorize access to Coalesce. Provider responses are not recorded in Coalesce application logs. Apple-connected account deletion requires fresh Apple authentication and successful authorization revocation after confirmed content cleanup; cancellation or failure does not mean the account was deleted.

Google’s sign-in services process network information, including IP addresses that can indicate general location for fraud prevention. Its bundled SDK privacy manifest also declares linked name, email, phone number, coarse location, user/device identifiers, usage data and other data, with app-functionality and/or analytics purposes, and declares no tracking. These vendor declarations extend beyond the basic OAuth permissions shown by Coalesce. Coalesce does not request a phone-number scope or upload Living sky coordinates; Google may separately request information on its own sign-in pages. We retain the vendor manifest and account for it in release privacy reporting rather than treating missing app fields as proof of no provider collection. See Google’s sign-in privacy information and Google’s privacy policy.

Information stored by the service

Firebase stores your account identifier, receiving preferences, accepted connections, invitations, sharing permissions, explicitly shared passage references, optional notes, Together posts, reactions, comments, reports and deletion-request records. Scripture and edition choices may reveal religious interests or beliefs.

How it is used

These records support authentication, private sharing, recipient-controlled widgets, abuse controls and account management. Your reading history and saved passages are not automatically published or synchronized to Coalesce’s Firebase backend.

Information on your device

Reading preferences, saved passages, reading history, personal widget settings and sky-location preferences are stored locally. Personal widget settings and the sky-location preference are shared between Coalesce and its widgets through their private App Group.

You can select a city manually or optionally allow a one-time location request while using the app. Coalesce rounds the resulting coordinates to 0.1 degree and stores only that approximate area, an update time and the device time zone. Coalesce does not retain raw coordinates or movement history, upload this location information, send it to analytics, request geocoding, track location in the background or use the compass. Device backups remain subject to Apple’s settings and services.

In Living sky, Off removes the saved device area, and selecting a city replaces it. Revoked location permission clears the device area when next detected by the app; an existing widget display may remain until iOS refreshes it. Signing out does not clear this device preference.

Optional notifications

Morning and evening reading reminders, where available in your beta build, are scheduled on your device. Their times and choices stay local.

Remote notifications are an optional pilot feature. If you separately enable shared-passage alerts or updates from Coalesce, the app asks for Apple’s notification permission. Coalesce’s notification service receives your account identifier, this app installation’s identifier and security proof, Apple’s device notification token, your category choices and consent version. It stores a hashed installation identifier and proof, the device token and account association, category choices, registration-update and expiry times, and a revision that protects against outdated registration requests. These identifiers are linked to your account; they are not anonymous. The app keeps its token and installation proof in this device’s private, non-synchronizing Keychain.

For attempted alerts, the service also stores a recipient and registration reference, a shared-item or announcement reference, an attempt time and a technical outcome. These records help prevent duplicate alerts and open the correct item. They do not copy scripture or personal notes, but their references can link to existing sharing records. An accepted attempt does not establish that an alert was displayed or that a passage was read.

Alerts contain only a generic message and an opaque reference that Coalesce checks when you open it. They contain no scripture text, personal note, sender identity or location. Notification choices do not change sharing, receiving or widget permissions.

Notification providers, retention and controls

Google Firebase and Google Cloud process account verification, notification registrations and routing records for Coalesce. The notification database is configured in us-east4 in the United States. Apple Push Notification service receives the device token and generic alert for delivery. Provider infrastructure may process network and operational information under its own arrangements. Coalesce’s application logs do not record notification tokens, request bodies, private passages or authentication credentials; this does not mean provider request or security logs are absent.

A registration becomes ineligible for new alerts 30 days after its most recent registration update unless renewed. Notification-service links stop resolving after 24 hours. Neither deadline automatically deletes stored records. Automatic notification cleanup is not enabled in this pilot; expired registrations and technical delivery records may remain until an implemented removal action or authorized cleanup. Remaining notification metadata is also subject to the beta’s manual account-deletion cleanup process. You can contact the privacy address above to request removal.

You can switch either remote category off in Coalesce, revoke notification permission in iOS Settings or sign out. Switching all remote categories off or signing out attempts to remove the active server registration and token association. When the app next detects revoked iOS permission, it clears its remote choices and attempts the same removal. If the device is offline or the request fails, server withdrawal remains pending. Already queued generic alerts may still arrive, and technical records can remain. Signing out does not erase the installation proof or token from this device’s Keychain; uninstalling may not erase Keychain data.

Sharing and widgets

Sharing requires an accepted connection and appropriate receiving permission. Trusted-feed permission is separate. Your own widget selection takes priority. Current widgets do not display private notes or sender identity. Scripture placed on a Lock Screen may be visible to someone looking at that screen.

Access and security

Private sharing is access-controlled, but is not end-to-end encrypted. Authorized project operators can access backend records for support and administration. Recipients may retain copies or screenshots that Coalesce cannot remotely erase.

Providers and diagnostics

This build contains no advertising, Google Analytics or Crashlytics SDK. Firebase may process network information for authentication security and abuse prevention. Apple TestFlight separately provides beta usage metrics, crash reports and submitted feedback to developers.

Processing location

The Firestore database is configured in the United States, in us-east4. Authentication and provider operations follow Google’s applicable processing arrangements.

Retention

Account records remain until deletion or another implemented removal action. An invitation becoming unusable does not automatically erase its record. Account deletion requires manual cleanup in this beta. Some records remain afterward, including deletion receipts, relationship/safety metadata and other participants’ independent content. These retained records currently have no automatic expiry configured. Provider security logs follow the provider’s retention practices.

Your controls

You can pause receiving, revoke trusted-feed permission, disconnect, block, sign out or request deletion. Signing out clears Coalesce’s stored session and shared-account widget selection while retaining personal reading preferences. Removing the app is not equivalent to deleting the server account and may not remove Keychain credentials.

Website analytics

With your permission, coalescely.com uses Google Analytics cookies to understand visits to our marketing pages, traffic sources, device/browser information and clicks on a few general website buttons. We do not enable advertising features or send private app readings, passage content, Together activity, form values, names, email addresses or account identifiers to website analytics. Personal query strings and full referring-page addresses are not forwarded. Privacy, support and account-deletion pages are not measured.

You can decline analytics or change your choice using Analytics settings in the footer. Declining does not affect your use of the website or app. A browser Global Privacy Control signal keeps analytics off. Your choice is remembered in this browser. This optional website measurement is separate from the Coalesce app described above. Google’s privacy policy explains Google’s processing.