Legal

Privacy Policy

Effective: 2026-10-30 · Version: 1.11

1. Who We Are

SquareKeeper is operated by SquareKeeper LLC ("SquareKeeper", "we", "us"), a California limited-liability company. Mailing address available on request via hello@squarekeeper.com.

2. What We Collect

We collect information in three categories:

  • Account data: name, email, property name, role, and authentication credentials for users you invite.
  • Operational data: vehicle registrations, work orders, time-clock events, photos, incident reports, and similar business records you create using the Service.
  • Location data: collected only where a feature uses it — GPS coordinates captured when staff clock in or out at an organization that has enabled geofenced time clocks, an optional location on a vendor's on-site check-in, optional GPS tags a crew chooses to attach to jobsite photos in SquareKeeper Works, and, in SquareKeeper Fleet, the coordinates stamped onto a driver's service photo at the moment of capture when the driver's device has granted location access.
  • Technical data: IP addresses, browser type, page views, and error logs for the purpose of operating the Service.
  • Website chat: if you use the "Ask SquareKeeper" assistant on this website, we store the conversation so you can return to it later. It is kept against an anonymous identifier held in your browser — not your name or email, and not tied to any account. You can erase it at any time with the assistant's Start over control, and it is deleted automatically after about 30 days of inactivity.
  • Referral cookie: if you reach this website through a referral link (a web address that carries a referral code, such as one shared by a property you work with, by another SquareKeeper customer, or by one of our referral partners: creators and others we pay to tell people about SquareKeeper), we keep that code in a first-party cookie named sk_ref so it can be filled in for you if you sign up within the next 30 days. The cookie holds only the code, never your name, email, or browsing activity; it is set only for squarekeeper.com; and it is not used for advertising or cross-site tracking. It expires on its own after 30 days, or sooner if you clear your browser's cookies, and you can change or remove the code on the sign-up form before you submit it. When a link carries a code, the page you land on may ask our servers whether the code is valid so it can show you the code's gift; that check sends only the code. If you install our Android app from such a link, Google Play passes the code to the app so it can be filled in for you; an App Store link carries the code only as a campaign name in Apple's reports, which we see as totals. If you sign up with a code, we record it on your account. When the code belongs to another customer, that customer can see your organization's name and whether the referral has been credited. When it belongs to a referral partner, the partner sees only a line for each sign-up: the date, whether it came from the web, Android or iPhone or the code was added later, whether the account was confirmed and whether it became a paying subscription. A referral partner never sees your name, your organization's name or your email address.
  • Referral partners: if you are one of our referral partners, we keep your name, your email address and sign-in, your codes and deals, the sign-up counts described above, the payments we make to you, and the payment and tax details you give us (such as a Zelle or PayPal address and an IRS Form W-9 or W-8BEN, which carry your taxpayer identification number). We use them to run the program, to pay you and to meet our tax and legal duties, and we share them only with the payment service you choose, with our bookkeeping service and our accountant, and with tax authorities where the law requires. When you accept the Referral Partner Terms, we record the version you accepted, the time, and the IP address and browser it came from, so we can show what was agreed.
  • Bot protection: on our sign-up, contact and sign-in pages, in the website assistant, and on a page that checks a referral code, we use Google reCAPTCHA v3 through Firebase App Check to keep out automated abuse. reCAPTCHA collects hardware and software information, such as device and application data, and sends it to Google for the purpose of providing, maintaining and improving reCAPTCHA and for general security purposes; Google may set its own cookie on google.com for this. Its use is subject to Google's Privacy Policy and Terms of Service. We receive only Google's answer, not that information. Where our mobile apps run the same check, they use the checks built into the phone instead (Google Play Integrity on Android, Apple App Attest on iPhone), which confirm that a request comes from our genuine app and do not identify you.
  • Advertising measurement cookies: we advertise SquareKeeper on Google, and the Google tag on this website sets first-party cookies (names beginning _gcl) that let Google Ads tell us when a click on one of our ads led to a store badge click or a sign-up here. They identify the ad click, not you, and we do not build audience lists or show you ads based on your visit. For visitors in the European Economic Area, the United Kingdom and Switzerland the tag is set to deny these cookies. Google's handling of this data is described in Google's advertising privacy page.
  • App usage data (mobile apps): starting with Restroom Manager 1.0.1, our mobile apps send Google Firebase Analytics anonymous usage events: the app was opened, a screen was viewed, a sign-up step was reached or failed, a sign was printed, a report was opened, a plan was viewed or bought. The events are tied to an installation identifier the app generates on the device, never to your email, your name, your business name or an advertising identifier, and the app asks for no tracking permission. We use them to see where people get stuck and whether our own advertising brings in customers; they are not used to build audience lists or to show you advertising. When an install came from one of our own ads or from this website, the app store passes the campaign name to the app and we keep that campaign name on the account that is created. On iPhone, when an install came from one of our own App Store ads, Apple's AdServices framework tells the app which of our ads it was (the campaign, ad group, keyword and ad, as numbers in our own advertising account); the app asks for no tracking permission and uses no advertising identifier, and we keep those numbers on the account that is created so we know which of our ads bring in customers. Before any account exists, the app also adds the campaign and ad group numbers to our anonymous install count, so we know how many installs from each of our ads open the app and reach the sign-in screen; that count carries no identifier and is not linked to you.

