Privacy Policy
Effective 2026-11-03 · MAHAVIR TRADING CO (“Hukrr”, “we”, “us”)
This notice explains what personal data we collect when you use Hukrr, why we collect it, who we share it with, how long we keep it, how we protect it, and the rights you have under the Digital Personal Data Protection Act, 2023 (the “DPDP Act”). It is given under Section 5 of the DPDP Act, and should be read together with our Terms & Conditions and our Refund Policy.
- 1. Who we are and what this notice covers
- 2. Definitions
- 3. What we collect
- 4. Why we use it
- 5. Who we share it with
- 6. Where it is processed
- 7. How long we keep it
- 8. How we protect it
- 9. Your rights
- 10. Marketing preferences
- 11. Cookies and tracking
- 12. Children
- 13. Automated processing
- 14. Changes to this notice
- 15. Grievance officer and complaints
1.Who we are and what this notice covers
MAHAVIR TRADING CO operates Hukrr as a marketplace on which creators supply content to brands. We are the Data Fiduciary for the personal data described below. Our registered office, support contact and Grievance Officer are set out at the bottom of this page.
This notice covers personal data about Brands, Creators, and visitors to the platform. It does not cover the practices of third parties we integrate with (payment processors, social platforms, cloud storage, email delivery, real-time messaging, error reporting, or the social-channel verification provider named in Section 5), each of which publishes its own policy. It also does not cover the personal data a Creator or a Brand puts into a Contract — that is entered into directly between them, and we process it as an intermediary under the Terms.
2.Definitions
- Personal Data
- Any data about an individual who is identifiable by or in relation to that data.
- Data Principal
- The individual to whom personal data relates — that is, you.
- Data Fiduciary
- The person who alone or in conjunction with others determines the purpose and means of processing personal data — that is, us.
- Processing
- Any operation performed on personal data, including collection, storage, use, sharing, disclosure, and erasure.
- Consent
- A free, specific, informed, unconditional and unambiguous indication of your agreement to the processing of your personal data for a specified purpose. Where we rely on consent, it is requested through a clear affirmative action and can be withdrawn at any time.
- Grievance Officer
- The person appointed by us under Section 13 of the DPDP Act and Rule 3(2) of the IT Rules, 2021, whose details are in Section 15.
3.What we collect
We collect only what we need to run a marketplace where money moves between parties and the tax authorities receive their share. The categories below correspond to what the platform actually stores.
3.1 Account and sign-in
- Your email address, name and (if you sign in with Google) the profile picture returned by Google.
- A password hash if you register with email and password — stored as a bcrypt hash, never in plaintext, and never displayed back to you.
- Your role (Creator, Brand or Admin) and account status (active, disabled, banned or deleted).
- Whether your email has been verified, and the timestamp of verification.
- Session cookies and, if you sign in with Google, the OAuth tokens that let us sign you in — stored by our identity library, not by application logic.
3.2 Profile
- For Creators: display name, bio, location, website, pricing guide, portfolio, avatar and banner images.
- For Brands: company name, industry, website, logo, legal name, PAN, GSTIN, billing address and billing state.
- Niche categories you select, so that brands can filter for you and our brief matcher can reach you.
Much of this section is public. A Creator's display name, bio, location, website, portfolio, avatar, banner, niches, connected channels and the number of completed reviews are visible on the public profile page to anyone — including anonymous visitors. A Brand's company name and logo are visible to Creators they interact with. PAN, GSTIN, billing address and payout details are never public; see Section 3.3.
3.3 Tax identity and payout details
We are required to collect this to compute TDS, to issue the tax invoices described in Section 9 of our Terms, and to route your share of a settlement to a bank account that belongs to you.
- For Creators: tax entity type, PAN, PAN holder name, GSTIN, and the verification timestamp of each.
- For Creators: payout method (bank or UPI), account holder name, account number (encrypted at rest using AES-256-GCM), last four digits of the account, IFSC, or UPI VPA.
- The beneficiary identifier issued by our payments partner, and that partner's verification status for your account.
- For Brands: legal name, PAN, GSTIN, billing address and billing state code.
Your full account number is encrypted at rest and is used only to register a payout beneficiary with our payments partner and to route settlements. Only the last four digits are ever shown back to you or to any member of staff. Editing these details requires re-entering your password, even while signed in, and the change is logged.
3.4 Content you upload
- Images and videos you upload as profile pictures, banners, service covers, galleries, portfolio items, deliverables, dispute evidence, review attachments, or chat attachments.
- The text of messages exchanged in an order workspace, a deal conversation, a service inquiry or a dispute negotiation.
- Files you upload as brief reference material or as a revision reference.
Uploads are stored by our file-storage provider. Portfolio items and service media are public. Deliverables, revision references, chat attachments and dispute evidence are visible to the two parties to the order and to platform administrators as described in Section 5.
3.5 Connected social channels
When you connect a social channel — directly via YouTube, Instagram, or Facebook, or through the verification provider named in Section 5 — we store the account identifier returned by the platform, the handle, profile URL, avatar, follower count, engagement rate, video view counts and the timestamp of the last sync. OAuth access and refresh tokens returned by the platform are encrypted at rest using AES-256-GCM and are used only to fetch updated statistics and, where relevant, to refresh the token itself.
We never see or store the password to a connected social account. Disconnecting a channel, or your account deletion, removes the stored tokens and the connected-channel row.
3.6 Orders, contracts, payments and payouts
- The content of a Service Order or Deal, including the agreed scope, amount, delivery period and revisions.
- The signed Contract — the frozen terms, the SHA-256 hash, and the record of each signature (signer name, IP address, user agent and timestamp).
- Payment records, refund records, payout records, wallet ledger entries and withdrawal records.
- The tax breakdown frozen onto each order — the Creator's price, GST on it, our commission, GST on the commission, TCS and TDS.
- The tax invoices issued against each order, in both directions.
3.7 Communications and support
- In-app notifications and the emails we send you about orders, contracts, deliveries, disputes, payouts and (if you opt in) product news.
- Your notification preferences — which of order updates, messages and marketing you want to receive by email.
- Reports you file against a service, creator, brand or review, and the platform's resolution of that report.
3.8 Technical, security and audit
- Your IP address, read from request headers for the purpose of rate limiting and for the account-change audit trail described below.
- The browser's User-Agent string, recorded against the same events.
- An append-only audit log of security-relevant events on your account: password changes and password-reset events, payout-account linking, tax-detail updates, profile changes, account deletion, data export, and payout-edit unlock attempts. Each entry stores your user id, email, the action, the entity it affected, a redacted before/after diff, IP address, User-Agent string and timestamp.
- Server-side error reports sent to our error-tracking provider, which include the error trace and a user identifier so that a crash can be attributed to the request that caused it.
3.9 Third-party lookups we perform
When you register a password, we check it against a public breach corpus using a k-anonymous lookup: only the first five characters of a SHA-1 hash of your password ever leave our servers, and the full password and the full hash stay with us. When you add a YouTube channel by handle, we look it up on the public YouTube Data API using the handle you typed.
4.Why we use it
We process personal data for the following purposes. For each we indicate the ground on which we rely under the DPDP Act.
- To create and operate your account
- Performance of our contract with you under the Terms. Without an account there is nothing to sign you into.
- To compute TDS, TCS and GST, and to issue the tax invoices required by the CGST Act and the Income-tax Act
- Compliance with a legal obligation. We cannot offer the settlement service without this.
- To route your share of a settlement to a verified bank account
- Performance of our contract with you, and compliance with our payments partner's KYC obligations.
- To operate escrow, release funds, process refunds and settle disputes
- Performance of our contract with you.
- To keep an audit trail of security-relevant account changes and to detect and prevent fraud or account takeover
- Our legitimate use as a data fiduciary under Section 7 of the DPDP Act, and compliance with our obligations under the IT Act and the IT Rules, 2021.
- To send transactional emails about your orders, contracts, payouts and disputes
- Performance of our contract with you. These cannot be switched off, because they are how you learn that money has moved or a signature is required.
- To send you product news and feature announcements
- Your consent, which is off by default and can be withdrawn at any time as described in Section 10.
- To rate-limit login, registration, password reset, file upload and payout-edit endpoints
- Our legitimate use as a data fiduciary, to protect the service and its users.
We do not sell your personal data. We do not use it to build profiles for cross-context behavioural advertising, and we do not share it with advertising networks. We do not use your personal data for automated decision-making that produces legal or similarly significant effects — see Section 13.
6.Where it is processed
Our application runs on cloud infrastructure hosted outside India. Your account data, order data, contracts, invoices, audit logs and uploaded files are stored on that infrastructure. Several of our service providers in Section 5 are also located outside India. Our payment gateway, our tax-invoice numbering and our statutory remittances operate in India.
Cross-border transfers are made under Section 16 of the DPDP Act. We do not transfer personal data to a country or territory that the Central Government has restricted by notification under that section. Where a transfer is made, the recipient is bound by a data-processing agreement that imposes safeguards no less protective than those described in this notice.
7.How long we keep it
We keep personal data only as long as we need it for the purposes in Section 4, or as long as the law requires us to keep it. The retention periods below reflect what the platform actually does, not a general aspiration.
- Account and profile
- Kept while your account is open, and anonymised on deletion as described below.
- Tax invoices, contracts, payment, refund, payout and wallet records
- Retained for at least eight years from the end of the financial year to which they relate. This is the period for which the GST and Income-tax authorities can require us to produce them, and it is not something we can shorten on request.
- Signed Contracts
- Retained for the same period, because a signed contract belongs to both parties to it and either may need it after your account is closed.
- Dispute records, including evidence and offers
- Retained for at least eight years, for the same reason as Contracts.
- Audit log entries
- Retained for at least eight years. These are append-only and include IP address and User-Agent string.
- In-app notifications and messages
- Retained while the account is open. Notifications are deleted on account deletion; messages are retained because they form part of the order record between the two parties.
- Session cookies
- Until you sign out, until the session expires, or until a password change or password reset invalidates every existing session — see Section 8.
- Email verification tokens
- 24 hours. Password-reset tokens: 1 hour. OAuth state nonces: 10 minutes. In all three cases, the token is single-use and is stored as a hash, not as the raw value.
- Rate-limit counters
- Minutes. Upstash retains counters only long enough for the window they enforce.
- Error reports
- Up to 90 days, which is the default retention of our error-tracking provider.
- Uploaded files
- Until you remove them and ask us to erase them — see the note on file deletion below.
Account deletion. When you delete your account from Profile, we remove your personal details from the account and your profile, disconnect your social channels, pause your services, and sign out every session. Your email address is replaced with a placeholder and your name with the string “Deleted user”. We retain the transaction and contract records described above, with your identity replaced by that placeholder. Records of reviews you have left, and messages you have exchanged with a counterparty, remain in the system as part of the other party's record of the transaction, and may continue to be shown attributed to “Deleted user”. We cannot delete a record that belongs to the other party to the contract, just as we cannot delete a tax invoice.
Files you upload. When you replace an avatar, a banner, a service cover or a portfolio item, the new file is stored and the old one is no longer referenced — but it is not automatically removed from our file-storage provider. If you want an uploaded file erased from storage, write to the Grievance Officer in Section 15 with the file's URL, and we will remove it.
8.How we protect it
We apply the following safeguards, each of which is enforced in the platform rather than being a statement of intent.
- Passwords are stored as bcrypt hashes with a work factor of 12; plaintext passwords are never logged and are never shown back to you.
- A password policy rejects passwords that are too short, too common, derived from your own name or email, or found in a known breach corpus (via the k-anonymous lookup in Section 3.9).
- OAuth access and refresh tokens returned by social platforms are encrypted at rest using AES-256-GCM, with a key held only on the application server.
- Payout account numbers are encrypted at rest using the same scheme. Only the last four digits are shown back to you or to any member of staff.
- Changing your password — whether from inside the session or through the forgotten-password flow — increments a per-user token version, which invalidates every existing session on every device. A password reset, in other words, signs out everyone, including an attacker on a stolen session.
- Editing your payout account, your tax identity or your bank details requires re-entering your password, even while signed in.
- Session cookies are marked HttpOnly, and CSRF protection is provided by the identity library we use.
- Login, registration, password-reset, upload, and password-change endpoints are rate-limited by IP address.
- Security-relevant account changes — password changes, payout-account edits, tax-detail edits, profile edits, account deletion, data export, and failed payout-edit unlock attempts — are recorded in an append-only audit log with IP address and User-Agent string.
- Administrative access is restricted by permission, and every administrative action is recorded in a separate append-only log.
- Administrative endpoints that read deal, order, payment, contract or dispute data return an allowlisted set of fields only. A Creator's PAN, GSTIN, billing address, payout account and beneficiary identifier are never returned to a Brand, and a Brand's equivalent details are never returned to a Creator.
If a personal data breach occurs, we will notify the Data Protection Board of India and each affected Data Principal as required by Section 8(6) of the DPDP Act, without undue delay, describing the nature of the breach, its likely impact, and the measures we have taken or propose to take.
9.Your rights
As a Data Principal you have the following rights under the DPDP Act. Each can be exercised from your account, or by writing to the Grievance Officer in Section 15.
- Right to access (Section 11)
- You can request a summary of the personal data we process about you, the identities of the data fiduciaries with whom it has been shared, and a description of the processing. A downloadable JSON export is available from Profile → Download my data, and covers your account, profiles, services, deals, service orders, contracts, invoices, reviews and audit-log entries. It deliberately excludes your password hash and any OAuth or payment-provider tokens.
- Right to correction and erasure (Section 12)
- You can correct your account details, your profile, and your tax details from the Profile and Public Page settings. You can delete your account from Profile → Delete account, subject to the retention obligations in Section 7. Deletion requires your password (for accounts that have one) and the typed word DELETE.
- Right to grievance redressal (Section 13)
- You can complain to our Grievance Officer about the way we have handled your personal data. See Section 15 for contact details and expected response times.
- Right to nominate (Section 14)
- You can nominate another individual to exercise your rights in the event of your death or incapacity. Nomination is currently handled by written instruction to the Grievance Officer; a self-service nomination screen is planned.
- Right to withdraw consent
- Where we rely on consent — product news and feature announcements — you can withdraw it at any time from Profile → Email notifications, or from the unsubscribe link in any marketing email. Withdrawal does not affect the lawfulness of processing that took place before it.
We will respond to a request within thirty days, or within a shorter period where the DPDP Act or the rules made under it require one. We may ask you to verify your identity before acting on a request, so that a request made by an attacker with your email address does not result in your data being handed over.
10.Marketing preferences
We send three categories of email, controlled from Profile → Email notifications:
- <strong>Order and deal updates</strong> — funding, delivery, approval, disputes, contract signatures and payouts. This category is on by default because it is how you learn that money has moved or that a signature is required. You can switch it off, but doing so will not stop account-security emails.
- <strong>New messages</strong> — a notification when the other party to an order sends you a message. On by default.
- <strong>Product news and feature announcements</strong> — occasional emails about new features. Off by default, and only sent if you turn it on or explicitly opt in.
Account-security emails — email verification, password reset, and responses to a data-rights request — are never suppressed by these preferences, because they are the mechanism by which you gain access to the account or exercise a right.
12.Children
The platform is not intended for children. You must be at least 18 to register, as stated in Section 3 of our Terms. We do not knowingly collect personal data from a person under 18, and we do not process the personal data of children in any way that would require verifiable parental consent under Section 9 of the DPDP Act. If we become aware that an account belongs to someone under 18, we will suspend it and delete the personal data associated with it.
13.Automated processing
We use automated processing in a few places, none of which produces legal or similarly significant effects on you in isolation.
- Search ranking and quality scoring. Creator profiles are ranked in search, and quality scores are displayed on their listings, based on verified channel statistics, engagement, platform diversity, verification status and profile completeness. A lower rank reduces visibility; it does not determine whether an order can be placed.
- Brief matching. When a Brand publishes a brief, the platform scores creators against the brief's channels, formats, niches, objectives, budget and turnaround, and invites the highest-scoring creators. An uninvited creator can still bid if a Brand chooses to accept their pitch by other means — the invite is not a gate.
- Fraud and abuse controls. Rate limiting, the append-only audit log, and the administrative moderation workflow described in Section 5.
- Dispute resolution. Disputes that reach arbitration are decided by a human administrator, not by an automated system. Offers exchanged during the negotiation stage are accepted or rejected by the parties themselves.
None of the automated systems above is the sole basis for a decision that produces legal or similarly significant effects. If you believe an automated outcome affecting you is wrong, you can raise it with the Grievance Officer, and a human will review it.
14.Changes to this notice
We may update this notice to reflect changes in the platform or in applicable law. Material changes will be notified by email and by a notice on the platform at least 15 days before they take effect. The effective date at the top of this page is the date of the current version. If a change requires a new consent under the DPDP Act, we will ask for it before the change takes effect, rather than relying on continued use as acceptance.
Changes required by a change in statute take effect on the date the statute changes, because we cannot contract out of a statutory obligation. We will notify affected users as promptly as possible in that case.
15.Grievance officer and complaints
If you have a question about this notice, a request under Section 9, or a complaint about how we have handled your personal data, contact our Grievance Officer:
Your complaint should describe the personal data at issue, what you have already tried, and the outcome you are seeking. We will respond in writing. If we cannot resolve your complaint within 30 days, or if you are dissatisfied with our response, you may complain to the Data Protection Board of India under Section 13(3) of the DPDP Act. For complaints about content, account conduct, or a specific user, our Terms & Conditions set out the same grievance route.
Registered office: MAHAVIR TRADING CO, Canal Road Jammu, Jammu and Kashmir 180002. Telephone: +91 9419135248, Mon–Sat · 10:00–18:00 IST.
Draft notice. This policy is a working draft prepared for the Hukrr platform. It reflects what the current code does, as far as that code has been reviewed; it has not yet been reviewed by counsel and should not be relied on as legal advice until it has been. Do not enable real-money payments (Cashfree production activation) until it has been signed off against the live system.
