logo-tikgo.me

Privacy Policy

Effective date

March 15, 2026

Last updated

March 15, 2026

TikGo is a browser-based downloader for public TikTok, Douyin, Facebook, Instagram, and X links. This policy explains what data we process to run the service, why we process it, how long we keep it, and what choices you have.

1) Scope

This policy applies to TikGo pages and downloader flows, including:

This policy covers how TikGo handles data on its own service. It does not replace the privacy policies of TikTok, Douyin, Facebook, Instagram, X, or other upstream platforms whose public URLs users may paste into TikGo.

TikGo operates independently and is not affiliated with TikTok, Douyin, Facebook, Instagram, or X.

2) Core principles

  • Data minimization: We try to process only what is needed to run the downloader, protect the service, and respond to support requests.
  • Session-based processing: TikGo is designed to process a request and return available download options, not to act as a long-term media library for users.
  • Transparency: We try to explain what data is used for security, troubleshooting, and product operations in plain language.
  • No sale of personal data: TikGo does not sell personal data.

3) Data we may process

3.1 Public link and request data

When you use TikGo, we may process:

  • the public post URL you submit
  • the TikGo page or flow you used
  • basic request metadata needed to generate a response

This data is used to fetch available media options and return the result for that session.

3.2 Technical and security data

To keep the service reliable and reduce abuse, we may process:

  • IP address
  • browser and device details
  • HTTP headers commonly available to web services
  • region or network-level diagnostics
  • error codes, response timing, and stability logs

This information helps with rate limiting, spam and DDoS protection, compatibility debugging, and operational troubleshooting.

If TikGo uses CDN, proxy, hosting, or security providers, those systems may also process standard connection data as part of delivering the service.

3.3 Session, cookie, and browser-storage data

TikGo may use cookies or browser storage for:

  • CSRF protection
  • short-lived access or workflow tickets
  • essential session continuity
  • language or interface preferences
  • limited operational measurement or advertising support, where applicable

You can block or clear cookies in your browser, but some parts of the service may work less reliably if security or session storage is disabled.

3.4 Support and contact information

If you contact us, we may process the information you choose to send, such as:

  • your email address or chat handle
  • the public link you need help with
  • device or browser details
  • screenshots or issue descriptions

We use that information only to review, reply to, and document the support request.

4) Why we process data

TikGo may process data to:

  • return download options for a public link
  • protect the service from abuse or overload
  • diagnose failed requests and compatibility issues
  • improve clarity in support, policy, and help content
  • answer copyright, privacy, or technical inquiries

We do not need a user account for standard downloader flows, and we do not operate TikGo as a personal cloud storage service.

5) Data retention

Retention can vary by system and incident type, but our current operating direction is:

  • Short-lived downloader/session data: kept only as long as needed to complete the request or related short-term workflow
  • Technical logs and diagnostics: typically retained for up to 7 days, then deleted, rotated, or anonymized where practical
  • Support messages: retained only as long as needed to review the request, respond, and keep a minimal support record

Some third-party infrastructure providers may keep their own logs under their own retention policies.

6) Third parties and service providers

TikGo may rely on third parties for functions such as:

  • hosting
  • CDN or proxy delivery
  • security and DDoS protection
  • analytics or operational monitoring
  • forms, communications, or advertising support

These providers only receive the data reasonably needed to perform their role. Their handling of data may also be governed by their own service terms and privacy policies.

7) What TikGo does not promise

To keep this policy accurate, it is important to be clear about limits:

  • TikGo does not promise that every public link will always remain available.
  • TikGo does not promise that every request can be tied back to a named user, especially when logs are short-lived or anonymized.
  • TikGo does not promise permanent storage of downloaded media.

For product-flow details, see /how-it-works.

8) Security and service protection

TikGo uses practical security controls such as:

  • HTTPS delivery
  • CSRF protection
  • short-lived request or access tickets
  • rate limiting
  • abuse detection and operational review

To protect availability for normal users, TikGo may temporarily restrict, hide, delay, or reject certain requests during high load, abuse events, or provider-side instability.

9) Your choices

You can:

  • stop using the service at any time
  • clear cookies or use private browsing
  • contact us to ask privacy or support questions
  • avoid sending extra personal data when contacting support unless it is relevant to the issue

Because TikGo is designed around short-lived processing and limited logging, we may not always be able to retrieve or isolate a specific historical request after the retention window has passed.

10) Children's privacy

TikGo is not intended for children. If you believe a child has sent us personal information through a support or contact flow, please contact us so we can review and take appropriate action.

11) Policy changes

We may update this policy when the service changes, when we improve documentation, or when legal and operational requirements change. Material wording updates may also be reflected in /changelog.

12) Contact

For privacy questions, support, or policy clarifications, contact us through /contact or use one of these channels:

Related pages: