ImgEx does not save, cache, mirror, catalog, or redistribute the images you extract. All image conversions, preview resolutions, and ZIP file creations occur ephemerally in your browser or through stateless streaming buffers. When you close your browser tab, your extracted media session is completely gone.
1. URL Processing & Scraping Mechanism
When you submit a target URL into ImgEx:
- Our serverless extraction runtime initiates a secure HTTP request to the publicly accessible webpage at that URL.
- The HTML document tree and associated public CSS stylesheets are parsed in real time to locate image tags, vector SVGs, and background declarations.
- The extracted URLs and metadata (e.g. alt text, source type) are returned directly to your browser application.
- No target webpage contents, rendered screenshots, or scraped images are saved to a permanent disk or database.
2. Server Logs & Ephemeral Buffering
Like standard web infrastructure, our hosting environment temporarily records transient edge server logs. These logs typically include:
- Timestamp of the request.
- HTTP response status code (e.g. 200 OK, 404 Not Found, 500 Error).
- Response latency in milliseconds.
These logs are used exclusively for real-time security monitoring, DDoS mitigation, and diagnosing server crashes. They are automatically rotated and permanently purged on a short rolling schedule.
3. Cookies & Local Browser Storage (localStorage)
ImgEx does not use third-party advertising cookies or cross-site tracking pixels.
We utilize your browser’s standard localStorage API solely to enhance your local workflow:
- Saved Collection Drafts: If you choose to save an extraction draft, it is stored locally on your device unless you explicitly sign in to sync it.
- User Settings: Custom batch renaming templates (e.g.
[original]_[index]), default compression preferences, and filter configurations. - Dropbox Tokens (Optional): If you provide a Dropbox Personal Access Token, it is held strictly in your local browser storage and never transmitted to our backend servers.
You can clear all saved local data at any time by clearing your browser cookies and site data for imgex.online.
4. Analytics & Tracking Policy
We prioritize visitor privacy. If any basic aggregate analytics are measured (such as total page visits or regional server load distribution), they are strictly anonymized, cookieless, and aggregated. We do not fingerprint visitor devices, sell demographic data, or run behavioral ad-retargeting campaigns.
5. IP Address Handling
When you interact with ImgEx, your IP address is processed in transient volatile RAM by edge routing networks (e.g. Cloudflare / Cloud Run) to securely route HTTP packets back to your browser and prevent malicious volumetric bot attacks. We do not store or associate your IP address with your personal identity or browsing history.
6. Third-Party Services & CORS Image Proxy
Many websites restrict cross-origin image loading via browser CORS (Cross-Origin Resource Sharing) security policies. To allow you to preview and download images from these websites, ImgEx provides a stateless streaming CORS proxy endpoint (/api/proxy-image).
This proxy acts solely as a pass-through pipe: it fetches the binary image stream from the third-party host and immediately flushes it to your browser with appropriate CORS headers. The proxy does not save the image to disk or keep persistent records of individual image transfers.
7. Cloud Storage Integrations (Google Drive & Dropbox)
ImgEx provides optional cloud backup triggers for users who wish to save ZIP archives directly to their cloud storage:
Google Drive Integration
When you initiate a Google Drive backup, authorization occurs via Google Identity Services client-side OAuth. ImgEx requests only the minimal scope required to upload the newly generated ZIP file (drive.file). ImgEx cannot view, modify, or delete any of your other existing Google Drive files.
Dropbox Integration
When you use Dropbox backup, you supply your personal access token. The upload occurs directly from your browser to Dropbox’s official content API (content.dropboxapi.com). Your token is stored only in your local browser storage and is never forwarded to any ImgEx servers.
8. Data Retention Policy Summary
| Data Category | Storage Location | Retention Period |
|---|---|---|
| Extracted Image Files | Client Browser RAM Only | 0 seconds (Destroyed on tab close) |
| Generated ZIP Files | Client Browser RAM / Local Disk | 0 seconds (Downloaded directly to user device) |
| Local Settings / Collection Drafts | Client localStorage | Until cleared by user |
| Server Edge Request Logs | Edge Serverless Logs | 7–14 days rolling (Aggregated security metrics) |
9. Privacy Questions & Data Controller
If you have questions about this policy, or wish to exercise any applicable data protection rights, please contact our data privacy officer at support@imgex.online or via our Contact Page.