Privacy notice
SagaTags lets you put a QR tag on a pet, a car, a person or a memorial. Anyone who scans the tag sees what its owner chose to show. This page explains, in plain words, what personal information that involves, why we need it, how long we keep it, who else sees it and what you can ask us to do. We follow the EU data protection law (GDPR).
Who is responsible
SagaTags decides why and how your information is used. If you publish a tag, you are also responsible for what you write about other people, such as an emergency contact or a family member, so make sure they are happy with it.
Questions or requests about your data: help@sagatags.com
What we keep, why, and for how long
Each card below is one kind of information: what it is, why we need it, why the law allows it, and when it is deleted.
Your account
- What we keep
- Your email address, your password (kept only in scrambled form, so nobody can read it, not even us), an optional name, whether you are a user or an admin, and the date you joined. We also keep whether and when you confirmed your email address and, for each confirmation or password-reset email we send, a scrambled fingerprint of its one-time link (never the link itself), the address it went to and the times it was sent and used.
- Why
- To create your account, sign you in and let you manage your tags. To confirm the address is yours, so scan alerts go only to a confirmed address, and to let you reset a forgotten password.
- Why it is allowed
- Your contract with us: we need it to give you the service you signed up for.
- How long
- Until an administrator deletes the account. You cannot delete it yourself yet, so email us (see Your rights). Deleting an account also deletes its tags, profiles and scan records. The records of one-time links are removed once they are 7 days old (checked whenever a new link is sent); deleting an account detaches them from it and they go the same way. A confirmation link works once, for 48 hours; a reset link works once, for 1 hour.
Details you publish on a tag
- What we keep
- Whatever you type into a tag. Pet: the pet’s details, and your name, phone, email, address, messenger handles and vet. Person: name, date of birth and emergency or medical details (this can be health information). Car: contact details and the plate. Memorial or life story: names, dates and text. Photos are only linked by the web address you give us; we do not store the files.
- Why
- To show it to whoever scans the tag, which is the service. Tag pages are public: anyone with the tag or its link can read them.
- Why it is allowed
- Your contract with us: publishing the page is what you asked for. You decide what goes on it, including any health details, and everyone who scans the tag sees all of it (it is shown to anyone who scans the tag), so write only what you want a finder or first responder to see. You must have the right to share other people’s details. To take the page down, deactivate or delete the tag.
- How long
- Until you delete the tag, or an administrator deletes it or your account. Deleting a tag also deletes its scan records, shared locations and likes.
Scan records
- What we keep
- Each time a tag page is opened: the time, a short piece of text that identifies the browser (cut to 256 characters) and a running scan count for the tag. The visitor’s IP address is not stored with the scan.
- Why
- To show the owner how often the tag is used, and to protect the service from abuse.
- Why it is allowed
- Our legitimate interest: simple statistics for the owner, and security. You can object (see Your rights).
- How long
- As long as the tag exists. We have not set a fixed time limit yet.
A location shared by a finder
- What we keep
- Only if you open a lost pet’s page and choose to share your location: the position your browser reports and the time. If you share again later, the new position replaces the old one from that visit. The owner gets each share by email as a map link, sent to the confirmed email address of the account that owns the tag (or to a separate owner address that was confirmed).
- Why
- To tell the pet’s owner where the pet was seen.
- Why it is allowed
- Your consent: your browser asks permission first, and nothing is sent until you tap the share button. You can take it back by not sharing again and by asking us to delete it.
- How long
- Kept with the scan record, so as long as the tag exists; there is no fixed time limit yet. Once the email reaches the owner, it is out of our hands.
Hearts on pet pages
- What we keep
- When you press the heart: a random code for your device (stored in a cookie on your device) and two scrambled fingerprints made with a secret key that only the service holds. One is of the device code, the other of your network (only the first part of your network address is used; the rest is thrown away before scrambling). We do not store your IP address or the device code itself.
- Why
- So one device counts as one like and can take it back, and so bots cannot pump up the counter.
- Why it is allowed
- Our legitimate interest: a fair like counter and protection from abuse. The fingerprints cannot be traced back to you without the secret key and your device.
- How long
- Your like is deleted when you take it back, when the pet’s tag is deleted, or after 365 days. The network fingerprint is deleted after 24 hours without activity on that pet. The total stays as an anonymous number.
Changes made to tags
- What we keep
- When an administrator or the tag’s owner edits a tag: the email of the account that saved the change, the time, the tag’s public code and the names of the fields that changed (never the old or new values).
- Why
- So we can tell who changed a public page, and keep it safe.
- Why it is allowed
- Our legitimate interest: accountability and security.
- How long
- Kept with no automatic expiry for now; we will set a limit. If an account is deleted, its email in these entries is replaced by “deleted account”; the time, the tag code and the field names stay.
Technical data
- What we keep
- Your IP address and browser details are handled by our hosting provider to deliver the site and, for a short time in server memory, to slow down repeated requests. SagaTags does not store IP addresses in its own database.
- Why
- To deliver the site, keep it secure and stop abuse.
- Why it is allowed
- Our legitimate interest.
- How long
- Hosting logs follow the host’s own rules. The short-term counters in memory expire within an hour.
Who else gets your data
These companies help us run SagaTags and handle data only on our instructions.
Vercel
- What they do
- Hosts and delivers the website.
- What they get
- Everything sent to or from the site, and request logs.
- Where
- Servers in the United States (East).
Neon
- What they do
- Our database.
- What they get
- All the information listed above.
- Where
- In the region chosen in our Neon project.
Resend
- What they do
- Sends our emails: scan alerts to tag owners, and the confirmation and password-reset emails to account holders.
- What they get
- The recipient’s email address and the message. For a scan alert: the pet’s name, the map link with the shared position and the time. For an account email: the one-time link.
- Where
- Run by the provider.
Anyone who scans a tag sees what its owner published. Map links open the map app you choose, which has its own privacy policy. We use no third-party analytics or advertising, and we never sell personal data.
Data leaving the EU/EEA
Some of these companies are based in, or have servers in, the United States. When personal data leaves the European Economic Area, it is protected by a mechanism the GDPR accepts, such as an adequacy decision or standard contractual clauses (a legal agreement with the provider).
Cookies and similar storage
We use no advertising or analytics cookies. This is everything SagaTags stores on your device.
session (cookie)
- Why
- Keeps you signed in. It is a signed token that scripts cannot read, it is only sent to us, and on the live site it travels encrypted.
- How long
- 30 days
- Needed to use the site?
- Yes. It only exists after you sign in or register.
lang (cookie)
- Why
- Remembers the language you picked.
- How long
- 1 year
- Needed to use the site?
- A choice you made; set only when you pick a language. Not used for tracking.
qrtag-theme (local storage)
- Why
- Remembers light, dark or automatic theme.
- How long
- Until you clear site data
- Needed to use the site?
- A choice you made; stays on your device and is never sent to us.
qrtag_voter (cookie)
- Why
- Tells your device apart so one device counts as one like. It is only sent to the like feature, never when a page loads.
- How long
- 1 year
- Needed to use the site?
- No. It is set only when you press the heart.
qrtag:liked:… (local storage)
- Why
- Remembers in this browser that you liked a pet, so the heart looks pressed.
- How long
- Until you clear site data
- Needed to use the site?
- Set only when you press the heart; stays on your device.
Your rights
Under the GDPR you can ask us to:
- show you the personal data we hold about you;
- correct anything that is wrong;
- delete your data;
- pause using your data while a problem is sorted out;
- give you your data in a file you can reuse elsewhere;
- stop using your data where we rely on our legitimate interest;
- take back a consent you gave, for example a shared location, at any time.
- You can also complain to the data protection authority in your country.
Email us at the address above. We may ask you to prove who you are. Tag owners can also deactivate or delete their tags in the dashboard; deleting a tag removes everything linked to it.
For reference, these rights are set out in Articles 15, 16, 17, 18, 20 and 21 of the GDPR, and withdrawing consent in Article 7(3).
Likes and shared locations are not linked to your name, so to find one we need to know which tag and roughly when. A like can only be matched to you if you still have the device that made it. You can also remove your own like by pressing the heart again.
Security
Passwords are stored in scrambled form and everything travels over HTTPS (encrypted). The secret keys we use for like fingerprints are kept outside the code. Only accounts with the admin role can use the admin area. No system is perfectly safe; if you find a problem, email the address above.
Changes to this page
We update this page when the way we handle data changes. The date at the top shows the latest version.