Asharaአሻራ
Browser Extension · Legal & Compliance

Ashara TikTok Collector

የግላዊነት ፖሊሲ

Effective Date: 28 October 2026 • Last Updated: 21 November 2026 • Extension Version: 0.4.0

Scope of this policy: This page covers only the Ashara TikTok Collector browser extension (currently distributed for Microsoft Edge). It does not replace or modify the Ashara website Privacy Policy, which continues to apply to the ashara.com.et website and platform services.

1. Operator Identity

This extension is developed and operated by Ashara, a digital marketing analytics service based at Bole, Addis Ababa, Ethiopia. Contact: ykebed40@gmail.com — see Section 10 for the full contact block.

The extension is designed for internal use by Ashara team members and authorized clients for digital marketing prospect research. It is not a consumer product for general public download.

2. Information Accessed and Captured

The extension reads only publicly visible information from TikTok profile and video pages. It never reads private messages, draft content, authenticated account data, or any information that is not visible to a logged-out visitor.

Profile-page fields

  • username — the @handle shown in the URL and page heading
  • displayName — the public display name shown below the avatar
  • profileUrl — canonical TikTok profile URL
  • bio — public biography text
  • bioLink — external URL in the bio, if present and public
  • isVerified — presence of TikTok's verification badge
  • followers, following, totalLikes, totalVideoCount — public engagement counters shown on the profile page
  • capturedAt — timestamp when the extension read the page (set by the extension, not TikTok)
  • pageUrl — the TikTok URL that was open

Video-page fields

  • videoId, videoUrl — TikTok video identifier and link
  • ownerUsername — @handle of the account that posted the video
  • caption — public text description of the video
  • displayedDate, publishedAt — publication date shown publicly on TikTok
  • isPinned — whether the video is pinned to the top of the profile
  • views, likes, comments, shares, saves — public engagement counters
  • hashtags, durationSeconds, sound — the video's hashtags, length and the title of its sound, as shown publicly
  • detailSource — where the numbers came from (page data, page text or profile grid), so reports can show how reliable they are
  • topComments — a sample of public comment text; see "Comment sample" below
  • capturedAt, pageUrl, pageType — metadata added by the extension

Session metadata (stored with each capture)

  • captureId, captureStartedAt, captureEndedAt
  • collectionMode (basic / video-detail / deep), status, stopReason
  • visitedPages (list of TikTok URLs visited during the session)
  • limitations and warnings recorded during extraction
  • pageData — whether per-video details were read automatically, and if not, why

Comment sample (video captures only)

When the user captures a single video whose comments are open on the page, the extension keeps up to 20 of the most-liked public comments: the comment text and its like and reply counts only. It does not keep the commenter's username, display name, user ID or profile picture, and @mentions inside the text are replaced with "@…". The purpose is to show a business what its audience asks about (for example prices or locations), not to profile individual commenters. Comment text can still contain personal details that a commenter chose to write publicly; users should not use the sample to identify or contact individuals.

Note on personal information: Public usernames and display names can identify real individuals, including the owners of the TikTok profiles being captured — not just the person operating the extension. This policy applies to data about those captured-profile owners as well.

3. How Collection Works

User-triggered only

No data is extracted automatically. All collection begins only when the user clicks a button in the extension popup ("Extract account data", "Capture this video", or "Collect more videos"). The extension's content script is injected into TikTok pages when they load (which is required for it to be ready), but it performs no extraction until it receives an explicit instruction from the background service worker in response to a user action.

Profile capture (basic mode)

When the user is on a TikTok profile page (@username) and clicks "Extract account data", the extension reads the profile fields and the video cards currently rendered in the DOM. Only videos already loaded on screen at that moment are captured.

Video detail capture

When on a single video page, clicking "Capture video" extracts that video's statistics and associates them with any existing session for the same account.

Deep collection (bounded scroll)

"Collect more videos" triggers a bounded scroll loop on the profile page, capped at 30 videos and 45 seconds. The extension performs smooth scroll steps (900 px each, with ~1.4 s pauses) and reads newly rendered video cards. It stops when: the video or time limit is reached, no new cards appear after three consecutive attempts, the user clicks Stop, or TikTok shows a CAPTCHA or login prompt.

No background activity between sessions

The extension uses a Manifest V3 service worker, which the browser shuts down when inactive. No data is collected while the popup is closed. The service worker wakes up only to handle popup messages.

Data source: public TikTok page content only

The extension reads visible DOM elements and page-embedded JSON hydration data (__UNIVERSAL_DATA_FOR_REHYDRATION__/SIGI_STATE) that TikTok already delivers to all page visitors. From version 0.3.0 it also reads the video-list and comment responses that the TikTok page itself requests while the user browses or scrolls, keeping only the fields listed above. It does not make any additional API calls to TikTok or any other server, and it does not change what TikTok sends. If TikTok changes these responses and the extension cannot read them, the capture says so and falls back to the visible page.

4. Storage and Retention

Browser local storage (chrome.storage.local)

Captured data is stored exclusively in the browser's local extension storage under these keys: ed_tiktok_capture (the capture on screen), ed_tiktok_captures (up to 20 finished captures, newest first) and ed_popup_lang (the popup language). This storage is local to the device running the extension and is not synced to the browser account or any cloud service. It persists across popup close/reopen until explicitly cleared.

No server storage

The extension does not transmit captured data to any Ashara server, cloud database, or third-party service on its own. Data leaves the device only when the user exports the JSON file, or clicks "Get from extension" on the Ashara dashboard and picks a capture (see section 5).

Retention

Data remains in local storage until the user deletes it in the popup ("Delete this capture", or Delete in the Saved list), or until the extension is uninstalled. Up to 20 finished captures are kept; when a 21st is saved, the oldest is removed.

What deleting a capture does and does not do

Deleting a capture removes it from chrome.storage.local. It does not delete any JSON files the user has already downloaded to their computer, nor does it affect any copies shared externally by the user.

5. Transmission, Sharing, and Third Parties

TikTok page interaction

The extension operates by reading pages already open in the browser. Normal network requests to TikTok are made by the browser itself (not the extension) as a consequence of browsing TikTok. The extension adds no extra network requests to TikTok servers.

JSON export (user-created local file)

When the user clicks "Download JSON file", the extension generates a JSON file from the locally stored capture and downloads it to the user's device using the browser's standard download mechanism. The file is saved locally; where the user subsequently shares or uploads that file is entirely under the user's control.

No extension-initiated uploads

The extension makes no outbound network requests to any server — including Ashara servers — from within the extension itself. Captured data does not leave the browser automatically.

Sending a capture to Ashara (user-initiated)

Only pages on ashara.com.et (and the former ethiodigitals.com.et) can ask the extension for captures. When a signed-in user clicks "Get from extension" on the dashboard, the page receives the list of saved captures (account name, date, number of videos) and, once the user picks one, that capture. The dashboard then sends it to the user's Ashara account exactly as if the JSON file had been uploaded. Nothing is sent without that click.

Website hosting, analytics, and support

Any analytics or tracking tools used on the Ashara website (ashara.com.et) are governed by the website Privacy Policy, not this document. The extension itself installs no trackers.

No advertising, sale, or credit decisions

Captured data is not sold, rented, or licensed to third parties. It is not used for advertising targeting, creditworthiness assessment, or any purpose unrelated to digital marketing prospect research.

No analytics, crash reporting, or third-party SDKs in the extension

The extension contains no analytics libraries, crash-reporting services, telemetry hooks, or third-party SDKs. Its only external dependency at runtime is the browser's own extension APIs (Chrome/Edge WebExtensions).

6. User Controls and Privacy Requests

The following controls are available directly in the extension popup:

  • Start / stop collection: Click the relevant capture button to begin; click Stop at any time to cancel an in-progress deep collection.
  • Preview captured data: The results panel shows a summary of profile and video data before export.
  • Export to JSON: Downloads a JSON file of the current capture to the user's local device.
  • Delete a capture: "Delete this capture" in the popup, or Delete in the Saved list, removes it from extension storage. Does not affect already-downloaded files or captures already sent to Ashara.
  • Uninstall the extension: Removing the extension from the browser deletes all extension storage, including any retained capture.

Requests from captured-profile owners

If you are a TikTok account owner whose public profile data may have been captured by a user of this extension and you want to request information about or deletion of that data, please contact us at ykebed40@gmail.com.

We will respond to verifiable requests. However, because captured data is stored locally on individual users' devices, we cannot guarantee deletion of data that has already been exported to files outside our control.

7. Extension Permissions

The extension requests the following permissions:

storage

Used to persist captured data between popup sessions. Only chrome.storage.local is used (browser-local, not synced).

scripting

The content scripts are declared in the manifest and load with TikTok pages. The scripting API is used only when a TikTok tab was already open before the extension was installed or updated, to add the same scripts to that tab instead of asking the user to reload it.

activeTab

Grants access to the currently active browser tab after a user action (popup open). Used to detect the tab's URL and to send messages to the content script in that tab. Does not grant access to other tabs or browsing history.

Host access: https://www.tiktok.com/*

The extension can read the content of pages at www.tiktok.com. This access is technically broad in scope (covering all TikTok pages) but the extension's code limits its actions to profile (@username) and video (@username/video/ID) page patterns. It does not access TikTok settings, messages, or any authenticated area.

8. Security

  • All TikTok page content is treated as untrusted data and is never executed. Displayed values are HTML-escaped before rendering in the popup.
  • Data is stored in the browser's local storage, which is isolated to the extension and not accessible to web pages or other extensions. The browser enforces this isolation.
  • The extension has no server component and makes no outbound network requests, so there is no server-side attack surface for captured data.
  • The extension does not claim or implement encryption at rest of local storage, as browser extension local storage is already protected by the OS user account. No additional at-rest encryption is applied.

9. Policy Changes

We may update this policy when the extension's data practices change. Updates will be published at this URL (https://www.ashara.com.et/privacy/tiktok-collector) with a revised "Last Updated" date at the top of the page.

If a future update materially expands the categories of data collected, introduces server transmission of captures, or adds new sharing recipients, we will communicate that change through a visible notice in the extension popup or through the Microsoft Edge Add-ons store update description before the change takes effect.

Continued use of the extension after a policy update does not constitute consent to new data practices that materially differ from those described when the extension was first installed. Where applicable law requires affirmative consent for new practices, we will obtain it before those practices begin.

10. Contact Information and Privacy Requests

For questions about this policy, access and deletion requests, or concerns about extension data practices, contact us:

Organization: Ashara

Email: ykebed40@gmail.com

Phone: +251 922 76 15 94 / +251 941 14 88 87

Address: Bole, Addis Ababa, Ethiopia

Website: https://www.ashara.com.et

This policy is specific to the Ashara TikTok Collector browser extension. For the Ashara website and platform privacy policy, see ashara.com.et/privacy.

11. JSON Export Format Reference

When a user exports captured data, the JSON file follows a versioned schema (schemaVersion: "1", source: "browser-extension"). The file contains only the fields listed in Section 2. It includes a unique captureId (randomly generated per session, not linked to any user account), collection timestamps, and the public TikTok data captured during that session.

No user-account identifiers, browser identifiers, or device fingerprints are included in the exported file.