Skip to main content
CompliMaint™RequirementsSmall care homesAssisted living & multi-siteContractorsPricingSign inTry it free
Small care homesAssisted living & multi-siteContractorsPricing
Legal

Privacy Policy

Last updated: October 2026

CompliMaint LLC ("CompliMaint," "we," "us," or "our") operates complimaint.com. We publish free document tools and calculators and run 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.
  • Earlier forms: CompliMaint previously operated a maintenance-services business that took job applications and facility service requests through this site. 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 never ask you to type a Social Security number, a bank account number or a card number into CompliMaint. Where a payment needs them, Stripe collects them on its own pages.

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 the service providers that help us operate (listed below under Service providers we use), 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 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.

A few optional features are exceptions, and each involves an address or a location you enter.

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.

Two lookups go straight from your browser instead of through our server. The evacuation route maps in the Emergency Plan builder, when you ask for them, send the facility and shelter locations to Photon (to place an address that has no saved location), to the OSRM routing service (for the driving routes) and to OpenStreetMap's map-tile servers (for the map pictures). And when you type a ZIP code into an address form, the five-digit ZIP code alone is sent to Zippopotam.us to fill in the city and state. Those services see the request and your connection's IP address, as any website you visit does; nothing else you entered is sent.

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, with it, where your visit came from: the campaign tags in the link that brought you to the site (such as utm_source and utm_campaign), the kind of site that referred you (a search engine, a social network, another website), whether you are on a phone or a computer, whether this browser has been here before, a random key this browser keeps so that a start can be joined to a finish, and a coarse city and region from your connection. There is no field in any of it that can hold text you typed into a tool: every value is an identifier from our own list of tools and categories, a campaign tag or referrer group, 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: a message or request you deliberately send us through a form, 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 account terms you accepted.

We also keep, with your account, how you reached the sign-up: the campaign tags in the links that first and most recently brought you to the site (source, medium, campaign, content and term), the kind of site that referred you, the first page you landed on (its address without anything after a question mark), which sign-up button and join page you used, and when the account was created and when its email address was confirmed. Your browser keeps the campaign tags and sends them with the join form; we keep them so we can count real sign-ups once and learn which pages and campaigns bring people. That record holds no name, email address or anything you typed into a tool, it is readable only by our own server, and it is deleted with your account. Creating an account and confirming its address are each counted once, with those same details, and an address that already had an account is not counted. 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.

Payments (Stripe)

If you connect Stripe to get paid, the identity and bank details Stripe asks for go directly to Stripe on Stripe's pages; we do not see or store them. We store your Stripe account ID and whether it can take payments.

When your customer pays, they enter their card on Stripe's checkout page; we never see the card number. Stripe tells us the result, and we record the amount, date, status, refund or dispute status, and the invoice it belongs to.

Stripe's handling is described in the Stripe Privacy Policy.

Information about your customers

When you use CompliMaint to send an invoice, estimate or billing link, it holds the details you enter about your customer (name, email, address, the document) and anything your customer submits through a billing-update link. We process that information on your behalf to deliver the document and record the payment, not for our own marketing. A customer who wants their information changed or removed can ask you, or write to us and we will pass the request on.

Service providers we use

  • Supabase — database, file storage and sign-in (United States).
  • Vercel — hosting, and Vercel Web Analytics page-view counts (United States).
  • Resend — sending email.
  • Stripe — card payments in Get Paid.
  • Google Analytics — site analytics.
  • Impact — affiliate link tracking for the advertising link in our footer.
  • US Census Bureau geocoder, Photon and OpenStreetMap Overpass — the optional address and nearby-services lookups, through our server.
  • Photon, OSRM, OpenStreetMap map tiles and Zippopotam.us — the route maps and the ZIP-code fill, straight from your browser.
  • Have I Been Pwned — when you choose a password, our server checks it against known breached passwords by sending only the first five characters of a one-way hash of it, never the password.
  • Your browser's push service (Apple, Google or Mozilla) — only if you turn on notifications.
  • Microsoft 365 — our own email.

Children

CompliMaint is not directed to children under 13, and we do not knowingly collect their personal information. If you think a child has given us information, write to us and we will delete it.

Analytics & cookies

We use privacy-conscious analytics (Google Analytics) to understand general site traffic. It receives the same usage events described above and, as Google’s tag does on any site, the address of each page you view, including anything in the link after a question mark. When the page you open, or the page you opened it from, has an email address in the part of its address after the question mark, Google Analytics is told to send nothing from that visit to the page and our affiliate partner’s tag is not loaded on it. This is checked when the page loads: if an email address only appears in the address later, while you use the page (for example, typed into a filter), Google Analytics may still receive it. See our Cookies page for details.

Test traffic is marked, not guessed. A browser driven by automated testing software declares that itself, through the browser's own automation flag, and so do the browsers our own team marks as ours. For those browsers our own usage counts and sign-up records are marked as tests and left out of reporting, and Google Analytics is told to send nothing from an automated browser. Nothing about this is worked out from your IP address, your email address or how you use the site, so an ordinary visitor is never counted as a test.

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 can ask to see, correct, export or delete the information we hold about you, or to stop marketing email, by writing to info@complimaint.com or to the postal address below. We answer within 30 days.

Contact us

Questions about this policy? Email info@complimaint.com, or write to CompliMaint LLC, 1209 Mountain Road Pl NE #12103, Albuquerque, NM 87110.

This page is provided for general informational purposes and does not constitute legal advice.

CompliMaint™

Get started

For care homesFor assisted living & multi-siteFor contractorsPricingTry it free

Tools

All toolsMoney and follow-upsWork ordersDocumentsMy FacilityWhat my facility requires

Learn

Help CenterCrash coursesHow we verify rulesFAQ

About

HomeHow CompliMaint worksIndustriesAbout CompliMaintContact ussupport@complimaint.com

Legal

Privacy policyTerms of useCookiesAccessibility
LinkedInFacebookSign in

© 2026 CompliMaint LLC.