Effective October 17, 2026. Version tu-agent-2026-10-17-v2.
Service and License Agreement · Privacy Policy · Account and subscriptions
Scope and operator
Integrity Syndicate LLC of Boise, Idaho operates True Unitarian Agent at TrueUnitarian.com. This policy covers its website accounts, subscriptions, text, file and voice features. The separate Discord bot has its own privacy policy. Privacy contact: support@integritysyndicate.com.
What we process
For accounts, we process your email address, Google account identifier and verified profile details if you choose Google sign-in, verification status, sign-in sessions, account identifiers, legal-acceptance version and timestamps. Authentication and security systems can process IP addresses and browser/device information; request-limit identifiers are stored as hashes. Sign-in codes are stored hashed, expire after ten minutes and have attempt limits.
For debate simulation, accepted exchanges and requested transcript-based ratings follow the subscriber-history and cache rules. Ratings assess transcript content rather than voice delivery. For chat, we process submitted prompts, conversation context, checked answers, source references and source text needed to respond. For uploads, this includes the filename and extracted readable text. Webpage and YouTube caption retrieval in Critique accesses the public links you paste. For voice, temporary audio is used for transcription and speech generation, and content-free usage totals enforce allowances.
For subscriptions, we store the Stripe customer/subscription references, plan, payment-access status, renewal-period information and event identifiers needed to reconcile access. Stripe/Link collects payment and billing details. The application does not store full payment-card numbers or security codes.
Why we use information
We use information to authenticate accounts, provide replies and source review, generate and transcribe speech, save subscriber chats, reuse matching checked answers, deliver subscription access, administer invitation codes, prevent misuse, provide support and meet applicable obligations. Depending on the circumstances and applicable law, processing supports the requested service, security and other legitimate operational needs, legal obligations, or consent where required. Theological use does not require you to identify your own or anyone else’s religious beliefs. Avoid private or sensitive information.
Saved chat history
Chat history is saved privately for subscribers, including eligible invitation users, so the signed-in account can reopen and continue conversations. Saved history includes accepted prompts/replies and relevant source context, including extracted file text. Free Chat without subscriber access does not create saved chat history. Other users cannot browse your account’s history.
You can delete a saved chat in the sidebar. Starting a new chat or signing out does not delete saved history. An active subscription is required to reopen it after invitation or subscription access expires. Deleting chat history does not automatically remove a separately cached reusable answer.
Reusable answers and cross-user caching
Prompts and answers may be cached, and answers may be reused. A private cache stores checked answers, references and cryptographic request fingerprints. When the same complete request has the same model, instructions, mode, source content and conversation context, the service may return the earlier checked answer to another participant without another language-model call. The cache is separate from saved account history and is not a public chat directory.
A cached answer can contain wording from a submitted prompt or source. This reuse is a reason to avoid private information and material you cannot authorize for this purpose. Model or system-instruction changes invalidate the relevant cache; different source text and conversation context prevent a match. Old cache versions are removed when a new version is activated. The application has no separate chat-training-data pipeline or session improvement switch. Provider policies govern their own processing.
Files, voice and temporary processing
Original upload bytes are processed temporarily to extract text and are not retained as a document archive. Extraction excludes images and layout and reports partial coverage; scans without readable text require OCR outside this service. Extracted text can remain in subscriber history and reusable answers as described above.
Microphone recordings and generated audio buffers are temporary; the application does not retain a library of voice recordings. Transcribed text and accepted assistant text follow the chat-history and cache rules. Voice usage records contain durations and account identifiers, not stored audio. Your device or browser can retain downloads or copies you choose to save.
Service providers and sharing
Cloudflare hosts the service and its private application storage, email delivery, authentication records and security controls. OpenAI receives model requests and relevant context when inference is needed, and audio submitted for transcription. OpenRouter and Google receive accepted text for Gemini speech generation. Google processes the identity sign-in flow if you select Sign in with Google; only basic sign-in scopes are requested. Google access, refresh and ID tokens are not retained by this application after sign-in. Stripe/Link processes payments, subscriptions and transaction support. A fetched public website or caption service receives an ordinary request for the link you submit.
We do not publish a directory of account conversations or sell account contact information. Providers process information under their own applicable terms and policies; this policy does not promise zero provider retention. Information may be disclosed where needed for authorized support, security, legal obligations or enforcement of service terms. Providers can process information internationally; no single-country storage promise is made.
Cookies and security
The service uses necessary secure cookies to recognize anonymous active chats and signed-in accounts. Account cookies are HTTP-only and same-site protections help prevent cross-site misuse. Clearing cookies signs you out or removes anonymous session recognition; it does not delete saved account data. The agent does not require advertising cookies.
HTTPS and server-side access checks protect traffic and private records. Secrets are kept server-side. Subscriber histories are scoped to the verified account, and the reusable cache is private application storage. No internet service can guarantee absolute security. Service providers may retain their own operational or security records.
Retention and your choices
Active chat context expires or is cleared when ended. Subscriber history remains until deleted or otherwise removed as part of account administration. Reusable answers remain in the active cache version until invalidation or removal. Account, subscription, invitation, acceptance, abuse-prevention and billing records are kept as needed to operate the account and service and meet applicable obligations. There is no promised fixed thirty-day deletion schedule. Backups and provider records can follow separate retention and deletion cycles.
To request access, correction, export or deletion of account information, contact support@integritysyndicate.com using the account email. We may verify ownership before acting and explain any information that must be retained for billing, security or legal obligations. For a cached answer containing information you want removed, provide enough detail to locate it without sending additional sensitive information. Applicable rights can include restriction or objection and a complaint to a relevant regulator. Stripe/Link requests may also need to be made to them directly.
Updates
This policy is effective October 17, 2026, version tu-agent-2026-10-17-v2. Material changes will be disclosed through the service or account contact as appropriate. Questions: support@integritysyndicate.com.