Cookie Policy
This page is the only complete list of cookies and similar technologies (localStorage and sessionStorage browser storage) used by Qerify. The rules for using them follow from Article 399 of the Polish Electronic Communications Law and the GDPR. We store necessary and functional files without asking for consent, because without them the service would not work the way you expect. We store analytics files only with your consent given in the cookie banner. We do not use advertising cookies.
| Name | Provider | Purpose | Lifetime | Category | Requires consent |
|---|---|---|---|---|---|
sb-*-auth-token*cookie | Supabase | Session of a logged-in user: keeps you logged in across pages. Logging out removes it. | 400 days | Necessary | No |
tos_v_*cookie | Qerify | Confirms that a logged-in user has accepted the current Terms of Service, so that we do not ask on every page. | 30 days | Necessary | No |
cookie_consent_v1browser storage (localStorage) | Qerify | Remembers your choice in the cookie banner, so that it is not shown on every page and analytics does not start without consent. | until you click “Cookie preferences” or clear browser data | Necessary | No |
q_impcookie | Qerify | Qerify administrators only: marks a preview of a user account, so that every page shows that a preview is in progress. | 30 minutes | Necessary | No |
qerify_locale_previewcookie | Qerify | Qerify administrators only: preview of a page in another language while editing content. | 30 minutes | Necessary | No |
qerify_localecookie | Qerify | Remembers the language you choose in the language switcher. It contains only the language code. | 1 year | Functional | No |
q_themecookie | Qerify | Logged-in users: remembers the panel theme (light or dark) you choose. | 1 year | Functional | No |
qerify-sidebar-collapsed, concierge_state, q_ann_dismissed, q_ann_seen:*, q_prelaunch_intro_v1, qerify.portfolio.*browser storage (localStorage) | Qerify | Remembers interface settings and state on your device: a collapsed sidebar, an interrupted conversation with the AI Concierge (for 2 hours), closed announcements, the selected project template. It is not sent to our server. | until browser data is cleared | Functional | No |
audit-wizard-v1, concierge_pending_message, qerify:m1-annual-savings-pln, qerify:new-project-draft:*tab storage (sessionStorage) | Qerify | Data of an unfinished form in the open tab: an audit order, a message to the AI Concierge, the result of the savings calculator, a new project draft. It is not sent to our server. | until the browser tab is closed | Functional | No |
pending_refcookie | Qerify | Remembers the referral code from the registration link, so that after you create an account you are linked to the person who referred you. We store it only with your consent to analytics files in the cookie banner; without that consent the referral is not recorded. We delete it right after registration or when you make a choice without analytics files. | 1 hour | Analytics | Yes |
_gacookie | Google Analytics 4: a random browser identifier that makes it possible to tell returning visits from new visitors in the statistics. | 2 years | Analytics | Yes | |
_ga_*cookie | Google Analytics 4: remembers the current visit and its number in the statistics. | 2 years | Analytics | Yes | |
ph_*_posthogbrowser storage (localStorage) | PostHog | PostHog: a random browser identifier for statistics on how the service is used (page views, clicks).This tool is currently disabled and stores nothing. | until browser data is cleared | Analytics | Yes |
ph_*_window_id, ph_*_primary_window_existstab storage (sessionStorage) | PostHog | PostHog: recognises the browser tab within a single visit.This tool is currently disabled and stores nothing. | until the browser tab is closed | Analytics | Yes |
Tools that do not store cookies on the Qerify domain
The tools below work on Qerify pages, but they do not store their own cookies on the qerify.com domain, or they do so only on their providers’ pages and frames.
- Vercel Web Analytics (Vercel Inc.): Aggregate visit statistics. It does not store cookies or any data in browser storage, which is why it works without consent.
- Qerify page view counter: It records the visited address, the traffic source and a salted hash of the IP address (without the IP address in plain form). It does not store cookies and does not work when the browser sends a Do Not Track or Global Privacy Control signal.
- Cloudflare Turnstile (Cloudflare, Inc.): It checks whether the login and registration form, a conversation with the AI Concierge or a report is sent by a human. It works in a frame from the challenges.cloudflare.com domain and reads information about the browser for this purpose. It is necessary for the security of the forms, so it works without consent.
- Sentry (Functional Software, Inc.): Application error monitoring: when an error occurs, it sends a technical description of the event, with e-mail addresses masked and without session recording. It does not store cookies. This tool is currently disabled and stores nothing.
- Google Tag Manager (Google): Google’s tag management script. It loads only with consent to analytics files and only if we enable it in the service settings. It does not store cookies itself.
- Stripe: Payments and setting up the payout account take place on Stripe pages, to which we redirect you; there, Stripe stores cookies under its own rules. The Stripe script does not load on Qerify pages.
- Embedded content: videos and calendars: Videos in profiles and projects (YouTube, Vimeo, Loom) and calendars for booking calls (e.g. Calendly, Cal.com) load from these providers’ servers only after you click; the provider may then store its own files in your browser. If a blog article contains an embedded video (YouTube, Vimeo), it loads together with the article.
You can change or withdraw your choice at any time with the “Cookie preferences” button in the page footer. Withdrawing consent turns off the analytics tools from the next page load; files already stored in your browser can be deleted in its settings. The “Marketing” option in the banner does not concern cookies: it is consent to e-mails with offers, described in the Privacy Policy.