easyPass Privacy Policy

1. Information easyPass Accesses

easyPass may request authorization to access Google Drive. Depending on the permissions displayed on the Google consent screen, this access may allow easyPass to create, locate, read, update, and synchronize files used for the application's membership-management functionality.

The Google Drive information accessed by easyPass may include:

• easyPass membership database files, such as database.xlsx.
• easyPass configuration files, such as config.json.
• File names, identifiers, modification dates, and other metadata required to locate and synchronize those files.
• The contents of easyPass files needed to display, update, synchronize, or verify membership records.

2. How Google User Data Is Used

easyPass uses Google user data only to provide and improve user-facing application functionality, including:

• Saving and loading the organization's easyPass membership database.
• Synchronizing membership records across devices authorized by the organization.
• Storing and retrieving easyPass configuration and organizational branding settings.
• Supporting membership management, QR-pass generation, and membership verification.
• Diagnosing errors directly related to the storage or synchronization features.

easyPass does not use Google user data for advertising, marketing profiles, creditworthiness decisions, or unrelated analytics.

3. Storage and Processing

easyPass stores its Google Drive files in the Google account authorized by the user. The application may also keep a local copy or cache on the user's device so that the app can operate and synchronize correctly.

Easy-Apps Solutions does not operate a central membership-content database unless this statement is later updated to describe such a service. Google authentication tokens may be stored securely on the user's device as required to maintain the authorized connection.

4. Data Sharing, Transfer, and Disclosure

Easy-Apps Solutions does not sell Google user data. easyPass does not share, transfer, or disclose Google user data to third parties except:

• When the user or organization explicitly directs or authorizes the disclosure.
• When required to comply with applicable law, legal process, or a valid governmental request.
• When necessary to protect users, the public, Easy-Apps Solutions, or the security and integrity of easyPass, where permitted by law.

easyPass does not allow humans to read Google user data unless the user has given explicit permission for support or troubleshooting, access is required for security purposes, access is required by law, or the data has been aggregated and anonymized for internal operations where permitted by Google policy.

5. Data Protection

easyPass applies reasonable administrative and technical safeguards appropriate to the nature of the data. These may include transport encryption provided by HTTPS and Google APIs, Android platform protections, access controls, and secure token storage mechanisms supported by the device.

No storage or transmission method is completely secure. Users should protect their devices, Google accounts, passwords, and organizational access credentials.

6. Data Retention and Deletion

easyPass files remain in the user's Google Drive until the user or an authorized organization administrator deletes them. Local application data may remain on a device until the user clears the application's data or uninstalls the app.

Users can stop easyPass's future access to Google data by:

• Revoking easyPass access from their Google Account permissions.
• Signing out or disconnecting Google Drive within the app, where available.
• Deleting easyPass files from Google Drive.
• Clearing the app's local data or uninstalling easyPass.

For assistance with deletion requests or privacy questions, contact emad.mpm@gmail.com.

7. Permissions and User Control

Google Drive access is granted only after the user completes Google's OAuth consent process. Users may decline the requested permission, although Google Drive-based storage and synchronization features will then be unavailable.

Users can review or revoke easyPass's access through their Google Account's third-party connections or permissions settings.

8. Children's Privacy

easyPass is intended for use by organizations and authorized administrators. It is not directed to children for independent consumer use. Organizations using easyPass are responsible for ensuring that their collection and handling of member information complies with applicable laws and consent requirements.

9. Changes to This Privacy Policy

This Privacy Policy may be updated when easyPass functionality or data practices change. The effective date at the top of this page will be revised when an update is published. Material changes will be communicated through the application or website where appropriate.

10. Contact

Application: easyPass
Developer/Operator: Easy-Apps Solutions
Email: emad.mpm@gmail.com