Privacy Policy
Effective date: September 6, 2026
This Privacy Policy explains how Comment Viewer collects, uses, shares, and protects information when you use our website, products, and services.
Who we are
Comment Viewer ("Comment Viewer", "we", "us") is an independent project run by a solo developer. It is not a company, and it is not affiliated with TikTok, Instagram, YouTube, or their owners. For the purposes of applicable data protection laws, we are the controller of personal information processed through the service. You can reach us about any privacy matter, including a request to exercise the rights described below, at hello@commentviewer.net — that address is monitored by the person who runs the service, not by a queue.
Information we collect
Comment Viewer has no upload field and no free-text box. What you give us directly is limited to account details when you sign up, billing information when you buy, and anything you write to us in a support message.
We also collect usage and device information automatically, including log data, browser type, IP address, pages viewed, referral URLs, and approximate location derived from technical signals.
How we use information
We use information to:
- Provide, maintain, and improve the service.
- Create and manage accounts.
- Process payments, credits, subscriptions, and refunds.
- Generate, store, and deliver user-requested content.
- Detect, prevent, and respond to fraud, abuse, security incidents, and policy violations.
- Communicate service updates, support responses, and administrative notices.
- Analyze usage trends and improve product performance.
What you look up
To show you a post, the link you enter is sent to our data provider, which returns the public TikTok, Instagram or YouTube content behind it. We keep no per-person browsing history on our servers: we do not build a record of which posts a given visitor has viewed, and there is no such list to hand over or leak. The recent-lookups list under the search field is kept in your own browser's storage, never sent to us, and cleared with your browser data.
Public content that comes back — a post's public details and its comments — is cached on our infrastructure so that repeat views of the same popular post do not re-fetch it. That cache is keyed by the post, never by you, and it expires on its own: post details within six hours, comments within twenty-four. This content is published publicly by its authors; we neither add to it nor keep a copy past those windows.
The one exception to "not written down" is an export you pay for. A comment export creates a billing record with the post's link on it, so that the charge can be explained, refunded and audited — the way any receipt does. That record is tied to your account and is kept for as long as accounting and tax rules require.
Export files
A comment export is built in the background and stored in our object storage so you can download it when it is ready. Only your account can download it, and the file is deleted automatically seven days after it is finished. The partial pieces written while an export runs are deleted when it finishes, and within a day at the latest.
No AI training on your activity
We do not sell your personal information, and we do not use what you look up to train machine-learning models. We may use aggregated or de-identified usage data that does not identify you to operate, secure and improve the service.
Legal bases for processing (EEA/UK)
Where the GDPR or UK GDPR applies, we process personal information on one or more of these legal bases: performance of our contract with you, your consent, our legitimate interests in operating and securing the service, and compliance with legal obligations. Where we rely on consent, you may withdraw it at any time without affecting prior processing.
Cookies and similar technologies
We use cookies and similar technologies to keep you signed in, remember preferences, secure the service, measure usage, and support payment and analytics integrations. See our Cookie Policy for more information.
How we share information
We rely on the following providers to run the service. Each processes only what its job requires, under its own privacy terms:
- Cloudflare — hosting, edge caching, the object storage that holds export files, and the Turnstile check that runs before a paid query.
- Turso — the database holding accounts, credit balances and billing records.
- TikHub — the data provider we send a post link to in order to retrieve public TikTok, Instagram and YouTube content.
- TikTok, Instagram and YouTube — images, avatars and the TikTok video player are loaded by your browser directly from their content delivery networks, and a YouTube video plays in YouTube's own embedded player (in its privacy-enhanced mode).
- Waffo — payment processing, subscriptions and the card details we never see ourselves.
- Google — sign-in, if you choose to sign in with a Google account.
- Resend or Cloudflare Email — transactional email such as sign-in codes and receipts.
- Google Analytics, Plausible, Microsoft Clarity and Google Ads — usage measurement and campaign measurement, where enabled. See our Cookie Policy for what each one sets and how to refuse it.
We may also disclose information when required by law, to protect rights and safety, to enforce our terms, or as part of a merger, acquisition, financing, or sale of assets.
Data retention
We retain information for as long as needed to provide the service, comply with legal obligations, resolve disputes, enforce agreements, and maintain security. Retention periods may vary depending on the type of information and the context in which it is used.
Security
We use reasonable technical and organizational measures to protect information. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.
Your choices and privacy rights
You may update account information, manage cookie preferences where available, request support, or ask us to delete certain information. Some information may be retained when required for legal, security, fraud prevention, or accounting purposes.
Depending on where you live, you may have rights to access, correct, delete, port, or restrict the processing of your personal information, to object to certain processing, and to withdraw consent. Where the GDPR or UK GDPR applies, you also have the right to lodge a complaint with your local supervisory authority.
If you are a California resident, you may exercise rights under the CCPA/CPRA, including the right to know, delete, and correct personal information, and the right to opt out of the "sale" or "sharing" of personal information. We do not sell personal information for money. To the extent any analytics or marketing measurement constitutes "sharing" under California law, you may opt out by contacting us at hello@commentviewer.net or using available cookie controls.
To exercise any of these rights, contact us at hello@commentviewer.net. We will not discriminate against you for exercising them, and we may need to verify your identity before responding.
Children's privacy
The service is not intended for children under 13 (or under 16 in the EEA and UK, where a higher age applies), and we do not knowingly collect personal information from children below the applicable age. If you believe a child has provided us personal information, contact us at hello@commentviewer.net so we can delete it.
International use
Your information may be processed in countries other than where you live. Those countries may have data protection laws that differ from the laws in your jurisdiction.
Changes to this policy
We may update this Privacy Policy from time to time. If we make material changes, we will take reasonable steps to notify users or update the effective date above.
Contact
If you have questions about this Privacy Policy, contact us at hello@commentviewer.net or through the support channel provided in the service.