Cook­ie Pol­i­cy

Last Up­dat­ed: Sun May 03 2026

This Cook­ie Pol­i­cy ex­plains how Spas Z. Spasov op­er­at­ing as SnapiX ("SnapiX", "we", "us", or "our") uses cook­ies and sim­i­lar tech­nolo­gies when you vis­it our web­site and use our Ser­vice. It ex­plains what these tech­nolo­gies are and why we use them, as well as your rights to con­trol our use of them.

This Cook­ie Pol­i­cy should be read to­geth­er with our Pri­va­cy Pol­i­cy.

Contents

• 1. What are Cook­ies?
• 2. Why Do We Use Cook­ies?
• 3. What Types of Cook­ies Do We Use?
• 4. Cook­ies We Use
• 5. How Can I Con­trol Cook­ies?
• 6. Use of Ses­sion­Stor­age
• 7. Changes to This Cook­ie Pol­i­cy
• 8. Where Can I Get Fur­ther In­for­ma­tion?

1. What are Cook­ies?

Cook­ies are small data files that are placed on your com­put­er or mo­bile de­vice when you vis­it a web­site. Cook­ies are wide­ly used by web­site own­ers in or­der to make their web­sites work, or to work more ef­fi­cient­ly, as well as to pro­vide re­port­ing in­for­ma­tion.

Cook­ies set by the web­site own­er (in this case, SnapiX) are called "first-par­ty cook­ies". Cook­ies set by par­ties oth­er than the web­site own­er are called "third-par­ty cook­ies". Third-par­ty cook­ies en­able third-par­ty fea­tures or func­tion­al­i­ty to be pro­vid­ed on or through the web­site (e.g., like au­then­ti­ca­tion, se­cu­ri­ty, and re­mem­ber­ing your pref­er­ences from that third par­ty).

2. Why Do We Use Cook­ies?

We use first-par­ty and third-par­ty cook­ies for sev­er­al rea­sons. Some cook­ies are re­quired for tech­ni­cal rea­sons in or­der for our Ser­vice to op­er­ate, and we re­fer to these as "es­sen­tial" or "strict­ly nec­es­sary" cook­ies. Oth­er cook­ies en­able us to re­mem­ber your pref­er­ences, such as your cho­sen cur­ren­cy or UI set­tings, and we re­fer to these as "func­tion­al" or "pref­er­ence" cook­ies.

Specif­i­cal­ly, we use cook­ies for the fol­low­ing pur­pos­es:

• To op­er­ate our Ser­vice: Es­sen­tial for func­tion­al­i­ties like user au­then­ti­ca­tion, ses­sion man­age­ment, and se­cu­ri­ty.
• To en­hance your ex­pe­ri­ence: Re­mem­ber­ing your pref­er­ences and set­tings.
• For se­cu­ri­ty pur­pos­es: Pro­tect­ing our Ser­vice and your ac­count.

3. What Types of Cook­ies Do We Use?

a. Strict­ly Nec­es­sary Cook­ies: These cook­ies are es­sen­tial to pro­vide you with ser­vices avail­able through our web­site and to use some of its fea­tures, such as ac­cess to se­cure ar­eas and user au­then­ti­ca­tion. Be­cause these cook­ies are strict­ly nec­es­sary to de­liv­er the web­site and ser­vice to you, you can­not refuse them with­out im­pact­ing how our Ser­vice func­tions. You can block or delete them by chang­ing your brows­er set­tings, as de­scribed be­low un­der the head­ing "How can I con­trol cook­ies?".

b. Func­tion­al Cook­ies (Pref­er­ence Cook­ies): These cook­ies are used to re­mem­ber choic­es you make when you use our Ser­vice, such as your pre­ferred cur­ren­cy or the state of UI el­e­ments (like the side­bar). The pur­pose of these cook­ies is to pro­vide you with a more per­son­al ex­pe­ri­ence and to avoid you hav­ing to re-en­ter your pref­er­ences every time you vis­it our Ser­vice. You can refuse these cook­ies, but if you do, you may have to man­u­al­ly set your pref­er­ences each time you vis­it.

4. Cook­ies We Use

Here is a more de­tailed list of the cook­ies we use on SnapiX:

• Cook­ie Name(s): __cf_bm

  • Provider: Cloud­flare
  • Type: Strict­ly Nec­es­sary
  • Pur­pose: Se­cu­ri­ty (bot de­tec­tion, anti-DDoS, iden­ti­fy­ing trust­ed web traf­fic).
  • Ex­am­ple Du­ra­tion: ~30 min­utes (e.g., 2025-05-10T11:52:10.399Z)

