Skip to content
amiamiahh

Privacy

No accounts

There are no accounts. We don't ask for your name or phone number, and we ask for an email only on the feedback form and for an anonymous inbox, both optional. Buying a Lifetime pack also asks for an email, as described under Packs, and a special letter can take one for a read notice, as described under Read notices.

What we store

The letters people send: the name a letter is addressed to, its text, its photos, and for locked letters a hint and a scrambled form of the password. We also store when it was sent, the campaign link code if you arrived through one, and any reports about it. For letters sent since October 2026 we also store a scrambled form of the writer's key, as described under Managing your letter.

Payments

When you buy a special letter, payOS (payos.vn) makes the VietQR code and tells us when the money arrives. We store an order and its payments: the order code, price, amounts, status, times and the bank's transaction references. We don't store the payer's name or account number. Your transfer reaches the seller's bank account, so the bank statement shows the payer's name and account, as with any transfer, and with it we can see who paid for which letter. We use that only for that payment and any refund, readers never see it, and we share it only when the law requires. Bank account details are sensitive personal data; we keep orders, payments and bank statements as tax records for as long as tax law requires. Refund and lost-link emails are deleted once the case is closed. payOS and the banks handle payment data under their own privacy policies. For every paid order we keep only a keyed hash of the account number, when the bank provides it (never the number), as described under Invites. If you pay by card, Stripe (stripe.com) takes the payment: it handles your card details, and we never see your card number. Stripe asks for your email to send its receipt. We keep the Stripe payment id, the amount in euros and a keyed hash of the card's fingerprint (Stripe's id for a card, which can't be turned back into the number), for the rule described under Invites and as tax records for as long as tax law requires. Stripe handles payment data under its own privacy policy.

Packs

A 3-letter pack needs no email: we store only a keyed hash of its code, never the code itself, and your browser keeps the code. A Lifetime pack is tied to the email you give: we store it encrypted, with a keyed hash to find it, and use it only to send your one-day codes and the purchase confirmation. To deliver those emails we send the address and the email's text to Resend (resend.com), our email provider, under its own privacy policy. To limit code requests we keep a log of the keyed hash for 1 to 2 days. To count a pack's uses and apply the Lifetime pack's limit of 3 letters a day, we link each letter sent with a pack to that pack for 1 to 2 days, then delete the link; only the site operator can see it, and readers never do. A pack also keeps the campaign link code, if you arrived through one. The email stays as long as the pack works: it is deleted when the pack is refunded or revoked, and a pack left unpaid is deleted with its email after 3 to 4 days. To delete it sooner, email takedown@amiamiahh.com; the pack then stops working, and an unused pack is refunded if you bought it in the last 7 days.

Invites

When you open someone's invite link, a cookie keeps that link's id for 30 days, and orders you make in that time carry the id. When you make your own invite code, a cookie keeps its id for a year, so orders from this browser count as your own; your browser keeps the code, and we store only a keyed hash of it and how many free letters it holds. So that an account that has already paid here doesn't earn a free letter, for every paid order we store a keyed hash of the account number it was paid from, when the bank provides it (made with a secret key, so it can't be turned back into the number). payOS gives us that number with the payment where the bank sends it; we never store the number itself. The hash is kept with the order, as long as orders are kept as tax records. Only the site operator sees which orders came through which invite; the person who invited you sees only how many paid orders earned them a letter.

Read notices

When you send a special letter you can give an email to hear when it is first opened. We store that address encrypted, in its own record and never with the letter, and use it once: the first time someone opens the letter (a locked one, with the right password), we send one short email and delete the address. The email holds the name the letter is addressed to and the letter's link, and to deliver it we send the address and the email's text to Resend (resend.com), our email provider, under its own privacy policy. It tells you only that the letter was opened, never who opened it or from where. If sending fails, we try again a few times over the next hour, then delete the address anyway. If nobody opens the letter within 90 days, the address is deleted unused, and it also goes if the letter is removed. Opening the letter in the browser you sent it from usually doesn't send the email, because that browser keeps a list of the special letters it sent; if that browser's data for this site is cleared, opening your own letter can send it.

