Paw & Story

Paw & Story — Cookie Policy

Version 2.0 — Effective: 2026-07-20

The short version: Paw & Story sets no cookies. We load no analytics, no advertising pixel, no social buttons and no third-party scripts of any kind. The only thing we keep in your browser is one small entry that lets you reopen your own tribute. This policy explains exactly what that is, and the two places where another company is involved.

1. Who is responsible

The data controller is Egységmester Kft., registered seat 2330 Dunaharaszti, Gyóni Géza köz 8., Hungary (company reg. no. 13-09-162959, registry court: Budapest Környéki Törvényszék Cégbírósága, EU VAT no. HU24291608). Contact: hello@pawandstory.com. For how we handle personal data more broadly, see our Privacy Policy.

2. What this policy covers

A cookie is a small text file a website stores in your browser so it can remember something between page loads. The ePrivacy rules cover not just cookies but any storing of or access to information on your device — including local storage. So this policy covers both, and it is local storage rather than cookies that we actually use.

3. Cookies we set: none

We set no cookies whatsoever on pawandstory.com — not for sessions, not for security, not for preferences, and not for measurement. Earlier versions of this policy described session, CSRF and analytics cookies; the Service does not set them, and we have corrected this page to say so.

4. The one thing we do store: your tribute key

When you create a tribute, we save a single entry in your browser's local storage, named paw_owner_ followed by your project's number. It holds a random key that acts as proof that this browser is the one that created that tribute, so that only you can open it. Without it you would lose access to your own memorial page and downloads.

5. Stripe's cookies, on Stripe's page

When you pay, you are taken to a checkout page operated by Stripe Managed Payments (the seller and merchant of record is Sold through Link, LLC, a Stripe company; Stripe Payments Europe, Ltd. acts as the payment processor). Stripe sets its own cookies there to process the payment securely and to prevent fraud. Those are Stripe's cookies on Stripe's page, governed by Stripe's cookie and privacy notices, not ours. We do not embed Stripe scripts into our own pages to track you.

6. Error reports we receive (no cookies involved)

So that we can find and fix faults, your browser sends a report to our own error-monitoring server at errors-c7f31a.practicalapps.studio when something goes wrong, and for roughly one page view in ten. The report contains the address of the page and technical details of the error. It sets no cookie and reads nothing from your device; tokens, cookies, request contents and program variables are stripped out before it is sent, and we never record your screen. The server is operated by us, not by an outside analytics company. You can object to this processing at any time — see Section 7 of the Privacy Policy.

7. What we do NOT use

8. How to control what is stored

You can clear or block site data — including local storage — in your browser settings at any time, and you can browse the public parts of the site with it blocked. Because the entry described in Section 4 is what proves a tribute is yours, blocking or clearing it will stop you reopening your tribute from that browser until we restore your access.

9. Changes

If this policy changes in a way that matters, we will post the new version here with a new effective date.