Privacy Policy | Community Connect Australia

This policy covers Community Connect | Events, including Registration Only Events, and Community Connect | Business Directory across web, PWA, Android and iOS.

1. Who We Are

Community Connect Australia ("we", "our", "us") is operated by Sajjad Zaheer, an individual based in New South Wales, Australia. SIZA Apps is the product and initiative name. The service helps people discover, create, share, manage and stream community events and discover or manage community business listings.

Website: siza.info
Privacy and support email: support@siza.info

2. Information We Collect

Depending on how you use the service, we may collect and hold:

Your verified mobile number, name, email address, account identifier, verification status and role.
Account-linking information used to connect a phone login with a previous Google or Microsoft account profile.
Event information, including host and contact details, dates, fixed or prayer-based times, addresses, map coordinates, event type, recurrence details, audience, subject, optional notes, speakers, reciters, posters and organisation details.
Registration Only Event information: the event purpose, capacity, number of places, registration status, form version, question snapshots, answers, consent confirmations, submission and update times, and selected occurrences in a recurring series. Depending on the organiser's form, answers may include names, email addresses, phone numbers, ages, parent or guardian details, dietary requirements, accessibility requirements, selections and free text.
Information about additional attendees when one user registers several people. A registration can request up to five places, and participant information may be submitted for more than one selected occurrence.
Business Directory information, including private listing-owner details, optional ABN details, declarations, referrer information, contact-routing data, exact address and the separately prepared public business profile selected by the owner.
Contact Host or Contact Business enquiries, feedback, reports, replies, support correspondence and moderation history.
Information supplied about another person when an event is submitted on their behalf.
Your selected default city, favourites, layout, map/list preference and notification preferences.
Calendar subscription records, email delivery preferences and push-notification tokens.
Camera, microphone, audio level and orientation information used while preparing or transmitting a live stream.
Live-stream metadata, including event and YouTube identifiers, watch URLs, visibility, start/end status and availability.
AI search prompts, generated responses and reports about AI-generated output, including report reasons, comments, user role, app version and device/browser information.
Technical information such as browser type, operating system, user agent, error information and local app/cache state.

Use of a community events service may reveal or allow inferences about religious interests or affiliations. Registration answers such as dietary or accessibility requirements may also reveal health or other sensitive information. Organisers should collect only what is reasonably necessary. Do not submit sensitive personal information about another person unless it is necessary and you have authority or consent to do so.

3. How Information Is Collected and Held

We collect information directly from you when you create an account or profile, create or share an event, build or complete a Registration Only form, manage attendees, create or contact a business, send a message, choose settings, use AI search, report an AI response, subscribe to notifications or calendars, or start a stream. We may also receive information from another user who submits an event, business or registration on your behalf, and from service providers used to authenticate users and operate the app.

Information is primarily held in Firebase and Google Cloud systems. Some app data is cached on your device to improve launch speed, offline operation and reliability.

4. Why We Use Information

Authenticate users and maintain accounts.
Link eligible former accounts to verified phone accounts.
Create, display, search, share, edit, archive and administer single and recurring events.
Create and administer Registration Only Events, reserve capacity, store versioned questions and answers, provide organisers with response views and CSV exports, and give confirmed attendees controlled access to private venue information.
Create, review, publish, search and administer business listings and promotions, and route private business enquiries without unnecessarily exposing owner contact details.
Provide city filtering, map/list views, favourites, calendar sync and personalised settings.
Send opted-in event reminders, push notifications, community updates and administrator alerts.
Provide AI-assisted event search and investigate reported AI output.
Create, relay, resume, list and administer YouTube live streams.
Prevent misuse, enforce permissions, troubleshoot failures and improve security and performance.
Comply with legal obligations and respond to valid requests.

5. Event Visibility and Sharing

