Skip to content
TenhariRequest access

What the hosted service keeps, and who sees it

This page says in plain words what the hosted Tenhari service at pinpoint.rapidimpactlabs.com stores, where it is stored, who can see it, and how to have it deleted.

It describes how the product behaves today. It is not a legal agreement, and it does not replace the company policies linked at the foot of the page.

Last updated 21 November 2026.

What is stored

When you review a site through a share link, or run a board as its operator, the hosted service saves what you add to that board.

Your name

The display name a reviewer types when the link opens. It is shown beside every note that reviewer leaves, and the reviewer can change it later. No account is asked for. A member of the operator's team signs in with an account, and the name on that account is shown beside what they write in the same way.

Accounts on the operator's team

Each member of the operator's team signs in with their own account. It holds their email address, their name, their role on the team, and their password, kept only as a salted hash that cannot be turned back into the password. Each browser signed in to an account is recorded with when it signed in and when it was last used, so the server can sign it out after 14 days without use, and 30 days after sign-in in any case. The team's admins see each person's name, email address, role and when they last signed in. Nobody is shown a password or the list of browsers. The service keeps each team apart: the people of one team are never shown another team's boards, people or reviewers, and one person may belong to more than one team, with a role in each. Removing someone from a team ends everything they could do in it at once; when it was the only team they belonged to, their account is deleted too and they are signed out everywhere. What they wrote keeps their name. Reviewers on a share link need no account.

Your email address

Optional. A reviewer can type one when the link opens, or add, change or remove it later from their name at the top of the page. It is used to email that reviewer when the operator's team answers or resolves a pin they left. Other reviewers are never shown it. The operator's team sees only its first letter and its domain, which tells two reviewers with the same name apart, and sees the whole address only in the copy of a reviewer's data it downloads when that reviewer asks for one. It is kept with the reviewer's sign-in record, not with the board or its notes, and it is removed when the link is revoked, a month after the link expires, when the board is removed for good, when the operator removes that reviewer, or after six months without a visit.

Visits

For each reviewer on a share link, when they first opened it and when they were last seen. For each link, when it was last used and how many times someone has signed in through it. A reviewer's record is removed when the link is revoked, a month after the link expires, when the board is removed for good, when the operator removes that reviewer, or after six months without a visit.

Notes

The text typed on a pin, and the transcript of a voice note when there is one.

Screenshots

The image captured for a pin, including anything drawn on it.

Voice recordings

The audio of each voice note.

The board

Its title, the address of the site under review, and the position of each pin on the page: where it was placed, on which layout (desktop, tablet or phone), and a short fingerprint of the element it sits on, so the pin can find that element again when the page changes. The fingerprint is the element's tag and a hash of up to 80 characters of its text. The text is hashed in the page itself and never leaves it in the clear, and native fields, editable regions and text-entry widgets are never read.

Sign-offs

When the operator's team checks a change and marks it done, the after picture they approved is saved with the pin, beside the screenshot it was compared with, and so are the before and after at the other screen sizes (desktop, tablet, phone) when the team checked the change at those too. A reviewer with a comment link can then approve the change or ask for changes. The service saves which they chose, the name shown beside their notes, when, and which of the operator's share links it came through; that last part is shown to the operator's team only. Asking for changes reopens the pin, and the note that goes with it is saved like any other note and cannot be deleted while the request stands. The operator's team can clear a decision, and when the team marks the pin done again, the earlier decision and pictures are replaced.

Proof of a change

When the operator runs a coding agent on their own machine, the pins it changed keep what proves the change: the names of the files in the operator's project that the run changed for each pin and which lines, the commit that carried them once the operator pushes it, and a mark on any other pin whose area the run changed too. Reviewers on a share link never see it. The operator's team does, and the file names, lines and short commit id go with the pin to a model provider or coding agent when the operator runs one on that pin, as described below. It is deleted with the pin, except that the activity log keeps its record that proof was attached, with the number of files and the short commit id (never a file name), for up to a year.

Answers to the team's questions

The operator's team can ask a reviewer a question on a pin, with answers to tap. A coding agent can write a draft of one, but only a person on the team asks it, and a draft is never shown on a share link. When a reviewer with a comment link answers, the service saves the answer they tapped or the words they typed, the name shown beside their notes, when, and which of the operator's share links it came through; that last part is shown to the operator's team only. An answer cannot be changed afterwards. It is kept with the pin, and when the operator removes a reviewer at their request, the answer stays without their name and without any words they typed. The exception is an answer on a pin that reviewer dropped: it goes to the Recently deleted list with that pin, name and words included, comes back if the operator restores the pin, and is removed for good with it.

Technical details

Dropping a pin also records the browser and system you use, your screen size, your language, and any errors the page reported or requests it failed around that moment, so the team can reproduce a problem. Addresses on the site under review keep their query strings with anything that looks like a credential removed; other addresses lose theirs. Anything that looks like a password, a token or an email address is removed from the error text. Reviewers on a share link never see it, not even for their own pins. The operator's team sees it, and it goes with the pin to a model provider or coding agent when the operator runs one on that pin, as described below. It is deleted with the pin; when the operator duplicates a board, the copy keeps its own copy until it is deleted too.

Activity

A log of what changed on each board: who (the name shown beside their notes) did what, to which pin, and when. It records that a note was added, never what it says, and that proof of a change was attached, with the number of files and the short commit id, never a file name. Changes to the team are logged the same way (an invite made, a person joining or removed, a role changed, a password reset link issued), by name and never by email address. Only the operator's team can read it.

IP addresses

The address a request comes from is used to limit how fast one visitor can send requests, and how many wrong passwords can be tried from it. It is held in the server's memory for that purpose and is not saved with the board.

Where it is stored

In a database we host ourselves, on our own host. Screenshots and voice recordings are stored there as files, beside the notes they belong to.

That database is backed up on the same host, so something deleted today can still be present in a backup taken before the deletion, until that backup is deleted in turn (see How long it is kept).

A note, a screenshot or a recording that could not be sent, because the connection dropped or the server could not be reached, is kept in your own browser until it can be, and is sent the next time the board is opened in that browser under the same name. It is deleted from the browser as soon as it is saved. It is also deleted when the person it belongs to signs out of that browser, which asks first, because signing out discards it. One that is never sent is deleted the next time the app is opened in that browser after twenty hours.

Tenhari can also be run on a person's own machine. Run that way with no environment configured, it keeps boards in that browser's own storage instead of on a server.

Who can see it

Everyone who holds a board's share link. They can read every note on that board with the name typed beside it, see every screenshot, including the before and after of each change the team approved at each screen size the team checked, see who signed off on a change or asked for changes, read each question the team asked with the answer given and the name beside it, and play every voice recording. A link with comment scope also lets its holder add pins and notes, approve a finished change or ask for changes on it, and answer a question the team asked; a link with read scope does not.

The operator, meaning the team that made the board and sent you the link, sees everything on it too.

