This Cookie Policy explains how Realvore uses cookies and similar technologies on our public site and authenticated application. It should be read together with our Privacy Policy.
1. What cookies and similar technologies are
Cookies, local storage, SDKs, and similar technologies store or read information on your browser or device. We use them to keep Realvore working, remember choices, improve reliability, and, where accepted, understand product usage.
2. Cookie and storage inventory
This inventory covers the technologies currently used by our public website, authenticated web application, and native apps. “Necessary” means the technology supports authentication, security, preferences, feature delivery, reliability, or core app state and is not controlled by the optional analytics choice. “First party” describes where the cookie or storage is placed; a named service provider may still manage it for us. In the Heap names below, APP_ID is replaced by the Heap environment identifier.
| Name/key | Provider | Purpose | Necessary or optional | Storage duration | First or third party |
|---|---|---|---|---|---|
affinity (cookie) | Realvore hosting platform | Keeps requests routed to the same application instance. | Necessary | 2 days | First party |
auth-session (cookie) | Realvore authentication service | Stores a signed, opaque session identifier for web sign-in. Authentication tokens remain server-side. | Necessary | 30 days from the latest session save | First party |
cookie-consent (cookie) | Realvore | Records whether optional analytics were accepted or rejected on the website. | Necessary | 180 days from the latest choice | First party |
service-token (session storage) | Realvore | Temporarily caches the access token used by the authenticated web application. | Necessary | Until the browser tab or window session ends; also removed on sign-out or when invalid | First party |
auth-logout-event (local storage) | Realvore | Notifies other open tabs that sign-out occurred. The value is a timestamp and random event marker. | Necessary | Until overwritten or browser storage is cleared | First party |
selected-household (local storage) | Realvore | Remembers which household the user selected. | Necessary | Until changed or browser storage is cleared | First party |
meal-plan-shopping-list-preview (local storage) | Realvore | Preserves temporary shopping-list selections and quantity changes while a list is being prepared. | Necessary | Until the list is created, another meal plan is opened, or browser storage is cleared | First party |
scroll-restoration:<container>:<history-entry> (session storage) | Realvore | Restores list position and loaded-item count when navigating within the application. | Necessary | Until the browser tab or window session ends | First party |
cookie-consent (Capacitor Preferences) | Realvore, using Capacitor Preferences | Records whether optional analytics were accepted or rejected in the native app. | Necessary | Until the choice is changed, app data is cleared, or the app is removed | First-party app storage |
com.realvore.authentik / auth_state (Android private app preferences) | Realvore authentication service | Maintains the native Android OpenID Connect sign-in state and tokens. | Necessary | Until sign-out, app data is cleared, or the app is removed | First-party app storage |
com.realvore.authentik / com.realvore.ios-auth-state (iOS Keychain) | Realvore authentication service | Maintains the native iOS OpenID Connect sign-in state and tokens in the device Keychain. | Necessary | Until sign-out or the device's Keychain data is erased | First-party app storage |
_hp2_id.APP_ID (cookie) | Heap | Stores Heap's user identifier, identity, and related identifiers after analytics consent. | Optional | 13 months minus 1 day | First-party cookie managed by Heap |
_hp2_ses_props.APP_ID (cookie) | Heap | Stores Heap session properties, including a timestamp and cookie domain/path. | Optional | 30 minutes | First-party cookie managed by Heap |
_hp2_props.APP_ID (cookie) | Heap | Stores event properties used by Heap analytics. | Optional | 13 months minus 1 day | First-party cookie managed by Heap |
_hp2_hld. (cookie) | Heap | Temporarily checks the highest domain on which Heap can set its first-party cookies. | Optional | Temporary; should not persist | First-party cookie managed by Heap |
ld:<client-side-environment-id>:$diagnostics (local storage) | LaunchDarkly | Stores SDK diagnostic counters and the last diagnostic reporting time for feature-flag reliability. | Necessary | Until overwritten by the SDK or browser storage is cleared | First-party storage managed by LaunchDarkly |
No persistent browser or device-storage key (current Sentry configuration) | Sentry | Operational error monitoring. Session Replay, offline event storage, and browser tracing storage are not enabled. | Necessary | Not applicable | No client-side storage |
3. Optional analytics cookies
We use Heap for optional product analytics to understand feature usage and improve the service. The Heap SDK is first initialized only if you select Accept in the cookie banner or cookie preferences dialog. Depending on the features used during a visit, not every Heap cookie listed above will necessarily be present.
If you reject analytics before Heap is initialized, Heap cookies are not created by our app. If you withdraw consent after previously accepting, we disable future analytics tracking and reset the Heap identity, but existing Heap cookies may remain until they expire or you clear them in your browser.
4. Necessary feature delivery and error monitoring
LaunchDarkly supplies feature flags used to deliver and safely roll out application functionality. The contexts we provide already contain an explicit key, so the SDK does not need to create its optional anonymous-user ID storage key. It does store the diagnostics entry listed above.
We use Sentry for operational error monitoring and reliability. Sentry is used to identify crashes, performance issues, and technical failures. It is not used for behavioural analytics. With our current configuration, Sentry does not set a cookie or persistent browser/device-storage key, and Session Replay is not enabled.
We configure Sentry to avoid collecting recipe content, allergy data, passwords, payment details, or form field contents unnecessarily.
5. Changing your choice
You can reopen Cookie preferences at any time from the footer on the website or in the app. If you withdraw consent, future Heap analytics tracking stays disabled. You can also remove stored browser data using your browser settings. Removing necessary storage may sign you out, forget app choices, or prevent parts of the service from working as expected.
6. More information
For more detail about how we handle personal data, read our Privacy Policy. For the rules that govern the service, read our Terms of Service. Food, nutrition, allergy, and AI-assisted information is covered by our Disclaimer.