ReelCove Privacy Policy

1. About ReelCove

ReelCove helps a user save a currently visible video from a supported social website when the page exposes a direct downloadable HTTP or HTTPS media file.

ReelCove is intended only for videos the user owns or is authorized to download. It does not bypass private accounts, login restrictions, paywalls, download settings, regional restrictions, encryption, or digital-rights-management controls.

2. Information ReelCove may process

On supported social-media pages, ReelCove may temporarily process:

• The current website hostname and page address
• The currently visible video element and its direct media address, when exposed by the page
• Limited page metadata such as the platform name, creator label, post title, and post identifier
• For a selected Reddit, Instagram, TikTok, Facebook, or 9GAG post, matching post data requested from that same service after the user clicks Download
• For Instagram/TikTok/Facebook/9GAG, response headers and at most the beginning of each item in a short selected media-candidate list requested with the byte range 0-4095 to reject HTML, images, expired links, or invalid files before creating a download
• Video source type information used to choose a file extension
• The user’s download and filename preferences
• A count of successful downloads used only to control an optional local support reminder

This information is processed to identify the selected video, construct a safe filename, and start the user-requested Chrome download.

3. Information ReelCove does not intentionally collect

• Passwords or authentication credentials
• Cookies or authentication tokens
• Private messages, comments, email content, or form entries
• Payment-card or financial information
• A persistent browsing history
• Complete webpage text unrelated to the current video
• Precise location, health, or biometric information
• Network request or response bodies unrelated to the selected post refresh and bounded media validation described in this policy

4. Direct downloads and technical limits

ReelCove starts downloads only after a user action. It passes a direct HTTP or HTTPS video address to Chrome’s downloads system.

For an indirect Instagram, TikTok, Facebook, 9GAG, or LinkedIn candidate, ReelCove may first refresh the exact selected post on that platform. LinkedIn uses only a matching embedded or refreshed activity download address, a direct player source, or a current activity-scoped media resource on licdn.com carrying video evidence. For Instagram, TikTok, Facebook, and 9GAG, ReelCove requests only bytes 0–4095 from a short candidate list on the selected platform media host. It uses response headers or a short file signature to skip HTML, images, expired, or otherwise invalid candidates, then cancels each probe stream. LinkedIn signed media is refreshed at click time without signed-media cache reuse, checked locally for a known expiry, and passed directly to Chrome. ReelCove does not buffer the complete video.

ReelCove does not intercept network traffic, reconstruct segmented audio or video, decrypt media, or convert protected browser streams. Videos delivered only through blob URLs, MediaSource, segmented streaming, or protected delivery may be unavailable.

5. Local storage

ReelCove stores settings locally in the Chrome profile, including whether the in-page button is enabled, save-location preference, filename style, enabled platforms, the one-time permission acknowledgement, successful-download count, and support-reminder timing.

ReelCove does not operate a cloud account, synchronization server, or remote video library.

6. Data sharing and external transmission

ReelCove does not sell, rent, share, or transmit social-media page information, direct video addresses, download activity, or settings to advertisers, data brokers, analytics providers, or developer-operated servers.

The extension does not use analytics services, advertising networks, tracking pixels, remote logging, externally hosted executable code, or an external video-resolution service.

When the selected player does not expose a reliable direct file, ReelCove may refresh only the matching post on Reddit, Instagram, TikTok, Facebook, 9GAG, or LinkedIn. For Instagram/TikTok/Facebook/9GAG it may also make the bounded media-validation requests described above to that platform’s selected media CDN. LinkedIn media is handed directly to Chrome after refresh and local expiry checks. ReelCove does not read or store cookies; Chrome may attach the user’s existing service session context. These requests are not sent to the developer or a third-party resolver, and ReelCove does not proxy the complete video.

7. Browser permissions

• activeTab: Allows the toolbar popup to communicate with the supported page the user is actively viewing.
• downloads: Starts and monitors a download after an explicit user action and can open the default Downloads folder.
• storage: Stores local extension preferences and counters.
• Supported-site and named media-host access: Identifies the visible video, reads a direct media address when exposed, displays the download button, derives limited filename metadata, refreshes the exact selected Reddit/Instagram/TikTok/Facebook/9GAG/LinkedIn post when necessary, performs bounded Instagram/TikTok/Facebook/9GAG media validation, and hands refreshed LinkedIn signed media directly to Chrome.

8. Buy Me a Coffee

ReelCove may display an optional link to support independent development through Buy Me a Coffee. ReelCove does not contact or load content from that service automatically. The connection occurs only after the user explicitly opens the support link, after which the external service’s own terms and privacy policy apply.

9. Retention and deletion

Local settings remain until the user resets extension data or removes ReelCove. Because ReelCove does not maintain a developer-operated account or remote database, there is no separate online ReelCove record to delete.

10. Security

ReelCove reduces external exposure by processing data locally and avoiding developer-operated media servers. No local system can guarantee absolute security, and a person with access to an unlocked Chrome profile may be able to view locally stored settings.

11. Children’s privacy

ReelCove is not specifically directed toward children and does not knowingly collect children’s information through a developer-operated server.

12. Chrome Web Store Limited Use disclosure

ReelCove’s use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including Limited Use requirements. Information is used only to provide or improve the disclosed, user-facing video-download function and is not used for advertising or unrelated profiling.

13. Changes

This Privacy Policy may be updated when ReelCove’s functionality, data practices, or legal obligations change. The dates at the top of this page will be revised when material changes are published.

14. Contact

Questions can be sent to tahaemredemirkol@gmail.com.