Data InstaDown handles
When you use InstaDown on Instagram, the extension may process the current Instagram URL, visible creator username, shortcode or media ID, surface such as Feed, Reels, Stories, Highlights, or a profile section, media type, carousel position, source publication date when supplied, Instagram-hosted thumbnail or media URL, and metadata Instagram returns for media you select or ask InstaDown to discover from a profile you can view.
Persistent local records can include profile selections and the selected 25, 50, or 100 item discovery limit; queue identity, status, generated filename, thumbnail and resolved media URLs, Chrome download ID, byte progress, pause or retry state, errors, and timestamps; compact completed-media history; and folder and filename preferences.
InstaDown does not ask for, read, or store your Instagram password. Chrome sends required requests directly to Instagram using the Instagram session already present in your browser. InstaDown does not read or retain authentication cookies.
How data is used
Each request is bound locally to creator, shortcode or media ID, surface, and carousel position. The fetched file is checked by media ID or shortcode, expected media type, and carousel position. If Instagram supplies a different owner username than the page showed, InstaDown keeps the verified file and uses Instagram's owner for the save path. Surface remains queue context and is not claimed as a separate property proved by a CDN file. Data is also used to maintain the background queue, monitor progress, organize filenames for Chrome Save As or inside a zip, use source dates when supplied, skip completed stable media IDs, pace profile discovery, honor 429 cooldowns, and retrieve the selected media file.
Where data goes
InstaDown has no developer-operated server. It does not transmit page data, media, settings, queue records, selections, history, or usage information to the developer. Necessary HTTPS requests go only to Instagram domains (www.instagram.com and i.instagram.com). After you add an item to the queue, InstaDown retrieves that file over HTTPS from an Instagram/Meta media-delivery domain (*.cdninstagram.com or *.fbcdn.net). Chrome asks where to save one file or one zip. File bytes may be prepared through a local offscreen document and are not copied into extension storage.
Data is transferred only to Chrome and Instagram/Meta as necessary to provide the feature you request. InstaDown does not sell personal data, use it for advertising or analytics, share it with data brokers, or transfer it for unrelated purposes. It contains no analytics or tracking SDK.
InstaDown's use and transfer of information complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Data is used only to provide or improve the requested user-facing feature.
Storage and retention
chrome.storage.local retains preferences, profile selections, discovery limit, queue pause or cooldown state, queue records, and compact skip history on your device. Queue records, including thumbnail and resolved media URLs, can remain after completion, failure, or cancellation so status, retry, and restart reconciliation work. Applicable completed records remain until cleared; older terminal records are pruned at the queue cap; failed or cancelled items may remain until retried or pruned; and all extension records are removed when extension data is cleared or InstaDown is uninstalled.
Compact skip history is capped at 2,000 entries made from verified media ID, carousel position, media type, and completion time, not temporary CDN URLs. Downloaded files remain where Chrome asked you to save them until you delete them.
If Chrome restarts after creating a download but before InstaDown can persist its assigned download ID, InstaDown may inspect at most 20 recent filename/time candidates locally and compare candidate URL and start time. It attaches only an exact match to the extension-created queue record. Candidate details are not stored as new queue items, and unrelated downloads are never changed.
Permissions
downloadsstarts Chrome Save As for one file or one zip, recovers an extension-created queue item by its own download ID, infers the Chrome Downloads folder so the popup can show a full save path, pauses, resumes, or cancels those extension-created items, and reveals an already-saved location in File Explorer. Unrelated downloads are never changed.storagestores the local records described above.alarmswakes delayed queue work after a scheduled retry or Instagram rate-limit cooldown. It is not used for tracking or unrelated periodic activity.offscreenprepares media bytes or a zip in an isolated page. It does not start Chrome downloads. Chrome then asks where to save.www.instagram.comsupplies visible controls and Feed, Reel, Story, Highlight, carousel, and profile context.i.instagram.comsupplies metadata for selected media and user-requested, rate-limited profile discovery.*.cdninstagram.comand*.fbcdn.netretrieve the exact photo or video file you queued so Chrome can save it or InstaDown can pack it into a zip.
Security
InstaDown uses HTTPS. All executable code is bundled with the extension; no remote code is downloaded or executed. Media downloads are limited to HTTPS Instagram/Meta delivery hosts.
Your choices
You can pause or resume the queue, cancel extension-created downloads, retry failed or cancelled items, clear applicable completed records, use Open folder or Copy path, remove profile selections, clear Chrome extension data, disable InstaDown, or uninstall it. You control downloaded files through Chrome and your operating system.
Children and policy changes
InstaDown is not directed to children under 13 and does not knowingly collect information from children. If this policy changes materially, this page and the Chrome Web Store disclosures will be updated before the new practice takes effect.
Contact
Publisher: GilCoupons. For privacy questions, email airbnbrbt@gmail.com. For product help, visit InstaDown support.
InstaDown is independent and is not affiliated with or endorsed by Instagram or Meta.