SUKSHM CRM

Privacy Policy

DEV environment · Updated 3 November 2026. This notice describes the current SUKSHM development and testing workspace. Use synthetic test records, not real customer or financial information.

Who operates this workspace

SUKSHM CRM is operated by Ashutosh Singh. For support or a privacy request, contact 83ashutoshsingh@gmail.com using the contact options below.

Information used

Account email, identity and verification information support sign-in and access administration. Authorized users can enter lead details, notes, visits, tasks and other workspace records. Hosting and authentication providers may process technical request, device and security information needed to operate their services.

Purpose and access

Information supports authentication, account approval, authorized CRM workflows, troubleshooting and testing. Workspace information is shown according to the current account, role and permissions. Do not share credentials or enter records you are not authorized to use.

Current service providers

The DEV service uses Google Firebase for authentication, Cloudflare for hosting and access-request storage, and Google Apps Script/Sheets for the CRM backend. These providers process information needed for their respective services. This notice does not promise a particular production hosting region or certification.

Browser storage and support

Remember email stores the email address only when selected; that feature does not store your password. Tab-session information supports sign-in and protects unsaved or uncertain operations. Signing out does not itself delete server records. Help reports are prepared on your device and copied only when you choose Copy issue report. Opening Gmail starts a message composer; it does not send a ticket or email automatically.

Demo enquiries

Request a walkthrough opens the separate SUKSHM website enquiry form. Review the enquiry privacy notice displayed on that form before submitting. No information is submitted merely by opening the link.

Correction, export and deletion requests

Contact the operator with the account email and the type of request. Do not email passwords or customer records. Identity and workspace authority must be verified before any record is disclosed or changed. Available export and deletion actions depend on the stored records and their authorized owner; submitting a request does not itself perform those actions.

Do not use DEV as a permanent archive. Signing out or closing a tab is not a deletion request, and no retention or deletion deadline is promised by this testing notice. Production retention and account-closure arrangements will be supplied with the applicable service offer before customer onboarding.