Privacy Policy

01Plain-English summary

Dwize collects only what is needed to operate your Care Year and respond to your inquiries. We do not sell your data. We do not run retargeting or third-party advertising networks on the sites we build for customers. On dwize.in itself, Dwize may run consent-based remarketing for its own advertising, described in section 12. Optional analytics and conversion measurement are deployment-configured and disclosed below. Your contact details, business details, and project context are visible only to the Dwize people required for your account and our infrastructure providers acting under our instructions.

02Who we are

DWIZE OFFICE SOLUTION, registered in Bikaner, Rajasthan, India, GSTIN 08FPPPR8719E1Z5. Public contact: Dwize team. Contact: hello@dwize.in or WhatsApp +91 96024 85318.

03What we collect

• Inquiry data — name, contact channel (WhatsApp / email / phone), business name, brief description of what you need. Voluntarily provided when you contact us.
• Care Year data — content, brand assets, login details for any third-party services you ask us to integrate. Strictly for delivering and operating your product.
• Site analytics — anonymized page-view, referrer, and rough geography via Google Analytics 4 (only when configured by the customer or on dwize.in itself). No personal identifiers.
• Campaign attribution — when measurement is configured, limited campaign parameters such as UTM tags and ad-click identifiers may be held in session storage to associate a visit or contact action with its source. Reported page locations contain only the origin and path, not arbitrary query strings or fragments. We do not infer a person’s name, phone number, or email address from these parameters.
• Server logs — IP address, user agent, request path on dwize.in, retained for 30 days for security and abuse handling.

04What we do not collect

• Bank account / card details (handled by Razorpay or your payment gateway directly; Dwize never sees them).
• Aadhaar, PAN, or any KYC documents — not needed for product purchase.
• Your customers’ personal data (when we operate your Store / Brand, your customer data remains yours; Dwize accesses it only as needed for operations under written contract).
• Behavioural data for advertising without your consent. Remarketing on dwize.in runs only after you accept advertising cookies, and we do not use fingerprinting.

05How long we keep it

• Active Care Year customers — for the duration of the year plus 30 days for handover.
• Inquiry data from non-customers — up to 12 months unless you ask us to delete sooner.
• Server logs — 30 days, then automatically purged.

06Who sees it

Inside Dwize: only the people required to deliver your Care Year, including the delivery team and technical lead. Outside Dwize: carefully selected service providers acting under data-processing terms.

• Cloudflare and other edge delivery and security providers (site delivery, caching, security, and cookieless page-view analytics)
• Razorpay (payments, when applicable to your product)
• Database and storage providers (customer records and operational data)
• Email and messaging providers (transactional communication)
• Session and caching providers (security, performance, and continuity)
• Google Analytics 4 (only when configured)
• Google Ads conversion measurement and remarketing (only when its identifiers are configured, and remarketing only with your consent)

07Cookies

dwize.in does not use a theme-preference cookie: your Light, Auto, or Dark choice is kept in your browser’s local storage on your own device. When Google Analytics 4 is configured, it sets standard GA cookies. When Google Ads conversion measurement is configured, the Google tag may use measurement cookies to attribute conversions. If you accept advertising cookies, Google and Meta tags may also set cookies used for remarketing — showing Dwize ads to past visitors of dwize.in. If you choose “Essential only”, no advertising cookie is set.

08Your rights

• Access — ask what we have on you. We respond within 7 business days.
• Correction — fix any wrong data we have.
• Deletion — delete inquiry data on request. Active-contract data is deleted within 30 days of contract end (covenant 08).
• Portability — export your Care Year data in a portable format at any time, free.
• Complaint — write to us; if not satisfied, complain to the relevant Indian regulator.

09Cross-border transfer

We use India-first data handling wherever the chosen provider and customer setup allow it. Edge delivery layers may serve cached static content from non-Indian locations; this never includes personal data. Email and messaging content may traverse provider infrastructure for delivery. We make reasonable efforts to keep personal data handled with appropriate regional, security, and access controls.

10Updates to this policy

We refresh this policy when we materially change how we handle data. The “Last refined” date at the top reflects the current version. Material changes are notified to active Care Year customers by email at least 14 days before they take effect.

