Privacy policy

Updated: 6 September 2026

This page describes plainly what data the Shanoba service stores, where it lives, and how to remove it. The data controller is Maksym Rudchuk, Ukraine; contact: abuse@shanoba.com. We answer requests sent to that address within 30 days, and requests to take something down much sooner than that.

What data we store

Card content: the title, the name of the person the card is dedicated to, the occasion and date, the creator's name (if given), the names of wish authors, the texts of wishes, and uploaded photos.
Reports: the address of the card, the reason chosen, whatever you write in the comment, and the contact you leave for a reply — if you leave one; it is optional.
Technical logs (IP addresses, request metadata) — in Cloudflare's infrastructure, short-term, to protect against abuse.

There are no accounts and no passwords, no analytics and no advertising trackers. We do not sell data, do not build profiles, do not use the content of cards to train models, and nothing about you is decided automatically.

Photos carry no hidden data

Before a photo is sent anywhere, your browser resizes it and encodes it anew. What leaves your device is the visible picture only: the metadata a camera writes into a file — the model, the timestamp, the GPS coordinates — does not survive that step and never reaches us.

Cookies and what stays in your browser

The service sets three cookies, all of them functional — there is nothing here to ask consent for:

shanoba_admin — the card owner's access key. It is HttpOnly (scripts cannot read it), is sent only to the API of that one card, and lives 180 days.
shanoba_owner — a plain marker that this browser owns the card, so the page knows to offer the editing controls; same lifetime, on the page of that card alone.
shanoba_lang — your choice of interface language.

Your browser also keeps things it never sends us on its own: the name you last signed a wish with, an unsent draft, and the list of the cards and wishes you made — with the keys that let you edit them. That list is the reason "Your cards" works on a device where you have lost the link, and it is also why anyone using your browser can edit those cards. On a shared computer, clear the site data afterwards.

Where the data lives

The entire infrastructure is Cloudflare (Workers, D1, R2), which processes the data on our behalf: it is stored and served from Cloudflare's global network and may therefore be handled on servers outside Ukraine and the EEA, under Cloudflare's data processing terms and the standard contractual clauses. Notifications about reports reach us by email through the same infrastructure.

Third parties

Two, and both are named above: Cloudflare — hosting, database, photo storage, logs and mail; and KLIPY — the GIF catalogue. Searching the catalogue goes through our server, so the provider sees us rather than you, but the GIF itself is loaded by your browser from their CDN — at that moment they see your IP address, as with any external image.

Who can see a card

A card is available only to those who have the link: the addresses are 16 random characters and cannot be guessed, there is no catalogue of cards, and every response tells search engines not to index the page or its photos. What we cannot control is where the link goes next — anyone holding it can pass it on.

How long we keep it

A card and its photos are deleted three months after the occasion it was made for — or three months after it was created, when no date was given. The exact date is shown to the card's creator in the editor. Until then a card lives as long as its creator wants: it can be deleted at any moment with the "Delete the card forever" button in the editor. Deletion is complete either way: the database records, the photos, and the caches. A card hidden after a report and not unblocked after review is permanently deleted after 30 days. Photos uploaded to a form that was never submitted are deleted within a day.

Records of reports outlive the cards they were about: the card's address, the reason and your comment stay with us as the record that the complaint was looked at, so that repeat abuse is recognisable. Ask us and we will delete the contact you left as soon as your case is closed.

Legal basis for processing

For users in the EU and the EEA, under the GDPR:

what you submit about yourself — your name, your wish, your photos — rests on your consent, which you withdraw by deleting the wish or by writing to us;
the name of the card's recipient and the photos of them rest on the legitimate interest of the card's creator in congratulating them — an interest that always yields to the objection of the person concerned;
logs, request limits and moderation rest on our legitimate interest in keeping the service working and lawful;
records of reports rest on our legitimate interest in handling complaints and being able to show how one was dealt with.

Children

The service is not intended for children, and we ask no one's age because we ask for no data about the person browsing at all. If a card holds a child's name or photographs, a parent or guardian can have them removed the same way as anyone else — the "Report" button or the address below, no proof of authorship required.

Your rights

If a card contains your data or photos without your consent, you have the right to have them removed, and you do not need to be the card's creator to do so:

press "Report" on the card page and leave a contact, or
write to abuse@shanoba.com with the link to the card.

We hide the card while the report is reviewed and delete the data if there was no consent to it. Beyond erasure you have the right of access to your data, of rectification, of restriction, of objection to processing based on legitimate interest, of withdrawing consent, and of receiving what you submitted in a portable form — the same address serves all of them.

If our answer does not satisfy you, you may complain to a supervisory authority: in Ukraine, the Verkhovna Rada Commissioner for Human Rights; in the EU or the EEA, the data protection authority of the country you live in.

How the data is protected

Everything travels over HTTPS. The owner's key lives in an HttpOnly cookie narrowed to a single card rather than in the URL, which would otherwise end up in browser history and in the chats the link is pasted into. Writes are rate-limited, and photos of a blocked card stop being served immediately. None of this changes the main thing: a card is as private as the link to it.

Changes to this policy

If what we do with data changes, this page changes with it — the date of the current version is at the top, and we describe anything substantial in plain words rather than by amending a clause number.