Send the page.
Hide the numbers.
gotin finds sensitive details on your device and you approve what to hide. The recipient gets a redacted copy. The original opens only with a second password.
Planned for after launch. Nothing on this page is available yet. It shows how each piece will work.
Checked on their device, before it is sealed.
The wrong file, a cut-off scan and a number nobody asked for are caught before anything is sent. The check runs in your client's browser, so nobody else reads the file to do it.
They pick a file
It stays on their device.
gotin checks it
Is it readable, are all the pages there, and is it the kind of document you asked for.
It marks numbers you did not ask for
An account number or a Social Security number the request does not need. Your client hides it or keeps it.
Then it is sealed
You receive the copy your client approved. We never see the file, before or after.
Find it, approve it, seal it.
Drop a file
It stays on your device.
gotin marks what looks sensitive
Social Security numbers, account numbers, names, dates of birth. The scan runs in your browser.
You decide
Hide or keep each mark, and add anything it missed by hand.
One sealed package, one link
You share a reveal password separately, by phone or Signal.
A redacted copy first. The original with a second password.
They open the link with a passkey
The first time, they create one and the link is bound to it. They see the redacted copy.
If they are entitled to the original
They enter the reveal password. The original appears on their device.
Without the password
The hidden details are not in the redacted file at all. They cannot be recovered from it, by anyone.
Five parts, all on the device.
Detection, redaction and reveal run in the browser. The only part that runs elsewhere is training, and it never sees a customer file.
Detection engine
Rules for structured numbers such as SSNs, EINs, cards and routing numbers. A small model for names and addresses. Both run in the browser.
Training pipeline
Runs offline on made-up documents only. It produces the model the browser loads. It never touches customer files.
Redaction pipeline
Builds a new file with the sensitive content removed. Pages are rebuilt from the page image, so nothing sits under a black box. The copy is a picture, so its text cannot be selected.
Reveal layer
The original, encrypted under a key that needs both the passkey and the reveal password. Either one alone fails.
Review and reveal screens
The sender's approval screen and the recipient's step to reveal the original.
Sorts what arrives, and tells you what is still missing.
After you open a request on your device, gotin works out what each document is, gives it a clear name, and checks it against the list you asked for.
- Recognizes common documents: W-2, 1099, bank statement
- Names each file the same way every time
- Shows what the client has not sent yet
- Pulls out the values you asked for, so you can keep those and delete the document
- Makes a redacted copy for staff, with the original behind a second password
Checklist
2 of 3Encrypted pieces and rounded sizes.
It sees
- Encrypted segments of the package
- Their sizes, rounded up
It does not see
- What is in the file
- What was detected or hidden
- The reveal password
- Whether a package has a reveal layer at all
What it is not.
Not guaranteed detection
It is assisted redaction. A person approves every package, and should read the page first.
Not recoverable
If the reveal password is lost, the original cannot be opened. We cannot reset it.
Not FIPS validated
The cryptography runs in the browser and is not FIPS validated there.
Sending documents with numbers in them?
Show us a page you would redact. Fifteen minutes on a call.