Effective Date: 23 March 2026 · Last Updated: 9 November 2026
Product Growth AI ("we," "us," "our") operates the website productgrowth.in and associated products and services (collectively, the "Platform"). This Privacy Policy explains how we collect, use, store, share, and protect your information when you use our Platform, including any features that integrate with Google APIs or process payments through Razorpay.
By accessing or using the Platform, you agree to the practices described in this Privacy Policy. If you do not agree, please do not use our Platform.
1. Information We Collect
1.1 Information You Provide Directly
When you interact with our Platform — for example by booking a meeting, purchasing a service, filling out a form, or contacting us — we may collect:
- Full name and email address
- Phone number (if provided)
- Company name, job title, and industry
- Messages, feedback, and communication content you send us
- Billing information (processed securely via Razorpay — see Section 5)
1.2 Information Collected Automatically
When you visit our website, we automatically collect certain technical information:
- IP address, browser type, operating system, and device information
- Pages visited, time spent, referral source, and click patterns
- Cookies and similar tracking identifiers (see Section 8)
1.3 Information from Third-Party Services
If you choose to authenticate or connect a third-party account (such as Google), we receive certain data from that service as described in Section 2 below.
2. Google User Data
2.1 Data Accessed
When you sign in or connect your Google account to our Platform, we may request access to the following types of Google user data depending on the features you use:
- Basic profile information: Your name, email address, and profile picture (via Google Sign-In / OpenID Connect scopes).
- Email (Gmail API): If you use features that involve sending or reading emails (such as the Inbox advisory product), we may request access to read, compose, or send emails on your behalf. We only request the minimum scopes necessary for the feature you are using.
- Calendar (Google Calendar API): If you use scheduling features, we may access your calendar to create, view, or manage events related to advisory sessions or meetings.
YouTube is covered separately in Section 14: we do not ask visitors to connect a YouTube account.
We only request scopes that are necessary for the specific features you choose to use. You will see the exact scopes listed on the Google OAuth consent screen before granting access.
2.2 How We Use Google User Data
Google user data is used solely to provide and improve the user-facing features of our Platform that you have chosen to use. Specifically:
- Authentication: To verify your identity and sign you in to the Platform.
- Email-based advisory: To read incoming advisory queries and send AI-generated responses via the Inbox product, only when you opt in to this feature.
- Meeting scheduling: To create or manage calendar events for booked advisory sessions.
- Personalization: To display your name and profile picture within the Platform for a personalized experience.
We do NOT use Google user data for:
- Advertising, ad targeting, or ad profiling
- Selling or sharing data with data brokers
- Training machine learning or AI models (except for the specific advisory features you opt in to, and only using your own data in your own session)
- Any purpose unrelated to providing or improving user-facing features of our Platform
2.3 How We Store Google User Data
- OAuth tokens (access and refresh tokens) are stored in encrypted form in our secure database (Supabase) with row-level security enabled.
- Email and calendar content is processed in real-time and is not permanently stored on our servers unless explicitly required for the feature. Any stored content is encrypted at rest.
- Basic profile data (name, email) is stored in your user account record for authentication and display purposes.
- All data transmission occurs over HTTPS/TLS encryption.
2.4 Sharing of Google User Data
We do not sell, rent, lease, or trade your Google user data to any third party. Google user data is shared only in the following limited circumstances:
- AI Processing: When you use advisory features, your question is sent to Anthropic's Claude API to write the answer. If semantic search is switched on, your question is also sent to OpenAI to find related news stories. If you play an answer aloud, its text is sent to a voice provider (OpenAI or ElevenLabs). These providers process data under their own privacy policies and API terms.
- Infrastructure Providers: Our hosting and database providers (Netlify, Supabase) may process data as part of providing their services to us. They act as data processors under our instructions and do not use your data for independent purposes.
- Legal Requirements: We may disclose data if required by law, regulation, legal process, or governmental request.
2.5 Revoking Access
You can revoke our access to your Google account data at any time by:
Upon revocation, we will delete or anonymize all Google user data associated with your account within 30 days, except where retention is required by law.
3. How We Use Your Information
- To provide, operate, and maintain the Platform and its features
- To process transactions and send related information (invoices, receipts)
- To respond to your inquiries, support requests, and advisory queries
- To send you updates, newsletters, or marketing communications (only with your consent; you can opt out at any time)
- To personalize your experience and deliver content relevant to your interests
- To analyse usage patterns, monitor performance, and improve the Platform
- To detect, prevent, and address fraud, abuse, or technical issues
- To comply with legal obligations and enforce our Terms of Service
4. Data Sharing & Third Parties
We do not sell your personal data. We may share information with third parties only in the following circumstances:
| Third Party | Purpose | Data Shared |
| Razorpay | Payment processing | Name, email, payment instrument details |
| Supabase | Database & authentication | Account data, encrypted tokens |
| Netlify | Website hosting | Server logs, IP addresses |
| Anthropic (Claude API) | AI response generation | Query content (not retained) |
| ElevenLabs | Voice/audio generation | Text content for audio conversion |
| Sarvam | Indian-language voices for Listen and the podcast; speech to text and spoken answers in Intelligence | Episode scripts (the text to be read aloud); in Intelligence, your voice recording (turned into text) and the answer read aloud |
| OpenAI | Search over our news; a backup voice | Our own news stories; your Kriyā question when semantic search is on; text read aloud when OpenAI voices it |
| Slack | Our team workspace, where enquiries reach us | When you write to us: your name, email and message |
| Resend | Sending email (the daily brief, sign-in codes, receipts, replies) | Your email address and the message |
| DigitalOcean | The server that makes audio and video | Episode scripts, links and titles. No account data |
| Google APIs | Auth, email, calendar, and YouTube (our own channel; see Section 14) | OAuth tokens, profile data; for YouTube: our own videos, and public comments on them |
| Google Analytics | Website analytics | Anonymized usage data |
| PostHog | Product analytics | Pages visited and actions on the site, device and browser details, a random visitor ID |
All third-party providers are contractually bound to use your data solely for the purposes specified and in accordance with applicable data protection laws.
5. Payment Data & Razorpay
We use Razorpay as our payment gateway. When you make a payment:
- Payment instrument details (credit/debit card numbers, UPI IDs, net banking credentials) are collected and processed directly by Razorpay. We do not store your full card number or financial credentials on our servers.
- We receive from Razorpay: transaction ID, payment status, amount paid, payment method type, and a masked reference (e.g., last 4 digits of card).
- Razorpay is a PCI-DSS compliant payment aggregator authorized by the Reserve Bank of India (RBI).
- All payment data is transmitted over secure, encrypted connections (TLS 1.2+).
For more information, see Razorpay's Privacy Policy and Razorpay's Terms of Service.
5.1 Invoicing & Financial Records
We generate and store invoices for completed transactions as required under the Goods and Services Tax (GST) Act and applicable Indian tax laws. Invoices may include your name, email, billing address, GST number (if provided), service description, amount, and tax details. These records are retained for the period required by law (minimum 8 years under the Income Tax Act).
6. Data Storage & Security
- Encryption in transit: All data transmitted between your device and our servers is encrypted using HTTPS/TLS.
- Encryption at rest: Sensitive data (including OAuth tokens and user credentials) is encrypted at rest in our database.
- Access controls: Access to user data is restricted to authorized personnel on a need-to-know basis with role-based access controls and audit logs.
- Infrastructure security: Our database is hosted on Supabase (built on AWS infrastructure) with row-level security (RLS) policies. Our website is hosted on Netlify with automated SSL certificates.
- Regular reviews: We periodically review our security practices and update them to address new threats.
While we strive to use commercially acceptable means to protect your data, no method of transmission or storage is 100% secure. We commit to promptly notifying affected users in the event of a data breach as required by applicable law.
7. Data Retention & Deletion
We retain your personal data only for as long as necessary to fulfill the purposes described in this Privacy Policy, unless a longer retention period is required or permitted by law.
| Data Type | Retention Period |
| Account & profile data | Until you request deletion or close your account |
| Google OAuth tokens | Until you revoke access or delete your account |
| Google user data (email/calendar) | Real-time processing; logs up to 90 days then deleted |
| Transaction & invoice records | 8 years (Indian tax law requirement) |
| Website analytics & logs | 12 months, then anonymized or deleted |
| Communication records | 3 years from last interaction |
7.1 Requesting Data Deletion
Delete your account yourself: sign in, open your account → Settings, scroll to Delete account at the bottom, press it and confirm. It deletes your profile, chats, saved episodes, plans and your sign-in for every product at once; invoices for payments stay on file because tax law requires it. What is deleted and what is kept.
You may also request deletion of your personal data at any time by emailing hello@productgrowth.in with the subject line "Data Deletion Request." We will:
- Acknowledge your request within 48 hours
- Delete or anonymize your data within 30 days
- Notify you once deletion is complete
- Retain only what is required by law (e.g., tax records), and inform you of exceptions
You may also revoke Google data access at Google Account Permissions.
8. Cookies & Tracking Technologies
- Essential cookies: Required for the Platform to function (session management, authentication). Cannot be disabled.
- Analytics cookies: Help us understand how visitors interact with the Platform. Used to improve performance and content.
- Preference cookies: Remember your settings and choices.
We do not use advertising or retargeting cookies. You can manage cookie preferences through your browser settings.
9. Your Rights
- Right to Access: Request a copy of the personal data we hold about you.
- Right to Correction: Request correction of inaccurate or incomplete data.
- Right to Deletion: Request deletion of your personal data (subject to legal retention requirements).
- Right to Data Portability: Request your data in a structured, machine-readable format.
- Right to Withdraw Consent: Withdraw consent for data processing at any time.
- Right to Grievance Redressal: File a complaint with us or with the relevant data protection authority.
9.1 For Indian Users (DPDPA 2023)
If you are a resident of India, your rights under the Digital Personal Data Protection Act, 2023 (DPDPA) include the right to access, correction, erasure, and grievance redressal. You may exercise these rights by contacting our Grievance Officer (see Section 13).
9.2 For Users in the European Economic Area (EEA)
If you are located in the EEA, your data is processed under the lawful bases of consent, contract performance, and legitimate interest as applicable under the GDPR. You have additional rights including the right to restrict processing and to lodge a complaint with your local data protection authority.
10. Children's Privacy
Our Platform is not directed at individuals under the age of 18. We do not knowingly collect personal data from children. If we become aware that we have inadvertently collected data from a child, we will delete it promptly. Contact us at hello@productgrowth.in if you believe a child has provided us with personal data.
11. International Users
Our Platform is operated from India. If you access the Platform from outside India, your data may be transferred to and processed in India. By using the Platform, you consent to such transfer. We ensure that all data transfers are conducted with appropriate safeguards in compliance with applicable data protection laws.
12. Changes to This Policy
We may update this Privacy Policy from time to time. When we make material changes, we will:
- Update the "Last Updated" date at the top of this page
- Notify you via email or a prominent notice on the Platform if the changes significantly affect how we handle your data
- Seek your renewed consent if required for any new use of Google user data
Your continued use of the Platform after changes take effect constitutes acceptance of the updated Privacy Policy.
If you have any questions, concerns, or requests regarding this Privacy Policy or your personal data, please contact us:
We will respond to all privacy-related inquiries within 48 hours and resolve them within 30 days.
14. YouTube API Services
Product Growth AI uses YouTube API Services. This section says what we access, what we do with it, and how to revoke access and have it deleted. By using the parts of the Platform that show or play YouTube videos, you agree to be bound by the YouTube Terms of Service. Google's handling of data is described in the Google Privacy Policy.
14.1 What we access
- Our own YouTube channel, as its owner. The owner of the channel signs in once with Google and lets us upload videos, set thumbnails, manage playlists and set a video private, public or scheduled (the scope
https://www.googleapis.com/auth/youtube). This is the only account that gives us access. We do not ask any visitor to sign in with YouTube or to share a YouTube account, so we hold no YouTube account data about visitors.
- Public data, read with an API key. The latest videos on our channel and their public view counts; public videos on a topic (title, channel name, thumbnail, length, link) for the /social/ page; and the public comments on our own videos (the commenter's public display name, the text and the time).
14.2 How we use it, and who it is shared with
- Uploaded files, titles, descriptions and thumbnails are our own content, published to our own channel.
- Video lists and view counts are shown on our pages and in our own daily report.
- Comments on our own videos are read once a day. The text is sent to Anthropic's Claude API to draft a short reply, and the list is posted to our private Slack workspace. Nothing is posted back to YouTube by software: the owner replies by hand. Our servers keep no copy of comment text.
- We do not sell YouTube data, do not use it for advertising, and do not allow third parties to serve ads or content using it. Besides Anthropic and Slack (above), it sits with our hosting and database providers listed in Section 4, who process it only to run the service.
14.3 What we store, and for how long
- The sign-in token for our channel: kept in the private settings of our own server, not in the website or in a public database, until access is revoked.
- An upload record: the video's ID, title, status and time, in a file on our server and in a log row in our database. Kept while the video exists on our channel.
- Public YouTube data shown on /social/ (video lists, topic lists, view counts): kept as public files that are replaced each time the feed is refreshed. We refresh or delete any stored YouTube API data at least every 30 days.
14.4 Cookies and device storage
We do not place YouTube cookies on your device. On /social/, a video plays only after you press play, using YouTube's embedded player from youtube-nocookie.com. YouTube (Google) may then store or read information on your device under the Google Privacy Policy. Our own cookies are described in Section 8.
14.5 Revoke access and delete your data
- Revoke: in addition to our normal procedure for deleting stored data, you can revoke our access to your data at any time on the Google security settings page (https://security.google.com/settings/security/permissions).
- Delete on request: email hello@productgrowth.in and we delete the stored data you ask about within 7 calendar days, and tell you when it is done.
- After revocation or token expiry: we delete the sign-in token and all YouTube API data stored under it as soon as possible, and no later than 30 calendar days.
- Deleting what we store does not change anything on YouTube. To remove data on YouTube itself, use YouTube Studio, a YouTube application, or an authorised API client.
14.6 Questions or complaints
About how we handle YouTube data, write to hello@productgrowth.in. We answer within 48 hours (see Section 13).
Google API Services Disclosure: Product Growth AI's use and transfer of information received from Google APIs to any other app will adhere to the
Google API Services User Data Policy, including the Limited Use requirements.