easyPass Privacy Policy

1. Information easyPass Accesses

easyPass requests your Google account email for sign-in and to check whether your account is authorized to access an organization and use a particular role. Its Google sign-in configuration also requests an account identifier and basic profile information, such as your name and profile photo, which Google may return with the sign-in result.

easyPass requests the per-file Google Drive permission drive.file. It accesses files you select or authorize through Google Picker and files the app creates, subject to your Google Drive permissions. This does not grant access to every file in your Drive. Information accessed may include:

• easyPass membership database files, such as database.xlsx.
• easyPass configuration files, such as config.json.
• Organization folders and branding or logo files selected or created for use with easyPass.
• File names, identifiers, parent folders, trash status, sharing permissions, and access capabilities needed to locate, manage, and synchronize organization files.
• Membership records: member names and IDs, membership status, QR pass credentials, update timestamps, and optional phone numbers, email addresses, addresses, and notes.
• Organization configuration: settings, the storage owner's email, authorized account emails, roles and access status, Drive permission IDs, role password hashes, organization name, colors and logo references, and optional-field settings.
• Pro status and, where present, the Google Play purchase token and activation timestamp stored in the organization's configuration.

2. How Google User Data Is Used

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

• Signing in and checking the signed-in email against the organization's authorized accounts and roles.
• Creating, loading, updating, and managing the organization's easyPass files and membership records.
• Synchronizing membership records across devices authorized by the organization.
• Storing, retrieving, and displaying organization settings, branding, logos, and Pro status.
• Managing invitations and file-level Drive access for authorized organization accounts.
• 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

Google Drive is easyPass's provider for organization-file storage and synchronization. Organization files are stored in the Google Drive account and folder chosen for the organization, under the storage owner's control. Authorized members access those shared files using their own approved Google accounts.

The app also stores membership records in an Android app-private local database and uses app-private preferences and cache files for connection settings, synchronization, and exports. Membership content is synchronized between the app and Google Drive; Easy-Apps Solutions does not operate a central membership-content database for this functionality.

4. Data Sharing, Transfer, and Disclosure

Easy-Apps Solutions does not sell Google user data or share it for advertising. easyPass transfers organization files and related metadata to and from Google Drive to provide storage and synchronization. Data may also be disclosed:

• To authorized organization members: the storage owner can use easyPass to grant file-level Google Drive access to the organization's database, configuration, and logo. Read or write access depends on the member's role and the permissions on each file. For example, Scanners receive read access, Managers can update the membership database, and Directors can also update configuration and branding.
• When the user or organization explicitly directs or authorizes another disclosure, such as sharing a QR pass or exporting membership records.
• 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.

Authorized organization users can view data available through their permissions. Easy-Apps Solutions does not routinely access organization files. Its personnel may read Google user data only with explicit permission for support or troubleshooting, when necessary for security purposes or legal compliance, or when the data is aggregated and anonymized for internal operations as permitted by Google's Limited Use requirements.

5. Data Protection

easyPass uses the following protections:

• HTTPS for Google API traffic.
• Google Picker and the per-file drive.file permission to authorize access to selected files and files created by the app.
• Checks of the signed-in email against the organization's active access roster and role permissions, together with file-level Drive permissions.
• Android app-private storage for the local membership database, preferences, and cache files.
• AES-GCM encryption for newly generated invitation payloads, using a key derived from the invitation access code. Invitations identify the organization configuration, invited email, and role; joining also requires the approved Google account and Drive access.

Invitation encryption does not mean that organization Drive files or the local membership database are encrypted end-to-end by easyPass.

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

Organization files remain in the chosen Google Drive storage until the storage owner or another account with the necessary permissions deletes them, or an organization access-reset operation replaces and deletes the old files. Local records and cached files may remain until removed by the app, cleared through Android's app-data settings, or removed when the app is uninstalled.

Users can control access and remove data in different ways:

• Revoke easyPass's authorization in Google Account permissions to stop future authorized Google API access. This does not delete organization files or erase local copies already downloaded.
• Use the app's leave-organization or sign-out controls to clear the local membership records and saved organization connection. These controls do not delete the shared Drive files or necessarily remove cached exports.
• Ask the storage owner to remove an authorized account's organization access and file-level Drive permissions. Removing access does not remotely erase copies already downloaded or exported.
• Delete organization files in Google Drive using an account with the necessary permissions. Drive deletion does not erase copies held on other devices or previously exported files.
• Clear easyPass's app data in Android settings or uninstall the app to remove its current app-private local data. This does not delete organization Drive files, separately saved or shared exports, or all backups. Android backup is enabled, so backup copies may remain outside the app installation.

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.

Google Picker lets users select organization files or folders when additional per-file authorization is needed. Authorization for easyPass to use a file and the Google account's permission to access that shared file are separate requirements; the app also checks organization account and role authorization.

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