Read the sections that matter to you
Each section stays collapsed until you choose to open it.
1. Data we processPhone, order, email, UTR and limited technical records.
For new gateway orders we process the Indian mobile number, order reference, language, provider order/payment identifiers, amount, payment state, refund/dispute state, legal acceptance, secure session, a one-way HMAC technical fingerprint and limited access/audit records. Card details and banking credentials are handled by Razorpay or the payment provider, not stored by this website. Legacy email and UTR records remain limited to their original orders.
The application does not store the raw IP address in the business database. Infrastructure providers may process network logs under their own security and service terms. We do not collect a school name, employer name, student data, employment records or institutional contacts merely to complete a purchase.
If Meta measurement is enabled and you allow optional ad sharing, the browser Pixel can send activity from the public English homepage, checkout opens, public page/referrer information and advertising cookies. For a new order started with that permission, the server can send a verified purchase event with its actual value and currency, capture time, an opaque event identifier, browser user-agent, available advertising identifiers and a SHA-256 hash of the normalised mobile number. The server does not send an unhashed mobile number, email, order reference, payment identifier, private access token or download link to Meta. Hashing is not anonymisation: Meta may use the hash and other identifiers to match an account. When a browser connects to Meta, Meta can also receive ordinary network information such as its IP address under Meta’s own privacy policy.
2. Why we use the dataOrder creation, recovery, verification, fulfilment, support and security.
Order and payment references are used to verify payment, grant protected PDF access, investigate refunds/disputes and provide support. Phone-only lookup is not permitted. Legacy email and UTR information remains used for its original manual order.
Separately permitted Meta sharing helps measure advertising, understand which ads lead to purchases and support relevant advertising or retargeting through Meta. It does not authorise promotional SMS, WhatsApp messages, email newsletters or sharing with an unrelated data broker. Tracking is incomplete when people decline, use privacy signals or blockers, or when a request fails. A Meta event is not proof of an individual’s identity or of why they purchased.
3. Consent and noticePurchase acceptance and optional advertising are separate choices.
Before a new order is created, the buyer sees the purchase notice, links to the legal documents and one unchecked purchase acceptance box. The system records its version, language, time, source path and a protected technical reference. That checkbox does not grant Meta advertising permission.
Use the separate optional ad-sharing control below the purchase area or the Privacy choices link in the footer to allow or decline Meta sharing. No choice is required to buy or download. You can change a saved choice in the same browser. Do Not Track and Global Privacy Control signals override an allow choice for optional tracking. A new browser or cleared cookies can require a new choice.
A confirmed withdrawal stops future optional sharing and cancels queued events that have not begun transmission. A request already in flight or accepted by Meta cannot be recalled by this switch. If saving fails, browser sharing is paused and the control asks you to retry; the server cannot act on a choice it did not receive. Contact customerbaconsultancy@gmail.com for a privacy request or use Meta’s own privacy controls for information it has already received. Essential order, payment, dispute, security and legal records can remain where needed.
4. Service providers and transfersHosting, payment and security providers; Meta only for separately permitted advertising.
Service providers include Vercel for hosting, Supabase for database/authentication/private PDF storage, Cloudflare Turnstile for abuse protection and Razorpay for payments. A mobile number may prefill checkout, and order references, amount and payment status are exchanged for processing and support. Providers may process data where they operate under their own terms and applicable law. This is not permission for marketing.
Meta Platforms receives optional advertising events through the Meta Pixel and Conversions API when separately allowed. Meta may match events with its accounts and process information in countries where it operates. Its privacy information is available at https://www.facebook.com/privacy/policy/. Optional advertising permission is not a condition of the services supplied by Vercel, Supabase, Cloudflare or Razorpay.
5. SecurityAccess controls, forced RLS, rate limits and audit records.
Controls include server-only secrets, forced database row-level security, protected database functions, admin authentication, secure HTTP-only order cookies, one-way hashing/HMAC, rate limits, Turnstile, same-origin checks, audit trails, encrypted transport and controlled backups.
No online service can promise absolute security. If a personal-data breach creates a material risk, BA Consultancy will investigate, contain it and provide notices required by applicable law.
6. RetentionCore order records are reviewed after 12 months.
Core order, consent, payment-review and fulfilment records are generally retained for at least 12 months after the latest relevant order, payment, support or delivery event. After that period, direct identifiers may be deleted or anonymised when no longer needed.
Some records may be kept longer for an active complaint, refund, fraud investigation, accounting or taxation requirement, legal claim, security incident or lawful government request. Non-identifying aggregate analytics may be retained longer.
The separate browser preference is valid for up to 90 days and is rechecked before optional sharing. Meta advertising cookies can remain in that browser subject to their own expiry; withdrawal attempts to clear the website’s _fbp and _fbc cookies. Matching details are cleared after delivery, final failure, withdrawal or expiry. Unpaid-order matching details can remain for up to 30 days. Diagnostic event records are retained for around 30 days, while preference and context records are reviewed after their 90-day expiry. Cleanup runs in bounded routine batches, so these are cleanup thresholds rather than a guarantee of deletion at an exact instant. Meta applies its own retention rules to events already received.
7. Customer rightsAccess, correction, updating, erasure and grievance requests.
A customer may ask what personal data is associated with an order, request correction or updating, request erasure where continued retention is not required, or raise a privacy grievance. Requests should include the order reference and matching phone or email so the requester can be verified without asking for unnecessary identity documents.
Requests may be sent to customerbaconsultancy@gmail.com. We aim to acknowledge within 48 hours and resolve within 30 days, subject to verification and legal retention requirements.
8. Adults onlyThe purchase flow is limited to adults.
The purchase flow is intended for buyers aged 18 or older. BA Consultancy does not knowingly invite children to submit order, payment or delivery data.
9. ContactPublished privacy and grievance contact.
Privacy and grievance contact: Grievance Officer — BA Consultancy, customerbaconsultancy@gmail.com. Operator: BA Consultancy, operated by BHAVANI ADVANCED TECHNOLOGIES. Correspondence address: 4, Doddapete, Ranebennur, Haveri District, Karnataka 581115, India. GST registration: GST registered — GSTIN 29GAFPB9063P1ZZ.