PRIVACY POLICY

1. Local Data

Most personal sanctuary data is stored in your browser on the device you are using. This can include local prayer conversations, journal sessions, journey progress, prayer intentions, preferences, and local theme memory.

• Lay It Down: Text entered into Lay It Down is intentionally not saved to local storage or uploaded as part of encrypted backup.
• Journal: The journal works locally without requiring sign-in. Clearing local browser data may remove this information unless you have created an encrypted backup.
• Bible: Public-domain Scripture files may be cached in your browser for offline reading and search.

2. Ask Deeper Cloud Processing

Ask Deeper is optional. When you choose it, the question you submit and limited recent conversation context needed to answer it are sent over an encrypted connection to our backend and the configured cloud AI provider. Local prayer features do not need this cloud request.

Cloud AI providers can change as the service evolves. Their processing is subject to the provider configuration and applicable provider terms. We do not intentionally send Lay It Down confession text through Ask Deeper.

3. Accounts, Entitlements & Abuse Prevention

Signing in is used for account identity, free Ask Deeper quotas, subscription entitlement, and optional Plus features. By default, signing in does not upload your journal, prayer intentions, spiritual-state summary, journey progress, or local conversation archive.

Limited technical information may be processed for security, rate limiting, fraud prevention, and service operation, including account identifiers and network information such as IP address.

4. Optional Plus Encrypted Backup

Plus users can explicitly create an encrypted cross-device backup. Selected local data is encrypted in the browser using AES-256-GCM with a key derived from the user’s backup passphrase before the encrypted ciphertext is uploaded to Firebase.

• The backup passphrase is not stored in the backup database.
• We cannot decrypt or recover a backup without that passphrase.
• Encrypted backup is off by default and is created only when the user presses the backup action.
• Users can delete their encrypted cloud backup without deleting local data on their device.

5. Analytics

We use product analytics to understand feature usage and improve the application. Analytics events may include actions such as opening a feature, changing a mode, or beginning checkout. We do not deliberately include the text of private prayers or journal entries in analytics event parameters.

6. Payments

Subscription checkout is handled by Lemon Squeezy, our payment provider / Merchant of Record. Payment-card details are entered into the payment provider’s checkout rather than stored by the 1into1 application.

7. Service Providers

• Firebase / Google Cloud: Authentication, entitlement records, and optional encrypted backup storage.
• Configured cloud AI provider: Processes Ask Deeper requests when that feature is used.
• Google Analytics: Product usage analytics.
• Lemon Squeezy: Checkout, payments, and subscription lifecycle events.

8. Your Controls

You can clear local journal/history from inside the application, avoid Ask Deeper and use local features only, choose not to create an encrypted backup, restore a backup with your passphrase, or delete the encrypted backup stored for your account.

For account or privacy inquiries, contact info@1into1.com.