Legal
Privacy Policy
Effective date: September 4, 2026 · Last updated October 16, 2026
Lock Check Cloud LLC ("Lock Check Cloud," "we," "us") operates lockcheckcloud.com (the "Site"). This policy explains what information the Site collects, why, and what we do with it. The Site currently has one function: an application form for the Lock Check Cloud Founding Member Program (our beta). There is no login or account on the Site; free-trial and payment sign-up happen on Stripe-hosted pages after your demo call.
Information we collect
When you submit the application form, we collect:
- —Name — as you enter it.
- —Work email address — used to contact you about the beta.
- —Company — the storage company or property management company you work for.
- —Role — one of four options you select (for example, Facility Manager), so we can route your application to the right person.
- —Number of facilities you manage — one of four ranges you select.
We do not ask for a password, payment information, or government ID anywhere on this Site. We do not currently run analytics or advertising tracking on this Site — see the Cookie Policy for what, if anything, is set in your browser.
How we use it
- —To follow up about your application and, if you're a fit for the beta, schedule the required demo call.
- —To understand demand for the beta by facility count (in aggregate).
- —To send you operational email about the beta you signed up for. We do not use your email for unrelated marketing without separate consent.
Who we share it with
We don't sell your information. It's shared only with the vendors that make the Site and the application form work:
- —Netlify, Inc. — hosts the Site and processes application submissions through Netlify Forms. Netlify's own privacy policy governs its handling of that infrastructure.
- —Akismet (Automattic) — Netlify Forms' built-in spam filter screens submissions for spam before they reach us.
- —Google (Google Sheets and Gmail) — a copy of your submission is also sent to a private Google Sheet we use to track applications, and Gmail is used to send you the application confirmation email. Google's own privacy policy governs its handling of that infrastructure.
- —Stripe, Inc. — if you start a free trial after your demo, your payment card is collected and processed by Stripe on Stripe-hosted pages. We never see or store your full card number. Stripe's own privacy policy governs its handling of that information.
- —Our demo-scheduling provider — if you book the required demo call, the scheduling tool collects your name, email address, and chosen time so the call can be set up. That provider's own privacy policy governs its handling of that information.
We may also disclose information if required by law, or in connection with a merger, acquisition, or sale of assets — in which case we'd expect any successor to honor the commitments in this policy.
How long we keep it
We keep application submissions for as long as useful for running the beta program and for our own business records, and delete or anonymize them on request (see below).
Your choices
You can ask us, at any time, to access, correct, or delete the information you submitted, or to stop contacting you about the beta. Email privacy@lockcheckcloud.com and we'll act on it.
If you join the beta
If you're accepted into the Founding Member Program, information you or your staff enter into the Lock Check Cloud app — such as lock-check records, photos, and notes — is governed by your Beta Access Agreement and Data Processing Addendum, not this policy. This policy covers only the Site and the application form.
We may create de-identified, aggregated data from information in the app to improve the service and build new features. That data cannot identify you, your company, your facility, or anyone else, and we commit not to try to re-identify it or let anyone we share it with do so.
California privacy rights
If you're a California resident, the CCPA/CPRA gives you the right to know what personal information we've collected about you, to request deletion of it, and to be free from discrimination for exercising those rights. We do not sell or "share" (as that term is defined under California law) the information collected through this application form. You can exercise these rights using the contact information above.
Security
We rely on our hosting, form-processing, and email providers' security practices (Netlify and Google) to protect data in transit and at rest, and we limit who at Lock Check Cloud can access application submissions. No method of transmission or storage is 100% secure.
Children
This Site is intended for business use by adults working in storage facility operations. It is not directed at children, and we don't knowingly collect information from anyone under 18.
Changes to this policy
If this policy changes materially, we'll update the date at the top of this page. Continued use of the Site after a change means you accept the update.
Legal
Terms of Service
Effective date: September 4, 2026 · Last updated October 16, 2026
Acceptance of terms
By using lockcheckcloud.com (the "Site"), you agree to these terms. If you don't agree, please don't use the Site.
What the Site is
The Site describes Lock Check Cloud, a lock-check and walk-through record platform for self-storage operators, and lets visitors apply to a limited beta, the Founding Member Program. Submitting an application is a request, not an enrollment — inclusion in the beta is at Lock Check Cloud's discretion and, per the Site, requires a demo call.
Eligibility
The beta described on this Site is currently limited to operators of self-storage facilities located in California. Applying for a facility outside that scope doesn't guarantee acceptance.
Acceptable use
When using the Site, you agree not to:
- —submit false or fraudulent information through the application form;
- —attempt to interfere with, disrupt, or gain unauthorized access to the Site or its underlying systems;
- —use the Site's content, design, or copy to build a competing offering; or
- —use any automated system to submit applications at scale.
Beta and pricing information
Pricing, founding-spot counts, free-trial terms, feature lists, and the product screenshots shown on the Site describe the Lock Check Cloud beta as currently planned and are subject to change. Product screenshots show sample data, and some are labeled as in development; the shipped product may differ. Nothing on this Site is a binding offer to sell or license software — actual beta terms, including pricing and the 14-day free trial, are set out in a separate Beta Access Agreement when an operator is onboarded. Free trials require a card on file and convert to a paid monthly subscription unless cancelled before the trial ends; cancellation and refund terms are set out in the Beta Access Agreement.
Intellectual property
The Site's text, design, and the Lock Check Cloud name and logo are owned by Lock Check Cloud LLC. You may view and share pages of the Site for personal, non-commercial reference, but you may not copy, reproduce, or reuse the Site's design or content for another commercial purpose without permission.
No warranty
The Site and the information on it are provided "as is," without warranties of any kind, express or implied. We don't guarantee the Site will be uninterrupted, error-free, or that beta acceptance, launch timing, or pricing described here won't change.
Limitation of liability
To the fullest extent permitted by law, Lock Check Cloud LLC is not liable for any indirect, incidental, or consequential damages arising from your use of the Site.
Changes
We may update these terms as the Site and the beta program evolve. The date at the top of this page reflects the last update.
Governing law
These terms are governed by the laws of the State of California, without regard to its conflict-of-laws principles.
Legal
Cookie Policy
Effective date: September 4, 2026 · Last updated October 16, 2026
This policy explains what lockcheckcloud.com (the "Site") stores in your browser, and why.
What this Site does not do
As built, this Site does not run analytics, advertising, or social-media tracking scripts, and it does not set first-party cookies to profile visitors or track you across other websites.
What this Site does use
- —Google Fonts — the Site loads the Sora typeface from Google's font servers (fonts.googleapis.com / fonts.gstatic.com). Loading a font this way sends your browser's IP address and user-agent to Google as part of that request, the same as loading any image from a third-party server. Google does not use Google Fonts requests to build ad profiles, per Google's own font-serving policy, but the request itself is a third-party network connection every visitor makes.
- —Netlify Forms — submitting the application form sends your entry to Netlify, our hosting and form-processing provider, and its built-in spam filter (Akismet) screens it. This may involve Netlify setting a minimal functional identifier tied to the form submission itself; it is not used to track your browsing beyond processing that one submission. See the Privacy Policy for how submitted data is used.
- —Netlify hosting — like any host, Netlify's infrastructure may log request metadata (such as IP address) for security and performance purposes, independent of anything this Site's own code sets.
- —Stripe checkout — if you start a free trial, Stripe's hosted checkout page sets its own cookies for fraud prevention and payment processing. Those are governed by Stripe's cookie policy.
- —Demo scheduling — if you book the required demo call, you'll use our scheduling provider's booking page, which may set its own cookies to run the booking. Those are governed by that provider's cookie policy.
Your browser controls
Most browsers let you block or delete cookies and third-party requests through their settings. Because this Site doesn't rely on cookies for its core function — browsing the page and submitting the application form both work without one — blocking cookies shouldn't break anything here.
Changes
If we add analytics, advertising, or any other tracking to this Site in the future, we'll update this page to reflect it — and add a consent mechanism if the change requires one under applicable law.
