Privacy Policy

Member reviews

Reviews are optional public contributions about your experience with LogosPharos. Publishing displays your public profile name, rating, review text and dates. We store your account association, text, rating, timestamps and revision to host and manage the review you request. Staff may remove abusive content with a privately recorded reason; disagreement or a low rating alone is not grounds for removal. Do not publish private information or infringe others' rights. You can edit or delete your review; account deletion erases its active text too. Private moderation records may remain for abuse prevention and dispute handling under our legitimate interests. Reviews are not sent to AI or used for advertising. Contact realcodegr@gmail.com to report abuse, appeal moderation or request review of retained records. Copies made by other visitors cannot be recalled. This optional supplement does not change the AI-consent version.

Human support

The support bubble sends your messages to the site owner, not the AI provider. Support messages, timestamps, status and account username/display name (for members), or a preferred name and random identifier (for guests), are kept privately to answer your request. Guest access uses the essential lp_support HttpOnly cookie, which expires after 30 days; the current conversation identifier and guest preferred name are held in session storage.

Typing indicators share only a temporary typing/not-typing signal, never your unsent text. The signal expires within eight seconds and is not saved to support history. Either participant can close a thread; closing does not erase its history.

Only the authenticated owner can read the support inbox. Support records are removed after 90 days without activity. Contact us to request earlier deletion. If the owner enables browser notifications, their browser push provider receives a generic support alert and conversation identifier, not your message text. This feature does not enable advertising or tracking.

If Discord alerts are enabled by the owner, Discord receives the member username or guest preferred name, ticket topic, a short first-message preview, and ticket link. Alerts are intended for an owner-only channel. Do not include passwords or sensitive personal details in a support message.

Optional daily Scripture likes and public streaks

When you click Like on the daily Scripture passage, we store that UTC date linked to your account and when you first used this optional feature. There is no separate approval dialog. These choices may reveal religious practice. Individual likes and dates are private; only your current and best consecutive-day streaks are shown publicly on your profile. There is no public like counter. No likes are sent to AI providers or used for advertising. Earlier consent timestamps, where present, are retained; new likes are not recorded as a separate explicit-consent declaration.

Each day begins at 00:00 UTC. You can remove today’s like by clicking the Like button again. There is no separate daily-card data-deletion control. Historical records remain until you delete your account or request erasure through support; backups follow the retention below. Copies of a public streak already seen by others cannot be recalled. The explanation is an original editorial context note, not a generated prediction or personal spiritual direction. This optional supplement does not change the AI-consent version.

Optional private reminders

Reminders require a free account and are off by default. Saving reminder settings requires separate explicit consent to storing choices that may reveal religious beliefs or practices (GDPR Articles 6(1)(a) and 9(2)(a)). This is independent of AI consent and your public profile. We store your selected church tradition and calendar, parish-calendar confirmation, time zone, notification language, quiet hours, routines, optional personal labels, device names and push subscriptions, and the time of your reminder consent. These settings are private account data, not public profile fields; the site operator and hosting infrastructure can access stored data to operate the service. No reminder data is sent to AI or used for advertising.

Browser permission is requested only when you choose to enable a device. Push subscriptions contain a delivery endpoint and encryption keys and are linked to your account. Your browser or operating-system push provider transports encrypted notification payloads and can observe delivery metadata. By default the displayed alert is generic. If you enable lock-screen details, religious practices and personal labels may be visible to anyone who sees your screen. Delivery can be delayed or prevented by device settings or connectivity; it is not guaranteed.

The server keeps a short scheduling ledger for up to three days to prevent duplicate alerts, delivery acceptance or failure status per device, and up to twelve recent reminder events for up to seven days. Recent events let you view a generic alert’s details after opening the site; saving new settings clears those recent events. Settings and subscriptions remain until you disconnect a device, delete reminder settings, or delete your account. Expired push subscriptions are removed when the push provider reports expiry. You can withdraw reminder consent and erase active reminder records with “Delete all reminder settings and devices” at any time, without deleting your account, chats or support messages. Backups follow the retention described below; notifications already delivered cannot be recalled.

