Privacy
Last updated 15 October 2026
The short version
iwrote is a page you write on. While you type, it counts how the writing arrives: how much was typed, how much appeared at once, how long the pauses were. That counting happens in your own browser, on your own machine, and what you write stays there.
Four things the page sends carry anything about your writing, and this is all of them. Only the last carries the words, and only for a piece you turned it on for:
- While you write, every two minutes at the keyboard or two hundred edits, whichever comes first, the page asks iwrote to countersign how far the record has got. It sends a 43-character hash of its log of edits so far, how many edits that covers, how many characters are in the box, how long you have spent at the keyboard, and the last countersignature it was given. The last one, taken when you certify, adds the fingerprint of the text. iwrote signs those with its own clock, hands them back, and keeps no copy. This needs no account.
- Each time you open Live, the page asks for a reading, and not otherwise. It sends the numbers certifying sends: the counts and times, how the pauses and sittings fell, the rhythm of the typing (the gaps between edits, and where in a word or a sentence you stopped), the shape of each passage you replaced, the drawing of the session and the countersignatures so far. Not the text, not the title, not its fingerprint. iwrote passes them to the model, hands the reading back, and stores none of it. A reading is skipped when nothing has changed since the last one, and this needs no account either.
- Certifying a piece sends those numbers again, with the fingerprint of the text and what the dialog shows it will print, which can include the title, and gets back a link.
- Saving a private copy sends the piece and its history of edits, including what you deleted, to the one place that then holds a copy of it, because you asked for that. While saving is on, each change follows a few seconds after you make it.
When does iwrote start recording?
From the moment you start typing. There is no button to start the recorder and nothing to switch on. The page counts as you write, before you have put your name to anything and before you have decided whether to certify the piece, because a recorder you have to remember to press would only ever record the pieces nobody later doubts.
What it counts is how the text arrived, not what it says. Characters typed, characters that appeared at once, characters deleted again, how many separate arrivals there were and how big the largest was, how long you spent at the keyboard, and how the gaps between edits fell. It knows a paste from typing because the browser tells it outright, not because it guessed from speed. That matters most for people whose typing looks unusual to a guess: swipe keyboards, input methods that commit a phrase at a time, autocorrect.
Does the proofreader send my writing anywhere?
No. Proofread checks spelling, grammar and punctuation, and it does it in your browser. Once you have typed a little, the page downloads the checker, Harper, which is open source, so it is ready when you press Proofread, and runs it on your machine. If your browser is saving data or your connection is slow, it waits until you press it. Your words are not sent to iwrote, or to anyone else, to be checked.
It suggests and you choose. Nothing changes until you press a fix, and a fix you press is recorded like any correction you make yourself: as typing, the same as your browser’s own spelling fix. The English you pick and the words you add to its dictionary are kept in this browser, and nowhere else.
What happens when I sign the pledge?
Signing has two halves. An address is verified, and then you put a name to the pledge.
You can verify the address either way. With Google, what iwrote gets is your email address and the name on your account. Not your contacts, not your documents, not anything else in it. With a link sent to your address, what iwrote gets is the address, because that is the whole of what you typed in. Either way what it keeps is the address, an opaque id, your writing name, and the display name if Google gave one.
A login link works once and lasts fifteen minutes. There is no password here to store or to lose, and the link carries nothing about you. It is a random value that iwrote turns back into your address at its end. The mail is four lines and a link, with no tracking pixel in it. It is sent through Resend, who carry it and see the address it is going to.
Beside your name is a box, unticked: email me when what’s next is ready. iwrote writes to you about that and nothing else, and only if you tick it. Your account page turns it off again.
Your writing name is public in one specific sense: it is printed on every record you make, and a record is a link you hand to strangers. It is unique, and it cannot be changed afterwards. A certificate already sent to somebody prints the name it was issued under, and moving a name later would make every record you had handed out describe a person who no longer exists.
You can write without a name. A name is asked for when you want to certify a piece or want iwrote to keep one, because both of those attach your name to something.
What does a certificate carry?
A certificate is a signed record, and the whole of it travels inside a link that verifies itself. Before a piece is certified, a dialog prints every line it will carry. It carries the counts, the times, your writing name, where you said the piece was going, and a fingerprint of the text: sixteen bytes of a hash, computed in your browser, which a reader who already has the text can check against. The text itself is not sent and cannot be recovered from the fingerprint.
It also carries a drawing of the session: sixty slices of time at the keyboard, each saying how much typing, deleting and pasting happened in it relative to the busiest slice, and where a new sitting began. It is a shape. It holds no text and no exact count, and nothing in it can be turned back into what you wrote.
The link is long, so you also get a short one: iwrote.co/yourname/ and six characters. That short address is kept in a table under your name, with the signed link it points to. You choose, per piece, whether it appears on your page at iwrote.co/yourname. A piece you leave off it is still opened by anybody you send the address to. Six random characters under a name is a billion possible addresses, so they can’t be guessed by counting.
When the short address is made, a timestamping service iwrote does not run is asked to date the certificate, so that its date does not rest on iwrote’s word. The service is sent a hash of the certificate and a random number, and nothing else. Its signed reply is kept beside the short address, and anybody with the address can download it and check it.
When the link is pasted into a post or a chat, it unfurls as a picture of the certificate, drawn from the same record. For a piece that carries “Written by a human” the picture shows that line, the title, the drawing and three numbers. For one that doesn’t, it shows the title and your name and nothing about the reading. Cloudflare may keep a copy of the picture for up to a day.
The dialog opens with every box ticked, and you untick what you would rather keep, per piece: showing it on your page; what the piece was called and what you wrote it on; for a piece you saved, the replay, which lets anyone with the link step through every edit, including the sentences you deleted; and the full reading, every number and chart from the Live panel. Nothing you untick carries over to the next piece.
Because the long link is self-contained, it keeps working without iwrote, and it cannot be taken back. You can retire a short address from Your pieces, which stops it working and takes the piece off your page; anyone already holding the long link keeps it. Whoever follows the short address after that is told you withdrew it, and nothing about the piece.
Who reads the counts?
Jev, a model TypeSafe runs, reads them and says what kind of working session they describe: when you certify, and each time the Live panel asks for a reading while you write. It is sent the numbers and nothing else: not the draft, not a sentence of it, not its subject. When TypeSafe does not answer, the same model is asked through Cloudflare, and sent the same numbers. A reading produced from counts cannot have been influenced by how the writing sounds, which is the whole reason to trust it over a detector.
Where does my writing live?
On your own machine, in your browser’s storage, written as you type. Unless you save a copy to iwrote, iwrote could not hand over your unfinished writing, because it does not have it.
That has a real cost and it is not hidden from you anywhere in the product: browser storage is per-device and it can be cleared by you, or by the browser itself under pressure, or by seven days of not visiting in Safari. The download button is the backup, and the line under the box says when you last took one.
What happens when I save a piece to iwrote?
This is the one thing iwrote does that puts your words on a server, so it is a button rather than a default, it is pressed per piece, and the sentence beside it says what pressing it does. What is stored is the piece, its title, the counts, and the history of edits that made it, including text you deleted. The counts and the history travel with it so that reopening it somewhere else resumes the same record instead of starting a new one. While saving is on, each change goes to iwrote a few seconds after you make it, and as you leave the page.
Removing iwrote’s copy, from the same menu, deletes the row. Not hides it, not marks it deleted: the row goes. What that cannot reach is a certificate you already made, which is a signed link and keeps working.
What does iwrote keep?
This is all of it:
- Your account: an opaque id, the email your login verified, the name Google gave if you used Google, your writing name, and when the account was made and last seen.
- If you ticked “Email me when what’s next is ready” when you claimed your name, when you ticked it. It is never ticked for you, and Stop on your account page clears it.
- Pieces you pressed save on: the title, the text, the counts, and the history of edits that made them, including text you deleted.
- For each piece whose replay you chose to publish, which part of that history readers may see.
- For each piece you certified: its short address, the signed link it points to, and whether it is shown on your page.
- For each short address you retired, the address and when, so it can say you withdrew it rather than that it never existed. It goes when your account does.
- If you close your account, your writing name and the date it was closed, and nothing else — so a name already printed on a certificate is never given to anyone else.
- For a day after iwrote sends any mail — a login link, an address confirmation, a notice that an address changed, a feedback message — a fingerprint of the inbox it went to and of the connection that asked, and when: not the address or the connection themselves. That is what stops anybody having a hundred links sent to one inbox, and after a day the row is deleted.
None of the certificate rows holds a word of the piece. They hold the same public link you were given, with what you left ticked for it to show, such as the title, and that link is already in the hands of anyone you sent it to.
What does iwrote never keep?
- A piece you did not press save on.
- The text of a piece, as part of a certificate. A certificate holds counts, times, a drawing of the session and a fingerprint of the text, and the title only if you leave that box ticked.
- What the page sends while you write. A reading is answered and forgotten, and so is what is sent to be countersigned: iwrote hands back its signature and keeps nothing of either.
- Anything you wrote, in any log. The line logged for a certificate, or for a reading while you write, has the reading, a word count, a few figures about the record, and the first six characters of an account id, or none when you have not logged in.
- Which keys you pressed. The recorder keeps a log of edits to the box: where each one landed, when, and what went in and came out. That log stays on your machine unless you save a copy to iwrote.
- Anything at all from outside this page. iwrote sees the box on iwrote.co and nothing else on your machine.
- A message sent from the feedback page. It is mailed to one inbox, with the page you came from and the address you typed if you typed one, and nothing of it stays on iwrote beyond the day-long count of mail above.
Who else sees any of this?
- Google, if that is the door you use, because you are logging in with Google.
- Resend, if you use the other door or send feedback. They carry the mail, so they see the address it goes to, and the words of a feedback message.
- TypeSafe, which runs Jev, the model that reads the counts. It is sent counts and never words.
- The timestamping service that dates a certificate: DigiCert, or FreeTSA when DigiCert does not answer. It is sent a hash of the certificate and a random number, never words and never your name.
- Cloudflare, which serves this site and runs the backend. When TypeSafe does not answer, Cloudflare runs the same model, and is sent the same counts and never words.
- Nobody else. Nothing here is sold, and there is no advertising identifier on any page.
The marketing pages count page views with Cloudflare Web Analytics, which uses no cookie and no identifier that follows anyone between sites. Certificates carry no analytics at all: a certificate is a page somebody opens because a stranger sent them a link, and measuring that visit would be taking something that was not offered.
How do I take it all back?
Delete a saved piece from the list and its row is gone. Retire a certificate’s short address from the same list and that row is gone too, leaving only the address, so it can say the certificate was withdrawn. Before you do either, your account page has a button that downloads everything iwrote holds for you, as one file.
For the account itself, the same page has a button for that too: it deletes the pieces you saved to iwrote and their writing histories, takes down your name and your page, and stops every short address you made from working. Nobody here has to read a request and act on it by hand any more. The certificates themselves go on working at their long links, because they were never ours to withdraw.
Who do I ask about any of this?
Write to arpan@iwrote.co.