Registered users: may view full event details, including addresses and host phone numbers, subject to their role and app permissions.
Guests and centre events: may see the centre event venue address, but do not receive private host phone details.
Guests and private events: see the suburb only and do not see the full address or host phone number. Directions are unavailable.
Sharing private events: normal users who do not own the private event receive suburb-only share text without the host phone. Owners, Admins and Super Admins may share full details.

Optional event notes are displayed on expanded event cards and included in generated share messages. Do not place confidential addresses, phone numbers or other private information in Notes because Notes may be visible to guests and recipients of shared messages.

6. Registration Only Events

For a Registration Only Event, the organiser chooses the stated purpose, capacity, questions, required fields and any event-specific consent or terms. The app stores a snapshot of the form shown when a registration is submitted so the answers remain understandable if the organiser later edits the form.

Access to answers: answers are available to the registrant, event organiser and authorised Admins or Super Admins where needed for event administration, support, safety or legal compliance. Other attendees and the public cannot see them.
Private venue access: public listings show suburb-level location. The full private venue, saved coordinates and protected poster are limited to the organiser, authorised administrators and confirmed attendees. Cancelling a registration removes attendee access.
Exports: organisers can export attendee responses. After export, the organiser is responsible for securing, using and deleting that copy lawfully.
Recurring events: each occurrence has its own capacity and registration record. Participant information entered for several selected dates is stored against each selected occurrence.
Changed forms: material form changes may require the registrant to review changed questions or consent before updating or confirming a registration.

Registration emails and push messages use minimal booking information and are designed not to include form answers, private venue coordinates or protected poster links.

7. Business Directory Privacy and Messaging

Private business submissions are stored separately from the public directory projection. Public directory data excludes the owner UID, private contact-routing information, ABN number, declarations, moderation records and exact home or mobile-service address unless the owner explicitly chooses and is authorised to publish a storefront address. An ABN status indicator records only the status/name check made at the stated time; it is not identity, ownership, licence, insurance, service-quality or endorsement verification.

When a user contacts a business, the business recipient receives the sender's name, reply contact detail, the business concerned and the message. In-app conversations and notifications may be retained to provide the inbox, delivery status, moderation and support.

8. Live Streaming and Stream History

Hosts may stream through the app or connect a YouTube stream created on another device. A host can choose Public or Private visibility. Private streaming uses YouTube's unlisted/link-only mode: it is not intended to appear in the public streamed-videos list or activate the public Watch on YouTube button, but anyone who receives the YouTube link may be able to view it.

Video and audio sent through the app are relayed to YouTube. We do not operate a separate permanent video archive, but YouTube may record and retain a broadcast under its own policies. We retain limited stream metadata to support resuming, status, visibility, history and link availability. Deleting a record in the app does not by itself delete a video from YouTube.

9. AI-Assisted Search and Reports

AI-assisted search uses Anthropic services to process a search prompt and relevant event information. AI output may be inaccurate, incomplete or inappropriate and should be checked against the event card or host.

Users can report AI output. A report may contain the prompt, response, reason, comments, user identifier or email, role, user agent and app version. Reports are stored in Firestore, emailed to the app operator for review, and used for safety, support and quality purposes.

10. Location, Maps, Prayer Times and City Preference

The app stores a selected default Australian city to filter events and businesses. With device permission, Near Me and Show My Location use your current location to calculate distance or centre a map. We do not use continuous background location tracking. Google Maps may process a searched address and provide a formatted address and coordinates. Directions open an external mapping service.

If an event is set to a prayer-based time, the app uses the event date, selected address coordinates and Australian time zone to calculate the relevant prayer time. The selected prayer name and offset are stored with the event so future recurring occurrences can be recalculated consistently.

11. Calendars, Emails, Azaan and Notifications

Calendar subscriptions may include event names, dates, calculated times, venues and audience details. The app may send daily event reminders, live alerts, community updates, private-stream host links, administrator alerts and operational reminders where enabled or appropriate to an administrator role. Users can manage normal and administrator email preferences in Profile. Device push permission can also be withdrawn in device settings.