11Contact

Questions or requests on this policy go to hello@dwize.in with subject “Privacy”. Dwize will respond through the agreed contact path.

12Analytics, advertising tags, and consent on dwize.in

This section describes the measurement and advertising tags, consent, campaign attribution, and Fit Brief handling on dwize.in itself. Where it is more specific than sections 3 and 7, it states what the dwize.in site actually does.

Optional tags

dwize.in can load five optional vendors. A vendor loads only if its identifier is set in the site settings; with no identifier, it is never requested.

• Google Tag Manager (googletagmanager.com) — a container for the tags below; when it is used, Google Analytics 4 and Google Ads are configured inside it.
• Google Analytics 4 — page-view and event measurement, with IP anonymisation, under Consent Mode v2.
• Google Ads — counts conversions such as a WhatsApp, call, email, or Fit Brief action, and — only if you accept advertising cookies — adds your visit to Dwize remarketing audiences so Dwize ads can be shown to people who have already visited dwize.in.
• Meta Pixel (connect.facebook.net, facebook.com) — reports page views and the same conversion events to Meta, which handles them under its own terms, and enables Dwize retargeting audiences on Facebook and Instagram. It loads only after you accept.
• Microsoft Clarity (clarity.ms) — optional heat-map and session analytics. It loads only after you accept.

Enabled on this version of dwize.in: none. No analytics or advertising vendor tag is switched on, so none is requested from your browser and no consent prompt is shown.

Separately from these optional vendors, dwize.in is hosted on Cloudflare (Cloudflare Pages). To deliver and protect the site, Cloudflare processes technical request data such as your IP address, browser user agent, and the page requested. When Cloudflare Web Analytics is switched on for the site, it counts page views and page-load performance without cookies or local storage and without fingerprinting visitors by IP address or user agent.

Consent

Google tags use Consent Mode v2. Their four consent signals (ad_storage, ad_user_data, ad_personalization, analytics_storage) start as denied until you choose. A prompt offers “Accept” or “Essential only”; it appears only when at least one vendor tag is switched on. The Meta Pixel and Microsoft Clarity are not requested from your browser at all until you accept.

Your choice is remembered in your browser’s local storage on your own device, and you can change it at any time with “Cookie preferences” in the site footer. Essential site functions work whichever you choose. When consent is denied, Google tags run in Consent Mode: they do not set analytics or advertising cookies and may send limited, cookieless signals.

Campaign attribution

If you arrive from a campaign link, dwize.in can keep its campaign parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content) and ad-click identifiers (gclid, gbraid, wbraid, fbclid, msclkid), together with the landing page, the date, and the external referrer. This is a first-party record: it is written to your browser’s session storage (not a cookie), stays on your device, and is cleared when the browsing session ends. It is kept whether or not you accept measurement cookies, and its only use is to label a conversion or your Fit Brief with its source, for example “Ref: google / cpc”. We do not infer your name, phone number, or email address from it. Clear this site’s data in your browser to remove it at any time.

Events

When a tag is enabled, your actions are reported as named events: clicks on WhatsApp, call, and email links, brochure downloads, Fit Brief submissions, and arrival on the confirmation page. An event carries only the page path, the link text and address, the part of the page it came from, and the product, channel, and timeline you picked in the Fit Brief. The text you write in the brief is never part of an event.

The Fit Brief

The Fit Brief on the contact page is composed entirely in your browser. When you press “Send on WhatsApp” or “Send by email”, your device opens WhatsApp or your email app with the message ready; nothing is sent until you press send there. dwize.in does not store the brief on a Dwize server. A copy stays in your browser’s session storage for that tab, so the confirmation page can show it to you, and it is cleared when the tab is closed.

This version of the site has no form service configured, so dwize.in itself sends no copy of the brief anywhere.

Once you send the message, it travels through WhatsApp (Meta) or your email provider and is handled as inquiry data under sections 3 to 5.

Everything else on the page

Fonts, images, and videos are served from dwize.in itself, so there are no third-party font or media requests. Photograph credits, WhatsApp, the office map, and the GST verification link are ordinary links: they open another service only if you click them.