Refund & Cancellation Policy

Refund & Return Policy for TalktoAcharya

1. Refund Eligibility
Refunds will only be considered if a request is sent to support@talktoacharya.in within 2 hours of payment. No refund requests will be entertained after 2 hours from the time of payment.

2. Incorrect Data
No refund will be issued if the customer provides incorrect data. However, if the customer notifies us within 1 hour of placing the order, we will make reasonable efforts to correct the data and adjust the service as needed.

3. Report Delivery
Once the report or service has been delivered to the customer, no refund will be issued.

4. Processing Refunds
All eligible refunds will be processed within 7 business days from the date of receipt of the refund request. Please note that this time frame is subject to the transaction and processing time taken by the bank/payment gateway.

5. Double Payment
If a customer mistakenly makes a double payment for a single order, one of the payments will be refunded.

6. Deduction of Charges
Refunds will be issued after deducting any transaction charges levied by the bank and/or the payment gateway, as well as any other charges that may have been incurred by TalktoAcharya in processing and/or delivering the service.

7. Return Policy
For physical products purchased from TalktoAcharya, returns are accepted within 5 to 7 days of receipt. To be eligible for a return, the product must be unused, in the same condition that you received it, and in its original packaging.

8. Return Process
To initiate a return, please contact us at info@talktoacharya.in with your order details. Once your return is approved, we will provide you with instructions on how to return the product. The customer will be responsible for the return shipping costs.

For any questions or further assistance, please contact us at info@talktoacharya.in.

Thank you for choosing TalktoAcharya for your spiritual needs. We are committed to providing you with the best possible service and support.

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