Vivies Toolkit for Instagram
Privacy Policy
Data Collection
The developer does not collect, store, transmit, or share user data with any developer-owned external server. Vivies Toolkit for Instagram processes the Instagram information needed for its user-facing features locally inside the browser.
Locally processed information may include Instagram usernames and profile metadata, followers and following lists, posts, stories, highlights, media URLs, post likers, story viewers, favorites, story alarms, and the signed-in account context. Preferences such as theme, language, module states, and locally generated cache data may be stored on the device with Chrome's storage API.
The extension does not use third-party analytics, advertising, telemetry, fingerprinting, or data broker services.
How It Works
The extension works with the Instagram session already signed in through Chrome. When the user opens a feature, it requests the required data directly from Instagram/Meta over HTTPS and processes the response locally. The developer does not operate a backend for these requests and cannot access the resulting data.
Downloader actions run only when initiated by the user. Insights analysis runs when initiated from the native side panel. Story alarm checks run locally on the schedule configured by the user.
Network Requests
The extension communicates only with the following Instagram/Meta domains required for its features:
www.instagram.com: Profile, story, highlight, search, feed, page integration, and authenticated web API operations.
i.instagram.com: Instagram API endpoints used for followers, following, posts, likers, stories, and related account analysis.
cdninstagram.com: Profile pictures and media assets delivered by Instagram's CDN.
fbcdn.net: Media assets delivered by Meta/Facebook CDN subdomains.
No request or response data is sent to developer-owned servers or to analytics, advertising, telemetry, or data broker services.
Authentication Information
The extension reads Instagram's csrftoken cookie only when needed to make authenticated requests to Instagram endpoints for user-requested features. The token is not sent to the developer, shared with another service, or stored in extension storage.
Third-Party Services
Instagram and Meta provide the website, APIs, and media CDN used by the extension. Data sent to those services is governed by the user's existing relationship with Instagram/Meta and their applicable policies. The extension does not integrate any additional third-party analytics, advertising, tracking, telemetry, or data broker service.
Permissions
The extension requires the following permissions, each used only for the stated purpose:
storage: Store module states, local caches, story favorites, story alarms, in-panel alerts, seen history, theme, language, and other preferences on the device.
downloads: Save media only after the user explicitly chooses a download action.
alarms: Schedule local checks for user-configured story alarms.
cookies: Read Instagram's csrftoken for authenticated requests made directly to Instagram.
declarativeNetRequest: Enable or disable the bundled local rule that blocks Instagram story seen/receipt requests while the Story Viewer protection feature is enabled.
sidePanel: Provide the toolkit interface in Chrome's native side panel and open it after a user action.
https://www.instagram.com/*: Run the Instagram page integration and access required Instagram web endpoints.
https://i.instagram.com/*: Access Instagram API endpoints required by Insights and Story Viewer.
https://*.cdninstagram.com/*: Load and download Instagram CDN media selected by the user.
https://*.fbcdn.net/*: Load and download Meta/Facebook CDN media selected by the user.
Local Storage
All extension-managed data remains on the user's device. Local storage may include:
Followers and Following: Usernames, IDs, and available profile metadata used for Insights.
Posts and Interactions: Recent post metadata, shortcodes, thumbnails, and liker mappings.
Story and Highlight Data: Active story/highlight metadata and viewer-related results used by the requested feature.
Story Viewer State: Favorites, alarms, in-panel alerts, and seen history.
Preferences: Theme, language, and module enable/disable settings.
Signed-in User Context: Locally cached account information used to run features efficiently.
Data Retention
Locally stored data remains on the device until the user:
Uninstalls the extension, which causes Chrome to remove extension storage.
Clears extension or browser storage manually.
Refreshes, removes, or overwrites cached data through extension features.
User Control
Users can:
Enable or disable the Stories, Insights, and Downloader modules.
Choose when to run analysis or download actions.
Remove favorites and story alarms from the interface.
Delete all locally stored extension data by uninstalling the extension or clearing extension storage.
Limited Use Disclosure
The use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
User data is used only to provide or improve the toolkit's clearly described Instagram features.
User data is not sold or transferred for advertising, creditworthiness, lending, or unrelated purposes.
User data is not used for personalized advertising or retargeting.
The developer does not permit humans to read user data, except if the user provides specific data voluntarily for support or when otherwise required by law.
Changes to This Policy
If this policy changes, the updated text and revision date will be published before any new data practice begins.
Disclaimer
Vivies Toolkit for Instagram is not affiliated with, endorsed by, or sponsored by Instagram or Meta Platforms, Inc.