The essential local-storage entries lp_reminder_device and lp_reminder_member identify the personal-reminder device and account in this browser. A separate IndexedDB record stores only the connected device identifier and local allow flag, so a stale push can be suppressed after sign-out or disconnection. Signing out through the site disconnects this browser’s personal reminders; owner support notifications remain separate. Other subscribed devices continue until disconnected. This optional supplement does not change the AI-consent version shown above.

Community forum — additional privacy information

The forum is publicly readable. Posting, replying, editing, voting, and reporting require your existing account. Published contributions show your public name, profile link, staff badges, timestamps, and aggregate vote score. Your individual votes and reports are not public. Owner, Admin, and Moderator badge holders can see reports, forum bans, and the moderation audit. Forum messages are not sent to the AI to generate answers.

We store posts, replies, votes, reports, forum-ban reasons and expiry dates, moderation records, and short-lived account-based rate-limit counters to operate and protect the community. Content hosting uses the account service you request; abuse prevention and moderation rely on our legitimate interest in community safety. Do not publish private or sensitive personal information. Forum participation can be suspended without deleting your account or restricting the chatbot. You can appeal by emailing realcodegr@gmail.com.

Contributions remain until you or staff remove them, or you delete your account. Removed text is erased from the active forum store; a blank placeholder may remain to preserve replies by other people. Account deletion also removes your votes and reports and anonymizes your moderation authorship. Moderation reasons and records may remain for abuse prevention and dispute handling; contact us to request review or erasure. Copies already read or made by other visitors cannot be recalled. This forum supplement does not change the AI-consent version shown above.

1. Who We Are (Data Controller)

The LogosPharos website is operated by an individual established in Greece (“we”, “us”, “our”), acting as the data controller for personal data processed through this website. Data-protection contact and all privacy requests: realcodegr@gmail.com.

This Policy explains what personal data we process, why, how long we keep it, who it is shared with, and the rights you have under the EU General Data Protection Regulation (GDPR) and Greek law (Law 4624/2019).

2. What We Process, and Why

We do not sell or rent your personal data. We do not use private chat contents, saved conversation titles, or declared religious beliefs to build advertising audiences or select personalized ads. There is currently no advertising processing. Planned advertising is described below and is separate from the processing needed to provide the AI service.

3. Conversation Content

• On our server: your session is held in memory — the last 12 messages of a conversation, expiring 30 minutes after you go idle, and wiped completely whenever the server restarts. If you choose to create an account, the conversation is additionally written to your account so you can find it again later; the passages of the Orthodox library that are quoted back to you are public texts, not your data.
• What a public profile shows: each account has a page at /u/<username> showing your public name, optional bio, profile picture, and badges. Saved conversation titles, message contents, chat counts, and last-login or last-visit metadata are not published there. Saved conversations are available only through their owning account; owner-only operational security records are separate.
• Last website visit: for signed-in accounts, we keep one timestamp of the last recorded website visit for owner-only account administration. Visible pages update it approximately once a minute; hidden-tab notification polling does not update it. It contains no browsing history or page list and is not sent to AI providers or used for advertising. It remains after sign-out and is erased with your account. Visits made while signed out cannot be attributed to your account.
• Religion and denomination — private unless you publish it: a religious belief is among the most sensitive things a profile can hold, and in some places disclosing it carries a risk of its own. So it works the other way round from everything else here: it is hidden by default, and reaching your public page takes a separate, deliberate click. Until you turn sharing on, your religion and denomination are visible to you alone. Turning it off again hides them at once.
• What sharing does and does not do: it adds a line to your public page naming your religion, and your denomination when you chose one. That is all it does. Your beliefs are never used to profile you, never passed to Google or to the search provider, never used to change how the assistant answers you, and never used to sort, filter or moderate the site.
• For processing: to answer you, your message, recent conversation context, and relevant excerpts retrieved from the Orthodox library are transmitted to Google. A verse-explanation request sends only the selected reference together with its matching study notes, and is not added to your conversation. Google processes this data under its own terms: Google Privacy Policy and the Google Terms of Service. We do not control Google’s processing.
• Other transfers: when the assistant performs a live web lookup, the search query text is sent to azbyka.ru or to our search provider (LangSearch). Only the query — not your identity — is transmitted.
• The security record: so the owner can investigate an attempt to break the assistant, the server also writes each completed question to a security record — the question, the reply, the time, your IP address, your username if you were signed in, and any safety flags. This applies to everyone, signed in or not, and it is a deliberate change from the earlier version of this policy, which said a guest's messages existed only in short-lived memory. They no longer do: a guest's entry is kept for a few days and then deleted, a member's for longer, and the log is stored on the server's own disk rather than in the database. It is read only by the site owner, through a private page that requires a signed-in account with the Owner badge; no token provides access. It is never shown to any visitor, never published, and never used to build a profile of you. If you would like your entries removed, email us (see 16) and we will delete them; because guest entries expire on their own, the simplest option is usually to wait.

