Engineer Pro

Privacy Policy

Last updated 12 October 2026 · Terms of Service

This policy explains what personal information Engineer Pro handles, why, who it is shared with, how long it is kept and what choices you have. It is written in plain language and describes how the product actually works.

1. Who we are and which role we play

Engineer Pro is job-management software used by field-service companies (our “Customers”) to run enquiries, quotes, jobs, maintenance visits, stock and invoicing.

We act in two different roles:

  • As a processor for our Customers. The records a company keeps in its workspace — its clients and their contacts, sites, jobs, photos, staff logins and so on — belong to that company. The company decides what goes in and why, and is the controller of that information. We process it only to provide the service and on the company’s instructions.
  • As a controller for our own website and business. For people who visit our website, ask for a demo, create a workspace or contact us, and for the billing contacts of our Customers, we decide how the information is used.

If you are a client, engineer or office user of one of our Customers and want to exercise a right over information held in their workspace, please contact that company first. We will help them respond. You can also contact us at hello@engineerspro.app.

2. The information we handle

Sign-in details
Name, work email address, role, preferred language, and a password that is stored only as a salted one-way hash. If two-factor sign-in is switched on, the authenticator secret is stored encrypted and backup codes are stored only as hashes. A person may optionally connect their own Microsoft 365 mailbox (an encrypted access token is kept) or sign in with Google (we use the verified email address Google confirms).
Business records entered by a Customer
Clients and suppliers, their contact people (names, phone numbers, email addresses), site addresses, enquiries, quotes, jobs, invoices, maintenance contracts, service and safety records, risk assessments, vehicle checks, stock, petty cash receipts and staff qualification records.
Field work
Job notes and updates, photos, client sign-off signatures, and the time engineers clock in and out. If the company switches the features on, GPS location is recorded when someone clocks in or out, and live team location may be shared on a map. Each person can pause sharing their location from My profile.
Messages and support
Internal team messages and support tickets raised from inside the app.
Client portal
The email address of a client contact who is sent a sign-in link, and the decisions they make on quotes.
Website visitors and sign-ups
Details you type into the demo-request or sign-up forms (name, email, company, phone, message) and your chosen website language.
Security and technical data
IP address and basic request details used to limit repeated attempts and protect accounts, plus activity logs of sign-ins and administrative changes within a company, and a log of any support access by our platform team.
Billing
Plan, billing status and the billing contact. Card details are entered with and held by our payment provider, Stripe; we do not store them.

3. Why we use it

  • To provide the service a company has signed up for — running its field-service operations (performance of a contract).
  • To keep accounts and data secure, prevent abuse and investigate problems (our legitimate interest in running a safe service).
  • To give support, and to send service messages such as sign-in links, password resets and maintenance-visit reminders to the people they concern.
  • To bill for plans and keep financial records (contract and legal obligation).
  • To respond to enquiries and demo requests (our legitimate interest, or steps you asked us to take before a contract).

We do not sell personal information, we do not use it for advertising, and we do not use analytics or advertising trackers on the website or in the app.

4. Who we share it with

We use a small number of providers (sub-processors) to run the service. They may only handle information to provide their service to us.

Vercel
Hosts and serves the application.
Supabase
Hosts the Postgres database (EU-West region) and, where enabled, file storage for photos and documents.
Stripe
Takes payment for plans and manages billing.
Email delivery
Email is sent through the mailbox or SMTP service the company (or, as a fallback, the platform) has configured, including Microsoft 365 where a company or person has connected it.
Google
Only if a company switches on Sign in with Google: Google confirms who the person is.
OpenStreetMap
Map tiles for the team-location map are fetched from OpenStreetMap, which therefore sees the viewer’s IP address.
Exchange-rate service
Daily currency rates are fetched from a public rates service. No personal information is sent.

We may also disclose information where the law requires it, or to protect the rights, safety and security of our users and the service.

5. International transfers

Some of our providers may process information outside the UK or European Economic Area. Where they do, we rely on an adequacy decision or on appropriate safeguards such as standard contractual clauses.

6. How we protect it

  • Each company’s data is kept strictly separate from every other company’s, and enforced in every query.
  • Connections are encrypted in transit, and the site sets strict security headers.
  • Passwords are hashed; mailbox tokens, SMTP passwords and authenticator secrets are encrypted at rest.
  • Two-factor sign-in is available to every user (and can be required per person), and our platform administrator accounts support it too.
  • Sign-in sessions end automatically after a period of inactivity, and are ended when a password is changed or reset.
  • Role-based access limits what each person can see and do, repeated sign-in attempts are rate limited, and sensitive actions are logged.

No system is perfectly secure. If a personal-data breach affects you or your company we will tell the affected Customer without undue delay so they can meet their own obligations.

7. How long we keep it

  • A company’s records are kept for as long as its account is active so that it can keep running its business.
  • When a record is deleted in the app it can be restored for 30 days from Settings → Recently deleted, after which it is permanently removed.
  • When a company’s workspace is deleted, its records and uploaded files are deleted with it. Copies in provider backups expire on the provider’s normal backup schedule.
  • Short-lived security records, such as the counters that limit repeated sign-in attempts, are kept only to apply those limits and are pruned automatically.
  • Billing records are kept for as long as the law requires.
  • Website enquiries are kept only as long as needed to respond and to keep a record of the conversation.

8. Cookies and similar technologies

We use only what is needed for the site and app to work. There are no analytics, advertising or third-party tracking cookies.

efp_session
Keeps a team member signed in. Ends after a period of inactivity and in any case 12 hours after sign-in.
efp_portal_session
Keeps a client signed in to their portal, for up to 12 hours.
efp_super_session
Keeps a platform administrator signed in.
site_lang
Remembers the language you chose for the public website.
efp_google_nonce
A short-lived value that protects a Sign in with Google attempt (about 10 minutes).
Browser storage
Your light/dark choice, your language on a company’s sign-in page, a note that you have seen the cookie notice, and a timer used to keep several open tabs in step with your session. These stay on your device.
Offline copies
If you use the installed app, it keeps copies of the screens you have opened and any changes you make without signal on your device, so you can keep working. They are erased when you sign out or someone else signs in.
Push alerts
Only if you switch on “Alerts on this device”: your browser gives us an address to send notifications to. Switching it off removes it.

Because none of these are used for analytics, advertising or tracking, we do not ask for cookie consent; if that ever changes, we will ask first.

When a customer pays an invoice by card, the payment page is Stripe’s and Stripe sets its own cookies there to prevent fraud.

9. Your rights

Subject to the law, you can ask to access the personal information held about you, to have it corrected or deleted, to restrict or object to how it is used, and to receive a copy in a portable format. Where we rely on consent you may withdraw it at any time.

For information that a Customer holds in its workspace, please ask that company; we will help them. For anything we hold as a controller, write to hello@engineerspro.app. If you are unhappy with how your information has been handled you can complain to your data-protection authority — in the UK, the Information Commissioner’s Office.

10. Platform support access

Members of our platform team can, for support purposes, sign in to a company’s workspace, suspend it or reset a user’s password. Every such action is logged and is visible to that company’s administrators under Settings.

11. Children

Engineer Pro is a business tool and is not directed at children. We do not knowingly collect information from anyone under 16.

12. Changes to this policy

We will update this page when the service or the law changes, and change the date at the top. For significant changes we will tell company administrators by email or in the app.

13. Contact

Questions about this policy or your information: hello@engineerspro.app. Please put “Privacy” in the subject line.