What we collect and store
AnalyzeYou uses the official YouTube Data API for public video, channel, playlist, search and comment information. It stores reusable response data, resource identifiers, ordered sample membership, collection outcomes and observation dates. Signed-in collections can also store private tool results and library associations.
Stored public comments can contain author display names and channel identifiers in addition to text, dates, likes and reply counts. Comment exports can include those public fields. Anonymous public-data collection is also stored where needed for tool operation; it is not anonymous account history that a later sign-in automatically owns.
We do not collect private YouTube analytics, transcripts or channel-management credentials in the current service. Google sign-in is identity-only. Local uploaded images, pixel data, manual calculations, QR generation and tag editing stay in your browser. Public image binaries are not archived on the server as research evidence; a thumbnail used in a local analysis can be kept with that result in browser history.
Reuse, freshness and report history
Saved views read stored data without automatically making new YouTube or AI requests. Video analysis can reuse recent public metadata for up to 24 hours by default; keyword results can reuse a matching result for 20 minutes. An explicit fresh-collection action bypasses the relevant reuse where supported.
Reports preserve the original evidence and calculation dates. A refreshed video does not silently replace an earlier AI report's sources. Compatible older reports may be reformatted without a new AI request; missing original evidence is shown as unavailable.
Each available tool has a Past usage link. Signed-in API collections reopen private frozen results without fetching current API data. Browser-only work, edited tag selections and completed comment draws reopen on the device where they were saved. Earlier shared lookups are labeled when the original tool was not recorded; overwritten history and anonymous usage cannot be reconstructed.
AI reuse requires a matching account, goal, selected sources, eligible evidence and provider configuration. Reading or comparing saved reports uses no weekly generation allowance. Reuse is an efficiency measure, not a promise that public statistics or comments are current.
Retention and expiry
| Data | Lifetime and deletion behavior |
|---|---|
| Public API observations and response copies | Eligible for up to 30 days from collection. Older observations must be refreshed or removed; omitted comments are not renewed by a limited refresh. |
| Derived tool artifacts, AI evidence and report versions | Bounded by the oldest included source's 30-day lifetime. A new version does not extend an earlier version's source dates. |
| Account identity and saved associations | Kept while the account exists, subject to applicable deletion requirements. Associations whose source resources are removed can also be cleaned up. |
| Session and login cookies | Sessions default to 30 days, configurable for 1–90 days; login nonces last 15 minutes. Sign-out revokes the current session; deletion removes the account's sessions. |
| Usage and safe operational records | May remain beyond a source's expiry for allowance accounting and service operation. Account-linked usage is removed with account deletion. No universal log or backup deletion period is claimed here. |
| Local browser data and exports | Tool history and its images are available for up to 30 days in this browser, with a maximum of 20 entries per tool / 100 MiB per account. Source-linked copies can expire earlier. Expired entries are pruned during history access; storage limits can remove older entries. Theme preference lasts until changed or cleared. Files or copies you export remain under your control. |
Expiry stops normal report reads and prevents expired evidence from entering new AI generation. Physical database removal requires the operator's cleanup process; it is not scheduled automatically in this local installation. Cleanup can prune copies up to 24 hours before their displayed expiry, so that date is a maximum eligibility bound, not guaranteed availability.
External-provider retention is separate from AnalyzeYou's source expiry. OpenAI may retain information under its own API data controls, even though AnalyzeYou disables saved-response storage.
Access, AI sharing and sensitive text
Your saved library associations, account tool history and AI reports are private to your account. Independently collected public metadata and reusable public analysis may be shared across tool requests. Operators and infrastructure providers can access information needed to administer the service; private does not mean inaccessible to the service operator.
New AI generation uses bounded stored evidence. Optional comment/channel sources are excluded when you choose not to include them. The provider receives no separate comment author names or identifiers, but source text can itself contain identifying or sensitive information. Review your source choices and avoid collecting material you are not entitled to use.
AnalyzeYou does not use these records to build an advertising profile. See the Privacy Policy's provider disclosures for Google sign-in, suggestions, public image hosts and OpenAI processing.
Deleting data and managing access
Use Account settings to delete your account and its private saved references, tool archives/results, AI evidence/report versions, usage records and sessions. Independently collected shared public resource data and anonymous collections are not removed merely because one user deletes an account; they remain subject to their own source lifetimes.
Use a tool's Past usage page to clear that tool's device history, or clear AnalyzeYou site storage in your browser. Account deletion attempts to clear local tool history for that account in the current browser. It cannot reach local copies on other devices; blocked browser storage can also prevent that clearing.
Account deletion does not remove your Google account, delete videos/comments on YouTube, revoke a separate Google permission, or erase exports you downloaded. Manage third-party permissions in Google Account settings. The current sign-in does not request YouTube account access.
For concerns about public information retained by AnalyzeYou, including a public comment that identifies you, contact the operator and identify the affected resource. The operator can assess identity, applicable rights and the stored copies concerned. There is no automatic third-party public-content removal workflow at present.
The service operator for this installation is AnalyzeYou.
For privacy questions, data requests, content concerns or questions about these terms, email chaudharyrajat80@gmail.com. Include enough information to identify the account or public resource concerned. Do not send passwords, API keys or other secrets.
Evidence limits and your responsibilities
Public counts can change or be corrected. Top-level comment samples are bounded and not representative of all viewers; replies are not fetched. Recent-upload samples have different video ages. Unavailable fields are not evidence of zero activity.
Calculated SEO/outlier/image checks are AnalyzeYou heuristics, not official YouTube ranking signals. Public information does not reveal private CTR, retention, demographics or actual creator revenue. Comparisons are dated observations and do not prove that a recommendation caused a change.
Public content remains subject to its owners' rights and YouTube's terms. Exporting it does not create permission to republish, identify or contact people, or use their content unlawfully. Keep your own copies secure and follow the Terms & Conditions.