Terms

These terms cover this copy of TapTrail, the program running on this machine. There is no account and no separate service behind the page.

Effective 1 October 2026. Updated 5 October 2026.

By recording a trail, following one, or adding the TapTrail script to a page, you agree to these terms. If you do not agree, do not use this copy of TapTrail.

Who is who

• The operator is whoever started this server.
• A recorder is someone who records a trail and gets its link.
• A follower is someone who opens a trail link.
• A site owner is whoever adds the TapTrail script to their own pages.

You run it

The operator is responsible for this server: who can reach it, where the trails are stored, how long they may last, which sites may upload to it, and whether a list of trails is public. TapTrail does not operate a hosted service of its own, and nobody else is watching over this copy.

A server that is reachable from the internet should sit behind a proxy that provides HTTPS, and should limit uploads to the sites it is meant for. Those choices belong to the operator.

The link is the access

A trail link is enough to follow that trail. There is no password and no login in front of it. Send it only to the people who should see the path, and treat anyone who has the link as able to open it until it expires.

What you may record

Record only pages you are allowed to show someone else. A trail stores the page address, the page title, the trail title you give it, and a short label for each click, such as a button name. It does not store what was typed into a field unless the site has opted that field in, and it masks email addresses and long numbers, but the rest can still be sensitive. A product name in an address or a customer's name on a button is kept as it appears.

Do not use TapTrail to capture credentials, private messages, or anything you would not hand to the person holding the link.

What you may not do

• Use a trail to trick a follower into an action they did not mean to take, such as changing a setting, sharing access, or paying for something.
• Send trails that lead to sites you have no right to point people at, or that impersonate another site or person.
• Flood the server with uploads, try to guess trail links, or try to get around the upload limits or the allowed-sites list.
• Use TapTrail in a way that breaks the law, or the terms of the site you are recording.

Following a trail

A trail shows where someone else clicked. It does not check that the path is safe or still correct. Read each step before you act on it.

Auto-tap is off until you turn it on. When it is on, it only opens links within the same site, tabs, section headers, and buttons that open menus or panels. It will not press anything whose label reads like a change, such as delete, revoke, pay, send or sign out. Those steps wait for you. A typing step waits for you to type, unless the site opted that field in and you have not typed in it yet; then auto-tap fills in the recorded text, which you should check before you use it. Typing steps you have moved past are filled in the same way even with auto-tap off, but text with a masked email or number never is. Auto-tap never submits a form. A step on another site is shown as a link, and is not followed for you.

Putting the script on a site

A site owner who adds the TapTrail script to their pages lets visitors record trails of those pages and send them to this server. A site owner who opts fields in with data-tt-record also lets the text typed there be stored in trails, and should only do that for fields that never hold personal or secret data. The site owner is responsible for telling their visitors about all of this, in whatever way their own privacy notice and local law require, and for making sure the operator of the server they point at is someone they trust with that data.

Trails expire

A trail lasts for the lifetime chosen when it was saved: a day by default, and three days at most, unless the operator has changed those limits. The recorder can delete it sooner with the token they were given when it was saved. If the server is running with nothing written to disk, every trail is forgotten when the process stops.

A trail may also go before its time. When the server holds its maximum number of trails, expired ones are cleared first, and then the client holding the most trails loses its oldest. The operator can also remove trails at any time. Do not rely on a trail as the only copy of anything.

Limits

Each trail can have up to 300 steps. Each client can save a limited number of trails in a ten-minute window, 30 unless the operator has changed it. Uploads that go over a limit, come from a site that is not allowed, or do not look like a trail are refused.

Other sites

A trail points at pages on other sites. Those pages, and what happens when you click on them, are governed by those sites and their own terms. TapTrail does not control them and is not responsible for them.

The demo

The demo app is fake. Nothing in it is a real workspace, invoice, teammate, or key, and nothing you do there changes anything real.

As it is

TapTrail is provided as it is, without a warranty of any kind, including that it will be available, that a trail will replay correctly, or that it is fit for a particular purpose. You are responsible for how you run it, for what you record, and for what you click while following a trail.

To the extent the law allows, the people who wrote TapTrail are not liable for any loss that comes from using it, including lost data, a wrong click, or a trail that someone else opened.

Changes

These terms can change. The date at the top of this page shows when they last did. Using TapTrail after a change means you accept the new version. Questions about this copy go to whoever runs this server.