Data Handling Policy

How We Handle Your Data

This page is a technical companion to our Privacy Policy. It documents, integration by integration, exactly what scopes we request, what data fields we receive, how each is stored and encrypted, how long we keep it, and how you can revoke access — for our own reference, for security reviewers, and for platform partners (Meta, Google, Snap Inc., Cashfree) evaluating our API integrations.

Last updated: August 24, 2026

Encrypted at Rest

Every OAuth access/refresh token is encrypted with AES-256-GCM using a unique random IV per record before it ever touches disk.

Least-Privilege Scopes

For social media OAuth integrations (Instagram, Facebook, YouTube, Snapchat), we request only read-only / profile-verification scopes — never posting or account-management permissions on your behalf. (Our WhatsApp Business messaging works differently — see the WhatsApp entry below.)

Deletable On Request

Disconnecting an integration purges its stored token immediately. Full account deletion is a manual request handled by our team — see our Data Deletion page.

Meta Graph API — Instagram & Facebook

Scopes / Permissions Requested: instagram_basic, instagram_manage_insights, pages_show_list, pages_read_engagement (via Facebook Login for Business, requested only from Creator Users connecting an Instagram Professional account).
Data Fields Received: Instagram Business Account ID, username, profile picture URL, follower/following counts, media list (permalink, caption, media type, timestamp), and post-level insights (reach, saves, shares, comments, likes) for authorized accounts only.
Purpose: Verify creator identity, display live audience/engagement metrics on the creator profile, and power brand-side creator discovery and campaign matching.
Storage & Encryption: OAuth access token encrypted at rest with AES-256-GCM (random IV per record) in our PostgreSQL database. Post/media metrics are fetched live on each request and are not persisted beyond the encrypted response cache used for performance.
Retention: Access tokens are deleted immediately on disconnect or account deletion, and in any case within 30 days of a verified deletion request.
Your Control: Disconnect any time from Profile → Social Accounts, or remove app access directly from Facebook → Settings → Apps and Websites.

Meta WhatsApp Cloud API

Scopes / Permissions Requested: whatsapp_business_messaging, whatsapp_business_management (server-side only, via our verified WhatsApp Business Account — not requested from individual users).
Data Fields Received: User's WhatsApp-registered phone number, message template category sent (Authentication, Utility, or Marketing), and delivery status webhooks (sent/delivered/read/failed).
Purpose: Deliver OTP verification codes, transactional/utility notifications (payouts, deal confirmations), and opt-in marketing/campaign alerts.
Storage & Encryption: Phone number stored in our encrypted database alongside the account profile. We do not store message body content beyond what is required for delivery-status debugging (90-day rolling log).
Retention: Delivery logs retained 90 days, then purged. Phone number retained while the account is active.
Your Control: Withdraw WhatsApp consent any time from Notification Settings, reply "STOP" to any message, or email us — see our Privacy Policy §3.

Google / YouTube Data API v3 & YouTube Analytics API

Scopes / Permissions Requested: youtube.readonly, yt-analytics.readonly (read-only scopes only — InfluenceNexus never requests upload, comment-moderation, or channel-management permissions).
Data Fields Received: Channel ID, title, custom URL, subscriber/view/video counts, thumbnail, uploaded video metadata and statistics, and channel-level analytics (watch time, audience demographics, top countries) where available.
Purpose: Verify creator identity, display live channel/video metrics, and power brand-side creator discovery.
Storage & Encryption: OAuth access + refresh token encrypted at rest with AES-256-GCM. Refresh tokens are used server-side only to mint short-lived access tokens; the raw refresh token is never exposed to the browser.
Retention: Tokens deleted immediately on disconnect. Google may independently expire a refresh token after 6 months of inactivity per their policy.
Your Control: Disconnect any time from Profile → Social Accounts, or remove access directly at myaccount.google.com/permissions.

Snap Kit / Snapchat Marketing API

Scopes / Permissions Requested: Snap Kit Login Kit (basic profile: display name, Bitmoji avatar, external ID) and Marketing API read-only scopes for connected public/business profile metrics, where the Creator User's Snapchat account is eligible.
Data Fields Received: Snapchat display name, Bitmoji avatar URL, external (opaque) user ID, and — where the connected account is a Snapchat Business/Creator profile — public engagement metrics made available by the Marketing API.
Purpose: Verify creator identity and, where available, display Snapchat audience metrics on the creator profile.
Storage & Encryption: OAuth access + refresh token encrypted at rest with AES-256-GCM. Refresh tokens stored server-side only.
Retention: Tokens deleted immediately on disconnect or within 30 days of an account deletion request.
Your Control: Disconnect any time from Profile → Social Accounts, or remove app access directly in Snapchat Settings → Connected Apps.

Tax & Compliance Information (KYC) — Collected Directly, Not From a Partner

Scopes / Permissions Requested: Not applicable — this data is entered directly by users on InfluenceNexus, not received via any third-party OAuth or API integration.
Data Fields Received: Creator's PAN (Permanent Account Number), collected as mandatory KYC before any payout is released. Brand and creator GSTIN (Goods and Services Tax Identification Number), where provided, for billing and tax purposes.
Purpose: Comply with Indian tax law, verify creator identity for payout eligibility, and support GST-compliant invoicing for brands.
Storage & Encryption: Stored directly in our PostgreSQL database as part of the creator/brand profile record.
Retention: Retained while the account is active and as required by Indian tax record-keeping law; deleted within 30 days of a verified account deletion request.
Your Control: Update from your Profile / Billing settings, or request correction or deletion by contacting us — see our Privacy Policy §6.

Cashfree Payments (Payment Gateway & Payouts)

Scopes / Permissions Requested: Server-to-server API integration authenticated with our merchant API key/secret — no OAuth consent flow from end users.
Data Fields Received: Order ID, transaction amount, payment status, payment instrument type (card network / UPI app / netbanking bank — never the full card/UPI number), and payout beneficiary bank/UPI details for creator payouts.
Purpose: Process brand wallet top-ups, campaign escrow, and creator payouts; reconcile payment/refund status via signed webhooks.
Storage & Encryption: We never store full card numbers, CVV, UPI PINs, or netbanking credentials used for inbound payments — those are handled entirely within Cashfree's PCI-DSS-compliant checkout. We do store the transaction/order references and status Cashfree returns to us, plus the payout beneficiary bank account number, IFSC code, and UPI VPA that creators provide to receive payouts.
Retention: Transaction and payout records retained 7 years to comply with Indian tax and financial record-keeping law.
Your Control: See our Refund & Cancellation Policy for dispute and refund requests.

Amazon Web Services — Amazon SES

Scopes / Permissions Requested: Server-side sending credentials (IAM), not user-facing.
Data Fields Received: Recipient email address and the transactional email content we send (account, campaign, and payment notifications).
Purpose: Deliver transactional platform emails (verification, notifications, receipts).
Storage & Encryption: Amazon SES processes messages in transit; InfluenceNexus retains delivery/bounce logs to keep sender reputation healthy.
Retention: Delivery/bounce logs retained 90 days.
Your Control: Manage email notification preferences from Account Settings.

Listmonk (Email Marketing & Campaign Lists)

Scopes / Permissions Requested: Self-hosted platform we operate — not a third-party OAuth integration. Sits behind Amazon SES for bulk/marketing-campaign email specifically, distinct from SES’s transactional-email role.
Data Fields Received: Recipient email address, mailing list/segment membership, and marketing/promotional email content and delivery status.
Purpose: Manage marketing mailing lists and send bulk promotional/campaign email (as opposed to transactional email, which is sent directly via Amazon SES).
Storage & Encryption: Runs on our own infrastructure; email addresses and campaign engagement data are stored in Listmonk’s database.
Retention: Retained while you remain subscribed; removed upon unsubscribe or deletion request.
Your Control: Unsubscribe via the link in any marketing email, or manage email notification preferences from Account Settings.

Supabase (Authentication & Database)

Scopes / Permissions Requested: Direct database/auth integration — Supabase is our infrastructure provider, not a data recipient acting on its own behalf.
Data Fields Received: All account, profile, campaign, and encrypted-token data described throughout this policy.
Purpose: Primary database and authentication provider for the platform.
Storage & Encryption: Supabase-managed Row-Level Security (RLS) policies govern access to file/media storage buckets. Core application data (profiles, campaigns, payments) is accessed via a direct Prisma/PostgreSQL connection, with access control enforced by our NestJS backend (authenticated, role-based application-layer authorization), not by Postgres RLS. Connections are encrypted in transit via TLS.
Retention: Matches the retention periods listed above per data category.
Your Control: N/A — Supabase is infrastructure, not a user-facing integration.

Questions from a platform partner or security reviewer?

For API review, business verification, or data-handling questions from Meta, Google, Snap Inc., or Cashfree, contact support@influencenexus.in. See also our Privacy Policy, Terms of Service, and Data Deletion Instructions.

How We Handle Your Data

Last updated: August 24, 2026