Privacy Policy

2. Submitted Links and Media Processing

When you paste a link into the downloader input field:

• Link Validation: The submitted URL is checked to ensure it points to a recognized public video format on a supported platform. Unsupported domains or malformed links are rejected immediately.
• URL Handling: The submitted link is processed in server memory to identify the target post and extract relevant video identifiers (such as a video ID or shortcode). While internal logs and public candidate previews use sanitized URLs that omit query strings, DownMigo does not promise that every tracking or query parameter is stripped prior to upstream extraction. Certain platform endpoints require specific query parameters (such as video watch identifiers) to resolve the requested media.
• Temporary In-Memory Processing: Submitted URLs and resulting stream metadata are held in temporary server memory only for the brief period needed to generate a temporary download ticket.

3. Media Delivery Paths and Network Visibility

Media downloads are delivered using different technical paths depending on the source platform and stream structure:

• Direct CDN Delivery: For eligible Facebook, Instagram, and TikTok streams, download links redirect your browser directly to the content delivery network (CDN) operated by the hosting platform (such as Meta or ByteDance CDNs). In this path, your browser connects directly to the third-party CDN, meaning the third-party CDN server observes your IP address and standard HTTP request headers.
• Gateway Proxy Streaming: When direct browser access is restricted or format negotiation is required, the media stream is proxied through our gateway to your browser. In this mode, DownMigo's server connects to the upstream provider, meaning the upstream server observes our gateway server's network address rather than your personal IP address.
• Temporary YouTube Preparation: Certain high-resolution YouTube video streams store video and audio as separate tracks. To deliver a standard, playable MP4 file, our server temporarily downloads and merges the separate tracks into a unified file. The prepared file is stored temporarily on local disk and is cleaned up shortly after transfer completion or upon ticket expiration.

Similarly, when your browser displays video thumbnails or preview images hosted directly on third-party CDNs, your browser makes direct requests to those external hosts, exposing your IP address to them under their respective privacy practices.

4. Operational Records and Server Telemetry

To monitor service health, analyze bandwidth usage, protect against automated abuse, and troubleshoot technical errors, our gateway records structured operational events in a database.

These technical records include:

• Platform name (such as Facebook, Instagram, TikTok, or YouTube).
• Public video identifier (such as the numeric ID or shortcode extracted from the link).
• Requested quality or resolution label (such as HD, SD, 720p, or MP4).
• Event type (such as link extraction request, extraction success or failure, download ticket issuance, stream start, transfer completion, cancellation, or error).
• Measured transfer metrics where applicable (duration in milliseconds and total byte count transferred during gateway proxy streams).
• Error code or status code if an extraction or transfer fails.
• Cryptographic hash of the client IP address (used for rate limiting and diagnostic pattern analysis; we do not store raw IP addresses in general operational event logs).
• Server timestamp of the event.

Important operational distinctions:

• Direct Redirects: When a download link redirects your browser directly to an external CDN, DownMigo records the redirect event, but does not measure whether your browser successfully completed the file transfer or how many total bytes were downloaded.
• YouTube Preparation: The completion of internal stream preparation on our server is distinct from the browser download itself. A prepared file may be generated even if a client disconnects before downloading the file.

Because these records are necessary for infrastructure capacity planning and troubleshooting, we do not claim that operations are completely unlogged or fully anonymous. However, these technical event records are not linked to individual user profiles or personal identities.

5. Cookies and Browser Storage

DownMigo minimizes browser-side persistence:

• Public Visitors: The public website does not issue tracking cookies, persistent advertising identifiers, or account login cookies to visitors.
• Administrative Authentication: Authorized administrators who sign in to the administrative panel receive a secure, encrypted session cookie to authenticate administrative requests. This cookie is never issued to public visitors.
• Local Session Storage: When advertising preview features are enabled, the website uses browser sessionStorage solely to remember if you dismissed the bottom advertisement preview banner. This value is stored only for your active browser session, expires when you close your browser tab, and is never transmitted to external servers or used for cross-site tracking.
• In-Memory Client State: Extraction results and current download selections are maintained temporarily in browser memory while you navigate the site and are cleared upon page refresh.

