1. Purpose and Scope
This page documents proposed privacy principles under consideration by the International Pagan Society. It applies only to future IPS-controlled website services, and only after any resulting policy is formally adopted. It does not create contractual rights and is not legal advice.
This draft does not claim present compliance with the GDPR, UK GDPR, CCPA/CPRA, COPPA, HIPAA, FERPA, PCI DSS, or any other data-protection law. Adoption of a final policy would require jurisdiction-specific legal counsel.
Nothing on this page should be read as stating that IPS is a controller, processor, charity, company, trust, foundation, archive, employer, university, publisher, religious institution, or otherwise regulated entity, except where that status is independently verified.
2. Current Website Data Flows
This inventory is based strictly on inspection of the website's source code. It lists only features actually present in the repository.
| Website feature | Current status | Possible data involved | Destination or processor | Verification status |
|---|---|---|---|---|
| Basic page requests | Static pages served on request | IP address and standard technical request data may be processed by hosting/CDN infrastructure | Hosting infrastructure details require deployment-level verification | Requires deployment verification |
| Footer newsletter signup | Interface present; input and submit button disabled in source | Email address, if ever enabled | No mailing-list service connected in source | Confirmed disabled in source |
| Contact & Correspondence framework | Disabled preview form; entire fieldset is disabled | Name, email, jurisdiction, subject, message, if ever enabled | No intake service connected in source | Confirmed disabled in source |
| Frequently Asked Questions search preview | Disabled input and button | None | Not applicable | Confirmed disabled in source |
| Site search & discovery preview | Disabled filters and controls | None | Not applicable | Confirmed disabled in source |
| Press & media inquiry form | Disabled preview form | Name, organization, email, topic, if ever enabled | No intake service connected in source | Confirmed disabled in source |
| Donate page (one-time USD donation) | Active external link to Stripe's hosted checkout; no local form | None collected by this website; payment and contact details are entered only on Stripe | Stripe (donate.stripe.com or buy.stripe.com) | Confirmed in source — this site stores no card or payment data |
| Other donation pages (Ways to Give, Why Donate, Institutional Giving) | Static informational pages; disabled inquiry forms for alternative giving channels | Contact/inquiry fields only, if ever enabled; no card data is present in source | Not connected | Confirmed disabled in source |
| Donation success & canceled templates | Static design previews; source comments confirm they do not read query parameters, cookies, or transaction state | None | Not applicable | Confirmed in source |
| Volunteer, fellowship & partnership application forms | Disabled preview forms | Application fields, if ever enabled | Not connected | Confirmed disabled in source |
| Header mobile-menu toggle | Local browser script only | None collected or transmitted | Runs entirely in the visitor's browser | Confirmed in source |
| External links (partners, references, etc.) | Standard hyperlinks | None collected by IPS by leaving this website | The destination site's own practices apply once a visitor leaves | Not applicable |
Hosting infrastructure details require deployment-level verification. No hosting, CDN, analytics, or email-delivery provider is named in this repository, and none should be inferred.
3. Proposed Data-Minimization Principles
Proposed principles — not verified operational controls- Collect only what is necessary for a specific, disclosed purpose
- Define a lawful, disclosed purpose before any collection begins
- Avoid collecting sensitive-category data by default
- Minimize free-text fields that could invite unnecessary disclosure
- Restrict access to any personal data on a need-to-know basis
- Avoid indefinite retention of personal records
- Verify any third-party processor before it is connected
- Document deletion procedures before intake begins
- Provide transparent, plain-language notices at the point of collection
- Apply privacy-by-design and privacy-by-default to any future feature
4. Legal and Governance Review
Adoption of a final privacy policy would require, at minimum:
- Determination of the Society's organizational and legal identity
- Identification of applicable jurisdictions
- Assignment of controller and/or processor roles
- Selection and documentation of lawful bases for any processing
- Age-restriction and children's-privacy analysis
- Cross-border data-transfer review
- Vendor and processor agreements
- Incident-response procedures
- A complaints and escalation process
- Regulator-cooperation responsibilities, where applicable
- A named approval authority
- A named policy owner
No lawful basis — consent, legitimate interests, public task, contractual necessity, or legal obligation — has currently been selected or applies to any processing described on this page.
6. Forms, Communications and Records
Every form currently present on this website is a natively disabled visual preview. None of them submit, store, upload, email, or transmit information. The Footer newsletter form exists as an interface only and is not connected to a mailing list.
| Form or control | Location | Operational status |
|---|---|---|
| Footer newsletter signup | Sitewide footer | Inactive visual preview |
| Correspondence intake worksheet | /contact/ | Inactive visual preview |
| FAQ search preview | /questions/ | Inactive visual preview |
| Site search & discovery preview | /search/ | Inactive visual preview |
| Media inquiry form | /press/ | Inactive visual preview |
| Giving inquiry form | /donate/ways-to-give/ | Inactive visual preview |
| Donate button (links to Stripe) | /donate/ | Active external link — no local form |
| Institutional giving inquiry | /donate/institutional-giving/ | Inactive visual preview |
| Volunteer & fellowship applications | /get-involved/volunteer/ | Inactive visual preview |
| Partnership application | /about/partnerships/application/ | Inactive visual preview |
| Dispatches subscribe form | /dispatches/ | Inactive visual preview |
No claim is made about encryption, confidentiality, deletion, access restrictions, or retention periods for these forms, because none of them are currently operational.
7. Donations and Payment Processing
The Donate page links to a Stripe-hosted Payment Link for one-time USD donations. Payment-card numbers, bank details, and billing information are entered only on Stripe's own checkout page and are never collected, transmitted, or stored by this website or its hosting infrastructure.
Source-code comments on the donation success and canceled templates confirm that those pages do not read query parameters, cookies, or any client-side state to determine transaction status. This website does not redirect Stripe checkout to those templates in this release.
A future server-side payment integration — transaction verification, webhook handling, donor-records controls, a refund policy, and independent security review — would require its own payment-specific privacy disclosures before it could be enabled. This draft does not claim PCI DSS compliance, and no receipts, donor records, recurring payments, tax records, refunds, or financial profiles are generated or stored by this website.
8. Cultural and Archival Sensitivity
Any future archival or repository work would need to apply heightened care to culturally sensitive material, sacred or restricted knowledge, oral histories, and community provenance. Proposed considerations include Indigenous or traditional-knowledge protocols, contributor consent, removal and correction requests, contextual integrity, access restrictions, community authority, and archival dignity.
No cultural-data governance, community-consent, restricted-access, archival-intake, or traditional-knowledge protocol has yet been adopted.
Nothing in this section should be read as a claim of ownership, custody, jurisdiction, or authority over any culture, tradition, or community.
9. Individual Rights and Requests
Legal rights over personal data depend on jurisdiction, organizational status, the specific data processing involved, and applicable law. This page does not state that every visitor automatically holds GDPR or other statutory rights through IPS.
No verified subject-access request system currently exists. No privacy officer or data-protection officer is currently published. No formal verification, correction, portability, objection, restriction, or deletion process has been adopted. Future procedures would require legal and security review, and no response deadline is promised here.
Access
Procedure not establishedCorrection
Procedure not establishedDeletion
Procedure not establishedRestriction or Objection
Procedure not establishedPortability
Procedure not establishedComplaint or Escalation
Procedure not established10. Security, Retention and Accountability
A future policy could propose a control framework including:
- Access control
- Least privilege
- Secure configuration
- Dependency updates
- Secret management
- Backups
- Logging
- Incident response
- Breach assessment
- Vendor review
- Data inventory
- Retention schedules
- Deletion verification
- Policy review
- Staff and volunteer training
Listing a control does not mean it is implemented, audited, certified, or continuously monitored. This draft does not claim encryption at rest, encryption in transit beyond ordinary HTTPS assumptions, ISO 27001, SOC 2, Cyber Essentials, penetration testing, vulnerability scanning, 24/7 monitoring, disaster recovery, data residency, geographic redundancy, immutable backups, certified deletion, privacy audits, or named security personnel, unless independently verified.
Proposed Retention Categories
| Data or record category | Current collection status | Proposed retention approach | Approval required |
|---|---|---|---|
| Hosting request logs | Processor behavior requires verification | No schedule adopted | Legal and technical review required |
| Newsletter submissions | Not collected by current page | Retention period not established | Legal review required |
| Contact inquiries | Not collected by current page | Retention period not established | Legal review required |
| Donation records | Not collected by current page | Retention period not established | Legal, financial review required |
| Media inquiries | Not collected by current page | Retention period not established | Legal review required |
| Volunteer/application information | Not collected by current page | Retention period not established | Legal review required |
| Safeguarding reports | Not collected by current page | No schedule adopted | Legal, safeguarding review required |
| Archival submissions | Not collected by current page | No schedule adopted | Legal, cultural-governance review required |
| Consent records | Not collected by current page | Retention period not established | Legal review required |
| Analytics data | Not collected by current page | Not applicable | Legal review required if ever introduced |