Cookie Policy

1. Introduction

This Cookie Policy explains how Ollify LLC ("Ollify," "we," "us," or "our") uses cookies and similar technologies when you use the Ollify platform and related services (collectively, the "Service"). It describes what cookies are, why we use them, which specific cookies we use, and what choices you have.

This Cookie Policy is incorporated into and should be read alongside our Privacy Policy at ollify.app/legal/privacy. Together, they describe how we collect and use information about you. Questions about this policy can be directed to privacy@ollify.app.

Cookies are small text files placed on your device when you use a website or application. They help the service remember information about your session — such as keeping you logged in and protecting against security threats. We do not use cookies for advertising or behavioral tracking. Our cookie usage is limited to what is strictly necessary to operate the platform securely, plus a small number of functional preferences stored locally in your browser. Every cookie used by Ollify is listed in this policy; see Section 3 for how we describe local browser storage.

1.1 Where This Policy Applies: Marketing Site vs. the App. This policy covers two different parts of the Service, which work differently.

The public marketing site (ollify.app pages you can visit without logging in) displays a cookie consent banner the first time you visit, with options to Accept All, Reject Non-Essential, or Manage your choices. A standing "Cookie preferences" link in the footer lets you reopen this banner at any time. Your choice is remembered in your browser and is tied to the version of this Cookie Policy you were shown — if we publish a materially updated version, the banner will show again.

The logged-in app (the Ollify platform itself, once you have an account) does not show a cookie banner. Your business already accepted the Terms of Service, Privacy Policy, and — by reference — this Cookie Policy when your account was created. The app sets only the strictly necessary cookies listed in this policy. Rejecting cookies on the marketing site has no effect on the app — they are governed separately. The app's Olli assistant asks for your agreement separately before it sends your messages to our AI provider; that request is about sharing your messages, not about cookies, and is described in our Privacy Policy.

2. Strictly Necessary Cookies

Strictly necessary cookies are required for the Ollify platform to function. Without these cookies, you cannot log in, use the Service, or be protected from security threats. Because they are essential to the operation of the Service, these cookies cannot be disabled through our platform. You may block them in your browser settings, but doing so will prevent the Service from working correctly.

3. Functional Browser Storage (localStorage / sessionStorage)

In addition to cookies, the Ollify platform uses your browser's localStorage and sessionStorage to store certain preferences and draft data locally on your device. This is different from cookies — these values are stored only in your browser and are not transmitted to Ollify's servers automatically with each request. They do not track you across websites and are not accessible to third parties. The table below covers the storage items that most directly affect your experience. Ollify also stores a number of smaller interface-state preferences the same way — for example, whether you've dismissed a notice, collapsed a panel, pinned a shortcut, or left in-progress text in a form field — so the interface remembers your choices between visits. These are functional only, never leave your browser, and are not used for tracking.

These browser storage values remain on your device until you clear your browser's local storage (through your browser settings) or until they expire. Clearing your browser storage will reset your theme and preference settings. Your form drafts will also be lost if you clear storage while a draft is active.

4. Third-Party Service Cookies

The Ollify platform integrates with third-party services that may set their own cookies when you use related features. These cookies are set by the third-party service, not by Ollify, and are subject to each service's own privacy policy. We describe these cookies below so you know what to expect.

Ollify does not control these third-party cookies and is not responsible for the data practices of Mapbox or Stripe. If you have questions about how these services use cookies, please review their respective privacy policies at the links above. Our AI provider for Olli, Anthropic, receives Olli messages from our servers rather than from your browser and does not set cookies on your device.

5. Analytics and Advertising Cookies (Two Separate Categories)

If and when Ollify adds any analytics or marketing technology in the future, we will:

• Update this Cookie Policy at least thirty (30) days before activating the new technology.

• Display a cookie consent banner to all users, clearly describing the new cookies and their purpose.

• Obtain your explicit consent before setting any non-essential cookies.

• Provide a straightforward opt-out mechanism.

• Send an email notification to account holders.

• If any such technology includes session replay, heatmap, or screen-recording capability, customer data fields will be masked at the point of capture so that sensitive content is never transmitted to the third-party tool.

