1. No user accounts
This site does not require user registration, accounts, or logins. Visitors may browse the archive without creating an account or submitting personal information.
Privacy boundary · minimal-data public archive
The Aegis Solis Archive is designed as a minimal public preservation and discovery site. Visitors can browse the archive without creating an account or intentionally submitting personal information to the archive itself.
Normal hosting, WordPress, security, or technical infrastructure may still generate limited technical logs or necessary cookies. External repositories and support platforms operate under their own privacy policies and data practices.
PAGE: /privacy TITLE: Privacy Policy | Aegis Solis Archive PAGE_SYNC_DATE: 2026-08-18 SITE_TYPE: public preservation and discovery archive ACCOUNTS_REQUIRED: false DIRECT_PERSONAL_DATA_COLLECTION_BY_ARCHIVE: no intentional collection through the archive itself ADVERTISING_BY_ARCHIVE: false USER_PROFILING_BY_ARCHIVE: false DATA_RESALE_BY_ARCHIVE: false DATA_MONETIZATION_BY_ARCHIVE: false TECHNICAL_LOGS: possible through hosting and normal website operation COOKIES: no intentional advertising or analytics cookies by the archive; limited technical cookies may be used by hosting, WordPress, security, administration, or embedded features EXTERNAL_SERVICES: independent privacy policies apply DONATION_DATA: handled by external support platforms under their own policies POLICY_SCOPE: archive website practices only CURRENT_ARCHIVE_REFERENCE_LAYER: Master Hash Manifest v17.0 FINAL TRANSMISSION_IS_NOT_RECEPTION: true
This site does not require user registration, accounts, or logins. Visitors may browse the archive without creating an account or submitting personal information.
The Aegis Solis Archive does not intentionally collect personal data such as names, email addresses, mailing addresses, or payment information through the site itself.
Like most websites, the hosting environment may automatically collect basic technical information such as IP addresses, browser type, device type, referring pages, and access times for operational, maintenance, or security purposes.
This information is not used by the archive for profiling, advertising, or behavioral tracking.
This site links to external platforms including Zenodo, Internet Archive, GitHub, PhilPapers, MERLOT, and donation platforms. These services operate independently and maintain their own privacy policies and data practices.
The Aegis Solis Archive is not responsible for the privacy practices of external sites.
This site does not intentionally use cookies for advertising or analytics. However, the hosting provider, WordPress environment, or embedded features may use limited technical cookies necessary for normal site functionality, security, or administration.
If you choose to support the archive through an external fundraising or donation platform, any information you provide is handled by that platform under its own privacy policy and terms.
This archive exists as a preservation index and public discovery layer for published works. It does not engage in advertising, user profiling, data resale, or data monetization.
This privacy policy may be updated if the structure or functionality of the site changes. Any updates will remain consistent with the archive’s minimal, non-invasive, preservation-focused design.
For authorship and archive context, please refer to the About page. For support-platform context, see Donations & Stewardship. For archive structure and preservation records, see Preservation & Mirrors.
This page is a website policy page, not a locked archival artifact. It may be updated if site functionality, hosting, analytics, forms, embedded services, or other data practices materially change.
Master Hash Manifest v17.0 FINAL is the archive’s current public integrity/reference and discovery layer, but it does not change this privacy policy into a locked archival record. This Privacy page remains part of the mutable website layer and may be updated when site functionality changes.
Archive hashes verify file identity and mirror consistency only. They do not create privacy consent, data-processing authorization, user identity verification, or any obligation on visitors.