21st Masonic District of Ohio — Privacy Policy
Effective November 22, 2026
This policy explains how information is handled by the 21st Masonic District of Ohio app and the District website at masonicoh21.com. Schill Solutions provides and maintains the app with authorized District administrators. For privacy questions or requests, contact chris@schillsolutions.com. Do not send your password.
Information We Handle
- Accounts and access: Name, email address, account identifiers, approval status, application role, profile changes, preferences, sign-in sessions and account requests. The app uses the existing District website login. For sign-in, you enter your password on the website in the system sign-in browser. If you change your password in the app, the new password is sent over HTTPS to the District website and is not stored on your device. WordPress stores the password as a hash. A confirmation email contains no password.
- District records: Member names and contact information, addresses, lodge relationships, offices, service history, honors, photographs and other information supplied by members, authorized administrators or existing District records. These are District records, not contacts imported from your phone.
- Content and communications: Event submissions, resource files, record changes and messages you send for support. Administrative audit records can identify the actor, action, affected record and recorded changes. Communication History can retain recipient names and addresses, sanitized subjects, delivery status, channel, timing and related record identifiers. That history does not store message bodies, attachments, passwords or password-reset links.
- Technical information: Network requests, search requests, IP addresses, browser or device information, sign-in/security activity, timestamps and errors may be processed by the website, hosting and security services. The app’s icon and display-mode choices are local device settings.
Why Information Is Used
Information supports sign-in, approval and access control; District directories, history, events and resources; account administration; requested communications; security; troubleshooting; service operation and recovery. Search requests are sent to the District service to return results. Public website analytics help us understand page use and improve the website.
Who Can Access Information
Approved members can view the District directory. Documents have additional folder-audience restrictions, such as All Members, District and Admin, or Admin Only. Authorized managers can administer the records and review tools available to their role. Publicly published website content can be viewed without signing in.
Authorized District and Schill Solutions administrators, and providers supporting hosting, security, communications or delivery, may handle information for those services. A shared WordPress login can also be used by other District services, including Masonic Bookkeeper. Communication metadata from those services may appear in the site’s administrative Communication History. Their separate records and policies are not replaced by this policy.
Website Cookies, Analytics and External Services
The website uses WordPress sign-in cookies and security services, including login-protection tools and Cloudflare bot protection. These may process IP addresses and request information and set security cookies. Blocking required cookies can prevent sign-in.
Public website pages use Schillytics analytics. It records page views, downloads, outgoing-link activity, site-search or interaction labels, referral/campaign information, general country information and coarse browser/device information. Its daily visitor identifier is derived from the IP address, date and coarse device/browser information. It does not store the raw visitor IP address in its analytics tables or use an analytics cookie or local-storage visitor identifier. This does not mean that hosting or security logs omit IP addresses. Schillytics excludes logged-in users and respects supported Do Not Track, Global Privacy Control and analytics opt-out signals; those exclusions do not disable necessary hosting or security processing.
Public pages also load GoDaddy performance-monitoring resources, Google Fonts and Zeffy resources used for fundraising forms. Loading external resources can disclose your IP address and browser/request information to their providers. If you use an external form, donation service, map or another website, information you enter there is handled by that provider. The native app has no advertising or native analytics integration and does not request access to your device’s contacts, calendar, microphone, camera or precise location. Opening a website from the app is subject to that website’s practices.
Provider information: GoDaddy, Cloudflare, Google, Zeffy and Expo. The District calendar uses a shared Google Calendar feed; it does not read your phone’s calendar.
Optional App Notifications
The District app offers optional push notifications. To receive them, turn on Push Notifications under Account, save your preferences, then select Enable This Device and allow notifications in your device settings. Your event preferences control which optional event alerts you receive. Device registration uses a device identifier, platform, Expo project identifier and push token associated with your app session. Expo processes the push token and notification payload to deliver alerts through Apple Push Notification service on iOS or Firebase Cloud Messaging on Android. Payloads use generic text and internal routing identifiers; protected records still require sign-in. You can change app preferences or turn off system notification permission. Signing out normally revokes the current session and its device registration when the server can be reached; if remote revocation cannot be confirmed, the app reports that.
Storage, Security and Retention
The app connects to the District service over HTTPS and stores its app credential using iOS Keychain or Android secure storage. Website data is hosted through GoDaddy; authorized Schill Solutions systems and protected backups support operation and recovery. Access controls restrict member records and private file downloads. These measures are not a claim of end-to-end encryption.
Sign-in requests and authorization codes expire after five minutes. App sessions have a thirty-day expiry and can be revoked sooner. Expiry limits access; it does not mean that every related database or log record is immediately erased.
Other District records, uploaded content, audit records, Communication History and website analytics do not currently have an automatic deletion schedule. They remain stored unless manually removed or changed. Signing out or uninstalling the app does not delete server records. Hosting/security logs and backup copies have separate lifecycles; no specific automatic expiry period for those copies is promised here. Contact us to ask what remains about you and to request correction or removal.
Your Choices and Account Requests
You can update the profile and notification preferences offered in the app. For directory corrections, access questions, a copy of your information or deletion, email chris@schillsolutions.com and identify the District app and your account email. We may need to verify your identity before disclosing or changing information.
The app’s Account → Request Account Deletion control records a request; it does not automatically erase an account or associated data. Email the privacy contact for follow-up, including if you cannot access that screen. Requests must account for the shared WordPress login, other connected services and independently maintained District records. Disabling access alone is not deletion. We will explain the proposed scope, any information that would remain and the reason before an irreversible action. This policy does not promise an automated erasure process or a fixed completion deadline that is not currently implemented.
Documents opened in the app can use temporary device storage. Copies you explicitly save or share to another app are controlled by that destination and are not removed by signing out here.
Policy Changes and Contact
Changes to these practices will be reflected on this page with an updated effective date. For questions about this policy or your information, contact Schill Solutions at chris@schillsolutions.com.