Skip to content

Cookie Policy

How we use cookies and similar technologies on Fostera.

Last updated

On this page

You can review or withdraw optional consent here at any time, whether or not you are signed in. Browser controls are also available as described below.

1. Introduction

This Cookie Policy explains how we use cookies and similar technologies when you visit or use Fostera. It covers our website, Progressive Web App (PWA) features, and related storage on your device.

2. Cookies and web storage

Besides cookies, we may use:

  • Local and session storage
  • IndexedDB
  • Cache storage (PWA and offline use)

3. How we use them

  • Remembering theme and consent preferences
  • Keeping you signed in and securing sessions where applicable
  • Preventing abuse of free trials and credits: an essential fostera_device cookie holds a random identifier, kept for up to two years and through sign-out, so we can recognize several accounts created on the same device (see the Privacy Policy)
  • Understanding usage and improving the product (with Analytics consent, or in the United States until you opt out; see Analytics delivery)
  • Enabling install, offline use, and push notifications when you opt in
  • Finding and fixing faults (error reports and performance measurements, which do not depend on consent; see section 6)

4. Types of cookies and storage

  • Essential: required for security, authentication, and core functionality.
  • Preferences: remembers choices such as theme and UI settings.
  • Analytics: helps us understand how the service is used (subject to your consent where required).
  • Marketing: used only if you consent, for relevant communications or ads.
  • OpenAI Ads pixel (Marketing): if you allow Marketing cookies, Fostera loads OpenAI's advertising pixel. When you arrive from an OpenAI ad it sets a cookie named __oppref that holds the ad click id, so we can measure which ads led to sign-ups and purchases. It is never set without Marketing consent. It does not load for signed-in users under 18, and we never report sign-ups or purchases by anyone under 18. A Global Privacy Control signal from your browser turns it off.
  • Ad campaign label (first-party): if you arrive from one of our ChatGPT ads, the page address carries a campaign label. We keep that label in your browser's tab storage, and for up to 10 minutes in a cookie named fostera_ad_src while you sign in with Google, then attach it to your sign-up record so we can count how many sign-ups a campaign produced. It holds no personal information, is used only for those aggregate counts, and is never shared. A Global Privacy Control signal from your browser turns it off.
  • PWA: service workers, caches, and manifest data for install and offline behavior.

5. Analytics delivery

When you grant Analytics consent, Fostera may load the Google Analytics 4 tag and send content-reduced, app-owned events. The tag is enabled only after Google's automatic measurements and user-provided-data detection are disabled for the stream. If the browser collector is unavailable—or when Marketing-only consent permits a limited conversion event—your browser sends the reduced event to Fostera and our server rechecks your consent before using Google's Measurement Protocol. Neither path includes raw query strings, fragments, document titles, referrers, or private Soul, project, conversation, or memory identifiers. No Google analytics script or direct Google request is created in your browser before Analytics consent, and events are marked non-personalized when Marketing consent is not granted.

Fostera also counts page visits with Vercel Web Analytics, a cookie-free measurement service from our hosting provider. For each page you open it records the page path with account, Soul, project, conversation, and memory identifiers removed, the website that referred you, your approximate location derived from your IP address, and your browser, operating system, and device type. It sets no cookies and stores nothing on your device. Vercel states that it counts unique visitors with a hash of your request that it resets daily, so visits cannot be linked across days or websites.

In the United States this page-visit count runs unless you opt out: choose Reject optional in the cookie banner, save your Cookie settings with Analytics Cookies off, or send a Global Privacy Control signal from your browser. Everywhere else, and for signed-in users under 18 or whose age is not yet confirmed, it runs only after you grant Analytics consent. Other analytics events sent to Google or Vercel require Analytics consent, except the limited conversion events described above, which can be sent to Google with Marketing consent alone.

6. Error reports and performance measurements

Error reports and our own performance measurements, described in Section 2 of our Privacy Policy, are not controlled by the cookie banner. They set no cookies. While a tab is open they keep up to three short entries in that tab's session storage: one, written when reporting loads, that keeps a recording together as you move between pages; one that lets the chat report a page your browser closed unexpectedly; and one that remembers you opened a Soul's private mode or your privacy settings, so reporting and measurement from your browser stay off for that tab. Your browser clears session storage when the tab closes.

7. Managing preferences

You can control cookies through your browser. For the PWA, you can uninstall the app, disable notifications in system or browser settings, and clear site data from your browser.

Disabling some storage may limit features such as staying signed in, offline mode, or notifications.

8. Changes

We may update this policy from time to time. The “Last updated” date at the top of this page shows when it last changed; material changes will be reflected on this page.

9. Contact

Questions about cookies or this policy: reach out on our contact page.