Privacy
Two different questions, answered separately.
Most privacy notices merge the website and the product into one document, which is how a reader ends up unable to answer either question. These are separate here because the answers are genuinely different: this website collects nothing at all, and the product holds a small, listable set of personal data on your people.
Last reviewed 11 August 2026. This describes what we actually do. Where the signed agreement says something different, the agreement governs.
This website sets no cookies, runs no JavaScript, and loads nothing from anybody else.
You can verify all three by viewing the source of this page. There is no analytics script, no tag manager, no embedded font from a third party, no tracking pixel and no consent banner, because there is nothing to consent to. The security headers block outbound requests to any other host, so it is enforced rather than promised.
This website
What is collected when you read these pages.
| Thing | What happens |
|---|---|
| Cookies | none set, of any kind |
| Analytics | none. No page views, sessions or events are recorded |
| Third-party requests | none. Fonts, images and styles are all served from this domain |
| Forms | there are none. Every call to action is an email link |
| Server logs | Our hosting provider records requests, including IP addresses, as part of running the service. We do not read them for any analytics purpose and we do not combine them with anything else. This is the one honest exception to "nothing", and it is here rather than omitted. |
| If you email us | We hold the correspondence, in our own mailbox, for as long as the conversation and any resulting relationship needs it. Nothing about that is unusual and it is worth stating rather than implying. |
The product
Personal data held about your people.
In this arrangement you are the controller and we are the processor: you decide why your people's data is handled, and we act on your instructions. The full technical inventory is on data handling. The personal part of it is short.
What we hold
- A verified work email address per person, and a display name where your administrator entered one.
- Their grants: which environment and which tools, who granted them, and when.
- The access record: which person called which tool, when, and whether it was allowed or refused. Never what came back.
- Authorship: the name of whoever wrote or approved a written rule.
What we never receive
- No passwords. Sign-in happens against your own directory and we never see one.
- No group memberships, directory roles, photos or reporting lines. One field crosses from your directory and it is the email address.
- No business data. No copy of your figures or documents is stored, so none of your customers' or employees' data passes into our keeping through a read.
- No behavioural profiling. The access record exists to answer who reached what. It is not analysed to characterise anybody, and no automated decision is made about a person from it.
Rights and requests
How a request from one of your people is handled.
Because we are the processor, a request from one of your employees is answered through you rather than around you. That is not a deflection, it is the correct route: you hold the relationship and the context, and we hold four fields.
| Request | What we do |
|---|---|
| Accesswhat do you hold about me | We supply everything held about that person, which is the list above. Your administrators can already see most of it themselves in the console. |
| Correction | Names and email addresses are corrected on your instruction. Access-record rows are not editable by anybody, including us, because a record that can be corrected is not a record. See append-only. |
| Erasure | The person, their grants and their written rules are removed on your instruction. Access-record rows referring to them are retained for the agreed period, because a trail that disappears when somebody leaves cannot answer the question it exists for. If that conflicts with your own obligations, it is a conversation to have before signing rather than after. |
| Portability and export | The access record is exportable by your own administrators at any time, without asking us. See the audit trail. |
| Objection to a sub-processor | The list is published and any addition is notified in advance. |
Contact. Privacy questions and requests go to info@proceptio.com. Security reports go to the same address with security in the subject line. There is no separate privacy team to route you to, and a named person answers.