1. Scope

This Privacy Policy explains how PILLAR handles information for the PILLAR mobile app, website, PILLAR Updates email communications, historical waitlist records, and connected AI apps such as Claude and ChatGPT, where available. PILLAR provides Scripture-grounded AI guidance for private questions, prayer, decisions, relationships, and faithful next steps.

2. Information We Collect

The information we collect depends on the features you use. The categories below describe what we process, why, and the service providers that receive it. Section 7 explains retention; Section 6 explains your controls.

Account and sign-in information: name, email address, account identifiers, authentication details, age-confirmation status, and settings. Authentication, hosting, and database providers process this information to sign you in, maintain your account, and apply access requirements.
PILLAR Updates email information: your email address, name if provided, signup source and date, consent record, and email preferences. Hosting and database providers process these records to manage signup and preferences. Email service providers process your contact details and preferences to send PILLAR Updates.
Historical waitlist information: records from the former waitlist may include name, email address, role, early-tester preference, signup source and date, enrollment or lifecycle status, email preferences, and any referral, campaign, or reflection information submitted. Hosting and database providers retain these records to preserve signup history and preferences.
Conversations, memory, and personal beliefs: questions, answers, conversation titles, identifiers and timestamps, relevant earlier messages, account context you provide, and account-bound memory when enabled. Preferences may include your preferred name, tradition, denomination, Scripture translation, and answer style. Your questions, preferences, and saved context may reveal religious beliefs or other personal information. Hosting, database, AI model, and AI routing providers process this information to generate and store guidance, maintain conversation history, and support personalization. See Sections 3 and 4 for belief information and model training.
Connected-app information: the app you authorize, account and authorization identifiers, requested permissions, and connection credentials. Authentication and infrastructure providers use these to connect your PILLAR account. The connected AI app receives the answers, conversation identifiers, Scripture references, and usage information returned for your requests, plus identity information covered by the permissions you approve.
Usage, analytics, and diagnostics: feature use, usage counters, timestamps, page visits, selected clicks, referral and campaign details, and technical or error records. These can include browser or device information and IP addresses in request or error records, plus crash and performance data if supplied. Hosting, database, analytics, and diagnostics providers process these to enforce limits, understand website use, and maintain reliability and security.
Feedback and support: contact details, feedback, issue reports, support messages, and any conversation excerpts or technical context included in a report. Database, hosting, email, and support providers process these to respond to you and investigate problems.
Restricted website access: for invited visitors, an access identifier, visitor label, permissions, session cookie, and records of documents viewed and when. Hosting and database providers process these to control access and understand document use.

3. How We Use Information

We use information to:

Provide, maintain, and improve the PILLAR app and related services.
Send one welcome when you first sign up, product news, and other PILLAR Updates according to your subscription preferences.
Generate responses and support Scripture-grounded guidance inside the app.
Manage PILLAR Updates signup, email preferences, historical waitlist records, and PILLAR communications.
Improve safety, reliability, debugging, abuse prevention, and product quality.
Enforce usage limits and account access.
Respond to feedback, support requests, account requests, and report-issue submissions.
Protect PILLAR, users, and others from fraud, misuse, security issues, or legal risk.
Comply with applicable law and enforce our Terms of Service.

Faith and personal-belief information. Questions and context may reveal your religious beliefs. PILLAR processes this information to provide the guidance you request. Our intended basis for this processing is your consent at signup or connection.

Model improvement. PILLAR uses user conversations to train PILLAR's models.

4. AI and Provider Processing

AI model and routing providers process your question, relevant conversation context, and enabled memory to generate and review responses on PILLAR's behalf. Hosting and database providers store account records and conversations. The other provider categories and their purposes are described in Section 2.

Claude and ChatGPT connections. When you connect PILLAR in a supported AI app, you sign in with your PILLAR account and approve the connection. Questions sent to PILLAR through that app and PILLAR's answers are processed and stored in your PILLAR account. They use your existing PILLAR context and memory settings and count toward your PILLAR daily and monthly limits. The connected app can also read your PILLAR usage. The connection receives the question sent to PILLAR; it does not independently retrieve your other chats or files from the connected app.

The connected AI app also handles the information in its own service under its own privacy policy and controls. Disconnecting and deleting data in PILLAR are separate from managing copies in Claude or ChatGPT. Third-party AI providers have their own training and retention terms; this policy does not promise that they exclude all data from training.

