Privacy & Cookie Policy

▸  2.1 Account Information

When you create an account, we collect your name, email address, and subscription tier. This data is required to provide you access to the platform. We use Supabase (Supabase Inc., USA) to store this data securely with AES-256 encryption.

▸  2.2 Payment Information

Our order process is conducted by our online reseller Paddle.com. Paddle.com is the Merchant of Record for all our orders. Paddle provides all customer service inquiries and handles returns. RenderCurve never sees or stores your full payment card details. Paddle receives your name, email, and billing address to process your subscription. Paddle's privacy policy is available at paddle.com/legal/privacy.

▸  2.3 Channel Data — YouTube

If you connect your YouTube channel via Google OAuth (or paste a YouTube URL during onboarding), RenderCurve accesses public channel metadata and, with your consent, your private channel analytics on your behalf, using the YouTube Data API v3 and the YouTube Analytics API (Google LLC). RenderCurve's use and transfer of information received from YouTube API Services and other Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. RenderCurve never uploads, modifies, or deletes videos on your behalf.

The full disclosure of what we access, how we use it, who it is shared with, how it is stored and protected, how long it is retained, and how to delete it is documented in Section 3 — How RenderCurve Uses Google User Data below, written in the structure required by the Google API Services User Data Policy. You can review Google's Privacy Policy at https://policies.google.com/privacy and revoke RenderCurve's access to your Google account at any time via https://myaccount.google.com/permissions or from your RenderCurve account settings.

▸  2.4 Channel Data — Instagram

If you connect your Instagram account via Meta OAuth, we access your account insights using the Instagram Graph API (Meta Platforms Inc.). This includes follower count, post reach, impressions, saves, and engagement rate for your own posts. This data is used exclusively to provide you with growth tracking and strategy recommendations within RenderCurve. We do not access your private messages, stories content beyond public metrics, or any data beyond what is necessary for analytics. Raw API response data is processed immediately and not stored beyond 30 days, in compliance with Meta's Platform Terms. You can revoke Instagram access at any time from your account settings.

▸  2.5 Generated Content

Scripts, hooks, titles, and strategy documents generated through RenderCurve are stored in your account vault. These belong to you. We do not read, analyse, or use your generated content for any purpose other than displaying it back to you.

▸  2.6 Usage Data

We collect basic usage logs including which tools were used, timestamps, and success or failure of operations, for debugging and service improvement purposes. These logs are anonymised after 30 days.

▸  3.1 Data Accessed

When you authorise RenderCurve via Google OAuth, you grant the following read-only scopes. RenderCurve never requests any write, upload, modify, or delete scope.

Scopes RenderCurve does NOT request: youtube.upload, youtube (write), youtube.force-ssl, youtubepartner, or any other scope that would permit RenderCurve to upload, edit, delete, or post on your channel. RenderCurve cannot and does not perform any write actions on your YouTube account.

▸  3.2 Data Usage

Google user data obtained through the scopes above is used only for the following purposes, all of which are user-facing features of RenderCurve:

• Channel Intelligence Profile — a synthesised baseline of your channel's niche, performance trend, and audience pattern. Generated when you connect, refreshed monthly.
• Strategy Blueprint — long-term content strategy recommendations specific to your channel. Refreshed every 90 days.
• Per-tool outputs that you explicitly request inside the dashboard — Idea Velocity, Growth Matrix, Strategy Pulse, Retention Stress Test, Weekly Debrief, and Your Strategy.
• 96-hour compliance and rescue check-in (Layer 8/9 of the strategic engine, tier-gated) — evaluates derived signals from your channel against policy-violation heuristics so we can warn you about potentially at-risk content. This evaluation operates on summarised signals; raw video content is not analysed.

