Contact

Support availability

Before you write

A few things solve themselves. If a lookup says a capability is unavailable, that is the product being honest about a source it cannot verify yet, not an error on your side; the tool page explains the limitation. If you hit a browse limit, the page shows when it resets. If a saved profile is missing on another device, check whether it was saved as a guest, which lives only in that browser, or in your account after sign-in.

If an export contains fewer rows than the platform count under the video, read the scope report first. Reported and retrieved counts answer different questions, and the guide on why comment counts differ walks through every case. Most questions about exports are answered there.

What to include

Tell us what you tried, what you expected and what happened instead. Include the visible error code or request ID shown on the page, the approximate time, and the browser and device you used. For an export, include the GlimTok job ID from the job page. For a saved-profile question, say whether you were signed in.

Do not send passwords, session cookies, Google tokens, API keys, private notes or entire comment exports. We never need them, and we would rather not hold them. A link to the public profile or video you were looking at is enough.

Account questions

Most account controls are already in your hands. Saved profiles can be removed from the Saved page, one at a time or in bulk. Sign-out for this device or all devices is in Settings. Account deletion is in Settings too and requires a fresh Google verification, so that returning from a sign-in page or holding an old session can never be mistaken for consent.

If deletion reports that a subscription cancellation is still pending, that means the payment provider could not confirm it at the time; your private data was still removed, and the status can be checked from the receipt shown on the page. Write to us if that status does not resolve.

Export and billing questions

Every export is quoted before it runs, and the confirmation names the credit ceiling you approved. If a job stopped earlier than you expected, the stop reason in the scope report says why, and unused reserved credits are released automatically. If you believe credits were settled for requests that failed, send the job ID and we will check the ledger.

Live billing is disabled in this release, so there are no charges to dispute yet. When it is enabled, checkout will show renewal, cancellation and refund terms, and the billing portal will handle subscription changes.

Creators and content concerns

GlimTok shows public content as a supported source returns it and does not host it. If you are a creator and have a concern about how your public profile, video or comments appear here, or you believe content shown through GlimTok infringes your rights, send the link, describe your relationship to the content and say what you would like to happen. Requests are reviewed against what GlimTok actually stores, which is limited to users’ private saved snapshots and temporary export rows that expire after 72 hours.

Privacy requests

To ask what GlimTok holds about your account, or to request deletion, use Settings first; it is faster and requires no email. For anything Settings cannot do, write with the email address of your GlimTok account. We will verify that the request comes from that account before acting on it. The Privacy page describes retention periods in full.

Feedback and suggestions

If a page was unclear, a limit surprised you or a guide answered the wrong question, say so. Short notes are welcome. Tell us what you were trying to do and where the product or the guides fell short, and if you have a use case the tools do not cover yet, describe it in a sentence or two. Requests are read with the same rules the product follows: public content only, nothing automatic and nothing that reaches into private accounts.

Security reports

If you have found a security issue, tell us before telling anyone else, and include enough detail to reproduce it. Do not access other users’ data to demonstrate a problem. We take reports seriously, will confirm receipt, and will not pursue good-faith researchers who follow these rules.

Reporting a problem with a lookup

If a public profile or video will not resolve, first check the input. Usernames use letters, numbers, periods and underscores, and links must be HTTPS links on a tiktok.com domain. A short link from the share sheet may be declined until redirect handling is verified; paste the full link instead. If the input is right and the page reports a source error, wait a little and try again before writing. If it fails repeatedly, send the exact input, the error code shown and the time, and say which tool you used.

Quick answers

What we will never ask for

A TikTok or media-source failure never requires you to supply a TikTok login. GlimTok will never ask for your TikTok password, a verification code, a Google password or a payment card by email. If a message claiming to be from GlimTok asks for any of these, it is not from us.