The operator can also download a copy of a board, or of every board, as one file: its pins with every note (the team's own notes too), the names beside them, screenshots, recordings, attached files, the before and after of each change, and the sign-offs and answers given on it. A share link is never in it. Once downloaded, that copy is the operator's and outside this service, and how long it is kept is up to them. When the operator imports such a file into another copy of the app, a note a reviewer wrote arrives with (guest) after their name.

An admin of the operator's team can also download everything the team holds as one file: every board as described above, and with it the people on the team with their email addresses and roles, the invites, the share links by the name the team gave each, the reviewers who signed in, the team's access tokens and webhooks by name, the activity log and the plan. A reviewer's email address is in it only as the team sees it elsewhere, by its first letter and its domain. No password, no share link's address and no access token is in it. Each such download is recorded in the team's activity log, with who made it.

A share link stops working when it expires, or sooner if the operator revokes it. The operator chooses how long a link lasts when making it: 7, 30 or 90 days, or no end date. The operator can change that later without changing the link.

Which third parties can receive it

Some of what you add can be sent on to a service outside our database. Each service below is reached only in the situation described, and receives only what is described.

Cloudflare

Every request to the hosted service passes through Cloudflare, the network provider in front of our host, on its way in.

Your browser's speech service

A voice note recorded in Chrome, Edge or Safari is transcribed by the browser's own speech service, which sends the audio to the browser vendor, unless the operator has switched that off. When that service is off, missing from your browser, or returns no text, the recording goes to the operator's transcription service if one is configured, and is otherwise kept without a transcript. The recorder says which of these applies before you record.

Model providers

Only when the operator drafts a change request from a pin or runs an agent on a board. The pins involved, with their notes and screenshots, go to the one model provider the operator chose for that board, or to the one the server is set up with when the board names none. If that provider does not answer, no other is tried. Before the text goes to the provider, the names people typed are replaced with labels such as Team and Reviewer 1. When the operator runs an agent, the technical details recorded with those pins (browser, screen size and the page's errors) go with them, and so does the proof of a change already made on them: the names of the files and lines changed, the short commit id and where its approval stands.

No outside model, per board

The operator can turn outside models off for a board. Its notes, names and screenshots then go to no model provider from the hosted service, except a model server the operator runs themselves. Change requests are drafted by built-in rules instead, and a coding agent the operator has connected cannot read the board.

A coding agent the operator connects

The operator can give a coding agent of their own an access token, and can revoke it. That agent can then read the pins on their boards, with their notes, screenshots, the technical details recorded with them and the proof of a change made on them (the names of the files and lines changed, the short commit id and where its approval stands), and add notes of its own, which reviewers on a share link never see. The names people typed are replaced with labels such as Team and Reviewer 1 before anything reaches it. What it reads goes to whichever model provider runs that agent, which is the operator's choice and outside this service.

The operator's own copy of the app

The operator can connect a copy of this app running on their own computer, with an access token of a separate kind, kept in that copy's .env.local and revocable in Settings. That copy shows and changes their boards as the hosted site does, with the names, notes and screenshots reviewers left, and an agent the operator runs there works from them. What happens on that computer, including which model provider such an agent uses, is the operator's choice and outside this service.

Email delivery

When the operator has configured email, notifications about a board are sent through the operator's own mail server or an email delivery service, which receives the recipient's address and the message.

Stripe, for payments

Only when a team pays for a plan, and only where the operator of the service has set payments up. The team's name and the email address of the admin who starts the purchase go to Stripe, the payment provider. The card is entered on Stripe's own page, so the hosted service never receives or stores it. The service keeps Stripe's reference for the team and its subscription, and whether the subscription is paid up. Nothing a reviewer adds is sent to Stripe.

Tracing

When the operator has configured it, each call to a model is recorded in the operator's tracing service: the model, the provider, how much text went each way, how long it took, whether it worked, and a hash of the prompt in place of the prompt itself. It holds no note, name or screenshot unless the operator turns on prompt capture, which also stores the text of the prompt and the answer.

Webhooks

When the operator has added a webhook, each entry in the activity log is sent to the address they chose, such as their team chat. It carries the board and pin titles and the names of the people involved, never the text of a note, a screenshot, a recording or an email address.

How long it is kept

Until the board is deleted, and then for 30 more days. Nothing a reviewer adds to a board expires on its own: a board, with its names, notes, screenshots and recordings, stays in the database until someone deletes it.

A deleted board or pin goes first to a Recently deleted list, where the operator can restore it for 30 days. After that it is removed for good, and its screenshots and recordings follow within a couple of days, when a daily cleanup removes the files nothing refers to any more. The operator can also remove something for good at once.

A reviewer's email address is the exception. It is not part of the board, and it is removed as described under What is stored.

A share link expiring or being revoked closes the link. It does not delete what was added through it. A month after a link expires, the email address the operator gave for it and the sign-in records of everyone who used it are removed.

The activity log keeps at most the newest 2,000 entries for each board, and nothing older than a year.

Backups of the database are kept on the same host. Each one is deleted once it is 30 days old, except that the seven newest are always kept, so a backup is older than that only while backups have stopped. If the operator also copies backups to another place, how long those copies are kept is up to the operator.

An account stays until an admin removes it from the last team it belongs to, or until that team itself is deleted. The record of a browser signed in to it is deleted when that browser signs out, or within two days of its sign-in running out. An invite, with the address it was made for, is deleted about five weeks after it was made, and a password reset link two days after it was made.

How to ask for deletion

Contact the team that sent you the link. They are the operator of the board, and the operator can delete it. They can also give you a copy of everything you wrote on it, and remove everything you wrote on it without deleting the rest. They find what you wrote by the sign-in you made through the link, not by the name you typed, so somebody else who used the same name is never mixed up with you; if you signed in from more than one browser, tell them. An approval or a request for changes you gave, and an answer you gave to the team's question, can still be found that way after your sign-in record is gone.

On the operator's team, ask one of the team's admins to remove you. That takes you off the team at once, and deletes your account too when it belongs to no other team on the service; the notes you wrote stay on their boards under your name until those boards are deleted.

Removing what one reviewer wrote deletes, at once, their notes on other people's pins (a pin that took its title from one of those notes gets its plain number back as its title), their sign-in record with any email address on it, and their name from the activity log, from any approval or request for changes they gave on other people's pins, and from any answer they gave on other people's pins, which keep that something happened (an answer also loses any words they typed). The pins they dropped, with every note, answer, approval and request for changes on them, go to the Recently deleted list: the operator can remove them for good at once, and otherwise they are removed on their own after 30 days.

Deleting a whole board works the same way: the board goes to the Recently deleted list with its pins and notes, and is removed for good after 30 days, or sooner if the operator chooses. When it is removed for good, its activity log goes with it, apart from the operator's record that the board was deleted, so no name of anyone who wrote on it is kept. Screenshots and recordings follow within a couple of days of what they belong to being removed for good.

An admin of the operator's team can delete the whole team, with every board it holds, in the team's settings. It asks for the team's name and the admin's own password, and it cannot be undone. Every share link, invite and access token of the team stops working at once, and everyone on the team loses access at once. Then everything the team held is removed from the database: boards, pins, notes, screenshots, recordings, attached files, reviewers' sign-in records with any email address on them, the activity log, and what was waiting in the Recently deleted list. This usually takes less than a few minutes, and the files do not wait for the daily cleanup. A person who belonged to no other team on the service loses their account with it. What is kept is a record that a team was deleted, by which account and when, with counts of what was removed, and a one-way fingerprint of each of its share links' addresses, kept so that nobody can ever make a link at an address its reviewers may still hold: never the team's name and nothing it held.

A team that pays for its plan cancels its subscription on Stripe's page first. The hosted service cancels and refunds nothing at Stripe, so it refuses to delete a team whose subscription is not cancelled. Stripe keeps its own record of the customer, which whoever runs the service removes there when asked.

A backup taken before something was deleted keeps a copy of it until that backup is deleted, as described under How long it is kept. That holds for a deleted team too.