1. Dual-Mode Processing Architecture & File Handling
ImgPipeline operates two distinct processing pipelines with strict isolation boundaries:
- Interactive Web Sandbox Tools: When you use our interactive web tools (including format converters, e-commerce product padders, image compressors, EXIF metadata strippers, colour replacers, and South African bank statement PDF-to-CSV parsers), all file decoding and transformation occur inside an isolated transient sandbox. Your source files and exported outputs are never retained on persistent servers.
-
Edge API & Cloud AI Compute: When you explicitly invoke our REST API endpoints (such as
/v1/shrink,/v1/removebg, or AI Vision Alt-Text / SEO Renaming) using a Bearer API key or studio credit action, the binary image payload is transmitted over TLS 1.3 to our secure edge compute nodes. The payload is transformed in volatile RAM, returned directly to your client, and immediately garbage-collected. Where an asynchronous job requires a temporary staging buffer, the object is cryptographically scoped and automatically purged upon completion.
2. Information We Collect
We collect only the minimum information required to provision developer accounts, authenticate API requests, prevent abuse, and process payments:
- Account & Authentication Data: When you sign in via Email + One-Time Password (OTP) or Google Sign-In (OAuth 2.0), we store your email address, account creation timestamp, hashed password or OAuth subject identifier, and generated API Bearer key in our encrypted relational database.
-
API Usage & Credit Ledger Telemetry: To maintain accurate credit balances and display your real-time usage split in the Dashboard, we record transaction metadata consisting of: user ID, endpoint identifier (e.g.,
removebg_api,tinypng_shrink), credits deducted or refunded, HTTP status code, and timestamp. We do not log the visual contents or filenames of your API payloads in usage logs. - Billing & Transaction Records: Payments for 72-Hour Pro Passes and Pay-As-You-Go Credit Packs are processed by Stripe, Inc. We store the Stripe Checkout session ID, payment status, package tier, and credit allocation. We never receive, process, or store your full credit card number or CVV.
- Security & Edge Request Metadata: Our edge network temporarily processes IP addresses, User-Agent strings, and automated bot-verification tokens to enforce rate limits and defend against automated credential stuffing or denial-of-service attacks.
3. Local Storage, Cookies & Analytics
We avoid intrusive third-party ad-tracking cookies. Instead, we use functional browser storage and privacy-focused edge telemetry:
-
Browser
localStorage: Used to persist your active API session token (api_key), UI preferences, and cached navigation partials so pages load instantaneously without layout shift. - First-Party Edge Telemetry: We use privacy-focused edge telemetry to measure aggregate page views, tool performance, and conversion events without loading heavy third-party tracking scripts on your device.
4. Sub-Processors & Infrastructure Partners
To deliver low-latency edge execution and global reliability, we rely on the following vetted infrastructure providers:
| Provider | Purpose | Data Scope |
|---|---|---|
| Global Edge CDN & Security Provider | Global CDN, Edge Security, WAF & Network Routing | Account records, API keys, transient API payloads, OTP emails |
| Stripe, Inc. | Merchant checkout, invoicing & payment processing | Billing email, payment method details, transaction receipts |
| Google LLC | Optional Google Sign-In (OAuth 2.0) authentication | Verified email address & OAuth profile token upon user consent |
5. Your Data Protection Rights (GDPR, CCPA & POPIA)
Regardless of your geographic jurisdiction — including the European Economic Area (GDPR), United Kingdom, California (CCPA/CPRA), or the Republic of South Africa (Protection of Personal Information Act, 4 of 2013 — POPIA) — you have the right to:
- Access & Portability: Request an export of your account profile, credit ledger, and API usage history.
- Key Rotation & Revocation: Regenerate or revoke your active API Bearer token immediately from your Developer Dashboard.
- Rectification & Erasure: Request correction of inaccurate account details or permanent deletion of your developer account and associated encrypted database records.
- Objection & Restriction: Object to non-essential telemetry processing at any time.
6. Data Retention & Security Controls
Account records and credit ledger balances are retained for as long as your developer account remains active, plus any statutory tax retention period required for completed financial invoices. All API communications are enforced over HTTPS (TLS 1.3), database queries are parameterized against injection, and failed upstream API operations automatically trigger atomic credit refunds.
7. Contact & Information Officer
For privacy inquiries, data subject access requests (DSARs), or security disclosures, please contact our team directly: