Table of Contents
- 1. Introduction and Scope
- 2. Architectural Core Principle: Client-Side Data Minimization
- 3. Proprietary Reconstruction Engine & Steganographic Integrity Architecture
- 4. Information We Collect and Receive
- 5. Legal Bases for Processing (GDPR & Global Standards)
- 6. Advertising, Analytics & Third-Party Service Providers
- 7. Device Permissions and Access Declarations
- 8. Cryptographic Safeguards and Data Security Architecture
- 9. Data Retention and Ephemeral Storage Disposal
- 10. Your Statutory Rights (GDPR, CCPA/CPRA, and International Frameworks)
- 11. Children's Privacy Governance (COPPA & Global Safeguards)
- 12. Cross-Border International Data Transfers
- 13. Policy Amendments and Material Revision Protocol
- 14. Contact Information and Data Protection Inquiries
1. Introduction and Scope
KRAFT CART, founded and operated by Vivek Vaghela ("KRAFT CART," "PixFlow," "we," "us," or "our"), provides the PixFlow™ Mobile Application (Package Identifier: kc.pixflow.kraftcart, hereinafter the "Application" or "Service"), available across authorized distribution channels including the Google Play Store and Apple App Store. This Global Privacy Policy ("Privacy Policy") governs the manner in which KRAFT CART handles technical telemetry, device state, and analytical metadata resulting from the use of our high-efficiency digital media compression, perceptual optimization, and lossless fidelity restoration solutions.
We are firmly committed to upholding the highest global benchmarks in data privacy, transparency, and computational integrity. This document provides exhaustive disclosures required by the European Union General Data Protection Regulation (Regulation (EU) 2016/679 - "GDPR"), the United Kingdom Data Protection Act 2018 ("UK GDPR"), the California Consumer Privacy Act of 2018 as amended by the California Privacy Rights Act of 2020 ("CCPA/CPRA"), the Google Play Developer Program Policies, and corresponding statutory frameworks across all applicable international jurisdictions.
By downloading, installing, launching, accessing, or utilizing the PixFlow Application, you acknowledge that you have read, understood, and consented to the operational practices, telemetry policies, and data processing protocols detailed within this document.
2. Architectural Core Principle: Client-Side Data Minimization
PixFlow adheres to a strict "Zero-Knowledge Raster Storage" philosophy regarding your personal photographs, camera captures, and gallery graphics. We do not maintain centralized image warehouses, facial recognition indexes, biometric signature stores, or human-reviewable photo archives. Your raw image rasters never traverse our servers in human-viewable, persistent gallery formats.
The Application's primary objective is to optimize digital storage consumption on the user's physical device while retaining maximum perceptual fidelity. Consequently, data processing is engineered to minimize external data propagation to the absolute technological limit required for operational stability, ad monetization, and proprietary lossless decompression services.
3. Proprietary Reconstruction Engine & Integrity Architecture
To enable the Application's signature lossless restoration capability—allowing users to restore carrier images back to their authentic full-resolution state without physical payload overhead on their device—the Service employs mathematically synthesized, ephemeral reconstruction coefficients and cryptographic SHA-256 integrity tokens:
- Cryptographic Quality Tokens: When an optimization operation is initiated with restoration features enabled, the engine calculates non-reversible algorithmic perceptual coefficients and a deterministic mathematical hash. These tokens describe structural spatial matrices necessary for reverse reconstruction without exposing raw raster bitmaps.
- Ephemeral Cloud Synchronization: To facilitate instant cross-session restoration across compatible ecosystem instances, the encrypted reconstruction parameters may be securely stored in enterprise-grade, high-security cloud object repositories (managed via ISO 27001 and SOC 2 certified Firebase Infrastructure). These parameter bundles are fully anonymized, contain zero personal identity data, and are governed by strict automated lifecycle retention rules.
- Tamper-Resistant Verification: The Application utilizes steganographic integrity headers embedded within the carrier bitstream to ensure mathematical parity prior to decompression. If an image is manipulated, altered, or transcoded by external third-party communication networks, the verification engine dynamically detects the alteration and alerts the user.
4. Information We Collect and Receive
We collect and process categories of information strictly proportional to providing, maintaining, and improving the Service:
4.1. Data You Provide Directly
- Customer Support Correspondence: If you initiate communication via our designated support channels, we retain your email address, message body, attached diagnostic logs, and relevant thread history to resolve your technical inquiries.
- In-App User Preferences: Local application configuration variables, such as your designated default compression preset, preferred output container format (e.g., JPEG, PNG, WEBP, or .PIXFLOW), and UI theme preferences, which are stored strictly in local on-device application sandboxes (Shared Preferences / UserDefaults).
4.2. Automatically Collected Device & Performance Telemetry
- Device Identifiers & Hardware Metrics: Device manufacturer, hardware model, system architecture, operating system version (e.g., Android 15, iOS 18), system locale, preferred language, total available physical RAM, and display density.
- Application Performance Telemetry: Compression execution duration, codec initialization latency, memory consumption benchmarks, app lifecycle transitions (foreground/background states), and non-fatal runtime anomalies collected for stability tuning.
- Crash Diagnostics & Stack Traces: In the event of an abnormal application termination, standardized anonymized crash logs detailing machine code traces, device state, and operating memory conditions are aggregated via automated analytics platforms.
4.3. Digital Media Technical Metadata (Non-Personally Identifiable)
During the optimization workflow, the engine reads local file attributes strictly necessary to compute compression matrices. This includes:
- Original file size (bytes), target file size, and measured byte-reduction ratios.
- Pixel dimensions (width × height), color bit depth, color space profiles (sRGB, Display P3), and container MIME types.
- Deterministic cryptographic checksums (SHA-256) utilized exclusively for file identity matching during decompression sequences.
4.4. Third-Party Advertising & Measurement Identifiers
To support the free tier of the PixFlow Service, we partner with industry-standard programmatic advertising networks (including Google AdMob). These networks may collect and process:
- Google Advertising ID (GAID) on Android devices, or Identifier for Advertisers (IDFA) on iOS devices (subject to explicit App Tracking Transparency consent).
- IP addresses (collected solely for localized region determination and fraud detection).
- Ad interaction logs, impression timestamps, click-through frequencies, and ad rendering completion telemetry.
5. Legal Bases for Processing (GDPR & Global Standards)
In accordance with Article 6 of the General Data Protection Regulation (GDPR), PixFlow processes personal and diagnostic telemetry only under established, legitimate statutory grounds:
| Processing Activity | Categories of Data | Statutory Legal Basis (GDPR Art. 6) |
|---|---|---|
| Core compression, format conversion, and lossless restoration | Local image bitstreams, cryptographic tokens, file metadata | Performance of Contract (Art. 6(1)(b)): Necessary to execute requested image optimization services. |
| Displaying contextual or non-personalized advertisements | Pseudonymous ad identifiers, coarse geographic IP region, device telemetry | Legitimate Interests (Art. 6(1)(f)): Funding ongoing development, infrastructure hosting, and maintenance. |
| Displaying personalized programmatic advertisements | Google Advertising ID (GAID), IDFA, user behavioral engagement data | Explicit Consent (Art. 6(1)(a)): Gathered via Google-certified Consent Management Platforms (CMP). |
| Crash analytics, bug remediation, and stability optimization | Anonymized stack traces, device hardware attributes, memory utilization | Legitimate Interests (Art. 6(1)(f)): Ensuring robust reliability, security, and continuous functionality. |
6. Advertising, Analytics & Third-Party Service Providers
PixFlow integrates select third-party Software Development Kits (SDKs) to perform infrastructure management, stability monitoring, and ad mediation. Each provider processes telemetry under independent contractual privacy commitments:
- Google AdMob (Google LLC): Serves programmatic advertisements. Google utilizes pseudonymous device identifiers and SDK cookies to serve contextual or personalized advertisements and prevent ad fraud. Users may review Google's policies at: https://policies.google.com/technologies/ads.
- Google Firebase (Google LLC): Provides real-time synchronization databases (Cloud Firestore), encrypted object storage (Firebase Storage), and infrastructure telemetry. Firebase complies with rigorous enterprise security certifications (ISO/IEC 27001, SOC 1, SOC 2, SOC 3). Review Firebase data policies at: https://firebase.google.com/support/privacy.
- Google Play Services: Core application maintenance, in-app billing verification, and operating system bridge libraries.
7. Device Permissions and Access Declarations
The Application requests explicit runtime device permissions solely when required to execute user-requested features. PixFlow strictly conforms to the Android 13+ Granular Media Permissions architecture and Apple iOS PhotoKit guidelines:
| Permission Name | Platform Target | Operational Purpose |
|---|---|---|
READ_MEDIA_IMAGES |
Android 13 (API 33)+ | Allows user to select specific photographs from the system picker for compression or decompression. |
READ_EXTERNAL_STORAGE / WRITE_EXTERNAL_STORAGE |
Android 12 & earlier | Enables reading target images and writing optimized JPEG/PNG/WEBP files to the public Pictures/PixFlow directory. |
INTERNET & ACCESS_NETWORK_STATE |
All Platforms | Verifies active connectivity for Google AdMob ad mediation, telemetry reporting, and cloud integrity synchronization. |
NSPhotoLibraryUsageDescription |
iOS / iPadOS | Prompts for explicit permission before accessing photo albums to import source photos and export compressed deliverables. |
8. Cryptographic Safeguards and Data Security Architecture
PixFlow employs state-of-the-art administrative, physical, and technical safeguards engineered to safeguard data against accidental destruction, unauthorized disclosure, tampering, or unlawful access:
- Transport Layer Security (TLS 1.3): All communications between the mobile application and cloud endpoints are secured with cryptographic TLS 1.3 tunnels, utilizing modern cipher suites with perfect forward secrecy.
- Advanced Encryption Standard (AES-256): Proprietary reconstruction parameter bundles stored within cloud repositories are encrypted at rest using industry-standard AES-256 cryptographic ciphers.
- Zero Local Persistence of Source Masters: The Application operates without mutating or overwriting your original master photographs. Original files remain untouched in their native file system directories unless explicitly managed by the user via native system utilities.
9. Data Retention and Ephemeral Storage Disposal
PixFlow maintains a strict data minimization schedule:
- Local Transient Cache: Temporary working bitstreams and preview thumbnails generated during active compression sessions are stored in designated app-private cache directories (
getTemporaryDirectory()). These files are automatically scrubbed upon task completion or can be instantly purged via the in-app "Clear Application Cache" button in Settings. - Reconstruction Parameter Bundles: Ephemeral mathematical restoration parameters synchronized to cloud infrastructure are retained under an automated lifecycle disposal schedule, after which stale parameters are permanently purged from active registries.
- Local Transformation Records: Local compression history stored in the local SQLite/NoSQL database is under total user control. Users may permanently erase their entire optimization log at any moment by selecting "Clear History" within the Application's Settings screen.
10. Your Statutory Rights (GDPR, CCPA/CPRA, and Global Frameworks)
Depending on your geographic residence, you hold comprehensive legal entitlements concerning your data:
10.1. European Union (EEA) & United Kingdom Residents (GDPR)
- Right of Access (Art. 15): Request confirmation of whether your telemetry is being processed and obtain a copy.
- Right to Rectification (Art. 16): Request correction of inaccurate personal data.
- Right to Erasure ("Right to be Forgotten", Art. 17): Demand immediate permanent deletion of all associated telemetry and cloud records.
- Right to Restriction & Objection (Arts. 18, 21): Object to processing grounded in legitimate interests or demand processing suspension.
- Right to Data Portability (Art. 20): Receive telemetry in a structured, machine-readable format.
10.2. California Residents (CCPA / CPRA Disclosures)
Pursuant to the California Consumer Privacy Act as amended by the CPRA:
- No Sale of Personal Information: PixFlow does not sell personal information, visual images, or biometric records for monetary consideration.
- No Sharing for Cross-Context Behavioral Advertising: Without your explicit consent via system-level ad tracking toggles, we do not share your persistent identifiers for third-party cross-context marketing.
- Right to Opt-Out & Non-Discrimination: You have the absolute right to direct us not to sell or share your data, and we will never discriminate against you (via degraded compression features or price alteration) for exercising your statutory privacy privileges.
10.3. In-App Self-Service Erasure Controls
You can execute immediate data erasure directly within the Application without submitting an email ticket:
- Open PixFlow → Tap the Settings icon in the top-right corner.
- Navigate to the Storage & Data Management card.
- Tap Clear Application Cache to instantly wipe all transient files, cached thumbnails, and intermediate codec tensors.
- Tap Clear History to permanently delete all local transformation logs.
11. Children's Privacy Governance (COPPA & Global Safeguards)
The PixFlow Application is designed as a general-audience digital utility. We do not knowingly solicit, collect, process, or aggregate personal data from children under the age of 13 (or under 16 in applicable European jurisdictions), in strict accordance with the United States Children's Online Privacy Protection Act ("COPPA") and European digital consent standards.
If we discover that personal data from an underage child has been inadvertently collected through ad mediation networks or diagnostic channels without verified parental consent, we will take immediate operational steps to purge such records from our databases. Parents or legal guardians who become aware of such occurrences are urged to contact our compliance desk immediately at kraftcarthelp@gmail.com.
12. Cross-Border International Data Transfers
Technical diagnostic data, cloud synchronization records, and advertising mediation signals may be transferred to, hosted, and processed in cloud data centers located in the United States and other global regions operated by our enterprise cloud partners (Google LLC). Whenever data originating in the European Economic Area (EEA), the United Kingdom, or Switzerland is transferred outside these territories, we ensure adequate legal transfer mechanisms are enforced, including Standard Contractual Clauses (SCCs) approved by the European Commission.
13. Policy Amendments and Material Revision Protocol
We reserve the right to revise, update, or amend this Global Privacy Policy at our discretion to reflect evolving technical methodologies, architectural upgrades, regulatory updates, or changes in legal obligations. When material revisions are executed, we will update the "Last Updated" timestamp at the apex of this document and provide prominent in-app notification banners prior to the modifications taking operational effect.
Your continued access to and utilization of the Application following the publication of any revised Privacy Policy constitutes your legally binding acceptance of the amended terms.
14. Contact Information and Data Protection Inquiries
If you have any questions, regulatory inquiries, requests to exercise statutory data rights, or complaints regarding this Privacy Policy or our algorithmic processing practices, you may contact our designated Data Protection Officer (DPO) and Corporate Compliance Department:
Founder & Developer: Vivek Vaghela
Application ID:
kc.pixflow.kraftcartLegal Affairs & Data Protection Compliance
Official Support & Privacy Email: kraftcarthelp@gmail.com
Website: https://creatoros-appvivek.web.app