Privacy Policy

Introduction

Psalmlog, LLC (“Psalmlog,” “we,” “us,” or “our”) provides an AI-driven Bible-journaling platform at psalmlog.com (the “Website”), through the Psalmlog mobile applications (the “Apps”), and as a software-as-a-service platform (the “Platform”). The Website, Platform, and Apps together are the “Service.”

This Privacy Policy describes the information we collect, how we use and share it, the choices and rights you have, and how to contact us. It is part of, and should be read together with, our Terms of Service.

By using the Service, you confirm you have read and understood this Privacy Policy. If you do not agree, do not use the Service.

Intended Audience. The Service is operated from and directed to users in the United States. We do not target the European Economic Area, the United Kingdom, Switzerland, or other non-U.S. jurisdictions through localized languages, currencies, advertising, or other affirmative offering of goods and services to those markets. To the extent users in those jurisdictions access the Service on their own initiative, we honor the rights described in Section 13.4 on a voluntary basis. We will revisit this position if our marketing posture changes.

1. Information We Collect

1.1 Information You Provide

• Account information — name, email address, password (stored as a salted hash), and any optional profile information you choose to provide.
• Subscription and billing information — billing name, address, payment-card details (processed and stored by our payment processor, Stripe, Inc., not by us; we receive only a token and limited metadata such as the last four digits of the card and expiration), and subscription history.
• Journal content — text you type, voice-journaling text transcribed on your device (see Section 2), prompts you submit to the AI, scripture cards you create, and any other content you add to the Service.
• Communications — emails, support tickets, survey responses, and other messages you send us.
• Newsletter and marketing preferences — if you sign up for our newsletter or otherwise opt in to receive marketing communications.

1.2 Information Collected Automatically

When you use the Service, we and our service providers automatically collect:

• Device and browser information — IP address, device model, operating system, browser type and version, language settings, device identifiers (for mobile, the OS-provided advertising identifier where you have permitted it).
• Usage information — pages or screens viewed, features used, search queries within the Service, timestamps, referrer URLs, crash and diagnostic data.
• Approximate location — derived from your IP address (city/region level only). We do not collect precise geolocation.
• Cookies and similar technologies — see Section 5.

1.3 Information from Third Parties

• Payment information — limited transaction metadata from Stripe.
• If you sign in through a third-party identity provider (for example, Google) — basic profile information that the provider shares with us under your consent.

1.4 What We Do Not Collect

• We do not collect precise geolocation.
• We do not collect biometric identifiers (see Section 17).
• We do not collect government identifiers (Social Security numbers, driver's license numbers, etc.).
• We do not knowingly collect information from children under 13 (see Section 11).

2. Voice Journaling

Voice journaling is a feature of the Psalmlog mobile applications only. It is not available on psalmlog.com.

When you use voice journaling in the mobile Apps, your audio is processed on your device by the operating system's on-device speech-recognition framework (Apple's SFSpeechRecognizer with on-device mode enabled on iOS, and the analogous on-device speech recognizer on Android). The transcript is then handled as ordinary journal text under Section 3 below. The audio recording itself is not uploaded to our servers, not stored by us, and is discarded immediately after transcription on your device.

If we ever change this — for example, by offering optional cloud-based transcription for languages that on-device recognition does not support, or by adding voice journaling on the web — we will update this Section and provide notice before the change takes effect.

3. Journal Entries, AI Processing, and Sensitive Information

3.1 Journal Entries Are “Private Content”

Your journal entries (text, transcribed voice, prompts you submit, prayers, and any reflections you create) are “Private Content” under our Terms of Service and under this Privacy Policy. We store Private Content securely to provide the Service to you. Private Content is:

• accessible only when you log into your account;
• never sold to third parties;
• never shared with advertisers;
• never shared with other users;
• never used to train third-party AI models (see Section 3.3).

3.2 Sensitive and Special-Category Information

Journal content frequently includes information about your religious or philosophical beliefs and may include information about your mental or physical health, family circumstances, or other deeply personal topics.

