Skip to main content

Cookie Policy

Last Updated: July 28, 2026

This Cookie Policy sets out how LoveKept, operated by Albatross Ecommerce LLC ("we," "us," or "our"), uses cookies and related technologies such as browser local storage. It covers what we keep, the reasons for it, and the ways you can control it. Think of it as a companion to our Privacy Policy, and read the two together.

1. What Are Cookies and Similar Technologies

A cookie is a small text file that a website saves to your device when you visit. We also make use of related browser features such as local storage, session storage, and IndexedDB, which let a site keep small amounts of data in your browser. Throughout this policy, "cookies" is our shorthand for cookies and these comparable technologies together. They keep the Service running, hold on to your preferences, and, where you permit it, gauge how the Service is used so we can make it better.

2. How We Ask for Your Consent

Essential cookies (Section 3.1) stay on at all times, since the Service simply cannot run without them. The functional storage in Section 3.2 and the first-party counters in Section 3.3 also work without the banner: they hold only your own details and choices, or a random number, and nothing in them goes to an analytics or advertising company. Analytics and advertising cookies (Sections 3.4 and 3.5), by contrast, are used only where we have a proper legal basis:

  • Visitors in the EEA and UK: Your browser's time zone tells us whether you are likely in the European Economic Area or the United Kingdom. When it does, we display a cookie banner and load no analytics or advertising cookies until you select "Accept." Selecting "Reject" keeps every analytics and advertising cookie off.
  • Visitors elsewhere: Analytics and advertising cookies may run by default to help us understand and improve the Service. You remain free to opt out at any point through your browser controls (see Section 5), and if your browser sends the Global Privacy Control signal we switch off advertising cookies automatically, wherever you are (see Section 6).

We record your decision in your browser's local storage under the key mt_cookie_consent, set to either "accepted" or "rejected." It is purely a functional preference and plays no part in tracking. Since the choice lives on a single browser and device, the banner may reappear on another browser or after you clear this site's data.

3. Categories of Cookies and Storage We Use

3.1 Strictly Necessary (Always Active)

These are essential for the Service to operate and cannot be switched off through our banner.

  • Authentication & session: Cookies from our authentication provider (Supabase) that keep you signed in and hold your session together securely.
  • Consent preference: The mt_cookie_consent local storage value that stores your cookie choice so that we can respect it.
  • Security & delivery: Cookies from our hosting and delivery provider (Vercel) that route requests, spread load, and help protect the Service.

3.2 Functional (Preferences and Convenience)

These remember choices you have made so the Service feels seamless between pages and visits. They are first-party, they contain no advertising identifiers, and no analytics or advertising company receives them.

  • Flower cart: The flower-cart local storage value holds the contents of your flower cart so it survives moving between pages. It stays until you empty the cart or place your order.
  • Flower order confirmation: A flowerOrder value in session storage carries your order summary to the confirmation page. Session storage lasts only as long as the browser tab, and we delete this value once your confirmation has been shown.
  • Guestbook comment details: If you comment on a photo without an account, we keep the name and email address you typed under tv.commenter.name and tv.commenter.email in local storage so you do not have to retype them next time. This is your own name and email stored on your own device; it leaves your browser only with a comment you choose to post, and you can clear it at any time through your browser settings.
  • Memorial builder draft: While you build a memorial, we may briefly stash your in-progress draft, including photos, in an IndexedDB database called lovekept-builder so that creating an account partway through does not lose your work. A saved draft is discarded after one hour.
  • Small flags and hints: A handful of small values remember one-time things, for example that you have already seen a welcome message or a photo-viewer hint, that you dismissed a particular offer, or the times of your recent AI obituary drafts so we can apply a fair usage limit (keys such as mt_preservation_welcome_*, tv.lightbox.coachmarked.v1, tree_upsell_declined_*, and obituary_generation_timestamps). None of these identify you. Our internal admin dashboard, which is not part of the public site, also sets a sidebar:state cookie for seven days to remember whether its sidebar is open.

3.3 First-Party Counters (Always Active, Never Shared)

Two random identifiers live in your browser's local storage to keep our counts honest. We generate them ourselves, no third party receives them, and we build no profile from them. Because they contain nothing personal and are never shared, they are not gated by the consent banner. Both stay until you clear this site's browser data.

  • tv_visitor_id: A random ID used to avoid double-counting memorial page views, so refreshing a page does not inflate a memorial's view counter. We fall back to it only when we have nothing else to count you by: if you are signed in we use your account, and where analytics run we reuse the analytics ID instead.
  • lovekept_fingerprint: A random value that records which guestbook messages you have appreciated, so each visitor counts once per message. It also accompanies guestbook messages posted without an account, which helps us prevent abuse.

