Cookie Policy

Cookies are small text files stored on your device when you visit a website. Similar technologies include local storage, session storage, pixels or analytics scripts, software development kits (SDKs), device identifiers, and server or security logs. These technologies help websites and apps remember preferences, keep sessions secure, measure performance, and deliver features you use.

Depending on how you use the Services, we may use:

• Cookies: small files placed on your browser for session management, security, preferences, or analytics where applicable.
• Local storage: data stored in your browser for longer than a session cookie, such as site preferences on rankk.me.
• Session storage: temporary browser storage cleared when you close the tab or browser, where used.
• Pixels or analytics scripts: code that helps us understand aggregated usage, performance, and reliability.
• SDKs or device identifiers: in app contexts where available, technologies that support authentication, analytics, crash reporting, security, or core app functionality.

We use essential and preference storage to operate the Services and remember choices you make, including:

• Theme preference: stored under the key rankk-theme in localStorage (light or dark mode on rankk.me) and mirrored in a same-named first-party cookie so the first paint can match your choice. When unset, appearance follows your device or browser setting.
• Accent color preference: stored under the key rankk-accent in localStorage (your chosen brand accent color on rankk.me) and mirrored in a same-named first-party cookie for first paint.
• Authentication, session, and security: where you use account sign-in or verification features, technologies that help keep sessions secure and protect the Services.
• OTP and abuse prevention: when you verify email or phone for early access or similar flows, session, security, and logging mechanisms may be used to deliver codes, prevent abuse, and protect the Services.

If you block or clear essential or preference storage, rankk.me may not remember your theme or accent preferences, and some features may not work as expected.

We may use analytics and performance tools to understand aggregated traffic, how visitors and users interact with the Services, and how we can improve reliability and product quality. On rankk.me, this may include website analytics in production to measure page views and general usage patterns.

Analytics data is used for understanding performance and improving the Services. It is not used to sell your personal information.

Vercel Web Analytics on rankk.me is cookie-free. It is separate from the optional first-party attribution cookies described below and is not controlled by the Privacy choices setting for those cookies.

With your choice, Rankk may set first-party cookies on rankk.me to understand how people arrive at the site and which marketing efforts work. These cookies are first-party (set by Rankk on rankk.me) and are optional.

• rankk-fp-visitor-id: anonymous visitor identifier; retained for about 1 year.
• rankk-fp-session-id: session identifier; retained for about 8 hours.
• rankk-privacy-preferences: stores your privacy choice for optional attribution (accepted or declined); retained for about 12 months. This preference cookie does not contain visitor IDs, session IDs, email, or profile IDs.

If you create a Rankk consumer account later, attribution evidence collected while your preference was accepted may be linked to that account so Rankk can understand acquisition. Declining stops future capture, removes the attribution cookies, and prevents new identity linking based on those cookies. Records already stored remain subject to Rankk's retention schedule and privacy-request handling.

Planned retention for raw attribution evidence: paid click identifiers about 30 days; landing and session evidence about 90 days; normalized reporting data may be kept longer as described in Rankk's internal attribution documentation.

You can Allow or Decline optional analytics from the on-site banner (when no choice is stored yet) or from the Privacy choices control in the site footer. Changing from accepted to declined stops future beacons and expires the attribution cookies.

If your browser sends a Global Privacy Control (GPC) signal, Rankk will not use optional first-party attribution while that signal is active. Rankk does not treat the older Do Not Track (DNT) browser signal as an automatic block for this optional feature; GPC is the privacy signal Rankk honors for first-party attribution. Browser cookie settings can still clear or block cookies at any time.

Our Contact and Feedback features allow you to send messages and, optionally, attach a screenshot. Screenshots are not cookies, but support and feedback workflows may involve storage, security, and logging technologies to process your submission, protect the Services, and route your request to our team.

Optional screenshots may be stored in private storage and shared internally through temporary signed links. For more detail on personal information involved, see our Privacy Policy.

If you choose to connect financial accounts, use crypto wallet features, or purchase subscriptions or other paid features where available, third-party financial account-linking providers, payment infrastructure, or related services may set or use their own cookies, SDKs, or similar technologies as part of those flows.

We do not control all third-party technologies used in those flows. Their practices are described in their own policies. Rankk only receives information from those flows as described in our Privacy Policy and as needed to provide the features you choose to use.

We do not currently use cookies to sell your personal information or to operate cross-site advertising on rankk.me. If our practices change, we will update this Cookie Policy and, where required, provide additional notice or choices.

Most browsers let you block or delete cookies and clear local or session storage through settings. If you block essential or preference storage, parts of rankk.me may not remember your theme or accent preferences, and some features may not function as intended. Blocking analytics may limit our ability to measure site performance but generally will not prevent you from browsing rankk.me.

For optional first-party landing attribution, use Privacy choices in the footer (or the banner when no choice is stored yet) to Allow or Decline. Declining removes the attribution cookies and stops future collection for that preference.

For more about how we handle personal information and privacy rights, see our Privacy Policy.

In addition to browser settings on rankk.me, the Rankk app (where available) may offer device or in-app settings that affect analytics, notifications, or certain technologies. Mobile operating systems may also provide controls for advertising identifiers or app tracking, depending on your device and version.

Because controls vary by browser, device, and platform, we cannot guarantee that every technology can be disabled individually. If you have questions, contact us using the details below.

We may update this Cookie Policy from time to time. We will post changes on rankk.me and update the "Last updated" date on this page. If changes are material, we may provide additional notice where required by law.

Questions about this Cookie Policy? Contact Rankk Labs LLC at support@rankk.me or through our Contact page.