Mobile app security and privacy

This article explains how the EnaFeedback mobile app protects data on the device and what it sends where: the app lock, how sessions are stored, what happens when you delete and reinstall the app, crash reports, how photos and recordings are handled, legal documents and the permissions the app asks for. It applies to visitor, staff and admin modes. For server-side security, see Security and data.

Required role / permission and versionCopy Anchor Link

• No role or permission needed; the settings are on the Settings tab in every mode.
• The device-passcode fallback for the app lock and crash reports need EnaFeedback Mobile 1.1.0 or later. The server receiving crash reports must be EnaFeedback 2.1.101 or later.

App lockCopy Anchor Link

The app lock stops someone else from using an open staff or admin session when they have your phone. We recommend it for shared shift phones.

While the lock is on:

• When you leave the app (send it to the background) and when you restart it, the Locked screen appears: "Unlock to continue." Tap Unlock.
• Biometrics are tried first; if the device has none or they fail, the device passcode (PIN) is asked for Requires: EnaFeedback Mobile 1.1.0.
• If the device has no screen lock at all, the lock cannot be turned on and this note appears: "This device has no screen lock, so the app lock stays off." This keeps you from being locked out of the app.

How sessions are storedCopy Anchor Link

• Staff and admin sessions, saved organizations and the location session are kept in the device's secure storage: on iOS in the Keychain, restricted to this device (not moved to another device by a backup); on Android in storage encrypted with the Android Keystore.
• Session credentials (sign-in tokens and the device ID) are sent only to the EnaFeedback server of the organization you are connected to; they never go to the organization discovery service or to other organizations.
• The staff session renews in the background. When you sign out (Sign out), the session is also ended on the server.

Deleting and reinstalling the appCopy Anchor Link

• iOS: iOS keeps Keychain entries on the device when an app is deleted. EnaFeedback detects a fresh install and clears old organizations, the location and sessions at launch Requires: EnaFeedback Mobile 1.1.0. After reinstalling, add the organization and sign in again.
• Android: deleting the app also deletes its data.
• Updating the app does not remove saved organizations or sessions.

Crash reportsCopy Anchor Link

Requires: EnaFeedback 2.1.101 · EnaFeedback Mobile 1.1.0

When the app crashes or catches an error, it creates a short error record. Records are kept on the device (up to 20) and sent to your organization's EnaFeedback server at the next launch or when you return to the app.

• A record contains the error message, a shortened stack trace, the platform and the app version.
• Sign-in tokens are removed from the record before it is sent.
• Reports go to your organization's server; the app has no third-party crash-tracking or ad-tracking service.

Photos, videos and voice recordingsCopy Anchor Link

• Visitor forms: photos are scaled down on the device so the longest side is 1920 pixels before upload. The server converts photos to WebP and does not keep photo metadata, including location. You can add up to 5 photos (up to 10 MB each), one video (up to 50 MB) and a voice recording (up to 15 MB); video and voice recordings are limited to 2 minutes.
• Message attachments Requires: EnaFeedback 2.2.0 · EnaFeedback Mobile 1.9.0: photos are scaled down the same way; the server confirms them, converts them to WebP and removes location data. Up to 5 photos per message.
• Media permissions are asked for only when you want to attach something.

Details: Media attachments.

Legal documentsCopy Anchor Link

Requires: EnaFeedback Mobile 1.3.0

Settings → Information and support → Legal and privacy opens the terms of use, privacy policy, KVKK and GDPR privacy notices, the end-user license agreement and other documents inside the app.

• Documents load from www.enafeedback.com: in Turkish when the app is in Turkish, otherwise in English.
• The latest version of an opened document is saved on the device. Without a connection, the saved copy is shown: "Showing the saved copy; the latest version could not be loaded."
• For a request about your personal data, use Data subject request. See KVKK compliance.

App permissionsCopy Anchor Link

The app asks for a permission only when you use the related feature. If you decline, only that feature stops working.

The app does not ask for location (GPS) permission; the location comes from a QR code or NFC tag. It does not ask for notification permission either, because push notifications are not active yet. Camera and NFC are not required hardware; on devices without NFC the app works with QR codes.

Known limitsCopy Anchor Link

• The app lock relies on the device's own screen lock; without one, the app lock cannot be turned on.
• Crash reports are written to your organization's server logs; there is no separate screen for them in the admin panel.
• The About screen shows the device ID masked. When you contact support, you can share the version and system status from this screen.

Related articlesCopy Anchor Link

• Mobile app overview
• Setup and organizations
• Security and data
• KVKK compliance
• Media attachments