4. Cookies and Local Storage

Current setup: no advertising or analytics cookies, tracking pixels, or fingerprinting are enabled. Future advertising technologies are described below. If you never use the AI features, no consent cookie is needed. Accepting the AI terms sets the strictly necessary lp_consent cookie with the accepted version, for up to 180 days. If you sign in, a separate first-party cookie lp_session keeps you signed in. Both are HttpOnly (invisible to scripts), SameSite=Lax, and limited to Path=/; the sign-in cookie expires after 30 days, and is removed immediately on sign-out. The Service also stores the following items in your browser’s local storage — first-party, on your device only:

• lp_sid — a random conversation-context identifier; the server binds member context to the signed-in account to prevent cross-account reuse;
• lp_msgs — a local copy of your recent conversation (up to 40 messages), so it survives reloads;
• lp_crisis — a flag so the crisis-support banner is shown only once;
• lp_conv — the identifier of the saved conversation you are reading, if you are signed in; and
• lp_legal — the version and date of the Terms/Privacy Policy you accepted.

Website language, color theme and calendar preferences are saved on your device. Your selected language is included with AI chat and verse-explanation requests so new replies use that language. Color theme and calendar preferences are not sent to the AI. The shared theological, source and safety rules stay unchanged.

Optional study progress is off by default. If enabled, lp_study_progress_v1 stores only completed reading-step IDs in this browser. It is not account data and is not sent to AI. Other users of a shared device can see it. Use “Forget study progress” on the study page to remove it without changing accounts, conversations or other preferences.

The owner panel uses the normal account sign-in cookie and a server-side Owner-badge check. There is no separate admin-token sign-in cookie. Signing out removes owner-panel access.

AdSense ownership verification: public pages include an account-verification meta tag and the site serves an ads.txt seller record. These do not load Google's advertising script, request advertisements, or set advertising cookies. Advertising remains disabled. Any future advertising requires separate disclosures and an appropriate advertising-consent setup; AI consent is not advertising consent.

Advertising — planned Google AdSense

We intend to show clearly distinguishable Google AdSense advertisements on eligible public content pages after approval and consent setup. This is not active today. Ads will not be placed on private AI chat, saved-conversation, account, owner-panel, error, or maintenance screens. Advertising is separate from Google's processing of questions to generate AI replies.

If enabled, Google and its advertising partners may receive information such as your IP address, browser/device details, the page displaying the ad, ad interactions, and cookie or similar identifiers. They may use cookies, local storage, web beacons, or similar technologies to deliver and measure ads and, where permitted by your consent choices, personalize them. Google processes advertising information under its own policies: How Google uses information for advertising and Google Privacy Policy.

Where required, advertising technologies will be subject to separate consent before activation. For EEA, UK, and Swiss visitors, applicable advertising consent will use a Google-certified consent management platform. You will be able to refuse optional processing and revisit or withdraw your choices through the advertising privacy controls provided when ads are enabled. Accepting the AI Terms does not authorize advertising cookies or personalized ads. No advertising-consent controls are shown now because advertising is disabled.

