Юридические документы доступны только на английском языке.

Minfis — minfis.com Revision 2026-09-13 · Last updated 9 September 2026

This policy lists everything Minfis stores in your browser: the cookies we set, the cookies our network provider sets, and the values we keep in your browser's own storage. It covers the public website at https://minfis.com and the signed-in application.

It is short because there is little to describe. Two of our cookies are necessary — they are how the service tells one person's work from another's. Everything else on this page is advertising measurement (section 5): the Meta pixel, and one cookie of our own that remembers which advertisement brought you. None of it starts until you press Accept on the notice at the bottom of the page. Until then, and forever after if you press Decline, no advertising script is fetched, no such cookie is written, and no company outside this list receives anything about you.

1. Cookies and browser storage are not the same thing

Both live in your browser, and they are often lumped together. They behave differently, so this policy keeps them apart.

	Cookie	Browser storage
Sent to a server	Yes, attached to every request to the site that set it	No. It stays in the browser until page code reads it and decides to send something
Set by	The server, or page code	Page code only
Expires	On a date the setter chooses	Never on its own. It stays until the page or you clear it
Cleared by	Clearing cookies in the browser	Clearing site data in the browser

Minfis uses two necessary cookies of its own, one further cookie that exists only if you accept advertising measurement, and a handful of browser storage entries. All of them are listed below.

2. The cookies we set

2.1 The two necessary ones

Name	What it does	How long it lasts
`zhk_auth`	Holds the proof that you are signed in. Without it the service cannot tell one signed-in person from another	Fourteen days, renewed halfway through while you keep using the service. An administrator's sign-in lasts eight hours
`zhk_anon`	A random identifier, generated when you first use the service without an account, which is what your anonymous projects belong to. Without it the service cannot tell your work from the work of somebody else on the same network. It is not derived from anything about you, and it carries no name, address or location. When you sign in, the projects it owns become your account's and the cookie is removed	Ninety days, restarted each time you use the service without an account

Their properties, which you can check in your browser:

Not readable by page scripts. The browser will hand it back only to our server. Code running on the page — ours or anyone else's — cannot read it.
Sent only to our own site, and not when another website links into ours in a way that could act on your behalf.
Sent only over an encrypted connection on the live service.
Valid across the whole site, because who you are must not change as you move between pages — nor as your browser fetches a project's own images and files, which is a request your browser makes on its own.

zhk_auth is set when you sign in, register, complete a Google or Apple sign-in, or reset your password. It is removed when you sign out and when you delete your account. zhk_anon is set the first time you use the product without an account — reading a brief, starting a project, opening your list of them — and is removed when you sign in.

2.2 The one that exists only if you accept advertising measurement

Name	What it does	How long it lasts
`zhk_utm`	The advertisement you arrived through: the campaign tags in the link you clicked, the site you came from — its address only, never the page — and the path of the first page you opened. It tells us which advertisement produced a customer, so an advertising budget is spent on what works. It is written only after you press Accept, it holds nothing you typed and nothing about who you are, and if you register while it exists, its contents are copied once onto your account and never changed afterwards	Thirty days from the first visit that set it. A later visit does not extend it and does not overwrite it: the source of a customer is where they first came from, not where they last came from

Like the two above, it is not readable by page scripts, is sent only to our own site, and only over an encrypted connection on the live service.

We set no other cookie of our own. The only remaining cookies are Cloudflare's, in section 3, and the two that the Meta pixel writes if — and only if — you accept it, in section 5.

3. The cookies our network provider sets

The site is served through Cloudflare — Cloudflare, Inc., of the United States — which sits in front of our server and filters attacks and bots. It sets its own cookies, whose names begin with __cf, at the network edge before a request reaches us.

Name	Who sets it	What it does
`__cf*`	Cloudflare	Tells automated traffic from people, and keeps the protection working across your requests

These are strictly necessary in the plain sense: with them blocked, the site can refuse to load. We do not control their names or their lifetimes, and they carry nothing about your account.

4. What we keep in browser storage

None of these are cookies. They stay in your browser, and only our own pages read them.

Name	What it holds	Why
`zhk_consent`	Your answer to the question on the cookie notice — `granted` or `denied`	So the question is asked once, and so the answer is obeyed on every page. This is the value the advertising pixel in section 5 checks before it loads anything
`lang`	The interface language you chose	So the site opens in your language next time
`zhk_session_id`	A random identifier your browser generates for itself	Sent to our own server with each request, and read by nothing there: telling one browser's work from another's is the job of the `zhk_anon` cookie in section 2. It is never sent to anyone else and identifies no person
`zhk_auth_hint`	A copy of the last answer we gave about who you are, including your e-mail address and name	So the header can draw your account straight away instead of showing you as signed out for a second on every page load. It is a display shortcut and never grants access on its own
`minfis.sidebar.collapsed.v1`	Whether you collapsed the sidebar	Remembering your layout
`balance-history-open`	Whether the statement list is open	Remembering your layout

