Privacy information for SaveMingo.

SaveMingo processes URLs that you submit so it can validate the platform, resolve supported public media, and prepare delivery. For X / Twitter, if X's public syndication response cannot expose an otherwise public post's media, SaveMingo may send that public post reference to a bounded external fallback resolver. Facebook copied-share and fb.watch links are not processed by a browser fallback; use the full public Facebook Reel or video URL instead. For TikTok, if the normal resolution or media-delivery path fails, SaveMingo may send the public TikTok URL to a bounded external fallback resolver to obtain another public media source. The first fallback runs from your browser. A video-only secondary fallback may run through SaveMingo only after the earlier video paths fail; known photo and slideshow content is not sent to that video-only path. These fallbacks are used only when needed. Do not submit passwords, cookies, private credentials, or other sensitive authentication material.

Operational diagnostics can include request IDs, platform/provider information, normalized error codes, timing, media counts, upstream host/status information, and other limited technical signals needed to diagnose reliability.

The application is designed not to log social-platform passwords, authentication cookies, or complete signed media URLs as routine operational fields.

The current media-delivery route is designed to stream resolved media rather than intentionally keep a permanent copy on SaveMingo servers. Processing paths that use temporary files are expected to clean those files up after the operation.

SaveMingo uses analytics to measure page visits and product events such as paste actions, resolve attempts, resolve outcomes, download intent, and whether the delivery preflight was ready or failed.

SaveMingo does not intentionally send pasted source URLs, signed media URLs, request IDs, passwords, cookies, or secrets as analytics event parameters.