Who is responsible

Binary Bliss Solutions, a sole proprietorship, at Near Mondha, Rajabazar, Chhatrapati Sambhajinagar (Aurangabad), Maharashtra – 431001, India. The business is responsible for the website’s enquiry processing described here. Privacy contact: [email protected]. Version: bbs-contact-agreement-2026-10-v1. Effective: 2026-10-25.

Enquiry information and purposes

When you use Contact, we receive your name, email address, selected service and message. We also process the submission reference and timing, security-verification result, agreement version/time and relevant preference or attribution fields. We use these to receive, assess and answer your request, arrange relevant follow-up, prevent abuse, troubleshoot delivery and recognise duplicate retries. Please do not include sensitive personal information in the message.

The website and email service use Hostinger. Cloudflare Turnstile verifies form requests for abuse prevention. Enquiries pass through our business mailbox and self-hosted n8n automation into Frappe CRM for follow-up. Agreement evidence includes a server timestamp, submission reference and document-version digest; the separate server evidence ledger stores a hash of the email rather than the raw address. A hash is not a guarantee that information is anonymous. Mailbox messages and CRM enquiry records contain the contact details needed for a reply.

Email and WhatsApp

We may reply by email and use information for relevant follow-up on the enquiry. If you choose to communicate through WhatsApp, WhatsApp/Meta also processes the conversation under its own terms and privacy notice. An enquiry or acceptance of these documents is not permission for promotional email or WhatsApp campaigns. Any such marketing must have its own applicable permission and withdrawal route. WhatsApp marketing is permitted only where the individual explicitly opts in. This form records no WhatsApp marketing permission. A separate Cloud API/webhook connection exists; its configuration is not proof that customer messaging, any history import, or any additional marketing automation is enabled.

Analytics, advertising and remarketing

Website analytics and advertising preferences are separate from the Contact agreement. The governed Google Tag Manager container is retrieved to coordinate these controls; this request sends normal connection metadata to Google before an optional choice. Analytics and advertising tags are separately gated. We do not claim that every third-party request is blocked before consent. Google Analytics, Google advertising services and Meta Pixel can process website event/device/browser information where the relevant optional choices permit them. Meta Conversions API can process event identifiers and hashed matching information for permitted conversion measurement; hashing does not make contact data anonymous. We do not send enquiry-message content through the website enquiry conversion path to advertising platforms.

The V2 Contact form provides no enquiry-level advertising or marketing opt-in: it submits both permissions as false and sends no browser Meta Lead event. The server workflow must suppress the matching enquiry CAPI/ad-conversion or marketing action without the required separately recorded permission. Agreement to these documents is not permission for remarketing, customer matching or advertising audiences, and a website advertising preference does not override this form’s lack of enquiry-level permission.

You can decline optional website measurement and still send an enquiry. Use the website preference controls to change analytics/advertising choices. The site’s bbs_consent preference cookie lasts up to 180 days; permitted first-touch attribution in bbs_attr lasts up to 90 days. Vendor cookies and account-level retention are separate. Our verified GA4 property retains event-level data for 2 months and user data for 14 months, with reset on new activity enabled. These settings do not govern most aggregated standard reports. Other provider/account retention and backup settings have not been independently confirmed; we do not promise matching erasure deadlines across Google, Meta, WhatsApp or Hostinger copies.

Service providers and international processing

The services above support hosting/email, abuse prevention, automation, CRM, optional measurement and communications. Provider accounts may process data in countries other than yours. Our self-hosted n8n and Frappe CRM run on Hetzner infrastructure in Nuremberg, Germany. The website origin identifies as in-mum-web1835.main-hosting.eu; we have not independently confirmed the account-specific hosting, email and backup locations or contracting entities. Cloudflare, Google, Meta and WhatsApp operate internationally. Their published terms describe processing and transfer mechanisms, but we have not verified an account-specific residency restriction, executed addendum or transfer assessment. We therefore make no claim that all processing stays in India or that a particular safeguard applies to every flow. Provider information: https://www.hostinger.com/legal/dpa ; https://www.cloudflare.com/cloudflare-customer-dpa/ ; https://policies.google.com/privacy/frameworks ; https://www.facebook.com/legal/terms/dataprocessing ; https://www.whatsapp.com/legal/business-data-processing-terms . Information may also need to be disclosed where applicable law requires it.

Retention and deletion

We have newly adopted a manual policy to review closed, non-client enquiries monthly and remove unneeded mailbox/CRM copies 12 months after the last meaningful contact, subject to active relationships, documented disputes and applicable legal requirements. Minimal agreement evidence is retained for at least 3 years and then reviewed; it is not a universal statutory retention claim. This policy is not an assertion that historic deletion automation existed. A metadata-only review packet is scheduled monthly; a person must complete the review and any authorised erasure. No automatic mailbox/CRM or ledger purge is currently enabled. Current n8n execution pruning uses a 336-hour age setting and 10,000-count limit, with pruning intervals and a hard-delete buffer. It is not an exact 14-day erasure guarantee for waiting/running executions or backups. Frappe log categories have configured 7/14/30/45/90-day cleanup. The adopted 35-day rolling backup target remains pending backup reconciliation and verification. Existing provider/local archives may persist longer. Backup copies are restricted and must not be reused for ordinary operations or marketing; completed deletion requests must be reapplied if a backup is restored. Mailbox deletion is trash-first; permanent deletion/expunge and reconciliation of CRM linked records, automation copies, evidence and channel history are separate manual steps, not an already-certified end-to-end erasure service. Different records can have different lifecycles. An applicable legal retention requirement may prevent immediate deletion of a particular record. Explain any such exception when handling a request. A backup’s retention does not authorise new marketing.

Rights and contact

Depending on applicable law, you may have rights to access, correct or delete information, restrict or object to processing, obtain portability or complain to a competent privacy authority. You can withdraw a separate optional consent for future processing without turning the Contact agreement into marketing permission. Withdrawal does not undo processing already lawfully completed. Send requests to [email protected]. We may request proportionate information to verify identity and will handle requests within applicable legal requirements. Binary Bliss Solutions handles these requests. The adopted process is to log the request, verify identity proportionately, check relevant active systems and backups, document any lawful retention exception, and record the outcome with minimal identifying information. We target acknowledgement within 7 days and resolution within 30 days, subject to any shorter applicable legal deadline. These are newly adopted operating targets, not a claim about past performance.

Security and updates

We use access restrictions and technical safeguards appropriate to the website and its systems; no internet transmission or storage can be guaranteed risk-free. The published version/effective date identifies this notice. Material changes and any new optional purpose will be handled as applicable law requires.