Prohibited uses (matching Google's Limited Use requirements). RenderCurve does not:

• Use Google user data to serve advertisements, including retargeting, personalised, or interest-based ads.
• Transfer Google user data to determine creditworthiness or for any lending purpose.
• Sell, rent, or licence Google user data to any third party.
• Allow humans to read Google user data, except where (a) we have obtained your affirmative consent for specific data, (b) it is necessary for security purposes (e.g. investigating abuse), (c) we are required to do so to comply with applicable law, or (d) the data has been aggregated and anonymised so it can no longer be used to identify any individual.
• Use Google user data to train, fine-tune, or improve generalised AI/ML models.

▸  3.3 Data Sharing

Google user data is processed by the limited set of sub-processors listed below. We do not share Google user data with any other third party.

RenderCurve does not share, sell, rent, or transfer Google user data to advertising networks, data brokers, analytics vendors, marketing platforms, model-training datasets, or any party outside the three sub-processors listed above. The full list of sub-processors is also published in our Data Processing Agreement.

Note on the Google Gemini API. RenderCurve uses Google's Gemini API for image generation and topical research. Gemini receives only topic and niche text that you have authored; it does not receive any data fetched from your Google or YouTube account (no channel metadata, no analytics, no OAuth tokens).

Note on payment processing. Paddle.com (our Merchant of Record for subscriptions) is not listed in the table above because Paddle does not receive any Google user data. Paddle only processes the billing information you enter at checkout (name, billing address, payment instrument); it has no access to your YouTube channel, your YouTube analytics, your OAuth tokens, or any data fetched from Google APIs. Paddle is described in Section 2.2 and listed in our broader third-party services table in Section 4.

▸  3.4 Data Storage & Protection

Google user data is protected by the following technical and organisational measures:

• Encryption at rest. OAuth access tokens and refresh tokens are encrypted with AES-256-GCM before being written to the database. Encryption uses a 256-bit key held in a server-side environment variable (TOKEN_ENCRYPTION_KEY) that is never present in client code, browser bundles, or version control. A unique 96-bit IV is generated per token and a 128-bit GCM authentication tag protects every record against tampering.
• Encryption in transit. All traffic — between your browser and RenderCurve, between RenderCurve and Google APIs, and between RenderCurve and Supabase — uses TLS 1.2 or higher.
• Server-side proxy architecture. Every YouTube Data API and YouTube Analytics API call is made by RenderCurve's backend, never by the browser. Access tokens are decrypted in process memory only at the moment of the API call and the decrypted value never leaves the server process or appears in any log.
• Database isolation. Supabase Postgres uses Row Level Security (RLS) on every table holding user data, with deny-all default policies. The application server uses a service-role key restricted to this single project; users have no direct database access.
• Hosting region. Database storage is hosted by Supabase in Singapore (ap-southeast-1).
• Access controls. Production database and secret access is restricted to the operator (Pranav Pravin Mandlik) using individual credentials with multi-factor authentication. We do not use shared credentials.
• Logging discipline. OAuth tokens, signed cookies, and authorization codes are filtered out of all server logs and error reports. Authorization codes are validated and immediately discarded.
• CSRF protection. The OAuth flow uses an opaque state parameter stored server-side with a 10-minute expiry; the state is validated and consumed exactly once.

▸  3.5 Data Retention & Deletion

Retention schedule for Google user data:

How to request deletion of your Google user data. Any of the four paths below is sufficient — choose whichever you prefer:

1. In-product, full account: go to Account Settings → Profile → Delete Account. RenderCurve immediately (a) calls https://oauth2.googleapis.com/revoke to revoke RenderCurve's access to your Google account, (b) marks your connected-account record as disconnected, (c) deletes your user record (which cascades and removes all derived engine data — diagnostics, goal maps, topic runs, monitoring snapshots, and rescue analyses), and (d) removes your authentication identity. You are redirected to a deletion-status page with a confirmation code.
2. In-product, disconnect only (keep RenderCurve account): Account Settings → Connected Accounts → YouTube → Disconnect. This revokes our tokens with Google and removes the connection without deleting your RenderCurve account.
3. Directly with Google: visit https://myaccount.google.com/permissions, find RenderCurve, and click Remove access. This immediately invalidates our tokens; the next time RenderCurve attempts an API call we detect the revocation and mark your connection as disconnected.
4. By email: email privacy@rendercurve.com from the address on your account. We complete the deletion within 7 days (well inside Google's 30-day requirement) and reply with confirmation.

After deletion, the only thing retained is payment records (name, email, billing address, transaction reference), kept for 7 years as required by Indian tax and accounting law. These records contain no Google user data — no channel data, no analytics, no tokens.