6. Your Choices

You have several options for controlling cookies, though some choices will affect how the Service works.

Cookie Preferences Panel (Marketing Site)

On the marketing site, click "Cookie preferences" in the footer at any time to reopen the preferences panel. There you can turn each of the four categories on or off individually — Strictly Necessary (always on, cannot be disabled), Functional, Analytics, and Advertising — and save your updated choice, which is remembered in your browser going forward.

6.1 Browser Cookie Settings. Most web browsers allow you to control cookies through your settings. You can typically:

1. (a)

   view all cookies set by websites you visit;

2. (b)

   delete existing cookies;

3. (c)

   block new cookies from being set; and

4. (d)

   set preferences for specific websites.

Refer to your browser's help documentation for instructions:

• Chrome: Settings > Privacy and Security > Cookies and other site data

• Firefox: Settings > Privacy & Security > Cookies and Site Data

• Safari: Settings > Privacy > Manage Website Data

• Edge: Settings > Cookies and site permissions

6.2 Browser localStorage and sessionStorage. You can clear your browser's local storage and session storage through your browser's developer tools or privacy settings. Clearing local storage will reset your theme preferences, map preferences, and notification sound settings, and will delete your saved Olli conversation. It does not withdraw your agreement to use Olli, which Ollify also records on its servers; to withdraw it, turn Olli off in your Profile. Clearing session storage during an active session will discard any unsaved form drafts.

6.3 Do Not Track. Some browsers support a "Do Not Track" (DNT) signal that tells websites not to track you. Because we do not currently use analytics or advertising cookies, our tracking practices do not change based on whether your browser sends a DNT signal — we respect your privacy the same way regardless. On the marketing site, our cookie preferences panel also treats a DNT signal the same way as a GPC signal (see Section 6.4): it keeps the Advertising category off by default and tells you it received the signal.

6.4 Sale, Sharing, and Global Privacy Control (GPC). Ollify does not sell or share your personal information, as those terms are defined under California and other state privacy laws — including for cross-context behavioral advertising — whether collected through cookies or otherwise.

Some browsers and browser extensions send a Global Privacy Control (GPC) signal, which communicates a request to opt out of the sale or sharing of personal information. Because Ollify does not sell or share personal information in the first place, honoring a GPC signal does not change how we treat your data — the opt-out you are requesting is already the case for everyone, with or without the signal. On the marketing site, when your browser sends a GPC signal, our cookie preferences panel keeps the Advertising category off by default, even if you select Accept All, and tells you it received the signal. You can change that choice in the panel. If we ever sell or share personal information, we will treat GPC signals as a valid opt-out request under applicable law.

6.5 Third-Party Cookie Controls. To opt out of cookies set by Mapbox or Stripe, please refer to their respective privacy policies and opt-out mechanisms:

• Mapbox opt-out: mapbox.com/legal/privacy

• Stripe opt-out: stripe.com/privacy

7. Changes to This Cookie Policy

We may update this Cookie Policy from time to time to reflect changes in our cookie usage, the technologies we use, or applicable law. When we make material changes — including adding any new category of cookies or activating analytics or marketing technologies — we will:

• Post the updated Cookie Policy at ollify.app/legal/cookie-policy with a new "Last Updated" date at least thirty (30) days before the change takes effect.

• Send an email notification to the email address associated with your account.

• Display an in-app notification.

• For non-essential cookies: display a cookie consent banner and obtain your consent before activating.

For minor changes (such as correcting a typo or clarifying an existing description without changing our actual practices), we may update this policy without advance notice.

8. Contact Us

If you have questions about this Cookie Policy, the cookies we use, or your choices, please contact us:

FULL COOKIE AND STORAGE REFERENCE

The table below lists every cookie used by the Ollify platform as of the Last Updated date, along with the local storage and session storage items that most directly affect your experience. Every item in the Strictly Necessary and Functional categories is first-party, set directly by Ollify. Every item in the Third-Party category, by definition, is set by that named third party (Mapbox or Stripe), not by Ollify. It does not separately list every smaller interface-state preference described in Section 3.