Privacy Policy — Zero File or Color Transfers
Every color value, brand palette, design token JSON, SVG, and reference image stays strictly inside your local browser memory.
Zero file or color data leaves your device
Colr operates no backend color API or file conversion server. Color calculations, Canvas image quantization, and Adobe .ase/.aco binary parsing run exclusively in client memory.
1. Client-side processing architecture
When you open an image, CSS stylesheet, .ase/.aco file, or .cube LUT inside Colr, the browser reads bytes directly via File.arrayBuffer() or Canvas 2D getImageData() inside RAM.
Once converted or exported, generated files live in local blob URLs and disappear automatically when the tab closes.
2. Zero accounts, ad trackers, or pixel logging
Colr never asks you to sign in and never stores behavioral ad cookies or copies of converted palettes.
- No server conversion endpoints or cloud storage buckets.
- No third-party ad networks tracking color queries or brand assets.
- Optional browser localStorage stores only your UI dark/light theme preference and recent tool shortcut.
Frequently Asked Questions
Can Colr inspect proprietary brand assets I drop into palette tools?
No. Everything runs locally in your browser sandbox with zero outbound payload transfers.