Privacy Policy

Scope and responsibility

This policy describes the information handled when you browse growwwth.net, use a Growwwth account and Studio Feed, view channel profiles and editorial pages, save a local watchlist, change preferences, or send us a contributor pitch. “Growwwth,” “we,” and “us” refer to the team operating the service.

You can sign in with Google to access the Studio workspace. Basic sign-in uses only your Google identity. Connecting YouTube is a separate, optional authorization for the read-only features described below; it does not create a paid subscription.

Public channel and editorial data

Growwwth obtains public channel information through YouTube Data API Services. This includes a channel identifier, name, handle, description, avatar, available banner, country, creation date, and public counts for subscribers, views, and videos. We record dated observations of channel counters to show changes over time. Public subscriber counts may be rounded or hidden by YouTube. Studio Feed also collects a sample of recent public videos, including titles, descriptions, tags, thumbnails, publication dates, durations, and available engagement counts.

The blog displays content from the Growwwth editorial installation at editorial.visualmodo.com/growwwth, including articles, images, categories, and author information supplied there. The public directory does not disclose a user's authorized private YouTube reports.

Information from visits

When you visit the site, the hosting and security infrastructure can process technical information needed to deliver a page and protect the service, such as your IP address, request time, requested URL, browser headers, and error details. Directory filters and sorting operate in your browser on the loaded channel list. The current frontend does not send those choices to a Growwwth search-history database.

External services that deliver images or other resources may receive a request from your browser when their content is loaded. Their handling of that request is governed by their own policies.

Cookies and browser storage

The theme choice and public watchlist are stored in your browser’s local storage. They are available only in that browser and can disappear if you clear site data. Google sign-in uses a necessary, signed, HTTP-only session cookie and temporary OAuth cookies. Session records are stored on the server and can be revoked from Account settings. The current frontend does not use an advertising or behavioral analytics SDK.

Hosting, security, and embedded third-party services may use technically necessary cookies or similar mechanisms to operate or protect their own services. You can manage browser storage and cookies in your browser settings; removing local storage also removes the watchlist and theme preference from that browser.

Google sign-in and your account

When you continue with Google, we receive your Google account identifier, name, email address, email verification status and profile photo. We store your Growwwth profile, linked Google identity, account preferences and session records in Growwwth’s dedicated PostgreSQL database. Session records may include your browser information, IP address and sign-in and expiration dates to support security and session management.

Google authorization credentials used by this integration are kept on the server; OAuth access and refresh tokens are encrypted when stored. We never receive your Google password. Basic sign-in requests only identity permissions. Optional YouTube authorization is described separately below. Appearance and time-zone settings are saved to your account. Other Studio drafts and example-tool state remain in this browser, separated by Growwwth user ID.

You can export your account data, edit your display name, revoke sessions, or delete your account in Account settings. The export includes Feed connections and your saved actions and notes, without credentials. Deletion removes your profile, preferences, linked identity, tokens, active sessions, Feed connections, private reports and Feed records from the live database, and clears this account’s Studio data from the browser where you perform deletion. Existing backups retain their separate rotation schedule; drafts in other browsers can be removed by clearing site storage there. Deleting a Growwwth account does not delete your Google or YouTube account.

Optional YouTube connection and Google user data

When you choose Connect YouTube in Studio Feed, Growwwth requests separate read-only permissions: youtube.readonly to identify channels you can authorize and read channel, video and comment information; and yt-analytics.readonly to read non-monetary YouTube Analytics and Reporting data. We verify the channel returned by Google before attaching private reports to your Growwwth account. Access and refresh tokens remain encrypted on the server so authorized data can be refreshed without asking you to sign in for every request.

Authorized reports can include views, watch time, average view duration, audience retention, subscribers gained and lost, traffic sources, search terms, referring videos, impressions and click-through rate. A sample of recent comment conversations may include authors' display names, text and dates. We use this information to show your private Feed, trends, source evidence and review suggestions. We also store channel connections, selected reporting periods, saved insights, review status, deferrals and your notes in PostgreSQL. Private reports are accessible only through your authenticated account and are not added to the public directory.

This permission does not allow Growwwth to publish videos, edit your channel, send comment replies, or read Gmail or Drive. Google user data obtained through this integration is not sold, used for advertising, or sent to a generative AI service. Hosting and database services process stored information only to operate Growwwth. Growwwth's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

You can remove a followed or connected channel in Studio Feed; this deletes its private Feed reports, cards, actions and notes from the live account database. You can revoke Google's permission at Google third-party connections. When a refresh detects revoked authorization, Growwwth clears private report evidence while retaining your authored notes and actions; revocation does not delete your Growwwth account. To remove the account's tokens and all private Feed records, use account deletion in Account settings. Backup copies remain subject to the separate backup rotation.

