Privacy Policy

What Tagsheep is

Tagsheep is a community-built clothing tag database. People sign in, upload photos of garment care and brand tags, and look up brands, RN numbers, and style numbers.

Information we collect

• Account data — when you sign in with Google we receive your Firebase Auth user id, display name, and email address from that provider.
• Contributions — tag photos you upload, the fields you fill in (brand, RN, style number, materials, notes, and similar), and who created each record.
• Usage signals — optional product analytics and error monitoring (for example Vercel Analytics / Speed Insights and Sentry) when those services are enabled in the deployed environment. These help us understand load and fix crashes; they are not used to sell ads.

How we use it

We use this information to operate the database, show records in browse and search, attribute contributions, moderate spam or abusive content, and keep the service reliable. Tag photos and public record fields are intended to be visible to other users of the site.

Where data is stored

Authentication and database records are stored with Firebase (Google). Uploaded photos are stored in Cloudflare Images when configured, otherwise in Firebase Storage. Hosting may run on Vercel or a similar provider.

Sharing

We do not sell your personal information. We share data with the infrastructure providers listed above as needed to run the product, and if required by law.

Your choices

You can sign out at any time. If you want a contribution removed or an account deleted, contact the operator using the email associated with your Tagsheep admin account / invite, or through the channel you received this invite from. Public tag records may remain if they are useful to the archive, with identifying account details removed where practical.

Children

Tagsheep is not directed at children under 13, and we do not knowingly collect personal information from them.

Changes

We may update this policy as the product grows. The date at the top will change when we do. Continued use after an update means you accept the revised policy.