App Privacy Policy
The ISPCS mobile app helps registered conference attendees plan their visit and, when they choose, connect with other attendees. The public schedule and conference information can be used without an account.
Information we collect
- Account information supplied by the conference organizers, including name, email address, affiliation, country, and conference role.
- Profile information you choose to add, including a profile picture, biography, interests, and attendee-directory visibility.
- Connections, in-app messages, reports, and account-security records needed to provide and protect attendee features.
- Technical records required for secure sessions, reliability, and abuse prevention. We do not use the app for cross-app tracking or advertising.
How information is used
We use this information only to operate the conference, provide requested networking and messaging features, identify authorized notification senders, secure accounts, enforce the Code of Conduct, and support attendees. A sender's name and optional profile picture may appear in conference notifications they are authorized to send. Directory participation is optional. Email addresses are not displayed to other attendees.
Service providers and disclosure
Cloudflare provides hosting, database, object storage, and security services for the app. Apple Push Notification service delivers iOS notifications; Google Firebase Cloud Messaging delivers Android notifications. These services process device delivery tokens and notification content. Private chat text is not included in push notifications. Information may also be handled by authorized ISPCS and IEEE event personnel for conference operations, safety, and legal compliance. We do not sell personal information.
Reliability reports group app errors by code-location fingerprint, error category, app build, and platform. They do not contain raw error messages, stack traces, passwords, or chat content. Reports are kept for 30 days after their last occurrence.
Optional native crash reporting
In app versions with the More → Crash reporting setting, you may choose to share additional diagnostic reports with Google Firebase Crashlytics. Sharing is off by default. When enabled, reports include crash stacks, relevant application state, app and operating-system versions, device information, and installation identifiers. They help us diagnose failures and receive reliability alerts. We do not attach account names, email addresses, profiles, chat messages, or location to these reports. Google Analytics, advertising identifiers, and advertising tracking are disabled.
Your choice is stored on this app installation and applies while signed in or signed out. You can turn sharing off in the same setting; restart the app afterward so the native SDK fully applies the change. Reports already sent are not removed by turning sharing off or deleting your conference account, because they are not linked to that account. Firebase retains crash data and associated identifiers for 90 days before starting removal from its live and backup systems. See Firebase Privacy and Security for details.
Retention and security
We retain account and conference data only as long as needed for event operations, safety, recordkeeping, and applicable legal obligations. Data is encrypted in transit. Access is restricted to authorized systems and organizers.
Your choices and account deletion
You can replace or remove your profile picture and hide your profile from the attendee directory at any time. You can also delete your account from More → My profile → Delete my account. Deletion removes the account and its associated profile picture, in-app profile, conversations, and messages, subject to limited records retained where required for safety or law.
Contact
Privacy and support questions can be sent to ahmadexp@gmail.com.