How STORI handles your information.

• When you join the waitlist: your email and whether you’re a restorer, a brand, or a piece owner. That’s it.
• When you request a partnership: your name, organisation, work email, an estimate of volume, and whatever you write in the message box.
• When a piece is recorded on STORI: the piece’s description, its photographs, its repair chapters, and the email of the person it’s registered to.
• Server logs: IP address, the URL you visited, the user agent your browser sent, and a timestamp. Kept for 30 days, used to keep the service running and secure.

• We don’t sell your data. Ever.
• We don’t load third-party tracking pixels, ad networks, or session replay tools.
• We don’t write AI stories about your ring, resell your photographs, or train models on your data.
• We don’t share your email between the brand, the restorer and the owner without a clear reason to.

A piece’s logbook is private. Opening it requires a STORI code and the email address the piece is registered to — we email a one-time link, which sets a session scoped to that one piece. The restorer who did the work can see the administrative side of the record; the brand, if there is one, can see it under their own portal.

Under UK GDPR you have a right to see the data we hold about you, to ask us to correct it, to ask us to delete it, and to ask us to export it. Email hello@stori.life and we’ll respond within a week.

STORI is hosted on Vercel and Supabase. For now, the database sits in Supabase’s EU region. If you’re a restorer or brand with specific residency needs, write to us and we’ll walk you through the options.

We use a single kind of cookie: a session cookie when you open a piece’s logbook, scoped to that piece, so you don’t have to click the email link every time. No advertising cookies, no analytics cookies. If and when we add analytics, we’ll use a cookieless tool (Plausible) and update this page.

Write to hello@stori.life. We read every message.