Privacy Policy
How Growwwth handles your account, optional YouTube reports and publishing controls, public channel history, and browser preferences.
The essentials.
Growwwth displays public YouTube channel information and editorial content. Google sign-in provides access to Studio and Account settings; connecting YouTube separately enables private, read-only Feed reports with your consent. Where enabled, editing video metadata, setting thumbnails and replying to comments require additional publishing consent and confirmation for each change. Feed connections, insights, notes and publication records are saved to your account. Google user data is not sent to generative AI; free-provider tests use fictional context only. Your public watchlist remains in this browser. Successful contributor pitches are delivered to our editorial mailbox. Paid subscriptions are not enabled.
Questions or requests can be sent to [email protected].
Private conversations and optional sharing
Studio Chat stores conversation titles, messages, selected channel identifiers, project folders and their briefs, stages and optional target dates, reusable instructions (skills), generation status, quoted credit usage and optional response feedback in the account-scoped PostgreSQL database. Conversation records and skills are accessible through authenticated, owner-checked requests; public directory readers and collection workers cannot read these tables. Responses use HTTPS and instruct browsers and shared caches not to store private data. Authored conversations remain available until you delete them or your account, independently of a paid AI entitlement. You can export conversations through the private history export. Workspace Search reads only your own saved work; recent-work lists are ordered by the last saved change rather than a visit log. Project folders can be removed without deleting their conversations. Older browser projects are copied into your account only after an explicit import, keeping the browser originals. Search terms are processed to return results and are not stored as a separate search-history database; requested URLs may still appear in infrastructure logs as described below. Unsent text and selected reference identifiers are recovered for ten minutes. Chat references, their metadata and file bytes are stored separately in the private PostgreSQL database until you delete them or your account. The library accepts up to 100 references and 128 MB per account: UTF-8 text up to 64 KB, images up to 8 MB, PDF up to 10 MB and MP4 up to 25 MB, with at most three references totaling 32 MB per request. Images are validated, stripped of embedded metadata and optimized to WebP. File access requires your authenticated account and uses no-store responses. Deleting an unused reference removes its live bytes and extracted text; historical messages retain a deleted-reference marker. Files used by an active generation cannot be deleted until it finishes or is canceled. Backup copies follow the separate rotation schedule.
Selected files are attached by private reference identifiers, separately from the message. Editable result drafts, including manually authored drafts, are stored with revision checks and remain available without a paid AI entitlement. Exports include metadata and authenticated download paths; download file bytes separately before deleting your account. A YouTube link alone does not provide its transcript or give the chat permission to view a video. In provider test mode, only fictional demonstration context is sent to the model: your actual messages, files, saved skills and channel reports are excluded, including for administrators. With an appropriately configured no-training provider, confirmed requests may send the bounded conversation, selected skill, explicitly attached text, image, PDF or MP4 content and available channel evidence necessary to answer. Real-data mode additionally requires verification of the billed provider project and exact API key. The current free-provider configuration remains fictional-only. A file upload alone does not send it to a model. Provider storage is disabled in the API request; infrastructure and provider policies still govern their processing. The chat does not publish content or execute changes to your YouTube account.
Sharing is optional and requires reviewing the full conversation and explicitly confirming a public snapshot. Anyone who obtains that unguessable link can read the saved snapshot without signing in, including any private information you included. Later messages are not added. Snapshots contain only the reviewed message text, excluding private file bytes and separately edited result drafts. Shared pages are marked not to be indexed, use no-store responses and suppress referrer information. Revoke a link from its conversation to remove the live snapshot. Deleting the conversation or account also revokes its links; we cannot remove copies already downloaded by recipients.
Voice input is optional and requires a separate confirmation and your browser's microphone permission. Your browser's speech-recognition service may process audio under its own policies. Growwwth does not save microphone recordings; only text you choose to send is kept. Local planning drafts from older Studio versions stay in your browser unless you explicitly import them. Imports retain a label identifying them as local drafts rather than generated model responses. Live database deletion does not immediately remove copies in backups, which follow the separate backup rotation schedule.
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 read-only reports. Where enabled, publishing controls require an additional, optional authorization as described below. Neither authorization creates 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.
Saved thumbnail projects and images
When you save a thumbnail project in Studio Feed, we store its name, optional target video identifier, version, preview and editable composition in your account. The composition includes independent text, photo and shape layers, fonts, colors, outlines, positions, sizes, rotation, opacity, visibility, locking and stacking order. A project can contain up to 40 layers and eight photo layers. If you upload photos, we validate their actual image format, remove embedded metadata and store optimized images of up to 2560 pixels per side. Each photo can be up to 5 MB, with up to 20 MB of uploaded source images in one save. The optimized photos remain separate from the composition so you can reopen and continue editing. We do not retrieve a video's existing thumbnail as your uploaded source photo.
Project metadata and image bytes are stored in Growwwth's dedicated PostgreSQL database. Each image and preview request requires an authenticated session belonging to the project owner; images have no public sharing URL, and responses instruct browsers and shared caches not to store them. These files are not sent to a generative AI service. Saving a project does not publish it to YouTube.
Authored thumbnail projects remain available until you delete them or your account, including after you stop following a channel or a report subscription expires. Deleting a project removes its composition and preview; a source photo is removed when no remaining project in your account uses it. Account deletion removes all saved projects and their photos from the live database. Backup copies follow the separate backup rotation schedule. Account exports include the editable composition and authenticated download paths for every saved photo; image bytes are not embedded in the JSON export. Download your photos or export a composed image from the editor before deleting your account.
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.