Privacy Policy
Last updated: August 2026
CompliMaint ("we," "us," or "our") publishes free document tools and calculators and operates CompliMaint, a set of connected work applications with an optional account. This policy explains what information we collect, how we use it, and the choices you have. By using our website, creating an account or submitting a form, you agree to the practices described here.
Information we collect
We only collect the information you choose to give us:
- If you create an account: the name and email address you enter, which workspaces you belong to and your role in them, and the records you create while signed in — described in full under CompliMaint Cloud Beta below.
- If you use a free tool signed out: nothing that identifies you. What you type stays in your browser. The exceptions — two optional address lookups, and anonymous counts — are described in the next section.
- If you write to us or ask to be told about a feature: your email address and what you asked about.
- Past applications and service requests: CompliMaint previously operated a maintenance-services business with a candidate application and a facility request form. Those forms are no longer offered. Information submitted through them while they were open is still handled under this policy, and you can ask us to delete it.
We do not ask for Social Security numbers, financial information, or any protected-class information through any form on this site.
How we use your information
- To provide the product: your account, your workspace, and the records in it.
- To answer you when you write to us.
- To decide what to build, from the anonymous counts and feature signals described below.
We do not sell or rent your personal information, and we do not share it with third parties except trusted service providers that help us operate (for example, our email delivery provider), or where required by law.
Free tools (Work Log, Estimate & others)
Our free tools (for example, the Work Log and Estimate makers) run entirely in your web browser. The details you enter — your name and business, your customers' names, line items, notes, photos, and any location you type or stamp — are used to build your document on your own device and are not transmitted to or stored by us, apart from the two optional lookups described in the next paragraphs. To make repeat use easier, some of that information may be saved locally on your device (in your browser), where only you can access it; clearing your browser storage removes it.
Two optional features are exceptions, and both involve an address you type.
The address lookup — the suggestions that appear as you type an address in the Emergency Plan builder and the Condition Report — sends the address text to our own server, which passes it to two public address services and returns the matches: the US Census Bureau geocoder and Photon (an OpenStreetMap search service). Because the request goes through our server rather than straight from your browser, the address text does reach our infrastructure in transit. We do not log or store it. Only the address text is sent — never your facility name, tenant details, contacts or other answers — and you can ignore the suggestions and type the address by hand instead, which sends nothing.
The nearby-services lookup in the Emergency Plan builder, which fills in local hospitals, fire and police, works the same way: our server sends the location to Photon and to OpenStreetMap's Overpass service and returns the names and phone numbers. It runs only when you ask for it.
To understand how the tools are used and improve them, we collect a small amount of anonymous, non-identifying usage data when you generate a document: the document type, the number of line items, total hours, price or rate figures, the number of photos attached, and a coarse city/region derived from your connection. This data cannot be linked to you or your customers and never includes names, photos, notes, or the specific addresses you enter.
We also count what happens either side of that, so we can tell a tool nobody opens from one everybody abandons half-way: that a tool page was opened, that somebody began using it, that a run finished, and that a document was produced, printed, saved or emailed. Each of those recordswhich tool and which kind of page sent you to it — the homepage, the tool directory, a requirements page, a related tool — and nothing else. There is no field in any of it that can hold text you typed: every value is an identifier from our own list of tools and categories, or a count. Not your facility, building, tenant, resident, employee or vendor names; not an address, email or phone; not a note, a description, a document’s contents, or anything you type into a search box; not even the file name, because file names here are built from what you entered.
If you tell us you are interested in a feature that does not exist yet — a waitlist, an “email me when this launches” box, or a premium-feature signal on a completion screen — we store the feature you clicked, which tool you were using, and your email address if you gave one. That is how we decide what to build, and it is the one place a free-tool interaction becomes something we hold rather than something your browser holds.
What stays on your device, and what does not
The free tools keep your work in your own browser: the documents you generate, your facility profile, your saved contacts and the record of what you have logged. We cannot read any of it, it is not backed up, and clearing your browser data deletes it.
What leaves your device is only what this page names: an application or a service request you deliberately submit, an email you ask a tool to send, a waitlist or feature-interest signal, the anonymous usage counts described above, analytics, and — only if you sign in to Cloud Beta and only for the records you choose — the workspace storage described in the next section. If anything else ever begins syncing your tool data to our servers, this page will say so before it does. A promise that something is local is only worth anything if it is updated the day it stops being true, which is what the section below is.
CompliMaint Cloud Beta (optional accounts)
Cloud Beta is an optional account, which you can create yourself or be invited into by an organization. Everything above stays true if you do not have one: signed out, the tools work on your device with no account, no login and nothing sent to us.
If you create an account, we store the name and email address you type into the join form, and the version of the Cloud Beta terms you accepted. Once the account is set up we store: your email address and the name you give us; which workspaces you belong to and your role in them; what your workspace is allowed to use; the facilities in your workspace; and the records you create while signed in — the documents, logs, registers, drafts and settings the tools produce, stored in your workspace so they reach your other devices. Files you attach, such as photographs and logos, are stored privately and are not readable without a signed, short-lived link issued to somebody with access.
Records belong to their workspace. They are readable by the people you have added to that workspace, at the access those people have been given. Row-level security in the database enforces that, not just the screen: a person limited to one building cannot retrieve another building’s records by any route.
CompliMaint staff administer accounts — approving beta requests, setting what a workspace may use, activating a facility — and are not members of your workspace. The administration screens show account and usage information such as how many records a workspace holds; they do not open records. If we ever need to look at your data to help with a support problem, we will ask you first.
You can export everything in your workspace at any time from Account, and ask us to delete your account and its records by writing to info@complimaint.com.
What we do not claim. Cloud Beta is early access. We have not established HIPAA compliance or any security certification for it, and it should not be used to store protected health information or other highly regulated personal information. We do not guarantee permanent retention, and you should keep your own copies of records you are required to retain. Storage is provided by Supabase and hosting by Vercel, both in the United States.
Analytics & cookies
We use privacy-conscious analytics (Google Analytics) to understand general site traffic. See our Cookies page for details.
The site also carries a tag from Impact, the affiliate network that runs the advertising link in our footer. It records that a page carrying such a link was viewed, and — if you click one — that the click came from here, so the advertiser can credit us. It does not read anything you type into the tools. What you enter into an invoice, a letter or a checklist stays on your device either way.
How your data is handled
Form submissions are transmitted over an encrypted (HTTPS) connection and delivered to our team by email. We retain submissions only as long as needed for the purpose they were sent for and for our ordinary operational purposes.
Your choices
You may request that we update or delete the information you have submitted at any time by emailing info@complimaint.com. You can also ask us to stop contacting you.
Equal opportunity
CompliMaint is an equal opportunity employer. We consider all qualified applicants without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, age, disability, veteran status, or any other characteristic protected by applicable law.
Contact us
Questions about this policy? Email info@complimaint.com.
This page is provided for general informational purposes and does not constitute legal advice.