Your app permissions.

Some permissions are requested during setup; others when you open a feature. The prompts and choices depend on your device, operating system and app version. A permission declared by the app is not the same as permission granted by you.

You can decline a request or change your choice later in device settings. This can limit the feature described below. Allowing a device permission does not subscribe you to the newsletter or give separate consent to publish your information.

• Camera: taking photos or videos and using video during SoApp calls. Without camera access, these capture and video features are unavailable.
• Microphone: recording voice messages, recording sound with video and speaking during voice or video calls. Without microphone access, SoApp cannot capture your voice for those features.

Joining a call with audio or video enabled sends that media to the call participants. Sending a recording or photo shares it with the recipients you choose.

Photo-library access lets you attach existing media and find photos or videos associated with an event. Event matching reads capture times, available photo GPS metadata and the device's local record of presence in the event zone. Matching runs on your device.

Library access can cover multiple photos and videos. On iOS, limited access restricts the scan to the items you allow. On Android, event scanning requests photo and video library access; older versions use storage permissions. Android can also ask for photo location metadata. Declining that extra location access still allows scanning, but GPS matching may be unavailable.

Manual sharing lets you review and choose items before sending. If you choose automatic event sharing, matching items with GPS inside the event zone are uploaded to the event gallery without a separate item-selection step. Library permission by itself does not start an upload.

Declining library access prevents event gallery scanning. Files you share may contain location or other metadata, so check what you share with other participants.

Location access supports finding an event address and detecting when you enter its geographic zone. Precise location helps determine whether you are inside the configured boundary; reduced accuracy can limit matching and arrival alerts.

Background location: SoApp can monitor event zones and notify you of arrival while you are not using the app. Android requests background location separately; on Android 11 and later, this is the Allow all the time choice in settings. iOS can request Always access for event region monitoring.

If you decline background access, arrival detection may still work while the app is open and foreground location is allowed. Background alerts also depend on notification permission, location services and the operating system's battery and delivery rules. Force-quitting the app can stop background delivery. Alerts are not guaranteed to arrive immediately.

With contacts access, SoApp reads contact names and phone numbers to display people you know and help you select recipients. Contact loading builds an index on your device; it does not upload contact names or the address-book rows.

Phone-number matching uses the SoApp service. Phone numbers for contacts displayed in a contact picker can be sent automatically to SoApp's search service to check for matching accounts. A lookup can also happen when you select a contact. This means phone numbers do not always stay on your device.

Declining contacts access prevents address-book loading. SMS invitations open your phone's messaging app with the recipients and message filled in; you decide whether to send. This invitation flow does not require access to read or send SMS in the background.

Notifications alert you to messages, event arrivals and incoming calls. Declining notifications can stop visible alerts, including background arrival and call alerts. You can manage notification categories and sounds in device settings.

SoApp calling also uses audio routing, Bluetooth headset support and the phone's call interface. Android may ask for Phone access during setup. Full-screen call alerts, ongoing-call services and wake controls help display and maintain calls when the screen is locked or the app is in the background.

Android phone permissions: the app currently declares access to phone state, the device's phone number, placing phone calls and reading the call log as part of its call integration. These are sensitive capabilities: if granted, call-log access can expose phone call history. Their availability and prompts depend on Android and installation rules. Declining phone or Bluetooth access can limit call setup, incoming-call handling or headset use.

On supported devices, you can opt into biometric login. SoApp uses the device's secure credential storage and biometric authentication to unlock saved sign-in credentials. SoApp does not receive your fingerprint or facial template from this authentication flow.

You can decline biometric login and use the ordinary sign-in process. Changing enrolled biometrics can invalidate saved credentials and require you to sign in again.

Internet and network access connect SoApp to its services. Vibration supports alerts and feedback. Restart handling restores Android event-zone monitoring after a reboot, and background call or notification capabilities support ongoing calls and alerts.

Android can check whether certain sharing or messaging apps are installed to open supported links or share content. This does not grant access to information inside those apps. An iOS development build can request local-network access to connect to the development server.

• Android: open Settings → Apps → SoApp → Permissions, then choose a permission and allow or deny it. Location, notifications and full-screen call alerts can have additional settings. Menu names vary by device.
• iPhone or iPad: open Settings → Privacy & Security and choose the relevant category, or open SoApp's settings. Review access to contacts, photos, camera, microphone and location; manage notifications separately.
• Webapp: camera, microphone and location access are managed through your browser's site permissions. A browser prompt is separate from mobile app permissions.

Revoking a permission stops future access controlled by that setting. It does not erase information or content already sent. For removal requests, see Delete account or contact contact@soappsocial.com.

For device-specific instructions, see Android permission settings or Apple privacy controls.

The public marketing website does not request the mobile permissions described above. It has a separate Website Privacy Notice and Cookie notice. If a prompt is unclear or a feature behaves differently, contact SoApp for help.