Google also provides My Ad Center for eligible Google ad-personalization settings. These settings do not replace this site's consent controls. Advertising partners' retention and processing are described in their own policies; we do not claim their data follows our chat-log retention schedule. Before activation, we will update these disclosures to identify the actual advertising configuration and available controls.

Nothing shared with third parties is stored through local storage. You can delete all of it at any time via your browser’s “clear site data” settings, “New chat” clears the conversation copy, and “Delete my account” in the account window removes the saved history and ends the cookie.

5. Safety Scanning and Crisis Detection

Messages are automatically scanned to detect prompt-injection/jailbreak attempts, harmful content, and crisis situations. These checks run automatically on the message text; outcomes are also recorded as short operational flags (e.g., “filtered”, “crisis: true”) in the security record, together with the message text itself (see 3). In a crisis, the support information (such as 988 or 112) is displayed to you in your browser — it is not sent to any person or authority.

6. Service Logs

Like most servers, we keep operational logs (timestamp, IP address, request path, processing time, and safety flags) for security, abuse prevention, and debugging. Logs are kept only for as long as needed for those purposes, then rotated/deleted, and are never used to build profiles.

Separately from those, and for the reason set out in section 3, the server keeps a security record of the questions actually asked — not just that a request happened, but what was in it. The two are different things and this one is the more sensitive: a request log cannot tell you what a visitor was trying to make the assistant do, and that is the whole reason for keeping it. It is held on the server’s own disk, separately for guests and for members so that each can be deleted on its own schedule, and it is read only through the owner’s private page.

7. Retention

• Conversation memory: up to 30 minutes of inactivity, or until server restart.
• Account data (only if you created an account): kept until you delete the account — deletion removes your profile, your profile picture, saved conversations and messages immediately, and ends your sign-in. You can do this yourself with “Delete my account” in the account window, or remove just the picture with “Remove picture”.
• Sign-in sessions: at most 30 days, or until you sign out.
• Consent record (server): in memory for up to 180 days, or until server restart.
• Operational logs: only as long as needed for security/debugging.
• Security record, guest questions: a few days. Guest entries are written to a separate file from members’ and deleted on their own schedule, so that deleting them never takes a member’s history with it. Currently three days.
• Security record, member questions: longer than a guest’s, and not a copy you need to keep, because the same conversation is already saved to your account where you can read and delete it. Currently thirty days. Both figures are set by the deployment and can be shortened by the owner.
• Your browser data: until you clear it (“New chat” or browser settings).

8. Who We Share Data With

• Google — to generate replies (see §3).
• azbyka.ru / LangSearch — search queries only, when a live lookup is performed.
• Our hosting/network provider — where the site is deployed; processes traffic data on our behalf.
• Authorities — only if we are legally compelled to do so.

We do not sell or rent personal data to advertisers or data brokers. We currently do not transmit visitor data to an advertising service; ownership verification alone makes no ad requests. If advertising is enabled, Google and its partners may receive the advertising information described above, subject to applicable consent requirements. Private chats and declared religious beliefs are not supplied for ad targeting. Data transfers outside the EU/EEA (e.g., to Google in the USA) rely on the safeguards provided by those providers under GDPR Chapter V (such as Standard Contractual Clauses).

9. Legal Bases Explained

• Contract (Art. 6(1)(b)): processing needed to provide the chat or verse explanations you ask for.
• Legitimate interests (Art. 6(1)(f)): security, rate limiting, abuse prevention, and keeping the service working — balanced against your rights, with minimal data and short retention.
• Consent (Art. 6(1)(a)): your explicit “I agree” acceptance before using the AI features, and any processing that requires it. You may refuse or withdraw consent at any time (stop using the chat or verse explanations, or clear your browser data) without any consequence other than losing the feature.
• Legal obligation (Art. 6(1)(c)): only if we are legally required to retain or disclose information.

10. Your Rights

Under the GDPR you have the right to: access your data; rectify it; erase it; restrict its processing; object to processing based on legitimate interests; data portability; and withdraw consent at any time.

