Cookie Policy

1. What Is a Cookie

A cookie is a small text file that a site you visit saves in your browser. In this policy, the browser's local storage areas (localStorage, sessionStorage) are treated like cookies. First-party cookies are written by riseluc.com; third-party cookies and tools are entries written or loaded by another company.

This policy describes the cookies used by the company that provides the Riseluc service, as data controller; the company's identity and contact details are in the Data Controller section of the KVKK Privacy Notice.

2. Categories and Legal Grounds

We use cookies in four categories. Essential and functional cookies do not require consent; analytics and marketing cookies run only with your explicit consent, and the two are switched on and off together with a single consent (there is currently no option to choose them separately). Data collected with Google's and Meta's tools may be transferred to servers in the United States and the European Union.

• Essential: signing in, security and remembering your cookie choice. No consent required; the legal grounds are the establishment and performance of a contract (KVKK Art. 5(2)(c)) and legitimate interest (Art. 5(2)(f)).
• Functional: remembering a choice you made (language, the store selected in the dashboard, theme, menu layout, an information strip you closed) and that you arrived through a referral or partner link. No consent required; the legal grounds are Art. 5(2)(c) and Art. 5(2)(f).
• Analytics: measuring how the site is used. Only with your explicit consent (Art. 5(1)).
• Marketing: measuring the results of our ads. Only with your explicit consent (Art. 5(1)).

3. How the Cookie Banner Works

• On your first visit, the cookie banner opens at the bottom of the page. The "Necessary" and "Accept" buttons are the same size and side by side; refusing is as easy as accepting.
• Until you make a choice, no analytics or marketing script is loaded and no measurement signal is sent; using the site without choosing does not count as consent.
• If you choose "Accept", your choice is written to the va_consent cookie for 1 year and the page reloads. From then on, Riseluc's own measurement, Google Analytics and the Meta Pixel run; in Google's consent mode, analytics and ad storage are granted.
• If you choose "Necessary", your choice is also remembered for 1 year; no analytics or marketing script is loaded and these cookies are not written.
• Even with your consent, Google Analytics and the Meta Pixel are not loaded on the admin panel, the partner dashboard, the sign-in, sign-up and password pages, or the payment, card and billing details pages.
• Query parameters other than campaign tags, and the part of the address after #, are removed from the page address sent to Google Analytics.
• You can change your choice at any time with the "Cookie preferences" link in the site footer: the link deletes the va_consent cookie and opens the banner again. Google and Meta cookies written earlier are not deleted by this link; you can delete them in your browser settings. After you withdraw consent, no new data is sent with these cookies.

4. Cookies We Use

Each line gives the cookie's name, provider, category, purpose and duration.

• sb-…-auth-token (split into .0, .1 parts if needed; the … is the project ID): Riseluc, first party (Supabase session infrastructure). Essential. Keeping your signed-in session open and secure. Up to 400 days; deleted when you sign out.
• sb-…-auth-token-code-verifier: Riseluc, first party (Supabase). Essential. Verifying that the request comes from you during email-link sign-in, email confirmation and password reset. Deleted when the sign-in step is completed.
• va_consent: Riseluc, first party. Essential. Remembering your cookie choice (accept or necessary only). 1 year.
• riseluc_partner_preview: Riseluc, first party. Essential. For Riseluc administrators only: a read-only preview of the partner dashboard. 8 hours.
• NEXT_LOCALE: Riseluc, first party. Functional. Remembering the language you chose, opened through the address or saved in your account. 1 year.
• riseluc_active_store: Riseluc, first party. Functional. Remembering the store you last selected in the dashboard. 1 year.
• riseluc_trial_strip_hidden, riseluc_activation_hidden: Riseluc, first party. Functional. Not showing the trial and getting-started strips you closed again on the same day. 26 hours.
• verimle_ref: Riseluc, first party. Functional. If you arrived through a referral link, keeping the referral code and arrival time so the referral discount can be applied to your account. 30 days; deleted once used in your account.
• verimle_partner: Riseluc, first party. Functional. If you arrived through a partner link, keeping the partner code and arrival time so the partner discount can be applied and your account linked to that partner. 30 days; deleted once used in your account.
• va_anon: Riseluc, first party. Analytics (only with consent). A random ID that distinguishes the browser in our own measurement; the IP address and full browser string are not stored. 1 year.
• va_signup: Riseluc, first party. Analytics. Counting the registration event once when you sign up; it carries only the sign-up method (email or Google). It is written regardless of your cookie choice, but without your consent it is deleted without any measurement signal being sent. 5 minutes for Google sign-up and up to 7 days for email sign-up; deleted on the first page you open other than the sign-in and sign-up pages.
• _ga and cookies starting with _ga_: Google (Google Analytics), third-party tool, on the riseluc.com domain. Analytics (only with consent). Aggregate statistics of site usage and measuring the results of our Google ads. 2 years.
• _fbp: Meta (Meta Pixel), third-party tool, on the riseluc.com domain. Marketing (only with consent). Measuring the results of our ads; reporting page-view, registration and subscription events to Meta. 90 days.

