DDeplyra
ProductsServicesGuidesAbout
Talk to usGet started
Foreman · Legal

Privacy Policy

Effective 18 August 2026

Who this app is for

Foreman is used by a tradesperson to record the evidence of a job as it happens and to issue a certificate for it. The account belongs to that tradesperson.

A large part of what Foreman holds is not about the account holder at all. It is about the customer whose home or site the job was done at, entered by the tradesperson. There is a section near the bottom of this page written for that customer.

What we collect

Your email address and display name, to sign you in. Sign-in is handled by Firebase Authentication, which is a Google service.

Your business details, which become the letterhead on a certificate: business name, contact email and phone, address, a logo if you upload one, and a credential line such as a registration number. We reproduce that credential line exactly as you typed it. We do not check it with any register or issuing body, and a certificate is not evidence that we verified it.

For each job: the customer's name, email address and phone number, the site address and the postcode, entered by you.

The evidence you capture: photographs, voice notes and typed notes, each with the time your phone recorded, the difference between your phone's clock and ours, and, where a fix is available, the coordinates at the moment of capture.

Sign-in sessions, which record the device description your phone sends with each request.

Location, and how precise it is

Foreman asks for location at the shutter, not at launch. When you allow it, a capture is stamped with the coordinates your phone reports, at full precision, and those coordinates are stored in our database and included in any export you make.

The coordinate printed on the certificate your customer sees is rounded to three decimal places, which is roughly 110 metres, and is left off entirely when the fix is not good enough to map.

If you work from home, a capture made at home records where you live. Declining the location permission is a supported answer and not a degraded one: the capture is stored with its location marked unavailable, and everything else about it works.

Photographs keep the metadata your camera wrote

We store the file your phone produced, byte for byte, and hash it on arrival so we can tell whether our copy changed. We do not strip EXIF data from evidence.

That means a photograph can carry its own embedded location and timing information into our storage, into a certificate, and into a share link you send to a customer. The only file Foreman re-encodes is your business logo.

Where it goes

Job records and evidence are sent over HTTPS to the Foreman service at foreman.deplyra.com, which runs on a server in the European Union. Files are held on that server's own disk rather than with a third-party storage provider, and each organisation's rows are separated from every other organisation's inside the database itself.

Sign-in traffic goes to Google, because Firebase Authentication and Google Sign-In are Google services. Google receives your email address and the ordinary connection details that come with any sign-in.

Foreman shows ads from Google AdMob, and the ad code runs on the sign-in screen too, which means an ad request is made before you have an account. Every request is marked as non-personalised, but AdMob still receives your device's advertising identifier, its IP address and information about the app. The shipped Android build asks for the advertising ID permission.

We put Google's consent form in front of you before the first ad request. If that form fails to load, times out, or is not available in your region, the app currently goes ahead and serves a non-personalised ad rather than holding it back. We would rather write that down than describe a consent gate that does not always close.

Job content is not sent to Google or to anyone else. Your photographs, voice notes, customer details and certificates go to the Foreman service and nowhere else.

Certificate share links

Sharing a certificate creates a link with a long random token in it. Anyone holding that link can open the certificate, its photographs and its voice notes without signing in, and can pass the link on. That is the point of it, because your customer has no account. A link can be created with no expiry date, and we show you the token once.

We record each time a share link is opened. We store a keyed hash of the viewer's IP address rather than the address itself, along with the device description their browser sends and the time.

How long we keep it

Indefinitely. Foreman has no retention schedule and no job that deletes anything on a timer. Records, files and expired sessions stay until a person removes them.

Deleting a capture removes its record from the database and deliberately leaves the stored file on the server's disk, because files are addressed by their contents and one file can belong to more than one record.

We are not currently able to point at a backup of this data, which cuts both ways: there is no extra copy in a third place, and there is no restore if the server is lost.

What sits on your phone

Your session tokens, a cached copy of your account and business records, and the queue of captures waiting to upload, including their full precision coordinates, are held in ordinary app storage in plain form. They are protected by your phone's app sandbox and its disk encryption, not by anything Foreman adds on top.

Deleting your account

Foreman has no delete-account button today, and there is no route behind one in the API. We are not going to print a menu path that does not exist.

To have your account and its data removed, email [email protected] from the address the account uses. That mailbox is monitored by a person, and the removal is done by hand.

If you are the customer, not the tradesperson

Your name, contact details, site address and postcode are in Foreman because a tradesperson put them there, along with photographs taken at your property. We hold that record on their behalf.

Foreman does not notify you that the record exists and gives you no way to sign in and look at it. If you want to know what is held about you, or want it removed, email [email protected] and we will deal with it. Asking the tradesperson directly is usually faster, because the record is theirs.

Children

Foreman is a tool for working tradespeople. It is not intended for or directed at children, and it has no age check.

Contact

Questions about this, or a request about your data: help@deplyra.com.

DDeplyra

A software company building AI-powered business tools and consumer applications, and providing DevOps and platform engineering consulting.

GitHubLinkedInhelp@deplyra.com
Products
AnseyaOpsCoresScanlyMiraajForemanRumiKeysaRedyRooftreeRivajCiteRightNoteSnapRoomMuseReliveEuroReadyDead GiveawayAll products →
Dev suite
Postmortem WriterKesvaraAuditPrepDependencyWatchDevOps AgentScanly web tools
Services
Kubernetes PlatformsCloud MigrationCI/CD & GitOpsDevSecOpsSRE & ObservabilityTerraform & IaC
Company
AboutServicesGuidesContactFree auditPrivacy policyTerms of useRefund policy
Guides
GitOps vs CI/CDEKS vs AKS vs GKEK8s Cost OptimizationGitOps best practicesAll guides →
© 2026 Deplyra. We build it. We run it.
PricingSupportContact