To exercise any right, email realcodegr@gmail.com. If you have an account, you can correct your display name, bio, religion and denomination yourself, and erase everything (access and erasure) with “Delete my account” in the account window — no email required. For guests, because the Service is anonymous, we may ask for your session identifier (found in your browser’s local storage) or other minimal information to locate your data, and we will respond within one (1) month. This includes the security record described in section 3: if you ask us to erase it, we will delete the entries we can identify, and because guest entries expire on their own after a few days, waiting is usually enough for a guest who has not told us who they are.

If you believe we have not handled your data properly, you have the right to lodge a complaint with a supervisory authority — in Greece: the Hellenic Data Protection Authority — or the authority in your country of residence.

11. Children’s Privacy

The Service is not directed to children under 13, and we do not knowingly collect personal data from children under 13. Minors above 13 but below the digital-consent age of their country (for example 15 in Greece, or 16 under the EU default) may only use the Service with parental permission, and their parent or guardian must accept the Terms. If you are a parent/guardian and believe a child has provided data to us, email us and we will delete it promptly.

12. Security

We apply proportionate technical and organisational measures for a service of this kind: minimal data collection, in-memory conversation storage, short retention of the security record, rate limiting, automated input/output safety filtering, a strict allow-list of what the server exposes, and encryption in transit when the site is served over HTTPS. Account passwords are stored only as salted scrypt hashes (never in plain text), and sign-in tokens are likewise hashed before they are stored. If accounts are switched off or the database is unreachable, the chat continues to work exactly as before, for guests. The security record is written outside the directory the web server can serve, is excluded from version control, and is readable only by an authenticated Owner account through the owner panel; legacy tokens do not authorize access. No system is perfectly secure, but our design goal is that there is very little to steal in the first place.

13. Automated Decision-Making

Automated processing is limited to generating the reply you requested and applying safety filters. There is no profiling, no scoring, and no automated decision-making that produces legal or similarly significant effects on you (GDPR Art. 22).

14. Do Not Track and Privacy Choices

The necessary first-party cookies described in §4 record AI-term acceptance and, if you sign in, maintain your account session. Advertising tracking is currently disabled. We do not use browser “Do Not Track” signals to change these necessary service functions. If advertising is enabled, use the separate advertising privacy controls to manage optional processing; a browser signal alone does not replace those choices.

15. Changes to This Policy

We may update this Policy; the current version and date appear at the top of this page. Material changes will require you to accept the new version before continuing to use the chat or verse explanations.

Factual clarification, 3 October 2026: descriptions of profile privacy, account-based owner authorization, necessary cookies, and disabled AdSense verification have been corrected to match the service. This clarification introduces no advertising processing and leaves the AI-consent version unchanged.

Planned advertising disclosure, 3 October 2026: this Policy now describes the intended AdSense use and separate advertising-consent requirements rather than promising the site will always be ad-free. No advertising script or tracking has been activated; disclosures and controls will be reviewed again before activation. The current AI-consent version remains unchanged.

What changed in version 2026-09-29.3: the site gained a prayer book, which displays the prayers of four books in our library and, for the bilingual one, sets the Greek beside the English. It is a reading section and nothing more: the prayers are the same text for everyone, are served from a file inside the site, and are not recorded anywhere. Reading them sets no cookie, creates no account, and writes nothing about you — this is recorded here so that a new section on the site is not mistaken for a new collection of data. The Terms were changed to describe the section and to say who owns the text. Nothing in this Policy was changed, because nothing about what we collect, who we share it with, or your rights has changed.

What changed in version 2026-09-29.2: the site began keeping a short-lived security record of every question, from signed-in members and guests alike, so that the owner can investigate an attempt to break the assistant. Sections 2, 3, 4, 5, 6, 7, 10, 12 and 14 were changed to say so. The previous version stated that a guest’s messages existed only in short-lived server memory; that is no longer the case. Nothing else about what we collect, who we share it with, or your rights has changed, and the belief fields added in 2026-09-29.1 are unchanged.

16. Contact

Privacy questions, rights requests, and data-deletion requests: realcodegr@gmail.com.