Privacy notice

Who holds this data

Irakli Mirotadze (trading as Own a Minute) is the controller for the data described here.

• Besarion Jgenti St. 76
• Tbilisi 0186
• Georgia

The named contact for privacy, takedown and erasure is registry@ownminute.com. We answer within 30 days.

What is published, and what is not

Published on the minute's page, in the certificate and in the open dataset:

• The UTC minute.
• The title and note you wrote.
• The display name you chose — which does not have to be your legal name.
• The certificate serial, the signature and the date the entry was recorded.
• Where an entry is a gift, the recipient's name once it is revealed.

Never published:

• Your email address.
• Your password, which we never hold — see below.
• Your gift message, which goes only to the gift link and the printable card.
• Your payment details, which we never receive — the merchant of record does.
• Your IP address, beyond transient use for rate limiting.

If you tick keep this private, the minute is still recorded and the certificate is still issued, but the public page shows only “Claimed — private” and the dataset carries no writing for it.

Why we hold it, and on what basis

• Contract. Your email and order record, to issue and support the thing you bought.
• Legitimate interests. Moderation records, rate-limit counters and the acknowledgement log — all of which exist so the register can be trusted and so we can show what a buyer was told.
• Your own publication. The title, note and display name are content you chose to publish through us.
• Legal obligation. Whatever the merchant of record and tax law require of the order record.

If you make an account

You do not need one. Buying a minute asks for an email address and nothing else, and no account is created for you.

If you choose to make one, we hold:

• Your email address, and whether you have proved it by entering a code we sent to it.
• A one-way hash of your password, using bcrypt. We do not hold the password, cannot recover it, and could not tell you what it is. Anyone who stole the database would have to guess each one separately, expensively.
• Sign-in records — one row per device you are signed in on, holding when it began, when it was last used and what kind of browser it is. Signing out revokes it; they are deleted 30 days after they expire.
• Six-digit codes, hashed, deleted automatically ten minutes after they are sent.
• If you sign in with Google: the account identifier Google gives us, your address and your name as Google states them. Google tells us nothing else, and we ask for nothing else. We never see your Google password.

A minute bought as a guest is linked to an account only when somebody proves that same address — by entering a code sent to it, or by signing in with Google. An address typed into a form proves nothing and gets nothing.

Other people's names

Notes contain other people's names — parents, partners, the dead. That is what this product is for, and it is also a real obligation. If you are named in an entry and you would rather not be, write to us and we will take it down or redact it. You do not have to prove anything first; we will act and then work out the details.

Do not publish a third party's personal data where you have no genuine connection to them and the minute. See the content policy.

Erasure, against a register that says it is permanent

These two things genuinely collide, so here is how we resolve it rather than pretending otherwise:

On an erasure request from the owner we redact the note, the display name and the account data, and retain the minute as claimed under an anonymous serial. The record survives; the personal data does not.

The minute is not released back into the pool when we do this, because it was genuinely bought. The public page then reads “Claimed — record redacted.”

The published dataset is refreshed monthly, so a redaction propagates to it at the next refresh. Copies other people already downloaded are beyond our reach, which is the price of the permanence commitment; we say so rather than implying we can undo a public dataset.

Your other rights

Access, rectification, restriction, objection, portability, and complaint to your supervisory authority. Ask and we will do it. Rectification of a note re-enters moderation; the minute itself can never change, because it is the identity of the record.

How long we keep things

• Registry entries: indefinitely, subject to redaction on request.
• Order records: as long as tax law requires of the merchant of record.
• Sign-in codes: ten minutes, hashed, deleted automatically.
• Sign-in sessions: until you sign out, and deleted 30 days after they expire.
• Rate-limit counters: minutes. They hold a truncated network address and a count, and expire by themselves.
• Accounts: until you ask us to close one.
• Moderation records: for as long as the entry exists.

Who else touches it

Four, and no others. Each processes data on our behalf under contract, and some operate outside your country under the transfer safeguards in their own terms.

• MongoDB Atlas — the database. Everything described above is stored there.
• Resend — sends the sign-in codes, your certificate and the anniversary message. They see the address and the message.
• Paddle.com Market Ltd — the merchant of record. They take the payment and hold the payment details; we never receive your card number. Charges appear as PADDLE.NET* OWNAMINUTE.
• Netlify — hosting. Serves the pages and keeps short-lived request logs.

We do not sell data, run advertising, or embed third-party trackers. There is no analytics script on this site — not a self-hosted one either. On every page but one, nothing you load causes your browser to contact any company but ours; the typefaces are served from this site rather than from a font network.

The exception is the payment page, and it is worth being exact about. When you pay, your browser loads the merchant's checkout code from their content network and shows their payment form inside this page. You are typing your card details into their form, not ours — we never receive the number — but their code is running in your browser and they can see that you reached the payment step. Nowhere else on this site does anything of the kind.

Cookies

Five, all of them there to keep you signed in or to finish a sign-in you started, and none of them set until you sign in. Browsing the register sets no cookie at all. The payment form sets its own while you are paying — the merchant's, not ours, and only there. There is no consent banner because every one of them is strictly necessary for something you asked for; the full list, and the reasoning, is in the cookie notice.

Email you can stop

We send: the six-digit sign-in code, your certificate, and once a year a note that a minute you recorded has come round again. Nothing else, ever — no newsletter, no offers. Every anniversary message carries a link that stops them for good, in one click and without signing in. The code and the certificate cannot be turned off, because they are the thing you asked for.