82nd 12th District Meeting

Information collected

Only what is needed for access and meeting participation

• Name, email address, account username, email-verification state, approval status, assigned roles, and internal account identifier
• Authentication tokens stored in platform secure storage; the app does not retain the password after entry
• Live meeting content published by authorized administrators, including the administrator username and update time in audit records
• Member posts, selected photos, photo descriptions, author display name, internal account identifier, post time, and moderation records
• Private suggestions, selected topic, account name and email, review status, and submission time
• Carpool request or offer, author name, approximate time, general route or public meeting point, seat count, coordination note, optional details, internal account identifier, and moderation record
• Poll participation stored with the poll ID and internal member identifier but no selected option
• Poll responses stored separately with the poll ID, random receipt, selected option, and submission time but no member identifier
• Aggregate poll counts emailed to the configured super-administrator addresses when a poll closes
• Optional device notification token, device platform, and alert preference when a member turns on push notifications
• Selected photos may contain visual details or image metadata supplied by the device; members should not share sensitive personal, financial, health, or membership information
• Security and operations metadata that hosting providers may process, including IP address, request time, logs, traces, and error details

How information is used

Meeting operations and member communication

• Authenticate members and restrict the meeting app to approved accounts
• Review registrations, assign roles, and provide approved meeting information, live updates, and venue logistics
• Deliver announcements and optional push alerts
• Display approved-member posts and photos, support author or administrator removal, and moderate meeting-inappropriate content
• Provide downloadable resources and route private suggestions to authorized organizers
• Run one-response meeting check-ins, restrict aggregate results, and email closing results to super administrators
• Publish festivities, Phoenix recommendations, transportation information, and approved-member carpool coordination
• Secure, troubleshoot, and operate the service

Registration and approval

Verification does not automatically grant access

A person can request an account and verify the supplied email address, but the app remains locked until a designated super administrator approves the request. Rejected accounts cannot enter the app. Super administrators can review account details, approve or reject access, and publish live meeting updates.

Service providers and external links

AWS-hosted accounts, updates, and private content

Amazon Web Services provides identity, API, logging, tracing, email-delivery, account-recovery, live-content, database, polling, aggregate result-email, carpool, and private photo-storage services. Expo provides device notification-token registration and push delivery after a member opts in. Google Maps, Uber, Lyft, Visit Phoenix, and the Arizona Grand Resort site open only when you select their links and then operate under their own privacy terms. GitHub Pages hosts this policy and support page.

Disclosure and sharing

No sale of personal information

Information is not sold or shared for behavioral advertising. Member posts, photos, and carpool details are disclosed to approved members. Suggestions, account details, and aggregate poll results are limited to authorized organizers. Information may also be disclosed to contracted service providers acting under instructions, or when reasonably required for security, legal compliance, or the protection of users and the service.

Retention

Limited by purpose

Cloud test accounts, approval records, test posts, test photos, suggestions, notification subscriptions, and live-content audit data are deleted or de-identified no later than 90 days after testing ends. Service logs are configured for 30 days. Production community posts, photos, and suggestions are deleted or de-identified no later than 90 days after the meeting ends unless they are needed to address a safety, conduct, security, or legal issue. Carpool posts are removed after the relevant ride or no later than 30 days after the meeting, subject to the same limited exceptions. Poll participation and separated responses follow the committee-approved poll retention schedule. Push subscriptions are removed when alerts are turned off, the member signs out, or an account is deleted, and are purged after the meeting. On-device authentication tokens remain until sign-out, expiry, app removal, or account deletion.

Security

Layered safeguards

Data is encrypted in transit, cloud tables use server-side encryption and point-in-time recovery, access is gated by email verification, administrator approval, and assigned roles, and private photos are stored in a non-public bucket and delivered through short-lived signed links, while uploads have type and size limits. Poll participation identity and selected responses are stored separately. No system can guarantee absolute security.

Audience

For adult meeting participants

The app is intended for adult meeting attendees, organizers, and authorized testers. It is not directed to children and does not knowingly collect personal information from children.

Artwork and local assets

Meeting artwork is bundled with the app

The district-meeting logo, fraternity shields, temple illustrations, and additional logo concepts supplied by the organizer are packaged inside the app. Merely viewing these images does not contact an external image server, create an advertising identifier, or disclose personal information. The app does not use the images as tracking pixels.