Under California law (CPRA), religious beliefs, the contents of your communications, and health information are “Sensitive Personal Information.” Under EU and UK law (GDPR / UK GDPR), data revealing religious or philosophical beliefs and data concerning health are “special categories” of personal data that receive heightened protection.

We treat your journal content as sensitive in every jurisdiction. Specifically:

• We process this information only to provide the Service to you (delivering biblical guidance, indexing your entries, generating Output you have requested), to maintain security, to comply with legal obligations, to verify and respond to public claims about AI-generated Output (see Section 7), or with your explicit consent.
• We do not process this information for advertising, profiling, automated decision-making with legal or similarly significant effects, or any purpose unrelated to the Service.
• For users in the European Economic Area, the United Kingdom, or Switzerland, the legal basis for processing this special-category information is your explicit consent under Article 9(2)(a) GDPR, which we obtain at account creation. Where we access journal content to verify or respond to public claims about AI-generated Output as described in Section 7, we rely on Article 9(2)(f) GDPR (establishment, exercise, or defense of legal claims). You can withdraw your consent under Article 9(2)(a) at any time by deleting your account (which deletes your journal content) or by emailing support@psalmlog.com; withdrawing consent does not affect processing already carried out under Article 9(2)(f).
• For California residents, you have the right to limit our use of your Sensitive Personal Information; because we already limit use to the purposes above, exercising the right will not affect your use of the Service. To exercise it formally, use the “Your Privacy Choices” link in our footer or email support@psalmlog.com.

3.3 AI Processing

To generate biblical guidance, summaries, reflections, and scripture suggestions, your journal text is sent to a third-party AI service provider through a secure application programming interface (API). Our current AI providers are Anthropic, PBC (Claude family of models) as the primary provider and OpenAI, OpCo, LLC (GPT family of models) as a fallback.

Each provider processes your text under a contractual data-processing agreement that:

• prohibits the provider from using your content to train its foundation or fine-tuned models;
• prohibits the provider from retaining your content beyond the period necessary for immediate processing (typically zero retention or up to 30 days for abuse monitoring, per the provider's standard API terms);
• requires the provider to apply appropriate technical and organizational security measures.

We do not use journal content to train any AI model — our own or anyone else's. We may use de-identified, aggregated patterns (for example: “what fraction of users journal about anxiety”) to improve the Service, but we do not review individual entries for that purpose.

3.4 Health-Adjacent Information and the FTC Health Breach Notification Rule

Because journal entries may include information about your physical or mental health, including topics such as anxiety, grief, sleep, or relationships, the Service may collect “personal health record identifiable health information” within the meaning of the FTC Health Breach Notification Rule (16 CFR Part 318). We have designed our practices, security controls, and incident-response processes with that Rule in mind. See Section 10 (Breach Notification) for more.

The Service is not a covered entity under HIPAA and is not a medical device. It does not provide medical, mental-health, psychiatric, psychological, or pastoral advice. See Section 8 of our Terms of Service for important disclaimers, including crisis resources.

4. How We Use Your Information

We use the information described above to:

We do not use information for any purpose materially different from those listed without first updating this Policy and, where required, obtaining your consent.

5. Cookies and Similar Technologies

We use cookies, local storage, and similar technologies to operate the Service, remember your preferences, measure usage, and (where applicable and with your consent) for marketing.

We classify cookies into:

• Strictly necessary — required for the Service to function (e.g., authentication, security). These cannot be disabled.
• Functional — remember your preferences (e.g., language, display settings).
• Analytics — help us understand how the Service is used so we can improve it. We currently use Google Analytics 4 (configured with IP anonymization and no advertising features) and Amplitude for product analytics.
• Marketing — used (only with consent in jurisdictions that require it) to measure ad campaign performance. Marketing tags currently fired through Google Tag Manager (GTM-K3SJLD64) include Google Ads conversion tracking and Meta Pixel, among others. This list is illustrative and may not be exhaustive. Marketing tags are added, removed, and rotated from time to time as our advertising mix changes; we will update this Policy when the categories or purposes of marketing tags materially change.

Managing your choices. In the European Economic Area, the United Kingdom, Switzerland, and other jurisdictions that require it, we present a cookie consent banner on your first visit and any time your preferences expire. You can change your choices at any time via the “Cookie Preferences” link in our footer. In all jurisdictions, you can also configure your browser to refuse or delete cookies; doing so may affect Service functionality.

Do Not Track / Global Privacy Control. Most browsers offer a “Do Not Track” (DNT) signal. There is no industry standard for how DNT must be honored, and we do not currently respond to DNT signals. We do honor the Global Privacy Control (GPC) signal as a valid opt-out of sale and sharing for California residents and as an opt-out of targeted advertising for residents of other U.S. states whose laws recognize universal opt-out mechanisms. See Section 13.

6. How We Share Your Information

We share information only as described below.

6.1 Service Providers (Processors)

We share information with vendors that perform services on our behalf under contractual confidentiality and data-protection obligations. Categories include:

• Hosting and infrastructure — Vercel, Inc. (application hosting and edge network); Cloudflare, Inc. (bot protection and edge security); Supabase, Inc. (database and authentication backend).
• Payments — Stripe, Inc.
• AI processing — Anthropic, PBC (Claude); OpenAI, OpCo, LLC (GPT).
• Email delivery and transactional messaging — Customer.io (Peaberry Software, Inc.).
• Analytics — Google LLC (Google Analytics 4 and Google Tag Manager); Amplitude, Inc.
• Customer support tooling — Help Scout PBC.
• Audio synthesis — ElevenLabs Inc. (used to generate AI audio output for the Psalmcast feature; does not process your raw journal text in identifiable form).

We require each provider to use information only to perform services for us and to maintain appropriate security. We do not authorize them to use journal content for their own purposes.

6.2 With Your Consent or Direction

We share information with third parties at your explicit direction (e.g., if you choose to publish a scripture card to a social platform).

6.3 Legal and Safety

We may disclose information if we believe in good faith that disclosure is necessary to:

• comply with applicable law or legal process (subpoena, court order, search warrant);
• enforce our Terms of Service;
• protect the rights, property, or safety of Psalmlog, our users, or others, including investigating suspected fraud or violations.

Where permitted, we will notify you of requests for your data before responding so you have an opportunity to seek a protective order.

6.4 Corporate Transactions

If Psalmlog is involved in a merger, acquisition, financing, reorganization, sale of assets, or bankruptcy, your information may be transferred as part of that transaction. We will notify you of any change in ownership or use of your personal information.

6.5 What We Do Not Do

• We do not sell personal information for money or other valuable consideration.
• We do not share journal content or any other Sensitive Personal Information with advertising partners under any circumstances.
• Limited “sharing” for marketing measurement. Certain marketing tags described in Section 5 (currently including Meta Pixel and Google Ads conversion tracking) transmit limited event data — such as page views, conversion events, and hashed identifiers — to advertising partners who may use that data for cross-context behavioral advertising or audience building. To the extent this constitutes “sharing” under the California Consumer Privacy Act, you may opt out at any time via the “Your Privacy Choices” link in our footer or by sending a Global Privacy Control (GPC) signal, which we honor automatically.
• We do not allow third parties to use journal content for their own commercial purposes.
• We do not use journal content to train AI models.

7. Internal Access to Journal Content

Access by Psalmlog personnel to the content of your journal entries is highly restricted. Specifically:

• Routine operations. No employee reviews the content of your journal entries as part of routine operations. Aggregated, de-identified metrics (e.g., total entries created, error rates) are used for product analytics; the content of individual entries is not.
• Support. If you contact support and explicitly ask us to look at a specific entry to resolve an issue, an authorized support team member may view that entry for that purpose. We document the access.
• Security and abuse investigations. If we have a good-faith basis to investigate a security incident, suspected fraud, or violation of our Terms of Service, an authorized team member may access affected entries to the extent necessary to investigate. We document the access.
• Legal process. If we receive valid legal process compelling disclosure, an authorized team member may access entries to the extent required to respond. Where permitted, we notify you before responding.
• Public claims about AI Output. If you publicly disparage, misrepresent, or quote AI-generated Output produced by the Service — for example in a social-media post, review, press statement, or legal filing — we may access the specific journal entry and Output referenced in the claim, solely to verify the accuracy of the claim and to inform our response or legal defense. Access is limited to the specific entry referenced, is performed only by authorized personnel, and is logged.
• Logging. Every access by personnel to journal entry content is logged, including the identity of the person, the date and time, and the reason. Logs are retained for at least twelve months.

We do not use access to journal entries for “quality assurance” review of individual entries. If we ever need to change this practice (for example, to investigate a class of bugs that requires looking at sample entries), we will do so only with your specific consent.

8. Data Retention

We keep information only as long as needed for the purposes described in this Policy:

If law requires longer retention (for example, to preserve records relevant to litigation or a regulatory investigation), we will retain the information for the required period.

9. Data Security

We use technical and organizational measures designed to protect personal information from unauthorized access, use, alteration, and disclosure, including:

• In transit — TLS encryption for connections between your device and our servers and for connections to our service providers.
• At rest — AES-256 encryption at rest, applied by our database provider (Supabase) using cloud-managed encryption keys.
• Access controls — role-based access; multi-factor authentication for employee accounts with production access; principle-of-least-privilege.
• Monitoring — security event logging, anomaly detection, and alerting.
• Vendor diligence — contractual and (for material vendors) due diligence of security practices.

No system is perfectly secure, and we cannot guarantee absolute security. You also have a role in protecting your account: use a strong, unique password; enable available account-protection features; and do not share your credentials.

10. Security Incidents and Breach Notification

If we become aware of a security incident that materially affects your personal information, we will notify you and applicable regulators in accordance with applicable law. Our targets:

• Affected users — within 60 days, sooner where required.
• U.S. state regulators — within the timeframe required by the applicable state breach-notification law (typically “without unreasonable delay” or within a hard deadline ranging from 30 to 60 days).
• FTC under the Health Breach Notification Rule (16 CFR Part 318) — within 60 days for incidents involving “personal health record identifiable health information,” together with notice to affected consumers and (for incidents affecting 500+ residents of a state) prominent media outlets.
• EU/UK supervisory authorities — within 72 hours under GDPR Art. 33 / UK GDPR if a breach is likely to result in a risk to the rights and freedoms of natural persons.

11. Children and Teens

11.1 Children under 13

The Service is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided personal information to us, contact support@psalmlog.com and we will delete it.

11.2 Users aged 13–17

Users between 13 and 17 may use the Service only with the consent and supervision of a parent or legal guardian. We do not sell or “share” personal information of any user we know to be under 18. For users we know to be under 16 (or as required in specific jurisdictions), we obtain affirmative consent before processing sensitive information.

11.3 California, Connecticut, New York, and other teen-privacy laws

Where state laws (including the California Age-Appropriate Design Code, Connecticut SB-3, the New York SAFE for Kids Act, and Maryland's Kids Code) impose additional protections for minors, we apply those protections to users in the relevant jurisdictions.

12. International Data Transfers

Psalmlog is based in the United States, and your information may be processed in the United States and other countries where we or our service providers operate. These countries may have data-protection laws different from those of your country.

For users in the European Economic Area, the United Kingdom, and Switzerland, we transfer personal information to the United States in reliance on one or more of the following:

• Standard Contractual Clauses (SCCs) — for transfers to service providers, we rely on the European Commission's Standard Contractual Clauses and the UK International Data Transfer Addendum, together with supplementary technical and organizational measures as required by applicable case law.
• Your explicit consent — for limited cases under Article 49(1)(a) GDPR.

We are not currently self-certified under the EU-US Data Privacy Framework. If that changes, we will update this Section.

To request a copy of our SCCs or further information about our transfer mechanisms, email support@psalmlog.com.

13. Your Privacy Rights

13.1 Rights Available to All Users

Regardless of where you live, you can:

• Access the personal information we hold about you;
• Correct inaccurate information through your account settings or by contacting us;
• Delete your account and your journal entries through the in-product Delete Account flow or by contacting us;
• Export your data through Account → Export Data;
• Opt out of marketing communications at any time, including via the unsubscribe link in any marketing email.

13.2 California Residents

If you are a California resident, the California Consumer Privacy Act, as amended by the California Privacy Rights Act (“CCPA/CPRA”), gives you the following rights:

• Right to know — what personal information we collect about you, the categories of sources, the purposes, and the categories of third parties we disclose to. See Section 13.2.1 for our categories disclosure.
• Right to access and portability — a copy of your personal information.
• Right to correct — request correction of inaccurate information.
• Right to delete — request deletion of your personal information, subject to legal exceptions.
• Right to opt out of sale or sharing — we do not sell personal information. We do “share” limited event data with advertising partners through certain marketing tags (see Sections 5 and 6.5). You may opt out at any time via the “Your Privacy Choices” link in our footer; we also honor the Global Privacy Control (GPC) signal as a valid opt-out.
• Right to limit use of Sensitive Personal Information — limit our use of your Sensitive Personal Information to what is necessary to perform the Service. As described in Section 3.2, we already limit our use of Sensitive Personal Information to that purpose; you can submit a formal request via the “Your Privacy Choices” link in our footer.
• Right to non-discrimination — we will not discriminate against you for exercising these rights.

To exercise any of these rights: use the “Your Privacy Choices” link in our footer, the in-product privacy controls, or email support@psalmlog.com.

13.2.1 California — Categories of Personal Information

In the past 12 months we have collected the following categories of personal information about California consumers:

13.3 Other U.S. State Residents

If you reside in Virginia, Colorado, Connecticut, Utah, Oregon, Texas, Montana, Iowa, Indiana, Tennessee, Florida, Delaware, New Hampshire, New Jersey, Minnesota, Maryland, Nebraska, Rhode Island, Kentucky, or another state with a comprehensive consumer privacy law, you have rights similar to those described in Section 13.2, which may include:

• the right to access, correct, delete, and port your personal information;
• the right to opt out of (i) the sale of personal information, (ii) targeted advertising, and (iii) profiling in furtherance of decisions producing legal or similarly significant effects;
• the right to opt in (or out) of the processing of sensitive data, depending on the state;
• the right to appeal a denial of a privacy request.

To exercise these rights, email support@psalmlog.com or use the in-product controls. We will respond within the timeframe required by your state's law.

Universal opt-out signals. For states whose laws recognize universal opt-out mechanisms (currently California, Colorado, Connecticut, and others adding the requirement on a rolling basis), we honor the Global Privacy Control (GPC) signal as an opt-out of sale, sharing, and targeted advertising.

13.4 European Economic Area, United Kingdom, and Switzerland

As described under “Intended Audience” in the Introduction, the Service is operated from and directed to users in the United States and we do not actively target the EEA, UK, or Switzerland. To the extent users in those regions access the Service on their own initiative, we extend the following rights — consistent with the General Data Protection Regulation, UK GDPR, and Swiss Federal Act on Data Protection — on a voluntary basis, even where those laws may not apply to us by their own terms:

• Right of access to your personal data
• Right to rectification of inaccurate data
• Right to erasure (“right to be forgotten”)
• Right to restriction of processing
• Right to data portability in a structured, commonly-used, machine-readable format
• Right to object to processing based on legitimate interests, including for direct marketing
• Right to withdraw consent at any time, where processing is based on consent (including for special-category data — see Section 3.2)
• Right not to be subject to a decision based solely on automated processing that produces legal or similarly significant effects (we do not engage in this kind of processing)
• Right to lodge a complaint with a supervisory authority in your country of residence, place of work, or place of the alleged infringement. A list of EEA supervisory authorities is available at edpb.europa.eu; the UK supervisory authority is the Information Commissioner's Office; the Swiss authority is the FDPIC.

To exercise these rights, email support@psalmlog.com.

Controller. Psalmlog, LLC is the controller of personal data processed in connection with the Service.

Data Protection Officer. We have not designated a Data Protection Officer because we are not required to do so under Articles 37 GDPR/UK GDPR. For privacy questions, contact support@psalmlog.com.

13.5 Identity Verification

When you submit a privacy-rights request, we will ask you to verify your identity by confirming information already associated with your account. We use a verification standard appropriate to the sensitivity of the request — for example, a request to delete an account is verified via confirmation from the email on file; a request for a full copy of your data may require additional verification.

13.6 Response Times

We will respond to your request within:

• 45 days for CCPA/CPRA requests (with one 45-day extension if reasonably necessary, with notice to you).
• 30 days for GDPR/UK GDPR requests (with up to a 60-day extension if necessary, with notice to you).
• The period required by your state's law for other U.S. state privacy requests.

13.7 Appeals

If we deny your privacy request, you may appeal by emailing support@psalmlog.com with “Privacy Appeal” in the subject line and a description of your appeal. We will respond within 60 days. If we deny the appeal, we will provide a written explanation, and you may contact your state attorney general or, in the EEA/UK/Switzerland, your supervisory authority.

14. Marketing Communications

• Transactional messages (account, billing, security, important updates to this Policy or the Terms) — we send these to all account holders and you cannot opt out without closing your account.
• Marketing messages (newsletters, product announcements, promotions) — we send these only with your consent in jurisdictions that require it, or as permitted by law in others, and you can opt out at any time via the unsubscribe link in any message or by emailing support@psalmlog.com.

We do not engage in SMS marketing without your express opt-in.

15. Third-Party Websites and Services

The Service may contain links to third-party websites or integrate with third-party services (e.g., social platforms where you choose to share a scripture card). We do not control those third parties and are not responsible for their privacy practices. We encourage you to review their privacy policies before sharing information with them.

16. Do Not Track and Global Privacy Control

We do not currently respond to browser-based “Do Not Track” signals because there is no industry-standard definition. We do honor the Global Privacy Control (GPC) signal as a valid opt-out of sale, sharing, and (where applicable) targeted advertising for users in jurisdictions whose laws recognize universal opt-out mechanisms.

17. Biometric Information

We do not collect or store biometric identifiers (such as voiceprints, faceprints, fingerprints, or DNA) and we do not derive biometric identifiers from voice audio or any other source. Voice audio in the mobile Apps is used solely to generate a text transcript on your device and is then discarded. See Sections 2 and 1.4.

If we ever introduce a feature that involves biometric processing, we will obtain your explicit, written consent in advance and update this Policy.

18. Changes to This Privacy Policy

We may update this Privacy Policy from time to time.

Most updates take effect immediately. Clarifying edits, updates to our list of service providers, additional user privacy protections, and other changes that do not adversely affect your rights take effect on posting, with a new “Last Updated” date. We are not required to give advance notice of these changes.

Material adverse changes require advance notice. For changes that adversely affect your privacy rights — specifically (a) a new category of personal information we collect, (b) a new purpose for which we use your personal information that is materially different from those described in Section 4, (c) a new category of third party with whom we share personal information for that party's own purposes, or (d) a reduction in the rights described in Section 13 — we will give at least 30 days' advance notice by email to the address on your account and through an in-product notice. The change will take effect on the date stated in the notice.

If a change requires your consent under applicable law (for example, a change to the basis for processing special-category data under Article 9(2)(a) GDPR), we will request your consent before the change applies to you.

19. Contact Us