Letters to amiamiahh

For letters addressed to amiamiahh or @amiamiahh, and no other name, we also record what readers do with them, each with its time: visits to those pages, which letters are opened, clicks on Copy link, how long the pages stay on screen, the reader's country (the two-letter code Cloudflare attaches to each request, not the IP address) and the wrong passwords typed into those letters (a right one is only noted as opened, never kept). A random id, kept for that browser tab, groups one visit's actions together, across both names and every letter opened; it is never an IP address or a device identifier. Only the site operator sees these records, and they are deleted after 30 days. Letters to any other name are not recorded, and the passwords typed into them never leave your browser. Special letters with a private link are never recorded.

Feedback

When you send feedback, we store what you wrote, whether it is a feature request or a bug report, the page on this site you came from, your browser's user agent (its name and version and your operating system, which help us reproduce bugs), the approximate city, region and country our host estimates from your connection, when you sent it and, only if you give one, your email, which we use only to reply to you. We don't store your IP address itself. Only the site operator reads feedback. Each message is deleted, with its email, 180 days after it was sent; to have it deleted sooner, email takedown@amiamiahh.com.

Visit statistics

Page views are counted by Cloudflare Web Analytics, the privacy-first analytics of Cloudflare, which hosts the site. A small script in your browser reports each page view to Cloudflare: the page, the site that linked to it and how fast it loaded, and Cloudflare adds the country, device type and browser from the connection. The script uses no cookies and stores nothing in your browser, and Cloudflare handles this under its own privacy policy. We see totals only, never a record per visitor: page views and visits per day, by country, page, referring site, device type and browser, and how fast pages load. We use them to see where and on what people read, so we can make the site work better for them. When you arrive through a campaign link a creator shared for us (one with ?src= and a code such as tt-01), one cookie keeps that code for 30 days (a newer campaign link replaces it), and we add one to that code's total for the day. A letter you send while the cookie is there keeps the code, so we know which campaign link brought its writer: the code names a link, not a person. On the writing page we also count, per day, how many times each step of writing a letter is reached (opening the writing page, starting to write, folding the letter, sealing it), as totals only, together with the campaign code when there is one; this uses no ID and no new cookie, and your browser tab only remembers, until you close it, which steps it already counted, so each counts once. Automated crawlers are not counted. Only the site operator sees these totals. The campaign and writing totals are deleted after about a year, as are the page-load totals we counted ourselves until October 2026; a letter keeps its code for as long as the letter is kept. A pack you buy while the cookie is there keeps the code too, and the operator sees only totals per code.

Reactions

Under a letter you can read, you can tap a reaction (a heart, a hug and four more). We store only how many times each reaction was given to each letter: a number per reaction, never who tapped it, when or from where, and the letter's writer gets no email about it. Your browser remembers on your device which reactions you tapped on which letters, so a second tap takes one back; if you clear this site's data in your browser, it forgets them and the numbers stay. Reactions are deleted with their letter.

Managing your letter

When you send a letter, the site makes a random key for it and gives it to the browser you sent it from, which keeps it on your device. We store only a scrambled form of the key that can't be turned back into it, never the key itself, and nothing that says who you are. With that key, the browser can hide the letter (it then disappears from the site for everyone, but nothing is deleted), show it again and, for a locked letter, change its password and hint: the new password is scrambled in your browser like the first one, so it never reaches us. You can copy a management link that carries the key, so another browser can manage the letter too; whoever has that link can hide or show the letter, so keep it private. If you clear this site's data in your browser and kept no management link, the key is gone and a removal by email is the way left. A hidden letter stays stored like any other letter until it is removed.

Anonymous inbox

