Cookies

Plain-English summary

• We only use cookies that are strictly necessary to run the Service during beta.
• We do not set advertising cookies, cross-site tracking pixels, Meta Pixel, LinkedIn Insight Tag, or Google Analytics during beta.
• We honor the Global Privacy Control (GPC) browser signal as a "Do Not Sell or Share" request.
• We will update this page (and add a consent banner if needed) before we add any analytics or marketing cookies.
• Questions: privacy@rizedigital.io.

1. About this page

This page explains the cookies and similar technologies SEO Genius uses. It is meant to be read alongside our Privacy Policy and is referenced from the footer of every page of the Service.

2. What is a cookie?

A cookie is a small text file that a website saves on your browser. Cookies are commonly used to keep you signed in, remember your settings, and protect the site against certain kinds of attack. Some cookies are set by the site you are visiting (first-party). Some are set by other domains the site loads resources from (third-party).

Other technologies in the same family include:

• Local storage (data your browser saves locally, similar to a cookie but typically larger).
• Session storage (data your browser saves only for the duration of the browser tab).
• Pixels / tracking beacons (tiny images that report when a page or email is opened).

For simplicity, we use "cookies" in this page to cover all of these.

3. Cookies we set

Every cookie in the table below is set directly by SEO Genius (first-party) and is strictly necessary to run the Service. They are not used for advertising, profiling, or cross-site tracking.

If you reject or clear these cookies, the Service may not work for you: you will be signed out, dashboard layout will reset to default, and certain forms may not submit due to CSRF protection.

Classification note (v1 interim): sg-theme and sg-dashboard-layout are classified here as "strictly necessary" to match the Privacy Policy Section 13.1. Because we do not run a consent banner and these are first-party preference values only, this classification triggers no consent obligation during beta. Counsel may set the final classification before public publish.

4. What we don't set during beta

We have made an explicit decision to ship the beta without any of the following:

• No third-party advertising cookies (no DoubleClick, no AdRoll, no Criteo, no Outbrain, no Taboola).
• No cross-site tracking pixels (no Meta Pixel, no LinkedIn Insight Tag, no Twitter / X Pixel, no TikTok Pixel, no Pinterest Tag).
• No Google Analytics on the marketing site or the application during beta. If we add lightweight first-party analytics later (for example, Plausible or PostHog self-hosted), we will update this page first.
• No session replay tools (no FullStory, no Hotjar, no LogRocket).
• No A/B testing tools that drop persistent cookies.

This list is meant to be specific. If you find a cookie or tag on a SEO Genius page that does not appear in section 3 above and is not strictly necessary, please report it to privacy@rizedigital.io and we will investigate.

5. California (CPRA) disclosure

The California Privacy Rights Act (CPRA) treats certain third-party cookie behavior (for example, cookies that power cross-context behavioral advertising) as "sharing" of personal information, which triggers a "Do Not Sell or Share My Personal Information" disclosure requirement.

During beta, we do not "share" personal information through cookies. Section 4 above lists everything we have explicitly chosen not to set. Because we do not share for cross-context behavioral advertising, the CPRA "share" obligation is not triggered by cookies.

We still surface a "Do Not Sell or Share My Personal Information" link and a "Your California Privacy Rights" link in the footer of every page. Those links point to a confirmation that we do not sell or share personal information for cross-context behavioral advertising and to the California section of our Privacy Policy. The final links resolve when the Privacy Policy publishes alongside this page (per L6).

If we change our position in the future (for example, by adding LinkedIn Insight Tag for retargeting), we will:

1. Update this page and the Privacy Policy.
2. Implement a consent banner that defaults to "strictly necessary only."
3. Honor opt-outs (including via GPC, see section 6).
4. Announce the change in our next sub-processor change notice if a third party is involved.

6. Global Privacy Control (GPC)

The Global Privacy Control is a browser-level signal that tells websites a User does not want their personal information sold or shared. As of January 1, 2026, California, Colorado, Connecticut, and several other states require businesses subject to their privacy laws to honor the GPC signal as a valid opt-out request for sale and sharing.

Our position on GPC:

• We honor the GPC signal automatically. No additional click, banner interaction, or account setting is required from the User. When we detect a GPC signal on a public page, we visibly indicate that the opt-out preference has been processed (Privacy Policy section 6.8, dependent on the L6 visible-indicator work).
• Because we do not currently sell or share personal information for cross-context behavioral advertising, there is functionally nothing to opt out of at the cookie layer today.
• If we add any tracking that would constitute "sharing" under California or other state law in the future, GPC will continue to be honored automatically and the change will be disclosed on this page and the Privacy Policy first.

You can turn on GPC by using a browser or extension that supports it. A current list of GPC-supporting browsers and extensions is maintained at https://globalprivacycontrol.org/.

7. Controlling cookies in your browser

You can clear or block cookies at any time using your browser's privacy settings. The major browsers each provide instructions:

• Google Chrome: Clear, allow, and manage cookies in Chrome
• Mozilla Firefox: Clear cookies and site data in Firefox
• Apple Safari: Clear the history and cookies from Safari
• Microsoft Edge: Delete cookies in Microsoft Edge

Blocking or clearing the cookies in section 3 will sign you out and may break parts of the Service. Blocking strictly necessary cookies entirely will prevent you from using the Service.

8. Future changes

If we add cookies beyond the strictly necessary set in section 3 (for example, lightweight analytics, A/B testing, or marketing cookies), we will:

1. Update this page with the new cookie name, purpose, type, and duration.
2. Where the change is California-impacting (for example, anything that would constitute "sharing" under CPRA), add a consent banner that defaults to "strictly necessary only" and respects GPC.
3. For material changes, update the Privacy Policy and email active accounts.

Until then, this page reflects the full and accurate state of cookies set by SEO Genius.

9. Contact

Email: privacy@rizedigital.io

Questions about cookies, opt-out behavior, or this page in general are welcome. We respond within 5 business days.

Open verifications (before public publish)

• [date of first publication]
• Final Better Auth session cookie name
• Final CSRF cookie name
• Session duration against the Better Auth config
• California-section deep link (resolves when the Privacy Policy publishes)

END OF v1 INTERIM. Adopted for beta per N18. Counsel ratification deferred to post-scale.