Skip to content

Privacy policy

Version 0.1 · Effective 15 Nov 2026

This policy explains what personal data CRW collects, why, where it lives and what rights you have. We have tried to keep it plain. If something is unclear, write to us at hello@crw.adwiz.in.

Who we are

CRW is a product of Adwiz Digital LLP, an Indian limited liability partnership. For the purposes of India's Digital Personal Data Protection Act, 2023 (DPDP Act), Adwiz Digital LLP is the data fiduciary for the personal data described here.

What we collect today

When you join the waitlist we collect:

  • your WhatsApp number or email address
  • your name, if you choose to give it
  • your city or pincode
  • the kinds of missions you are interested in
  • the version of this policy you agreed to, and the time you agreed
  • your IP address, used only to prevent abuse and spam

When a brand sends us a brief we collect the contact details and the brief the brand chooses to share. When someone uses the "Dare us" form we collect the message and the contact detail they give.

What we will collect once the app is live

When you use the CRW app to complete missions, we will also collect:

  • device identifiers, used to keep accounts honest and prevent duplicate accounts
  • your location at the moment you capture proof for a mission
  • the photos and videos you submit as proof
  • your PAN and UPI ID, at your first payout
  • the results of identity checks run by our verification providers

We will update this policy and ask for your consent again before we start collecting anything beyond the waitlist data.

Why we use your data

We use your data to run the waitlist, tell you when CRW launches, contact you about missions that match your interests, prevent fraud and abuse, and meet our legal duties. Our basis for doing this is your consent. You give it when you tick the consent box, and you can withdraw it at any time.

Where your data is stored

All data, including our database, encrypted database backups and, once the app is live, proof photos and videos, is stored on India-hosted servers. We do not use foreign object storage. An encrypted backup copy is also kept on the operator's own device in India.

Who else handles your data

We use a small number of service providers to run CRW. They process data only on our instructions:

  • Resend, to send email
  • Meta (WhatsApp Business), to send WhatsApp messages
  • Sentry, for error tracking. We configure it so that message contents are not sent to it.
  • Identity-verification and payout providers, once payouts begin

We do not sell your personal data.

How long we keep it

Waitlist data is kept until launch plus 12 months, or until you withdraw consent, whichever is sooner. Encrypted database backups are kept as 14 daily and 8 weekly copies, after which they are overwritten. Data needed for tax and accounting is kept for as long as the law requires.

Your rights

Under the DPDP Act you have the right to:

  • ask what personal data we hold about you and how we use it
  • ask us to correct or complete it
  • ask us to erase it
  • withdraw your consent at any time
  • nominate another person to exercise these rights if you die or cannot act for yourself
  • have a grievance heard and resolved

To use any of these rights, write to hello@crw.adwiz.in. We will respond within 30 days.

Grievance officer

Our Grievance Officer is reachable at hello@crw.adwiz.in, with the subject line "Grievance". We will acknowledge your message and respond within 30 days. If you are not satisfied with our response, you may complain to the Data Protection Board of India.

Children

CRW is for people aged 18 and over. We do not knowingly collect data from anyone under 18. If you think we have, tell us and we will delete it.

Security

We keep data on servers we control, encrypt our backups, restrict who can access the database and limit what our service providers receive. No system is perfectly secure. If a breach affects your data, we will tell you and the authorities as the law requires.

Changes to this policy

When we change this policy we will publish a new version number and effective date at the top of this page. Where a change needs your consent, we will ask again before it applies to you.