• Cook­ie Name(s): _cfuvid

  • Provider: Cloud­flare
  • Type: Strict­ly Nec­es­sary
  • Pur­pose: Se­cu­ri­ty (re­lat­ed to Cloud­flare's bot man­age­ment and se­cu­ri­ty fea­tures).
  • Ex­am­ple Du­ra­tion: Ses­sion

• Cook­ie Name(s): __clerk_db_jwt (and vari­ants like __clerk_db_jwt_qZcBeJ)

  • Provider: Clerk
  • Type: Strict­ly Nec­es­sary
  • Pur­pose: User au­then­ti­ca­tion and ses­sion man­age­ment (e.g., keep­ing you logged in).
  • Ex­am­ple Du­ra­tion: Up to 7 days (e.g., 2025-05-17T11:22:11.282Z)

• Cook­ie Name(s): __client_uat (and vari­ants like __client_uat_qZcBeJ)

  • Provider: Clerk
  • Type: Strict­ly Nec­es­sary
  • Pur­pose: Client state man­age­ment for au­then­ti­ca­tion process­es.
  • Ex­am­ple Du­ra­tion: Up to 7 days (e.g., 2025-05-17T11:22:11.285Z)

• Cook­ie Name(s): __snapix__session

  • Provider: SnapiX (First-par­ty)
  • Type: Strict­ly Nec­es­sary
  • Pur­pose: Man­ages your ac­tive ses­sion on the SnapiX ser­vice.
  • Ex­am­ple Du­ra­tion: Up to 6 months (e.g., 2025-11-06T11:22:11.249Z)

• Cook­ie Name(s): __snapix__currency

  • Provider: SnapiX (First-par­ty)
  • Type: Func­tion­al / Pref­er­ence
  • Pur­pose: Re­mem­bers your pre­ferred cur­ren­cy (e.g., EUR/USD).
  • Ex­am­ple Du­ra­tion: Up to 6 months (e.g., 2025-11-06T11:22:11.747Z)

• Cook­ie Name(s): __snapix__sidebar:state

  • Provider: SnapiX (First-par­ty)
  • Type: Func­tion­al / Pref­er­ence
  • Pur­pose: Re­mem­bers the state of user in­ter­face el­e­ments, like whether the side­bar is open or closed.
  • Ex­am­ple Du­ra­tion: Up to 7 days (e.g., 2025-05-17T11:22:52.665Z)

Note: The ex­act names and ex­pi­ra­tion pe­ri­ods of third-par­ty cook­ies (Cloud­flare, Clerk) are con­trolled by those third par­ties and may change. We will en­deav­or to keep this list up­dat­ed based on our un­der­stand­ing of their ser­vices.

5. How Can I Con­trol Cook­ies?

You have the right to de­cide whether to ac­cept or re­ject cook­ies (oth­er than strict­ly nec­es­sary cook­ies).

Brows­er Con­trols: Most web browsers al­low you to con­trol cook­ies through their set­tings pref­er­ences. You can set your brows­er to refuse all cook­ies or to in­di­cate when a cook­ie is be­ing sent. How­ev­er, if you do not ac­cept cook­ies, you may not be able to use some por­tions of our Ser­vice, and strict­ly nec­es­sary cook­ies are re­quired for the Ser­vice to func­tion. Find out how to man­age cook­ies on pop­u­lar browsers:

• Brave
• Google Chrome
• Mi­crosoft Edge
• Mozil­la Fire­fox
• Sa­fari (Desk­top)
• Sa­fari (Mo­bile)
• Opera

6. Use of Ses­sion­Stor­age

We use PostHog for prod­uct an­a­lyt­ics to un­der­stand how our Ser­vice is used and to im­prove it. PostHog is con­fig­ured to use sessionStorage in your brows­er, not cook­ies, for this pur­pose. Data stored in sessionStorage is spe­cif­ic to a brows­er tab ses­sion and is cleared when the tab or brows­er is closed. This method does not place per­sis­tent files on your de­vice like cook­ies do. In­for­ma­tion col­lect­ed may in­clude us­age pat­terns and fea­ture in­ter­ac­tion. This data helps us make SnapiX bet­ter for you.

7. Changes to This Cook­ie Pol­i­cy

We may up­date this Cook­ie Pol­i­cy from time to time in or­der to re­flect, for ex­am­ple, changes to the cook­ies we use or for oth­er op­er­a­tional, le­gal, or reg­u­la­to­ry rea­sons. Please there­fore re-vis­it this Cook­ie Pol­i­cy reg­u­lar­ly to stay in­formed about our use of cook­ies and re­lat­ed tech­nolo­gies.

The date at the top of this Cook­ie Pol­i­cy in­di­cates when it was last up­dat­ed.

8. Where Can I Get Fur­ther In­for­ma­tion?

If you have any ques­tions about our use of cook­ies or oth­er tech­nolo­gies, please email us at ad­[email protected].