6. User Controls

Website email signup subscribes you to PILLAR Updates and does not create an app account. You can unsubscribe using the link in any update. Unsubscribing from updates does not delete your app account or prevent essential account messages, such as password resets.

PILLAR is account-bound. You can sign out of the app, use available in-app memory and account controls, and contact us about access, correction, or deletion requests.

Access and correction: use your PILLAR conversation history to review saved conversations. Email support to request access to or correction of your personal information.
Memory: open Settings, then Memory, to turn memory off or clear it. These controls do not themselves delete conversation history.
Disconnect: select PILLAR in Claude's connector settings or ChatGPT's app or plugin settings and choose Disconnect. You can deny a new connection on PILLAR's approval screen. Disconnecting does not itself delete conversations already stored in PILLAR or in the connected app.
Unsubscribe: use the unsubscribe link in a PILLAR email, when provided, or email support to request removal. Unsubscribing records your email preference; it does not delete the underlying signup or historical waitlist record.
Website analytics: our public-site analytics respect browser Do Not Track and Global Privacy Control signals. They are configured without analytics cookies, persistent browser storage, or session recording. Sign-in may use browser storage, and restricted website areas use a session cookie. You can clear these through your browser; doing so may sign you out.

To request account deletion, email support@askpillar.ai from your account email with the subject "Delete my PILLAR account". You can also contact support about deleting email signup, historical waitlist, support, or restricted-access records. Disconnecting, unsubscribing, and deleting an account are separate requests.

7. Retention and Security

Retention depends on the type of information and the system holding it. The periods and deletion behavior below describe our current configuration.

Account data, conversations, and memory: we retain these while your account is active, unless you use a control that removes them sooner. When account deletion successfully completes, conversation, memory, settings, usage, and other account-linked records are removed from the live application database as part of that operation. Email deletion requests are handled by support; we do not currently guarantee a completion period for those requests.
Records retained after account deletion: an account record containing email and sign-in identifiers remains to block continued access. Certain audit and safety records also remain, with direct account links removed and a reference code retained. These records currently have no automatic expiration. Removing the remaining account identifiers requires a separate cleanup operation, so we do not promise that all account data is erased within 30 days.
Conversation and memory controls: clearing memory removes stored memory entries during that operation. Deleting chats marks conversations as deleted rather than immediately erasing their database records. There is no scheduled age-based purge of those chat records; successful account deletion removes them from the live application database.
Database backups: Supabase is configured for a rolling seven-day daily-backup retention window, with point-in-time recovery disabled. Deleting data from the live database does not remove it from an existing backup immediately. The configured recovery window is not a verified deadline for permanent erasure of every backup copy, and we do not currently promise that all backup copies are purged within 30 days of live deletion.
Email contact data: unsubscribing records your preference but does not delete your email signup, historical waitlist, or email contact record. Historical waitlist records have no automatic expiration. Account deletion does not automatically remove separate email signup or historical waitlist records, or existing email-provider contacts; removal of those records requires a separate request and cleanup. We do not currently guarantee a fixed completion period for that cleanup.
Connected apps: where a PILLAR connection is available, you can disconnect it in Claude or ChatGPT. Disconnection removes the connection in that app, but an access token already issued can remain valid until it expires, currently one hour after issuance. Successful PILLAR account deletion blocks further authenticated use of that account. Neither disconnection nor token expiry deletes previously stored conversations or copies held by the connected app.
Usage and diagnostic logs: Vercel runtime and observability logs are retained for 30 days under our current configuration. Supabase platform logs have a configured retention period of seven days. These periods do not apply to account-linked usage and provider-call records stored in our application database: those have no age-based expiration and are removed during successful account deletion. Audit and safety records follow the separate retention rule above. Website analytics and deployment or build records are separate from these platform logs and are not covered by these periods.
Restricted website access: the session cookie expires after 12 hours. Cookie expiry does not delete invitation, permission, or document-view records.

We use administrative, technical, and organizational safeguards to protect your information. No online service can guarantee absolute security.

8. Children

PILLAR is not intended for children under 13. If we learn that we collected personal information from a child under 13, we will take appropriate steps to delete it.

9. Contact

Questions or requests: support@askpillar.ai

PILLAR Guidance, Inc., a Delaware C-Corporation

Privacy Policy