5. Other Third-Party Cookies

Depending on the current version of their tools, Google and Meta may write other cookies too; for example, if you arrived by clicking an ad, cookies that keep the click ID (those starting with _gcl_, and _fbc). These cookies are also written only by scripts loaded with your consent; their names, durations and purposes are in the cookie policy of the company concerned.

Some cookie and storage names carry the brand's former name (verimle); they were deliberately kept because changing them would delete your saved preferences.

6. Browser Storage

The site's service worker does not cache page content; it is used only so that you can install the site as an app and so that the push notifications you switch on in the dashboard can be shown. The other entries kept in your browser are:

• verimle:theme (localStorage). Functional. Remembering the light or dark theme you chose in the dashboard. Until you delete it.
• verimle:sidebar-collapsed, verimle:sidebar-closed-sections, riseluc:sidebar-favorites (localStorage). Functional. The collapsed state of the dashboard menu, the menu sections you closed and your favourites. Until you delete them.
• riseluc-motion-paused (localStorage). Functional. Your choice to pause animations on the site. Until you delete it.
• verimle:exit-intent (localStorage). Functional. Showing the information window that appears when you leave the site at most once a week; it holds only the time it was last shown. Until you delete it.
• riseluc-motion-tier (sessionStorage). Functional. Switching to a lighter view for that tab if your device struggles with animations. Until the tab is closed.
• riseluc:last-dashboard-path (sessionStorage). Functional. Adding the dashboard page a support request came from when you create one. Until the tab is closed.
• va_sid (sessionStorage). Analytics (only with consent). Grouping page views in the same tab as one session in our own measurement. Until the tab is closed.
• verimle_purchase_tracked (sessionStorage). Analytics. Making sure a purchase event is not counted twice when the page is reloaded; its value is only "1". It is written regardless of your cookie choice, but without your consent no purchase event is sent. Until the tab is closed.

7. Third-Party Page Components

• Sign in with Google: the Google button on the sign-in and sign-up pages is loaded from Google's servers. Google receives your IP address and browser information at that point and uses its own cookies if you are signed in to your Google account. Because it is needed to sign in and sign up, the button loads regardless of your cookie choice.
• iyzico payment form: at the payment and card update step, iyzico's payment form or payment page opens; iyzico may use its own cookies or browser storage. These are subject to iyzico's policy.
• Cloudflare Turnstile: when bot protection is switched on for sign-in, sign-up and password actions, Cloudflare's verification tool is loaded from Cloudflare's servers; Cloudflare processes technical information about your browser for the verification.

8. Managing Your Preferences

• The "Cookie preferences" link in the site footer opens the banner again; your new choice applies from the next page load.
• You can delete or block cookies and site data in your browser settings. If you block essential cookies you cannot sign in; if you delete functional entries, your language, theme and dashboard preferences are reset.
• Riseluc's own analytics records are deleted after 180 days. Google and Meta apply their own retention periods.

9. Riseluc Radar Extension

The Riseluc Radar browser extension does not use cookies and makes no network requests. It keeps the values you enter only in your browser's extension storage; details are in the privacy section of the Radar page.

• Riseluc Radar privacy

10. Contact

For questions and requests under Article 11 of the KVKK: info@riseluc.com. Details of the processing of personal data are in the KVKK Privacy Notice and the scope of explicit consent is in the Explicit Consent Notice.

• KVKK Privacy Notice
• Explicit Consent Notice
• Privacy Policy