Azaan alarms and prayer reminders depend on device permission, operating-system scheduling, sound and Focus or Do Not Disturb settings. A notification may use a bundled alert sound. When a user taps an Azaan notification or selects manual playback, the app may download and cache the current administrator-selected Azaan recording.

12. Service Providers and Disclosures

We do not sell personal information. Information may be processed or disclosed to service providers required to operate the app, including:

Firebase and Google Cloud: authentication, database, storage, hosting, functions, notifications and stream relay infrastructure.
Google Maps: address search, place information and directions.
YouTube: live broadcasts, recordings, watch links and video availability.
Anthropic: AI-assisted event search.
Amazon Web Services Simple Email Service (AWS SES): reminders, community messages, stream-link messages, administrative alerts and AI-report notifications sent from support@siza.info, with replies directed to the same address.
Apple, Google Play and Microsoft: app distribution, installation and platform services governed by their own policies.

These providers may process information in Australia, the United States and other countries where they or their subprocessors operate. Their privacy terms also apply to their processing.

13. Security

We use phone verification, HTTPS, Firebase security controls, role-based permissions and managed secrets. No online service can guarantee absolute security. Please report suspected unauthorised access promptly.

14. Retention, Registration Answers and Archived Records

Events, business listings, promotions, user profiles, stream records, reports, operational logs and moderation records may be retained or archived for service administration, safety, audit, repeat-submission eligibility review, restoration, dispute handling and legal obligations. Public projections are removed when applicable content is archived or marked deleted. YouTube separately controls retention of videos held on YouTube.

Registration answers do not have an automatic 30-day or 90-day expiry. They remain until the organiser deletes the answers, the attendee cancels or deletes the registration, the account-deletion workflow removes them, or we remove them following a valid request or legal requirement. Attendee cancellation permanently deletes saved answers and question snapshots, releases reserved places and removes private venue access. An organiser may permanently delete answers without cancelling the booking; in that case, minimal booking, capacity, status, audit or retry information may remain. Copies already exported by an organiser are controlled by that organiser.

15. Account Deletion

You may delete your account through Profile or request assistance at support@siza.info. The workflow removes submitted registration answers and private registration templates and cancels upcoming Registration Only Events you organise so affected attendees can be notified. Other event, business, moderation and necessary audit records may remain in a restricted archive or community history as described in the deletion flow.

Stream metadata, AI reports, security or moderation records, organiser exports and third-party YouTube content may not be removed automatically. Contact us to request access, correction, restriction, deletion or de-identification review. Some information may be retained where reasonably required for legal, security, fraud-prevention or dispute purposes. See the Account Deletion page.

16. Access, Correction and Complaints

You can update your name, email and default city in Profile and can view, update or cancel eligible registrations in the app. Administrators can assist with corrections. To request access, correction, deletion or a copy of personal information, email support@siza.info.

Privacy complaints should describe the concern and relevant account or event. We will acknowledge the complaint and aim to respond within 30 days. If you are not satisfied and Australian privacy law applies, you may contact the Office of the Australian Information Commissioner at oaic.gov.au.

17. Administrative Access

Admins and Super Admins may access and manage user profiles, full event details, scoped Registration Only responses, archived events, business listings, reports and operational records where needed for moderation, support and service administration. Super Admins manage roles and can review archived or deleted records and previous business submissions. Administrative activity must be for legitimate app purposes.

18. Children and Information About Others

The service is not intended for children under 13 to create accounts independently. A parent or guardian should submit a registration for a child and provide only information reasonably required by the organiser. Some family-event forms may request a participant's age and parent or guardian name. Organisers are responsible for obtaining any consent required for collecting information about minors. A parent or guardian who believes a child's information was submitted without authority should contact us.

19. Changes and Contact

We may update this policy as features, providers or legal requirements change. The latest version and date will appear on this page.

Contact: support@siza.info