1. What Colorrow is
Colorrow provides browser-based color tools, palette discovery, educational guides, and local saved-palette features. The main tools do not require a Colorrow user account.
2. Browser storage used by Colorrow
The current site uses browser localStorage for product preferences and saved work. Known keys include:
colorrowThemefor light/dark theme preferencecolorrowCookieChoicefor the banner choice (acceptedoressential)colorrowSavedfor the current saved-palette format- legacy saved-palette keys
savedPalettes,colorrowSavedPalettes,saved-palettes, and on the Saved Palettes page,palettes
Saved palettes are stored by the browser on the device/profile where you save them. Clearing site data, using another browser/profile, or losing local browser storage can remove that data. Colorrow does not currently provide account-based cloud sync.
3. Google Analytics
Colorrow loads Google Analytics (gtag.js, measurement ID G-YHNWCR84RB) only after the browser has a stored accepted choice or the user selects “Allow Analytics.” If no choice exists, or if essential is stored, the Analytics loader is not inserted by the Phase 26 consent runtime. When Analytics is allowed, the browser connects to Google infrastructure and Google may process browser, device, network, and usage information under Google's own terms and privacy documentation.
The current Colorrow source does not implement a separate first-party analytics database for individual Colorrow accounts because the site has no user-account system.
4. Google AdSense
Colorrow is connected to Google AdSense publisher ca-pub-6240155602670919, but Phase 26 intentionally disables the live AdSense ad-serving script during review. Normal pages retain the supported google-adsense-account ownership-verification meta tag, and the site root retains the matching ads.txt seller record. Those verification mechanisms do not themselves display ads.
The current source contains no manual adsbygoogle units and no live Auto Ads loader, including on 404 pages, saved/private utility pages, palette-share routes, noindex category routes, or tool controls/results. If ad serving is enabled later, placement and consent must be reviewed again. Google currently requires a Google-certified CMP integrated with the IAB TCF for personalized ads to users in the EEA, UK, and Switzerland; Colorrow's local analytics-choice banner is not that CMP.
5. Supabase palette discovery
Explore and selected discovery surfaces request public palette records from a Supabase REST endpoint using a publishable browser credential. The selected data is palette metadata such as colors, title, category, tags, counts, and dates. Those requests are network requests to Supabase and therefore expose ordinary connection information to the infrastructure handling the request.
Colorrow does not use a Supabase service-role key in browser code, and the current palette-discovery request path is for reading the public palette catalog rather than uploading your saved palettes.
6. Uploaded images
The route-specific Image Color Picker and Color Blindness Simulator code processes selected image bytes in the browser. The current implementations create temporary object URLs, decode the image, and use canvas pixel data; those route scripts do not contain a fetch, XHR, sendBeacon, or form-upload path for the selected image.
This is a statement about the image-processing code, not a claim that the whole page is offline: Supabase or other shared resources can still make network requests where the route uses them, and Google Analytics can load after an “Allow Analytics” choice. Live AdSense ad serving is disabled in the Phase 26 build.
7. Email contact
Colorrow's contact page uses a mailto: link to contact.colorrow@gmail.com; there is no website contact-form backend in the current source. If you email Colorrow, your message, sender address, and any attachments you choose to include are transmitted through the email providers involved in delivery.
No fixed email-retention period is promised on this site. Do not send passwords, payment details, private keys, or other sensitive information that is unnecessary for support.
8. Cookies, choices, and browser controls
You can remove Colorrow's local browser data through your browser's site-data controls. The Phase 26 banner now gates Google Analytics: “Essential Only” leaves Analytics unloaded, while “Allow Analytics” permits the Analytics loader on that browser profile. Clearing the site's local storage resets the choice. Advertising remains disabled in this build pending AdSense review and certified-CMP setup; if advertising is enabled later, this policy and the consent implementation must be reviewed again.
9. External services and links
Colorrow links to external sites and uses third-party infrastructure. Those services operate under their own terms and privacy policies. Colorrow cannot describe or control every data practice of an external service from this site's code.
10. Privacy questions
For a question about Colorrow's current data behavior, email contact.colorrow@gmail.com. Depending on applicable law and the data actually held by the relevant service, you may also have privacy choices or rights through your browser, email provider, Google, or other third-party service.
11. Changes to this page
When Colorrow's implemented data behavior changes, this page should be reviewed so its description remains aligned with the code. The date above records the latest Phase 26 implementation review; it is not a promise that no later implementation change can occur.