3.4 Analytics (Consent-Gated)

These give us a picture of how the Service is used so we can improve it. They load only where permission allows, as Section 2 explains, and only when the relevant service has been configured.

  • PostHog (product analytics): Cookies and local storage from PostHog that count page views and feature usage. We route the requests through our own /ingest proxy, session recording is turned off, and PostHog loads only on our public site at lovekept.co, never on our admin subdomain, our staging site, or preview builds.
  • Google Tag Manager & Google Analytics: Where it is configured, Google Tag Manager can load tags such as Google Analytics, which set cookies (for instance _ga) to measure traffic and engagement.

3.5 Advertising Attribution (Consent-Gated, Off with GPC)

When an ad brings someone to LoveKept, we keep a first-party note of how the visit began so we can tell which advertising is worth paying for. Everything in this category follows the same consent rules as analytics (Section 2), and it is additionally switched off whenever your browser sends the Global Privacy Control signal (Section 6). If you rejected cookies through the banner, or your browser sends GPC, the record below is never written; under GPC, an existing record is not read either.

  • Google Ads: Where it is configured, a Google Ads tag may set cookies that gauge how well advertising campaigns are performing.
  • Reddit Ads: Where it is configured, a Reddit Pixel may set cookies that measure how well our Reddit advertising is performing. We do not send Reddit your email address, phone number, or name; a Reddit ad click is matched only by the click ID Reddit itself puts in the web address.
  • mt_attr cookie: A first-party cookie, kept for 90 days, recording how your first visit began: the page that referred you, the page you landed on, any campaign (UTM) parameters in the web address, any advertising click IDs in it (Google's gclid, wbraid, and gbraid, or Reddit's rdt_cid) along with the ad's match type, and a timestamp. It contains no name, no email, and no browsing history.
  • lovekept_attribution: A local storage copy of the same record, kept alongside the cookie so that if one is cleared the other can restore it.

4. Third-Party Cookies and Services

Certain cookies come from third parties that help us run the Service. During a purchase, our payment processor (Stripe) may set cookies on its own hosted checkout pages to handle the transaction securely and guard against fraud. Flower orders work differently: they are fulfilled by our flower partner (Florist One), whose payment processor (Authorize.net) runs a small script on our flower checkout page itself, so that the card details you enter travel directly from your browser to Authorize.net and never pass through our servers. Each of these third parties handles data under its own privacy and cookie policies:

5. How to Manage or Change Your Choices

  • Change your consent choice: Once you have accepted or rejected analytics and advertising cookies, you can start over by clearing this site's data in your browser, or just the mt_cookie_consent local storage value. Eligible visitors then see the cookie banner again on their next visit and can choose anew.
  • Browser controls: Most browsers include settings to block or delete cookies and wipe local storage. Keep in mind that blocking the strictly necessary cookies may stop you from signing in or using core features.
  • Opt-out tools: Google's browser add-on lets you opt out of Google Analytics, and Google's Ads Settings let you manage your advertising preferences.
  • Global Privacy Control: Turn on GPC in a supporting browser or extension and we treat it as an automatic opt-out of the advertising cookies in Section 3.5, with no banner interaction needed (see Section 6).

If you would like help adjusting your preferences, contact us at support@lovekept.co.

6. Do Not Track and Global Privacy Control

Some browsers send a "Do Not Track" (DNT) signal. Because the industry never settled on a consistent standard for handling DNT signals, we do not treat them differently for now, relying instead on the consent mechanism and controls set out above.

The newer Global Privacy Control (GPC) signal is different: we honor it. When your browser sends GPC, we treat it as an automatic opt-out of advertising measurement. Neither the Google Ads tag nor the Reddit Pixel loads, and the attribution record described in Section 3.5 is neither written nor read, even if it was captured before you turned GPC on. We apply this to every visitor, not only where the law requires it. GPC does not change the strictly necessary, functional, or analytics categories, which follow the rules in Sections 2 and 3. We neither sell your personal information nor share it for cross-context behavioral advertising.

7. Changes to This Policy

We may revise this Cookie Policy now and then to reflect shifts in the technologies we use or for legal or operational reasons. The current version always appears on this page with an updated effective date. We handle material changes in line with the notice practices set out in our Privacy Policy.

8. Contact Us

For questions about this Cookie Policy, reach us here:

Email: support@lovekept.co

Operator: Albatross Ecommerce LLC

Back to HomePrivacy PolicyTerms of Service