Privacy Policy
What we collect, why we need it, and how you can contact us.
Updated 16 November 2026 · Version 2026-11-16-privacy-v30
- We use information to answer enquiries, manage accounts and deliver services.
- We do not sell personal data or ask you to send payment passwords.
- For privacy or deletion requests, email support@digiflyx.marketing.
1. Scope and contact
Business name: DigiflyX (DigiFlyX). Business type: Proprietorship. Stated business location: Sector 63, Noida, 201301. Privacy and grievance contact: Bhanu Pratap, +91 9990934503, support@digiflyx.marketing.
This policy covers information handled by DigiFlyX through this website and its related customer services. It also covers enquiries submitted to a DigiFlyX advertisement or lead form that links to this policy. It does not replace the separate notice of a client business whose campaign we manage or of the separate CRM platform.
For questions about personal information, email support@digiflyx.marketing with “Privacy request” in the subject. General business enquiries go to support@digiflyx.marketing. We will help identify the relevant service and responsible contact.
2. Information we handle
Enquiries: your name, email, phone number and business details that you choose to give us, your message and the service you are interested in. We use these to respond and discuss the requested service.
Training purchases: contact and business details, client office address, city, state, six-digit PIN, team-size range and the selected program are stored with the order. Payment is verified separately. Training dates remain pending until our team records the discussed schedule in My training. We also keep the agreed logistics, session dates, attendance counts and duration, customer-visible session notes and completion confirmations. Earlier enquiry records remain historical records and do not establish a paid booking. Please do not include employee lists or patient details.
Accounts: name, email, password hash, verification and recovery records, sign-in/session records and policy acceptance. Passwords are stored as hashes, not readable passwords. The current website uses email and password for sign-in and email links for account verification and password recovery. Where offered, WhatsApp verification is for a verified account phone number or Lead Fetch pairing and reconnect, not account sign-in or password reset. Verification does not confirm payment.
Cashfree processes checkout payments. DigiFlyX sends your account identifier, payment contact number and order amount/reference to Cashfree. Cashfree hosts payment entry and processes the payment information you provide there. DigiFlyX verifies the result with Cashfree and keeps order/payment references, amount and status, including signed payment notifications, for access, billing, support and reconciliation. DigiFlyX does not receive or store your full card number, CVV or UPI PIN.
Orders and support: selected services, briefs, brand assets, delivery files, correspondence, billing details and payment references/status supplied by the payment provider. We use these to provide, bill, support and resolve issues with your order. We do not store full card numbers, CVV or UPI PINs.
Technical records help us serve the website, investigate faults and protect accounts. Application security records include a timestamp, request identifier, request method, route, access category, account identifier when known, response status and outcome. Those records exclude request bodies, passwords, tokens, raw URLs and queries, IP addresses, email addresses and exception text. The configured website access log records time, method, response status, response size and duration. Hosting, operating-system, email and payment providers can maintain their own operational records under their respective notices.
Do not send unnecessary patient or health records, government identity documents or financial passwords. Our website is for adult business users and is not intended for children under 18. If you believe a child has submitted personal data, please contact us so we can investigate and remove it where required.
3. How information is used
We use information to answer requests, verify accounts, provide agreed services, process payments and refunds, send necessary service notices, prevent misuse and meet legal obligations. Where consent is required, we ask for a clear choice for the stated purpose. Accepting service terms is not blanket consent to unrelated marketing.
If you request contact through a DigiFlyX ad or enquiry form, we use the details to follow up on that request. Promotional email or messaging beyond that request requires the appropriate permission. You can opt out by replying to the message or emailing support; necessary account and transaction notices may still be sent.
If we plan a new use that is not covered by the original purpose, we will provide an updated notice and obtain permission where required before starting it.
4. Client leads and the Lead Fetch service
When we handle leads on a client’s instructions, the client determines its campaign purpose and must provide the relevant notice and lawful permissions. We process that information for the agreed work, restrict access and do not independently sell or reuse it for unrelated campaigns. A service agreement should describe instructions, access, retention and deletion before client lead processing begins.
Lead Fetch captures normalised phone numbers and available sender names from an authorised WhatsApp Web session. It first uses a sender-provided WhatsApp profile name exposed in local contact or message-sender metadata. If that is unavailable, it uses an available saved contact name; if neither is available, it assigns a persistent Lead N label. It does not request hidden profile details or derive names from message text. It does not export message text, captions, media or group membership. The extension keeps the source number, connector settings and credentials, eligible capture intervals, queue and duplicate history in local extension storage. The customer-selected Google Apps Script receives the source number, connector key and batches of lead names and numbers over HTTPS, and the chosen Google Sheet stores the Name and Phone Number columns. Using the extension does not itself give permission to collect contacts or send messages.
A client’s connected sheet, platform account or exported file is also governed by that provider and the client’s controls. Removing your website account will not by itself erase copies you or a client have exported elsewhere. If your request concerns a client’s lead, we will help route it to that client and assist as appropriate.
DigiFlyX receives the account-linked source number, owned subscription and connection identifiers, pairing and recovery requests, activation/access/recovery events and term timestamps. The access APIs do not receive captured lead row bodies, WhatsApp message bodies, Google Sheet ID or URL, or the Google connector key. New setups use a verified-write connector: DigiFlyX receives a digest of each lead batch and issues a short-lived write permit that the Google connector must consume before writing lead rows. A digest is not necessarily anonymous. Existing legacy receivers need a separate migration; updating the extension alone does not upgrade them.
Successful Lead Fetch sync marks local records as synced or already present; it does not automatically erase the lead records or duplicate history from the extension. Clearing the extension or browser-profile storage, or uninstalling it, can delete local queue and history and lose unsent leads. It does not automatically delete rows already saved in Google Sheets or DigiFlyX server records. Pause and reconnect do not erase those copies. A time limit on tab-readiness status is not a lead-retention period.
Pending leads and duplicate history remain in the Chrome profile until you clear the extension’s local data. This version does not automatically delete older records. To clear them, use Chrome’s extension/site-data controls or remove the extension; first export or sync any leads you want to keep. Clearing local data does not delete previously exported Google Sheet rows or account, connection, payment or billing records held on the server.
After you accept the setup notice, WhatsApp account-number matching can continue while Sync is paused. Lead capture requires an eligible ON period and valid paid access or a separately verified capture-only permission. After paid expiry, that permission can keep eligible new leads locally only until 24 elapsed hours after the paid expiry; it cannot authorise unpaid Sheet writes. New capture stops at the end of that window, but existing pending leads and duplicate history remain until you clear them. Renewal can resume the prior ON choice and eligible pending delivery; a manual Pause stays effective.
6. Security and retention
We use measures appropriate to the information and service, including protected account access, password hashing and restricted permissions. No system can guarantee absolute security. Tell us promptly if you suspect misuse; we will investigate and provide notices required by applicable law.
Records may be needed for an active service, dispute handling or a legal obligation, including tax and payment records after account closure. A verification link, one-time code, session or write permission becoming unusable does not mean its associated record has been deleted. The application can stop showing certain older unpaid or failed orders in the customer view after 72 hours; that is a visibility rule, not deletion. Some verification cleanup runs only when another qualifying request is made, not at a guaranteed daily deadline.
Requesting account closure, clearing browser storage or uninstalling the extension does not by itself delete every record held by DigiFlyX, a provider or a customer-selected Google Sheet. A privacy request must be assessed for the relevant records and applicable retention duties.
The current service has no general automatic deletion schedule for server account, order, issued-bill, connection or security records, or for deployment backup copies. Expiry, revocation and a hidden order do not by themselves erase those records. Send a deletion request to support for a record-specific review; we will explain which records can be removed and which must be kept for an identified legal, accounting, dispute or security purpose. We do not promise immediate erasure of provider records or backup copies.
7. Your choices and deletion requests
Email support@digiflyx.marketing from your registered address, stating the account or service and whether you want access, a correction, deletion, account closure or withdrawal of consent. You do not need a paid subscription to make a request. Do not send a password, OTP, card details or identity document with the initial request.
We may request proportionate information to verify identity and authority before revealing or changing records. We will explain what we can do, any lawful retention exception and any effect on an active service. Withdrawing necessary permission may prevent us from continuing that part of the service, but does not make earlier lawful processing unlawful.
Contact support about a privacy complaint. A request does not restrict your right to approach a competent authority under applicable law.
Bhanu Pratap and the DigiFlyX support team handle complaints sent to support@digiflyx.marketing. We acknowledge consumer complaints within 48 hours, provide a copy of the complaint as recorded and work to redress them within one month, subject to any shorter applicable legal deadline. Keep the email thread and order reference so the request and outcome can be followed up.
