Privacy Policy

 

Privacy Policy for TalktoAcharya

At TalktoAcharya, we value your privacy and are committed to protecting your personal information. This Privacy Policy outlines the types of data we collect, how we use it, and the steps we take to safeguard it. By using our services, you agree to the terms outlined in this policy. Please take a moment to read through this document to understand how your information is handled.

1. Access and Subscription
To access and use our services, you must log in to the TalktoAcharya app. The app operates on a subscription-based model, which requires an active subscription to access our features.

2. Information Collection and Use
We collect certain personally identifiable information in order to enhance your experience and provide our services. The information we may collect includes, but is not limited to: Full Name, Email Address, Phone Number, Physical Address, Gender, Date of Birth, Anniversary Date, Profile Picture, and Location Information. This information is collected to personalize your experience and ensure that we can provide the best possible service to you. We retain and use this information only as necessary to provide our services and in accordance with this Privacy Policy.

3. Permissions Required
To offer our services effectively, the TalktoAcharya app requires the following permissions: Camera: For video meetings, ceremonies, and recording features. Device Audio: For video meetings, ceremonies, and voice-based services. Contacts (READ_CONTACTS, WRITE_CONTACTS): To manage and sync your contacts for relevant services. Location (ACCESS_COARSE_LOCATION): To offer location-based features. Device Permissions (INTERNET, ACCESS_NETWORK_STATE, RECEIVE_BOOT_COMPLETED, VIBRATE): For functionality and notifications.

4. Third-Party Services
TalktoAcharya integrates with several third-party services to enhance your experience. These third-party services may collect data used to identify you. Some of the services we use include: Google Play Services, Google Analytics for Firebase, Facebook. We recommend reviewing the privacy policies of these third-party services to understand how your data is handled.

5. Log Data
In the event of an error with our service, we may collect Log Data from your device. This information includes: IP address, Device name, Operating system version, App configuration, Usage statistics, and Other relevant details. This data is collected for diagnostic purposes and to improve the performance of our services.

6. Cookies
Although we do not directly use cookies in the TalktoAcharya app, third-party services integrated into the app may use cookies to collect anonymous data and improve their services. Cookies are small text files placed on your device to uniquely identify you. You have the option to accept or reject cookies, though rejecting them may impact some features of our app.

7. Service Providers
We may employ trusted third-party companies and individuals to assist us in providing and maintaining our services. These third-party providers have access to your personal information, but are obligated to keep it confidential and use it only for the purpose of providing services on our behalf.

8. Data Security
We take the security of your personal information seriously. While we implement commercially reasonable measures to protect your data, no method of electronic transmission or storage is 100% secure. As a result, we cannot guarantee absolute security.

9. Links to Other Websites
Our services may contain links to external websites. Please note that we do not control these external sites and are not responsible for their content or privacy practices. We encourage you to review the privacy policies of any third-party websites you visit.

10. Children’s Privacy
TalktoAcharya does not target or knowingly collect personal information from individuals under the age of 13. If we discover that a child under 13 has provided us with personal information, we will take steps to delete it from our systems. If you are a parent or guardian and believe your child has shared personal information with us, please contact us so we can take appropriate action.

11. Payments
For any paid services or products, TalktoAcharya uses third-party payment processors. We do not store or collect your payment card information. All payment transactions are processed directly by our third-party processors, and their respective privacy policies govern the handling of your payment information.

12. Changes to This Privacy Policy
We reserve the right to update or modify this Privacy Policy at any time. Any changes will be posted on this page, with an updated effective date. We encourage you to review this policy periodically to stay informed of how we protect your information. This Privacy Policy is effective as of 2024-07-01.

13. Contact Us
If you have any questions or concerns about this Privacy Policy, please feel free to contact us at info@talktoacharya.in.

Found it — the bug is a timing issue with hidden elements, and it explains why local "looks perfect" while live doesn't (timing is non-deterministic, so it's really just luck either way). Root cause javascript This runs initGoogleAuthButton() the moment the Google script finishes loading — which is almost immediately on page load, before the user has even opened the login modal. But your modal starts hidden: css .modal-overlay { display: none; ... } An element with display: none (or a hidden ancestor) always reports offsetWidth = 0. So: javascript width: container.offsetWidth, // reads 0 when the modal hasn't been opened yet Google then falls back to its own default minimum button width instead of matching your container — which is exactly the shrunk-looking button you're seeing. On local it likely "worked" purely by coincidence of load timing, network speed, or you happening to open the modal slowly enough for something to re-trigger — not because the code was actually correct. Fix — render the Google button only when the modal is actually opened, not on page load Since showLoginModal() lives in auth_system.js (which you haven't shared), the safest fix that doesn't require touching that file is to watch for the modal's active class being added, and render the button at that moment — when its real width is available. Replace your current Google script block with this: html