GCRflow Privacy Policy
Effective date: 2026-10-27
This policy explains what personal data we collect when you use www.gcrflow.com, cmykflow.com (CMYKflow), the developer API, the CMYKflow plugin for Figma, the Ink Checker and the assistant Flow, why we use it, who helps us process it, and how long we keep it. The China site (gcrflow.cn) has its own policy.
The controller of your data is the operator of GCRflow ("we", "us"). GCRflow is operated by an independent developer and is not yet incorporated. Contact: privacy@gcrflow.com.
In short: your files are used only to make your conversions and are deleted automatically after the retention period you choose. We do not use your files to train AI. We do not sell your data, we show no ads, and we use no analytics or advertising cookies.
1. What we collect
Account. Your e-mail address, display name and profile picture choice, your settings (for example how long files are kept), and your account role and team membership. Sign-in is handled by Google Firebase Authentication: if you use a password, Firebase stores it and we never see it; if you sign in with Google, Google shares your e-mail address and basic profile with us.
Sign-in history. For each of your 20 most recent sign-ins (none older than 12 months): the time, your IP address, browser and operating system, and the browser's user-agent text. You can see this list in Settings; our administrators can see it too, together with the country derived from the IP address.
How you found us. On your first visit your browser keeps, on your device, the referring site (domain and first path segment), the page you landed on, any campaign tags in the link (utm_…), whether the link carried an ad-click identifier (yes/no only, never its value), whether you came through the link of our Figma plugin, and the time. It also keeps the same details of your latest visit that came from another site or a tagged link. A link between www.gcrflow.com and cmykflow.com carries the first-visit record to the other site, so that site knows where you originally came from. When a guest or signed-in session starts in a browser tab, when you sign up or sign in, and when you create a file or a job, the page sends these two records to us and we keep them with your account or guest account, to learn which channels bring visitors: the first one stays as it was, the latest one is replaced by a newer one. For this we do not record your IP address, full web addresses, what you searched for or the pages you view; on the page you landed on, parts that look like an ID are replaced. If you create an account, the first-visit record is also saved once with the new account.
Files and jobs. The files you upload and what we make from them: converted files, previews, separation previews, the conversion report and a processing log. For each job we keep a record (until you delete the job or your account): file name and size, settings, status, ink figures, times and downloads. ICC profiles and presets you save are kept until you delete them.
Characterized templates (Custom Device Link). The chart files you return to build a template, the template's name and notes, and a record of each use of the template.
File statistics. For each converted file we keep technical statistics: size, page count, PDF version, page size, color spaces and profiles, counts of object types, ink coverage figures and the conversion settings. These records carry a random identifier and do not contain your account ID or file name. We use them to improve the conversion.
Payments and credits. Payments are made on Stripe's checkout page. We send Stripe your e-mail address and account ID, and we keep the payment session and payment identifiers, amount, currency, the credits added and refund information. We never receive your card number. Every addition and use of credits is recorded in your credit history. To show prices in the right currency, the country of your IP address is looked up in a database on our own servers; the country is not stored for this.
Teams. Team membership and role, and the credit allowance and usage of each member. The team owner can see members' e-mail addresses, display names, allowances and credit use.
Flow (assistant). Your messages, the earlier messages of the same conversation and, on www.gcrflow.com, an image you choose to attach are sent to Google's Gemini API to generate the answer. We do not store the conversation; it stays in the open page and is gone when you close it. To enforce daily limits we keep counters under keyed one-way codes made from your account or IP address together with the date, so the codes change every day; the counters contain no message text and are deleted automatically after 3 days. We use the paid Gemini API (a Google Cloud project with billing enabled). Under Google's Gemini API terms, Google does not use prompts or responses of the paid service to improve its products; it logs them for a limited time only to detect and prevent abuse. Please do not put sensitive personal information in your messages.
Abuse prevention and security.
- For free credits and e-mail verification exemptions, your e-mail address and IP address are stored only as keyed one-way codes.
- We check uploads for patterns that suggest an attempt to extract our conversion. For this we keep, per account, a score of suspicious uploads together with your e-mail address and display name, and with each upload a code derived from account, file name, file size and IP address.
- Our servers' request logs (kept by Google Cloud for 30 days) contain the IP address, browser user-agent, requested address and time.
Developer API. The name and a one-way hash of each API key (the key itself is shown to you once and not stored), webhook addresses and their signing secrets, and a record of API requests including the IP address.
CMYKflow guests. If you use CMYKflow without signing in, you get an anonymous account. Before the first upload Google reCAPTCHA checks that you are a person. Daily limits are counted under codes of your IP address that change every day; these counters are kept for about 2 days. Guest files are kept for 24 hours.
CMYKflow plugin for Figma. The PDF of the frames you select and your settings, plus a random installation number made by the plugin (we keep only a keyed code of it). Daily limits use the same daily-changing IP codes; those records are kept for 3 days.
Ink Checker. Files you open in the Ink Checker are processed in your browser and are not uploaded. We receive only event counts: the event name, where it was opened from and a rough device type.
Page counts. CMYKflow pages report events such as a visit, an upload started or a conversion finished, and www.gcrflow.com reports one visit per browser tab; we keep only totals of these events, also split by where the visitor first came from (for example a search engine, an AI assistant, a social network or one of our tagged links), and, to avoid counting a file twice, its file number, without IP address or browser details. Visits made while signed in to an administrator or test account are not counted.
CMYKflow referral links. If you open CMYKflow through a partner's link (with ?ref=…), your browser keeps the partner code for 90 days and the page reports the visit as a count (no IP address or browser details kept). If you then create a file or sign in, we record once which partner referred your account, and when. The partner sees only totals, not your e-mail address or files.
Support. What you write to us by e-mail.
3. How we use your data
- to provide the Service: accounts, conversions, previews, reports, teams, the API and Flow;
- to charge and keep credit and payment records;
- to keep the Service secure and prevent abuse and fraud;
- to answer support requests;
- to improve the conversion (using the file statistics described above);
- to meet legal obligations.
We do not sell your personal data, we do not share it for advertising, and we do not use your files to train AI or machine-learning models.
Legal bases (GDPR and similar laws): performance of our contract with you (providing the Service, including accounts, conversions, payments and support); our legitimate interests (keeping the Service secure, preventing abuse and fraud, and improving the conversion with the file statistics); and legal obligations (for example keeping accounting records).
5. International transfers
Your data is stored and processed in Singapore. Google and Stripe may also process it in other countries. For personal data from the EEA and the UK, these providers' data processing terms provide for the European Commission's standard contractual clauses (SCCs) or another transfer mechanism recognised by law: Google Cloud, Firebase, Google as a data processor, including the paid Gemini API and Stripe.
6. How long we keep it
| Data | How long |
|---|---|
| Uploaded files and results on www.gcrflow.com | Your setting: 1, 7 or 30 days (default 1 day); an original used by several jobs is kept until the last of them ends. |
| Files on CMYKflow | 7 days after upload; 30 days from payment for a paid file; guests 24 hours. |
| After deletion | Deleted files stay in Google Cloud Storage's recovery protection for 7 days, then they are gone permanently. In any case every uploaded original and conversion result is removed from storage no later than 45 days after it was created. |
| Chart files returned for a characterized template | 7 days |
| Characterized templates, presets, saved ICC profiles | Until you (or your team owner) delete them |
| Account, job records and other saved items | While your account exists; deleted when you delete your account (section 8) |
| Payment records and credit history | At least as long as the applicable tax and accounting laws require, also after account deletion (then without your account ID or e-mail address). |
| Sign-in history | The 20 most recent sign-ins, none older than 12 months |
| How you found us (first and latest visit records) | With your account until you delete it; for a guest session that never becomes an account, 90 days |
| Page and visit totals by source | Kept without a fixed end date; they contain no account ID |
| Records of suspicious use and of protected chart files (with your e-mail address) | 12 months (an account blocked for abuse, or exempted by us: while that decision stands) |
| Developer API audit records (with IP address) | 12 months |
| Administrator action log | 24 months |
| Flow daily counters | 3 days |
| Record that an account was deleted | Kept without the account ID or e-mail address (a keyed code instead), to finish and show the deletion |
| Keyed one-way code of the e-mail address used for the sign-up gift | Kept after account deletion, so the gift is given once per address |
| Server request logs | 30 days |
| Daily-limit counters (guests, Figma plugin) | About 2 to 3 days |
| File statistics | Kept without a fixed end date; they contain no account ID or file name |
7. Security
- All connections use HTTPS, and browsers are told to use HTTPS only.
- Passwords are handled by Firebase Authentication; we never store them.
- API keys are stored only as one-way hashes.
- Characterized templates are stored encrypted with a separate key for each file and are never offered for download.
- Administrator access is checked on every request, and each administrator download of a user file is logged.
- Identifiers used for free-credit and e-mail verification limits and for daily usage limits are stored as keyed one-way codes.
No system is perfectly secure. If a breach affects your data, we will inform you and the authorities as the law requires.
8. Your rights and choices
Depending on where you live (for example under the GDPR in the EEA and UK, or under California law), you can ask us to give you access to your data or a copy of it, correct it, erase it, restrict or object to its use, and you can withdraw consent you gave. You can also complain to your data protection authority. We will not treat you differently for using these rights. We do not sell or share personal data for cross-context behavioral advertising.
In the Service you can change your display name and file retention, see your sign-in history, delete jobs, presets and templates, and delete your account. For anything else, write to privacy@gcrflow.com from your account's e-mail address. We may need to confirm your identity, and we will answer within 30 days.
Deleting your account (Settings › Account) cannot be undone. It deletes your sign-in, your profile and sign-in history, the record of how you found us, your jobs with all their files, your presets and saved ICC profiles, the characterized templates you own, your developer API keys, your messages and your assistant counters — and your files on CMYKflow, which uses the same account. A team member leaves the team; a team owner first removes the team's members. Payment records, the credit ledger and the records we need for accounting, partner commissions and abuse prevention are kept (for a paid CMYKflow file: the payment, without the file name), but your account ID and e-mail address in them are replaced by an irreversible code. A keyed one-way code of your e-mail address stays so that the sign-up gift is not given twice. Stripe keeps its own payment records under its own privacy policy. Deleting a job deletes its files at once (a job that is still converting: within a few hours, after the conversion has ended); a file that another of your jobs still uses is deleted with the last of them. Deleted files stay in Google Cloud Storage's recovery protection for 7 more days, then they are gone permanently.
9. Children
The Service is not meant for people under 16. If you believe a child has given us personal data, write to privacy@gcrflow.com and we will delete it.
10. Changes
We will publish changes on this page with a new effective date, and tell you in the Service or by e-mail about important changes before they apply.
11. Contact
privacy@gcrflow.com