zhk_auth_hint holds your e-mail address in plain form. On a shared or public computer, sign out when you finish: signing out removes it along with the sign-in cookie.

An earlier revision listed zhk_cookie_ack, which recorded that you had read an informational notice. That notice has become a question, so the old value is not read any more and is not treated as agreement to anything: everyone is asked the new question once, including people who pressed the old button.

5. Advertising measurement, only if you agree

We advertise Minfis on Instagram and Facebook. To find out which advertisement brought somebody who then went on to create a project, we do two things, and one Accept covers both — you are not asked twice:

Our own record of where you came from, the zhk_utm cookie in section 2.2. It stays on our own server and is sent to nobody.
The Meta pixel — a small script belonging to Meta Platforms, Inc., which reports to Meta. The rest of this section is about that one, because it is the half that leaves our servers.

Earlier revisions of this page said there was no analytics, no advertising and no tracking on the site. That was true and it is no longer true, which is why this section replaces the one that said it.

It also does not run while no advertising account is connected. The pixel needs an account identifier to report to; the site is built without one unless we put it there. With no identifier, the script is never fetched no matter what you answered, and Meta receives nothing at all. Two conditions, both required: your consent, and a connected account.

It does not run unless you accept it. Until you press Accept, the script is never fetched: connect.facebook.net receives no request, www.facebook.com receives no request, and no cookie of Meta's exists in your browser. Pressing Decline keeps it that way for good, and also deletes the zhk_utm cookie if one had been written. Either way the product is the same — you can create a project, pay for it and download the booklet exactly as before.

Who receives it	Meta Platforms, Inc., of Menlo Park, California, United States. For people in the European Economic Area, the United Kingdom and Switzerland, Meta Platforms Ireland Limited, Dublin
What is sent	The address of the page you are on, the address you came from, your IP address, your browser's own description of itself, and the name of one of the events below
What is not sent	Your name, your e-mail address, your phone number, your brief, your project, and anything you typed into the service
The events	The pixel's own page view; opening the home page; opening the examples; opening one example; copying an example's prompt; registering; starting a project; paying. Nothing else is reported, and the list of them lives in one file of our source code so it cannot quietly grow
Cookies it sets	`_fbp`, a random identifier for your browser, written on our own domain. `_fbc`, holding the identifier of the advertisement you arrived through, if you arrived through one. Both last ninety days. Meta may also set cookies on its own domain when a measurement request reaches it
How to turn it off	The Decline button in section 6, at any time

We do not know who you are on Meta. We send no identifier of our own, so the matching of a measurement to an account on Facebook or Instagram is Meta's, done with what your browser already carries — and it is exactly what your Accept allows and your Decline prevents.

If we ever add a second measurement tool, it will be described here, with what it collects and who receives it, before it runs — and it will be behind the same question.

7. Clearing and blocking

You control all of it from your browser:

Clearing cookies for minfis.com signs you out. It also detaches any projects you started without an account: they are attached to zhk_anon and to nothing else, so once it is gone they can no longer be shown to you. It removes zhk_utm as well, if you accepted advertising measurement.
Clearing site data also removes the browser storage in section 4 — your language choice and the notice acknowledgement come back to their defaults.
Blocking cookies for this site leaves you able to read the public pages but unable to sign in, and unable to keep a project you start without an account.

We do not treat blocking as a reason to degrade anything else.

8. Payment pages

When you pay, the payment form is a page hosted by Polar, our payment provider, on its own address, not on ours. Polar is the merchant of record: it is the seller to you and takes the payment. Cookies on that page are Polar's and are covered by Polar's own policy.

No payment provider's script runs on our pages, so nothing about a payment is stored in your browser by minfis.com. Who receives what when you pay is in section 5 of the Privacy Policy.

9. More about the data itself

What we do with the data behind these — who receives it, how long it is kept and what you can ask us to do — is in the Privacy Policy.

10. Contact

Questions about this policy: [email protected]. We answer an e-mail within one business day; a formal request about your data is answered within thirty days, as the Privacy Policy says.

Anything else about the service: [email protected]

ANOMONUS - FZCO, DSO-IFZA, IFZA Properties, Dubai Silicon Oasis, Dubai, United Arab Emirates

Политика в отношении cookie