Explanation
Keys, passwords and your data
A migration needs the keys to two instances and handles everyone's data. The tool is built so that it holds as little as it can, for as short a time as it can, and so that nothing it holds can be read back out.
Signing in
- There are no passwords to steal. You sign in with a link emailed to you, which works once and expires after 15 minutes, or three days for an invitation.
- The link carries a token the platform checks against your account and a random code the tool stores. Only the code is stored, and using the link spends it.
- Opening the link changes nothing: a second step signs you in, so an email scanner that opens links first cannot use yours. That step works only in the browser that opened the link, so another site cannot sign you in to an account that is not yours.
- Your sign-in links, invitations and migration emails go to you alone. Insites keeps no copy of them in its own inbox.
- The sign-in page gives the same answer whether or not an address has access, and limits how often one address or network can ask.
- Once signed in, you stay signed in on that device while you keep using the tool. Each visit renews it. A device you do not use for 7 days asks you to sign in again. The button in a migration email signs you in for one hour, because those emails are often forwarded: ask for a link on the sign-in page to stay signed in longer.
- Signing in with Insites Console lasts 12 hours without a visit, renewed on use. A page left open keeps you signed in: it checks in with the tool every 10 minutes, even in a background tab. A migration never depends on your browser: a load, a check or a sync runs on our servers, and carries on if you close the tab or are signed out. If you are signed out with a page open, it says so and offers Sign in again in a new tab. Keep the old tab open: once you have signed in, it carries on by itself, with nothing on it lost. Signing in from the sign-in page also takes you back to the page you were on.
- The tool keeps a record of each device you are signed in on, and checks it on every page. Sign out, in the profile menu at the bottom of the menu on the left, ends this device. Sign out of all devices ends every one, for example after you used a shared computer. A device that was signed out shows "You were signed out on this device" and asks you to sign in again.
Keys
- A key goes from its field to the tool over HTTPS. It is never stored in your browser, never shown again, and never included in an email, a log or a report.
- Each key is encrypted with its own key, which is itself encrypted with the tool's master key. Neither half alone opens it. When it expires, and which instance it is for, are locked in with it, so neither can be changed without the key failing to open. A key kept the old way, before October 15, 2026, is not opened: it is destroyed, and the migration asks for a new one.
- A key is kept for as long as the migration needs it. Once a migration holds a key, the tool keeps it, encrypted, until you close the migration, until the workspace or account is closed, until you ask for it to be removed, or until nothing has happened on the migration for 90 days. It does not expire on a date, so a check, a sync or a rollback weeks after the load still works without asking for the key again. Keeping a key is recorded. How long a key is kept.
- A migration nobody has opened or worked on for 90 days loses its two keys, the same way as Remove the keys now. The person who started it is emailed 14 days before, and the keys never go sooner than 14 days after that email. Anything that happens on the migration starts the 90 days again, and a migration that is working or has a watch or nightly sync on is never counted as unused.
- A key you give and never use in a migration is kept for 24 hours. Then the tool's sweep, which runs every 5 minutes, removes it.
- Close the migration, on the Close step, removes its keys. So does Remove the keys now on the run's Key page, which keeps the migration open: anything that needs a key afterwards asks for a new one.
- A key held for longer is more exposed if the tool's store were ever read. That is why each key stays encrypted with its own key, bound to its workspace, never shown, and recorded every time it is used. This was a deliberate product decision, made on October 17, 2026.
- Every use of a key is recorded: who, when, and what for.
- Your Teamwork key, for pushing a To do list to Teamwork, is kept only if you tick Remember this key, and only once Teamwork has accepted it. It is encrypted the same way, and also locked to you and to the Teamwork site you saved it for: nobody else in the agency can use it, it is not there in your other accounts, and it is only ever sent to that site. It is never shown again, not even to you. Settings shows which site it is for, never the key. It has no expiry date, but it is removed when you forget it, when you are removed from the agency, and after 180 days without use. The tool sends a Teamwork key only to an address ending in teamwork.com, or to a custom domain whose DNS proves it is served by Teamwork (a CNAME record pointing to Teamwork's custom domain address). Your saved Teamwork key.
- Teamwork telling the tool about a task. When you push jobs to Teamwork, the tool asks Teamwork to tell it when one of those tasks is completed or reopened. Each message is signed with a secret that belongs to your account, and the tool ignores a message whose signature does not match. The secret is never stored, shown or written to a log.
- GitHub. When you send the code to GitHub, the tool keeps no GitHub key. Each time it sends, it asks GitHub for a short-lived permission for one repository, with the least access it needs. A GitHub organization is connected only to the account you connected it in, and only if your own GitHub sign-in can see it. The connection is removed after 180 days without use.
Passwords
The tool never keeps your Insites v5 Console or Siteglide password. It uses it once, when you connect, to get the key it opens, and keeps only that key. A source connected with a password before version 0.5.0 must be connected again.
If you choose to copy passwords, the tool reads each person's password in its one-way scrambled form (the form the source already keeps, not the password itself) from the source during the load, writes it as it creates that person, and forgets it. Scrambled passwords are never written to the copy of the source, a log or the report. The PASSWORDS check compares them in memory.
Constants and secrets in the data
Constant values are read and written in memory during the load, never stored. The secrets check reads every table and your code for anything that looks like a key, and the plan waits until each is redacted or kept with a reason. Findings are shown masked.
Password reset links never travel. Every value in a table of reset links is scrambled one way as it is read, except the email address, and the table is always left behind, on Insites v4 and v5 alike. A plan cannot choose to copy it, keep it or create it on the new instance. The new instance makes its own reset links.
Your data
The source is read into a copy encrypted with the tool's key and kept in private storage while the migration uses it. Closing the migration removes it, and so does 7 days with no activity on the run. A watch's look at the site and the start of a nightly sync count as activity, so a migration in use keeps its copy. The record of what the load wrote, which a rollback needs and which holds the rows it changed as they were, is kept until the migration is closed and 30 days after the load at most. The report never holds a row of data.
- What a check finds, such as a row's values on both sites when a check finds a row or a file that differs, is kept with the migration's record, encrypted the same way. Only a member of the agency sees it, on the migration's pages. Table names, ids, field names, emails and counts stay readable, so the record still says what was found.
- A code difference never shows a header's value or a key: an API call's headers are named, each with a fingerprint of its value.
- Long lists you give the tool, such as a form's past submissions or a site's redirects, are sent in pieces and encrypted beside the copy of the source. The migration's settings hold only how many there are, and the pieces are destroyed with that copy.
The run page
An open run page hears that its run changed, and then reads the run the way any page of the tool does, with your sign-in. The message it hears says only that the run changed. It never holds any of the run's data, and only the tool can send one. The page's access to these messages is renewed every hour, so a person removed from the account stops hearing them within two hours.
Recording problems on the page
To find and fix the problems people run into, Insites can record how the tool's pages behave with LogRocket: what was on the screen, what was clicked, and which requests failed. It is cut down in your browser before anything is sent:
- What you type is never recorded. Every field's value is hidden, including keys, tokens and passwords.
- The content of every request and answer is left out, and so are the headers that carry your sign-in.
- In the addresses it records, values such as a sign-in link's code are replaced. Only the migration, the step and similar values that say where you were are kept.
- You are named by your user number and email address, nothing else.
AI
When you ask about a migration, AI is sent that migration's own record: the plan, the load, the checks and what they found, the decisions, the transform settings, the To do list and the reports. Find out more on a To do job sends that job and a few facts about the migration: the two addresses and some counts.
- Never a key, a token, a password or its scrambled form, a credential, a constant's value, a redacted field's value, or a row of the site's data. Each part of the record is read field by field, and the text is then checked again for anything shaped like a key or a hash before it is sent.
- The email addresses of the site's own people are hidden. Your team's, as the record names them, stay readable.
- Only operators can ask about a migration or use Find out more, each up to 20 times an hour. A viewer cannot.
Three other parts of the tool can use AI. Each is described here so that nothing leaves the tool without being said.
- Names and tooltips for tables the load creates. Only the name of each table, and the name and type of each field, are sent. Never a record's value.
- Suggest a fix. On Verify, Suggest a fix sends one failing check: what it found, the files or records it names, why Copy again failed, the log lines and decisions that name them, and the values the check found where it keeps them, each cut short. Never a key, a token, a password or its scrambled form, a credential, a constant's value, a redacted field's value, or a field named like a secret, and the site's people's email addresses are hidden. A value from a record that AI repeats is taken out of its answer before the answer is kept. Only operators can ask, within the same 20 an hour.
- Page screenshots. The SCREENS check can ask the AI to compare the two screenshots of a page, when the two differ. Each picture is no larger than 1568 pixels on its long side. The picture is taken signed out, so it shows only what any visitor sees, and it is sent with the page's address. Nothing else is sent. This is off unless the tool's owner turns it on.