Privacy
Draft for review. Last updated 2 September 2026.
This is a plain description of what Sagenta collects, why, and what you can do about it. It covers the website at sagenta.com, the application at app.sagenta.com, the widget that appears on a customer’s site, and the emails we send. If anything here is unclear, write to privacy@sagenta.com and a person will answer.
Who we are
Sagenta is the company that runs this service. When we say “we” or “us”, that is who we mean. When we say “you”, we mean the person reading this: an agency or developer with an account, a site owner who was invited to mark up a site, or a visitor to sagenta.com.
The two kinds of people we hold data about
People with accounts. Agencies, freelancers and in-house teams sign in to the application to review requests. Site owners are invited by them and sign in from the site itself. Both are identified by an email address. We never ask for a password; sign-in is by an emailed link, or by a passkey your device keeps.
People who only visit sagenta.com. If you read the website and never sign in, the only thing we hold is what you type into the early-access form, if you use it.
The audit log
Each organisation keeps a log of who did what in it: invitations, roles, keys, endpoints, approvals, deletions and sign-ins, with the person’s email address, the time and the address the action came from. It never contains what anyone wrote in a request. The organisation chooses how long to keep it, never less than a year, and a person who leaves or deletes their account stays in the entries they made until that period ends. When one of our own people reads an organisation’s data, that is in the organisation’s log too.
What we collect, and why
To sign you in
Your email address, the time you signed in, the address your device connected from, and the name of your browser. If you add a passkey, we store the public half of it and a name you give it. We keep these so we know it is you, and so you can see and end your own sessions.
When you ask for a change on a website
This is the heart of the service, so here it is in full. When a site owner taps something on their site and says what they want changed, we store:
- the words they typed, and, in text-edit mode, the words that are there now and the words they want instead;
- the address of the page and a description of where on the page they tapped;
- a screenshot of the page as they saw it, with the element they tapped outlined. Anything typed into a form field on the page is blanked before the picture is taken, and a site can mark parts of a page to be blanked too;
- if they choose to record one, a short video of the page, with their voice if they allow the microphone. Recording never starts on its own;
- the size of their screen, how far down the page they were, the name of their browser, and any error messages the page itself reported;
- the notes that follow, from the owner and from the people reviewing;
- who approved the change, when, and against which preview.
We store this so the people who look after the site can make the change, show a preview, and record that the owner approved it. The request is also sent to the tools the site’s own team has connected: their own web service, a Slack channel, or an automation service they chose. Once it is there, it is under their control and their policies.
When you use the application
The name you give yourself, which organisation you belong to and your role in it, the sites and people you set up, the API keys and endpoints you create (we store keys as a one-way hash and never show them again), and your notification choices.
From the early-access form
Your name, email address, roughly how many sites you look after and what they are built with, and anything else you write. We use it to reply to you and for nothing else.
What we do not collect
We do not run advertising trackers, analytics cookies, or social-media pixels. sagenta.com sets no cookies at all. The application sets one cookie, to keep you signed in. The widget stores one value in your browser, on the customer’s site, so you stay signed in there; it is scoped to that site and we cannot read it from anywhere else.
Where it lives
Everything is stored with Amazon Web Services in the United States, in the us-east-1 region (Northern Virginia), in an account we control. Screenshots and videos are stored as files there; everything else is in a database. Email is sent through Amazon’s email service from the same account.
Who can see it
- The people in the organisation that looks after the site, according to their role.
- The site owner, for their own requests.
- The systems that organisation has connected: their endpoint, Slack channel or automation service. What those systems do with it is between you and them.
- Us, when we are fixing a problem or asked to by you. We look at customer data only for that reason, and access is logged.
We do not sell data, share it with advertisers, or use it to train anything.
How long we keep it
Requests, notes, screenshots and videos are kept for as long as the organisation’s account is open, because they are the record of what was asked for and approved. Sign-in links and widget links work once and expire in fifteen minutes. Sessions expire. When an organisation closes its account we delete its data within thirty days; backups roll off within a further thirty.
Your rights
Whoever you are and wherever you live, you can ask us to show you what we hold about you, correct it, or delete it, and we will do so within thirty days. If you are a site owner who was invited and would rather not be, tell the organisation that invited you or tell us, and we will remove you. If you live somewhere with data-protection law that gives you more than this, those rights apply too. Write to privacy@sagenta.com.
Children
The service is for people looking after business websites. It is not for children and we do not knowingly collect anything from anyone under sixteen.
Changes
If we change this page in a way that matters, people with accounts get an email first. The date at the top is the date of the last change.