Who touches your data.

How to read this page

Running a piece of software means paying other companies to do parts of it. Each one below has been chosen deliberately, is under written data protection terms, and may use what it sees only to do the job we pay it for. None of them may sell it, mine it or train on it.

This list is part of the data processing agreement. Before we add or replace anybody on it we update this page and email the admins on every account at least 30 days beforehand, which gives you time to object.

Where your records actually sit

• Amazon Web Services. The servers Pascal runs on and the database everything is stored in, in the London region. Also the service that sends every email Pascal sends, again from London, which means the contents of a quote or a certificate you email to a client passes through it. Amazon Web Services EMEA SARL, Luxembourg. United Kingdom.
• Cloudflare. Object storage for every file: photographs, uploaded documents, generated PDFs, company logos and signature images, and separately the nightly database backups. The buckets are set to the European Union jurisdiction, so the data stays in the EU. Cloudflare, Inc. European Union, covered by the UK adequacy regulations.

Payments

• Stripe. Takes your subscription payments and holds your card details, which never reach us. Receives your name, email address, billing address and what you bought. Nothing about your clients, your jobs or your certificates goes anywhere near it. Stripe Payments UK Ltd, with Stripe, Inc. behind it. United Kingdom and Ireland, with onward transfers to the United States under standard contractual clauses and the UK addendum.

Reading a board photograph

Used only when somebody in your company photographs a distribution board and asks for it to be read. Four things are sent: the photograph, the names of your saved circuit templates, which end of the board to count from, and whether the board is recorded as three-phase. Client names and addresses are not. Neither provider may use what we send to train a model.

Both are listed because either may be used. They work as an ordered pair: one is asked, and the other only sees a photograph if the first cannot answer.

• DeepInfra. DeepInfra Inc. United States, under the UK addendum to the standard contractual clauses.
• Together AI. Together Computer, Inc. United States, under the UK addendum to the standard contractual clauses.

Keeping the service working

• Sentry. Tells us when the application throws an error, so we find out before you have to report it. It receives technical detail: the page, the request and the account it happened on. It is deliberately configured not to send personal information, though an error report can occasionally carry a fragment of whatever was being processed when it failed. Functional Software, Inc. European Union, on Sentry's German-hosted service, covered by the UK adequacy regulations.
• Google Workspace. Our own email. If you write to us, your message and address sit in a mailbox there. It has no access to Pascal itself. Google Ireland Ltd. European Union, covered by the UK adequacy regulations.
• Google Analytics. Counts visits to the public pages: this one, the home page, the guides, the calculators and the pricing. It sees the page you are on, roughly where in the world you are, and what kind of device and browser you used to get here. It does not run inside Pascal, so nothing you do once you have signed in reaches it, and it does not run on the quote or invoice page an electrician sent you. We have turned off the settings that would let Google use any of it for advertising. Google Ireland Ltd, with Google LLC behind it. United States, under the UK extension to the EU-US Data Privacy Framework.

Things people assume are on this list, and are not

• Xero. Only involved if you connect it, and then it is not our sub-processor. You have your own relationship and your own agreement with Xero, and when Pascal pushes an invoice or a contact there it does so on your instruction. What happens afterwards is between the two of you.
• PDF generation. Certificates, quotes and invoices are rendered on our own servers. No document is sent to a third party to be turned into a PDF.
• Live updates. The websocket that keeps your screen current runs on our own servers too, not on a hosted messaging service.
• Uptime monitoring. UptimeRobot loads one health-check address every few minutes to see whether we are still up. It never signs in and never sees a record, which is why it is here and not on the list above.
• Analytics and advertising. There are none, on the public site or inside the product.

Our own people

Pascal is built and run by a small team in the United Kingdom. Support occasionally means looking at a record you have asked us about, and we do that as narrowly as the question allows. Nobody browses customer data for interest, and access to production systems is limited to the people who keep them running.

The privacy notice covers the rest of it, including what we do with information about you as opposed to information about your clients.