3. How We Use It

We use your data to provide the Service, communicate about your account, improve the product (in aggregate, anonymized form only), and comply with legal obligations.

We do not sell your data. We do not share customer data with third parties for marketing purposes. We do not use customer data to train AI models.

AI features. Some features send customer content to an AI provider in order to do their work: the daily wrap narrative, the AI File Builder (which processes the evidence you upload — emails, message screenshots, photos, PDFs), report drafting in SquareKeeper Works, the Office Assistant chat inside the application (which reads the records you ask it about, along with the messages you send it), and receipt reading. That content is processed by Anthropic (see §4) solely to generate the requested result and is not used to train AI models.

The "Ask SquareKeeper" website assistant. The assistant on this website answers questions about our products from a fixed set of information taken from these public pages. It has no access to any customer account, organization, or record. What you type is sent to Anthropic (see §4) to produce a reply, and is not used to train AI models. We keep the conversation so you can pick it up on a later visit; clearing it with Start over deletes it.

4. Subprocessors

We use a small set of infrastructure providers to run the Service:

  • Google Cloud / Firebase — hosting, database, authentication, and app analytics (Firebase Analytics, the app usage data in §2)
  • Google reCAPTCHA (through Firebase App Check): telling people from automated abuse on our sign-up, contact and sign-in pages, in the website assistant and in the referral code check, as described in §2
  • Stripe — payment processing (we never see full card numbers)
  • Twilio — SMS delivery for operational alerts (see §6 for full details)
  • SendGrid — email delivery for account, portal, and announcement email (invitations, password resets, notifications, and email announcements)
  • Anthropic — AI processing for the features described in §3 (daily wrap, AI File Builder, report drafting, receipt reading); content is processed to generate the requested output and is not used for model training
  • Plausible Analytics — cookieless analytics used across squarekeeper.com (marketing), app.squarekeeper.com (customer dashboard), portal.squarekeeper.com (tenant portal), and vendor.squarekeeper.com (vendor portal) to measure feature engagement and aggregate product usage. No cookies (the only cookie this website sets itself is the referral cookie described in §2), no personal data, no cross-site tracking, no IP addresses stored, no user profiles built. Plausible never receives phone numbers, message content, SMS recipients, or any SMS-related data — phone numbers and SMS delivery remain isolated to Twilio per §6.
  • Google Ads — measuring our own advertising on Google: the advertising measurement cookies on squarekeeper.com (§2) and, for the mobile apps, whether an install that came from one of our ads went on to create an account (reported by Firebase Analytics in aggregate; no advertising identifier is collected)
  • Apple Ads: measuring our own advertising on the App Store. On iPhone, Apple's AdServices framework reports which of our App Store ads an install came from (the campaign, ad group, keyword and ad, as numbers in our own advertising account, as described in §2); no advertising identifier is collected and the app asks for no tracking permission. Apple's handling of this data is described in Apple's privacy policy
  • YouTube (Google) — hosting and playback of the explainer videos embedded on this website. Nothing loads from YouTube until you press play; the player then loads from YouTube's privacy-enhanced domain, which sets no cookies before playback, and YouTube's own privacy policy governs what it collects while a video plays

Each subprocessor is contractually bound to protect your data. The only advertising tools we use are Google Ads and Apple Ads measurement (§2), on this website and in the mobile apps: they tell us whether our own ads worked and build no audience lists about you. The analytics we use, Plausible on our websites and Firebase Analytics in the apps, measure our product and our own advertising in aggregate; none of it builds an advertising profile of you or follows you to other sites or apps, and we use no session-recording tools that capture keystrokes or form inputs.

5. Portal Users (Tenants & Vendors)

If you grant a tenant or vendor access to a SquareKeeper portal, we store their name, email, and any data they submit (vehicle plates, maintenance requests, etc.) on behalf of the property operator. The property operator is the data controller for this information. Portal users may contact us directly to exercise data-subject rights.

6. SMS Alerts (Twilio-Sent Messages)

Phone numbers we collect. When a SquareKeeper customer enables operational SMS alerts (for example, restroom QR scan reports or work-order notifications), we collect and store phone numbers for the staff and recipients designated to receive these alerts. For the SquareKeeper Operational Alerts program, a phone number is entered by the property administrator within the SquareKeeper application only after the recipient has given prior written consent by completing and signing the SquareKeeper Operational Alerts SMS consent form. A specimen of that form, showing every program disclosure, is published at squarekeeper.com/legal/sms-consent.

How we use them. Phone numbers are used solely to deliver the operational alerts you have configured — for example, an SMS notification when a tenant scans a QR code to report a maintenance issue. We send these alerts via Twilio, our SMS infrastructure provider. We do not use phone numbers for marketing, advertising, promotional content, or any purpose other than the operational alerts you configure within SquareKeeper.