6. Advertising and Third-Party Partners

DownMigo includes an administrative advertising management system. Depending on runtime configuration, advertising may be set to OFF, Preview (simulated local banners), or Live integration:

• Local Preview Mode: When in preview mode, all banner and overlay demonstrations are inert, local simulations. They do not load external advertising scripts, connect to Google ad servers, or send data to third parties.
• Live Advertising Mode: If live advertising is activated by the site administrator, DownMigo integrates with Google AdSense (including Auto ads and manual display placements). In live mode, Google and its advertising partners may use cookies, device identifiers, and IP addresses to serve advertisements, evaluate ad performance, cap ad frequency, and detect invalid traffic.

To learn more about how Google collects and processes information when you visit sites that partner with Google, please review Google's official partner privacy disclosure at https://policies.google.com/technologies/partner-sites.

DownMigo does not claim that continued use of the website alone constitutes valid consent for advertising or tracking where affirmative consent is required by law. When live advertising is enabled in jurisdictions requiring user consent:

• European Economic Area (EEA), United Kingdom, and Switzerland: Google requires publishers serving ads to visitors in these jurisdictions to implement a Google-certified Consent Management Platform (CMP) that integrates with the IAB Europe Transparency and Consent Framework (TCF v2.3, following the industry transition from TCF v2.2). Under these standards, personal data for ad personalization and measurement is only processed when valid consent or legitimate interest signals are recorded by the CMP.
• United States State Privacy Regulations: Separate statutory frameworks and opt-out mechanisms (such as those in California, Virginia, Colorado, Connecticut, Utah, and other applicable states) govern opt-out rights for targeted advertising, rather than the European TCF. TCF certification is not a universal requirement across every jurisdiction globally.
• Pending Implementation Notice: DownMigo's live advertising consent management integration remains pending, and no CMP is currently active on the site. Updating this policy wording does not implement a CMP or establish regulatory compliance. Live advertising remains dormant until required consent controls are formally deployed.

7. Contact Form Submissions

If you choose to submit an inquiry through our Contact page, the following information is stored in our database:

• Your name (up to 120 characters).
• Your email address (up to 255 characters).
• Selected inquiry category (such as Download Issue, Feedback, Privacy Inquiry, or Other).
• Optional post or video URL provided for debugging purposes (up to 500 characters).
• The text of your message (between 5 and 3,000 characters).
• A cryptographic SHA-256 hash of your client IP address (used to prevent automated spam and rate-limit submissions).
• Submission timestamp and read status.

Contact messages are stored for the site administrator to review and address inquiries. We do not sell or share contact details with third-party marketing companies. Please do not submit account passwords, session cookies, or private credentials through the contact form.

8. Data Retention and Storage Practices

DownMigo maintains distinct retention handling across different categories of operational data:

• Temporary Media and Download Tickets: Download tickets held in memory are temporary and expire automatically after 5 minutes. Temporary video and audio files generated during YouTube preparation are automatically removed from disk shortly after transfer completion (within a 60-second grace window) or upon ticket expiration.
• Operational Telemetry Records: Structured event logs (such as extraction outcomes, transfer durations, and error codes) are stored in the database for infrastructure monitoring, bandwidth tracking, and error diagnostics. There is currently no automated expiration or scheduled purge mechanism for these operational records.
• Contact Messages: Inquiries submitted through the contact form are stored in the database for administrative review and ongoing support. There is currently no automated deletion schedule for contact records.
• Administrative Sessions: Active administrator sessions expire automatically based on predefined expiration timestamps and are immediately revoked upon logout or password modification.

The short 5-minute ticket lifetime applies exclusively to in-memory download tickets and temporary prepared media files. It does not apply to database operational event logs or contact form submissions.

9. Privacy Inquiries and Questions

If you have questions regarding this Privacy Policy, wish to inquire about contact messages you previously submitted, or have other privacy-related questions, please contact us via our Contact page and select the category "Privacy Inquiry".