When you make an inbox, we store the name on it, whether it is private or public, a random code (the end of its link) and when it was made. The browser you make it in gets a random key and keeps it on your device; for each browser that opens the inbox we store only a scrambled form of its key that can't be turned back into it, never the key itself. Changing the key from the inbox page signs out every other browser and the old management link. Letters sent through your inbox are stored like any other letter, with the inbox they came through. In a private inbox they never appear on the home page, on name pages, in name search or in our sitemap, and they ask search engines not to list them, but anyone who has a letter's own link can open it. Changing the mode applies only to letters sent after the change. The management link carries your inbox key: whoever has it can open the inbox and read every letter in it, so keep it to yourself. If you clear this site's data in your browser and kept no management link or email, the inbox can't be opened again. An inbox (its name, mode and key hashes) stays until you ask us to remove it: email takedown@amiamiahh.com with its link.

Opening an inbox by email

If you add an email to an inbox, we email a code to the address you typed to check that it is yours, and attach it only when you type that code back. We then store only a keyed hash of the email (made with a secret key, so it can't be turned back into the address), never the address. We use it only when you ask for a code, on the page for opening your inbox on another device or when you add an email. We then send one email to the address you typed, with a code that works once, for 15 minutes, and store only a keyed hash of that code with the request for 1 to 2 days, so we send at most 3 such emails a day to one address. You can remove the email at any time.

What we don't store

This site does not save IP addresses or device identifiers with letters or feedback. Cloudflare, which hosts the site, processes this data to deliver pages and to run the human check (Turnstile) before a letter or feedback is sent, under its own privacy policy.

Who can read a letter

Public letters: anyone who types the name, and they can appear on the home page and in search engines such as Google, together with the name they are addressed to. The writer can choose to keep a letter off the home page: it is then still found by name search and by its link, and can still appear in search engines. Locked letters: anyone with the password. A locked letter's sealed envelope (the name it is for, its hint and its envelope decorations) can also appear on the home page (unless the writer kept it off) and in search engines, but what is inside stays closed until someone enters the password. A reply is a letter like any other, and is also shown on the page of the letter it answers. A letter sent through a private inbox can be read by anyone with its link (and the password, if locked), but it never appears on the home page, in name search or in our sitemap. The site operator can read every letter, including locked ones, to handle reports and legal requests. A special letter shown publicly is like a free letter: it can appear on the home page, in name search and in search engines, and can be read like a public or locked letter above. One with a private link can be read by anyone with that link (and the password, if locked); it never appears on the home page, in name search or in our sitemap, and asks search engines not to list it. The first time a special letter is opened, its writer can get one email saying only that it was opened, if they asked for that; it never says who opened it. A reply that is a special letter with a private link is never shown under the letter it answers, and a reply to a private-link letter never links to it, though its page does show the name that letter is addressed to.

Unpaid letters

A special letter that is not paid within 48 hours of sending is deleted with its photos, within a day after that. Your browser keeps a list of the special letters you sent from it for 3 days, so you can come back to them; you can remove it from the Write page.

Photos

Photos are re-encoded before upload and stored without location or camera data. Photos in public letters and on envelopes can appear in search engines, image search included.

Cookies

Four cookies remember your language, your theme (system, light or dark), how you view the feed (wall or list) and the campaign link code described under Visit statistics. There is no advertising, and no tracking beyond the letters to amiamiahh, the visit totals and the campaign codes described above. Two more cookies hold invite ids, as described under Invites.

GIFs

GIFs come from KLIPY. When you search for a GIF, what you type is sent to KLIPY. When a page shows a letter that contains a GIF, your browser loads it from KLIPY. KLIPY can see your IP address and device information under its own privacy policy: https://klipy.com/support/privacy-policy

Removal

Letters stay until they are removed. To ask for a removal, email takedown@amiamiahh.com with the letter link. Search engines may keep showing a removed letter for a little while, until they visit the page again. If you wrote the letter, you can also hide it yourself from the browser you sent it from, as described under Managing your letter.

Legal requests

We may disclose stored data when the law requires it. For free letters we don't store who sent them, so we usually can't identify senders. For special letters, the bank record of the payment shows who paid.