Privacy Policy for EasyHisab
Last updated: 3 Nov, 2025
EasyHisab (“we”, “our”, or “us”) respects your privacy and is committed to protecting your personal information. This Privacy Policy explains how we collect, use, and protect the data you provide when using our mobile application (“App”).
When you use EasyHisab, we collect only the minimum information required to enable Google sign-in and personalize your experience:
Google Account Information: Your name, email address, and profile image provided by Google when you sign in.
We do not collect passwords or other sensitive account details.
We use the collected information to:
Authenticate your account through Google Sign-In.
Display your name and profile image inside the app.
Personalize your user experience.
We do not sell, rent, or share your personal information with third parties for marketing or advertising purposes.
Your data is stored securely using Google’s authentication and database services. We use industry-standard encryption and access controls to prevent unauthorized access or misuse.
We do not share your data with anyone except as required by:
Law or legal processes (if authorities request information).
Google services that handle sign-in authentication and data storage.
You have the right to:
Access and review the information we have about you.
Request deletion of your account and associated data.
To do so, contact us at: muhammadshahzaddeveloper@gmail.com
EasyHisab uses Google Sign-In for authentication. Your use of Google Sign-In is governed by Google’s own Privacy Policy.
EasyHisab is not designed for children under 13. We do not knowingly collect data from anyone under this age.
We may update this Privacy Policy periodically. The latest version will always be available in the app and will include the “Last updated” date.
If you have any questions or concerns about this Privacy Policy or your data, contact us at:
Email: muhammadshahzaddeveloper@gmail.com
Would you like me to adjust this for Google Play Console compliance format (so you can paste it directly in the “Privacy Policy URL” field)?