No sharing or selling for marketing. We do not sell, rent, share, or disclose phone numbers or SMS opt-in and consent data to third parties for their marketing purposes. Phone numbers are shared only with Twilio (our SMS subprocessor) for the sole purpose of message delivery. No phone-number data is shared with affiliates, advertisers, or data brokers.

Message frequency. Message frequency varies based on property events; there is no fixed cadence. See our Terms of Service §12 for full program details.

Opt-out and support. Recipients can opt out of SMS alerts at any time by replying STOP to any alert message. Reply HELP for assistance, or email hello@squarekeeper.com. Standard message and data rates may apply.

Tenant announcement SMS. Separately, tenants of a SquareKeeper customer's property may opt in to receive SMS announcements from that property (for example, building events, closures, schedule changes, maintenance notices, and reminders) under a program named “SquareKeeper Tenant.” Opt-in is explicit and self-service: a tenant signs in to the SquareKeeper Tenant Portal, opens Account › Notifications, turns on the SMS toggle (off by default), and provides a mobile number after reading the consent disclosure. The opt-in screen, showing every program disclosure, is published at squarekeeper.com/legal/sms-consent-tenant. We collect and store the tenant's mobile number solely to deliver these announcements via Twilio, our SMS subprocessor. As above, we do not sell, rent, share, or disclose these mobile numbers to any third party for marketing purposes; message frequency varies; message and data rates may apply; and a tenant may opt out anytime by turning the setting off or replying STOP (reply HELP for help). SMS consent is not a condition of tenancy.

Fleet service notification SMS. Separately, commercial customers of a waste-collection service that runs on SquareKeeper Fleet may request text notifications about service at their properties, under a program named “SquareKeeper Fleet.” Consent is collected before any text is sent, by either of two methods: office staff read the published consent script and record the contact's verbal agreement, or the office emails the contact a personal, single-use web consent link and the contact enters their own mobile number and actively checks an unchecked consent box on the linked page. Both specimens, showing every program disclosure, are published at squarekeeper.com/legal/sms-consent-fleet. No text is sent to any number until the consent event is recorded; a contact without recorded consent receives email only. We collect and store the contact's mobile number solely to deliver these notifications via Twilio, our SMS subprocessor. As above, we do not sell, rent, share, or disclose these mobile numbers or the related opt-in and consent data to any third party for marketing purposes; message frequency varies (typically a few messages per week); message and data rates may apply; and a contact may opt out anytime by replying STOP (reply HELP for help). SMS consent is not a condition of any purchase or service.

Restroom Manager alert SMS. Separately, businesses that use SquareKeeper Restroom Manager may have restroom alerts texted to their own staff and managers, under a program named “SquareKeeper Restroom Manager.” Consent is collected before any text is sent: the business owner reads the published consent script, and after an explicit yes records the person's agreement in the Restroom Manager app by checking a consent box, unchecked by default. The script, the in-app consent statement and every program disclosure are published at squarekeeper.com/legal/sms-consent-restroom. No text is sent to any number until the consent event is recorded; a person without recorded consent receives alerts by app notification and email only. We collect and store the mobile number solely to deliver these alerts via Twilio, our SMS subprocessor. As above, we do not sell, rent, share, or disclose these mobile numbers or the related opt-in and consent data to any third party for marketing purposes; message frequency varies with customer reports; message and data rates may apply; and a recipient may opt out anytime by replying STOP (reply HELP for help). SMS consent is not a condition of employment or of any purchase.

7. Data Retention

Operational data is retained for the duration of your subscription. Upon cancellation, data remains exportable for 30 days, after which it is archived. We retain your archived business records — including your SquareKeeper Works compiled reports and the client links that open them — until you request deletion, so those reports and links keep working. Some data is removed earlier: the raw source photos on a long-inactive SquareKeeper Works account are deleted after advance notice (see Terms §6 and our Data & Account Deletion page). Records we must keep to meet a legal obligation are retained for the period the law requires. When data is deleted, backup copies may persist for up to 90 days before final deletion.

Website chat conversations (§2) are deleted after about 30 days without activity, or immediately when you use the assistant's Start over control. The referral cookie (§2) expires on its own 30 days after it was set; a referral code you signed up with stays on your account record as part of your account data.

App usage events (§2) are kept by Firebase Analytics for 14 months and then deleted; the aggregate reports built from them are not personal data.

A referral partner's records (§2) are kept while the partner takes part in the program and afterward for as long as tax and accounting law requires us to keep payment records. The record of each acceptance of the Referral Partner Terms is kept for as long as those payment records.

8. Your Rights

Depending on your jurisdiction (California CCPA, EU/UK GDPR, etc.), you may have rights to access, correct, export, or delete your personal data. Email hello@squarekeeper.com to exercise these rights; we respond within 30 days.

9. Security

We use industry-standard encryption in transit (TLS 1.3) and at rest. Access to production systems is limited to authorized SquareKeeper personnel. We follow the principle of least privilege across all internal systems.

10. Children

The Service is not directed at children under 13, and we do not knowingly collect personal information from children.

11. Changes

We will notify you of material changes to this policy via email at least 14 days before they take effect. Continued use of the Service after changes constitutes acceptance.

12. Contact

Questions about this Privacy Policy? Email hello@squarekeeper.com.