Contributor submissions

If you use the Write For Us form, you provide a name, email address, and pitch. A successful submission sends that information to our server, then to our email delivery provider for a notification to the Growwwth editorial mailbox. The form does not save pitches to the public channel database or WordPress.

When configured, Cloudflare Turnstile checks the form for automated abuse. The server also uses the originating IP address for a short-lived rate limit. Please do not include private account credentials or sensitive personal information in a pitch. See the submission page for the editorial process.

Why we use information

We use the information described here to display public channel and editorial content, maintain a useful history of public counters, authenticate your account, manage sessions, save account preferences and Feed records, display your authorized YouTube reports and review suggestions, remember choices in your browser, respond to submissions and requests, diagnose failures, and protect the service from abuse. We do not use contributor contact information to populate public channel profiles or sell it as a contact list.

Services and external links

Growwwth uses Google OAuth for account sign-in and optional YouTube authorization, YouTube Data API Services for channel and video information, YouTube Analytics and Reporting APIs for authorized private reports, and a separate WordPress installation for editorial content. Where enabled, Cloudflare Turnstile helps protect the submission form and Resend delivers its email notification. Hosting and database providers process information necessary to operate the site. We share information with these providers only for the relevant service functions, or when required by applicable law.

Use of YouTube API Services is also subject to the YouTube Terms of Service. Google’s handling of information is described in the Google Privacy Policy. Third-party links and embedded content have their own privacy practices.

Retention and corrections

We maintain historical observations of public channel information so that comparisons and trends remain possible. There is no fixed deletion date for that public history. Editorial content remains available according to our publishing decisions. Information in contributor emails is kept for editorial correspondence and related records for as long as it is needed for those purposes.

Operational logs and abuse-prevention data are kept according to the needs and settings of the infrastructure that produces them. If a public profile appears incorrect, if you believe information should be removed, or if you want a contributor submission reviewed or deleted, contact us. We assess requests in light of the data source, the nature of the information, and applicable rights and obligations.

Your choices and rights

You can change the site theme at any time from More, remove a channel from the local watchlist, or clear local browser storage. You may ask about personal information you submitted to us, request a correction or deletion where applicable, or object to certain processing by emailing [email protected]. We may need enough information to verify and address the request.

Public channel details originate from YouTube. Changes made at the source can affect what new API responses contain, while previously recorded public observations may continue to appear as historical data.

Data protection and security

We use technical safeguards to protect the confidentiality of Google user data, including your account information, authorization credentials and private YouTube reports, against unauthorized access, disclosure or alteration:

• Encryption in transit. Connections from your browser to Growwwth use HTTPS with Transport Layer Security (TLS). Our server also uses HTTPS when exchanging authorization credentials and requesting data from Google APIs.
• Encrypted authorization tokens. Google OAuth access and refresh tokens are encrypted before they are stored in PostgreSQL. The encryption secret is kept in server configuration, separately from database records. Tokens, client secrets and encryption secrets are not included in browser code, account exports or public API responses. This stored-token encryption is separate from the access controls protecting account records and private reports.
• Authenticated, account-scoped access. The server validates your session and verifies the account and channel associated with each private request. Another Growwwth user cannot retrieve your private reports or manage your sessions and saved Feed records. Private account and report responses instruct browsers and shared caches not to store them.
• Restricted database access. Account and report data is stored in Growwwth's dedicated database on a private application network, with no publicly exposed database port. Separate database credentials and restricted roles limit what each service can read or change. Public-directory readers and public collection workers have no access to private account or YouTube Analytics tables.
• Session and request protection. Production session cookies are signed, HTTP-only and Secure. OAuth state and PKCE safeguards help prevent forged authorization requests, and sensitive account and Feed changes check the request origin. Authentication and Feed rate limits restrict repeated requests. You can revoke sessions, disconnect a channel or delete your account through the controls described in this policy.

No internet service can guarantee absolute security. Providers involved in hosting, email delivery, and source data may process information in more than one country, subject to their own infrastructure and policies.

Children’s privacy

Growwwth is intended for a general audience interested in public creator statistics and is not directed to children under 13. We do not knowingly seek personal information from children under 13 through the contributor form. If you believe a child provided such information, contact us so we can review it.

Changes and contact

We may update this policy as the product and its providers change. A revised version will appear on this page with a new update date. Material new practices, such as user accounts, private channel connections, or payments, require an updated explanation.

For privacy questions, corrections, or requests, email [email protected]. For the rules governing use of the service, see our Terms.