Privacy policy

Last updated: 7 September 2026. Applies to the Comment Sweep mobile app (Android application id and iOS bundle id io.naseeh.commentsweep) and to this website, commentsweep.naseeh.io.

The short version

• There is no Comment Sweep server, no database and no Comment Sweep account. Nothing about you is sent to us, because there is no “us” to send it to.
• The app talks to Google's own API from your device, using your own Google sign-in and one YouTube permission.
• Your Google Takeout file is read on the phone and is never uploaded.
• No analytics, no advertising, no tracking, no cookies — not in the app and not on this website.
• No human being reads your YouTube data. There is nowhere for a human to read it from.

Who is responsible

Comment Sweep is a personal project. Questions and requests go to ahmed@naseeh.io.

What the app is allowed to touch

Comment Sweep requests exactly one OAuth scope:

https://www.googleapis.com/auth/youtube.force-ssl

Google classifies this as a sensitive/restricted YouTube scope. It is the narrowest scope that can do what the app is for; there is no read-only scope that can also delete. The app uses it only to:

• identify your own channel, so it can tell your comments apart from other people's;
• list the videos you have liked, and the comments you have written, so you can see them;
• show a video's title next to a comment rather than an internal id;
• remove a like, or delete a comment, when you have selected it and confirmed.

The app does not post comments, leave ratings, subscribe, upload, or make any other change to your channel. The only changes it makes are the removals you select and confirm.

Google API Services User Data Policy — Limited Use disclosure

Because Comment Sweep uses the restricted scope https://www.googleapis.com/auth/youtube.force-ssl, the Limited Use requirements apply in full. Concretely:

• Use is limited to the user-facing feature. Data obtained through that scope — your channel id, your liked videos, your comments — is used only to show you those items in the app and to remove the ones you select. It is used for nothing else.
• No transfer. The data is not transferred to anyone, except as necessary to provide the feature itself: the API requests that carry it go from your device to Google. There is no other recipient, no third-party processor, no server of ours, and no sale of data. If that ever changed — for example an acquisition — you would be told first and it would only happen with your consent, or where the law requires disclosure.
• No advertising. The data is never used for serving advertisements of any kind, including personalised, retargeted or interest-based advertising. The app shows no adverts at all.
• No humans read it. No human reads this data. The app holds it in memory on your phone while a screen is open and discards it when the screen closes. There is no server-side copy for anyone to open, so none of the usual exceptions (security investigations, legal compliance, aggregated internal operations) can apply — there is nothing to inspect.

Google updates the wording it expects in this disclosure from time to time. The paragraph in the box above is the standard sentence as we understand the current guidance; if Google's verification review asks for different wording, this page will be changed to match it exactly rather than argued with.

What leaves your device, and where it goes

Everything the app sends goes to Google. There is no Comment Sweep server to send anything to.

• YouTube requests go from your phone directly to Google's API over HTTPS, carrying your own access token. Google receives them as the operator of the API; Google's handling of them is covered by Google's privacy policy, not this one.
• Google sign-in is handled by Google's own sign-in component and the account picker built into Android and iOS. The app never sees or stores your password.
• Images — your account's profile picture, and the thumbnail beside each liked video — are loaded from Google's and YouTube's image hosts, the same as they would be in any YouTube client. No access token is attached to those requests.
• Opening Google Takeout hands that address to your normal browser. That visit is between you and Google.

The app carries no analytics, no advertising and no tracking of any kind.

Your Google Takeout file

The complete list of comments you have written only exists in an export you request from Google. You download that file yourself and pick it in the app. Comment Sweep reads it on the device, shows the comments as a list, and forgets them when you leave the screen. The file is never uploaded, never copied to a server, and never sent anywhere. Deleting the file afterwards is up to you and your phone's file manager.

What is stored on your device

The app keeps a few small settings in the phone's ordinary local storage: how much of the daily API allowance this device estimates it has used and which day that count belongs to, a running total of how many items you have removed, and your light/dark appearance choice.

None of it contains a video, a comment, a channel, an email address or anything else that identifies you, and none of it is transmitted anywhere. Separately, Google's sign-in component and the operating system keep your signed-in session and access token in their own storage; that is Google's and the platform's mechanism, not something Comment Sweep writes itself.

This website

commentsweep.naseeh.io is static HTML and one CSS file. It sets no cookies, loads no fonts or scripts from anywhere else, embeds nothing, and runs no analytics. There is no form to submit and no login.

The site is served by a hosting provider. Like any web server, that provider keeps ordinary request logs — IP address, timestamp, path, user agent — as part of operating and protecting the service. Those logs are the platform's standard behaviour; nothing further is collected, and nothing on the site tries to identify you.

Children

Comment Sweep is not directed at children under 13 and collects nothing from anyone, of any age.

Taking the permission back

You can revoke the app's access at any time, from Google rather than from the app:

1. Go to myaccount.google.com/permissions while signed in to the Google account you used.
2. Find Comment Sweep in the list of apps with access to your account and open it.
3. Choose Remove access and confirm.

After that the app can do nothing at all with your account until you sign in again and grant the permission again. The app also has a sign-out button, which ends the session on the device but does not by itself revoke the grant at Google — use the page above for that.

Revoking does not undo deletions. Likes and comments the app removed are gone from YouTube and cannot be restored by Comment Sweep or by removing its access.

Deleting your data

There is no server-side data to delete, so there is nothing to request from us and no waiting period. To remove everything the app has kept locally:

• In the app: open the account menu at the top of the home screen and choose Clear local data. It names what it is about to remove, asks you to confirm, then re-reads the store and tells you whether anything is left. This removes the five values above and nothing else; it does not sign you out and it changes nothing on YouTube.
• Both platforms: uninstalling Comment Sweep removes the five stored values above along with the app.
• Android: if you want to keep the app but clear it, the system app settings for Comment Sweep can clear its storage too. The exact menu wording differs between Android versions and manufacturers, but it is under the app's own entry in Settings.
• iOS: iOS has no per-app “clear storage” button, so use the in-app button above, or delete the app.

Changes to this policy

This policy may be updated from time to time — for example when the app changes, or when Google changes what its API offers or what it asks this page to say. The current version is always the one on this page, and the date at the top says when it last changed. Continuing to use the app after a change means the updated policy applies.

Descriptions on this page explain how the app works in general terms; they are not a technical specification and are not a guarantee of any particular implementation. A change that widened what the app can reach would also mean a new Google consent screen, which you would have to accept.

Contact

ahmed@naseeh.io