Privacy Policy

Effective 13 October 2026

In short: Lamplighter is management software for Chabad Houses that serve travelers. The data a Chabad House enters belongs to it, and is never sold or shared. A user who connects a Google account sends contacts from Lamplighter to it, into a separate label only. Lamplighter does not read, change or delete any other contact.

1. Who we are

Lamplighter (also called Lamplighter CRM) is web-based software for Chabad houses that serve travelers. It is operated by Mendel Shpindler, United States ("we"). Contact: support@lamplightercrm.com.

2. Two kinds of data

Account data about our users (staff of the Chabad houses that use Lamplighter): name, email address, an encrypted password, and, if turned on, a browser push-notification subscription. We use it to sign users in, keep accounts secure and send system emails such as password resets and alerts.
Data a Chabad house enters (contacts, Shabbat registrations, donations, standing orders, Hebrew dates, notes, finances). The Chabad house decides what to store and why. We store and process it only on its behalf and on its instructions. Questions about this data should go to that Chabad house; if we receive such a request, we forward it to them.

3. Google user data

A user can choose to connect a Google account in Settings → Connections so that contacts from Lamplighter appear on their phone. This is optional and is done by each user separately.

What we access. We request the Google People API contacts permission (https://www.googleapis.com/auth/contacts) and the user's Google email address (openid, email).
How we use it. Lamplighter creates contacts in the user's Google Contacts under a separate label named "CRM · <organization name>", and keeps the name, phone number and email of those contacts up to date. When a contact is archived, merged or deleted in Lamplighter, we delete the contact we created in Google. If the user deletes one of these contacts in Google, we do not create it again.
What we do not do. We do not read, change or delete any other contact in the user's Google account. We do not import Google contacts into Lamplighter. We do not use Google user data for advertising, we do not sell it, and we do not use it to train artificial-intelligence or machine-learning models.
What we store. The user's Google email address, an OAuth refresh token, and the Google IDs of the contacts Lamplighter created, so that it updates them rather than creating duplicates. Only our sync service can read the token; other users of the same organization cannot.
Sharing. Google user data is not shared with anyone, except the service providers listed in section 6 that host our systems.
Disconnecting. The user can disconnect at any time in Settings → Connections. We then revoke the token with Google and stop syncing. Contacts already created stay in the user's Google account, under their label, until the user deletes them. Access can also be removed from myaccount.google.com/permissions.

Lamplighter's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

4. Email tracking

Emails a Chabad house sends through Lamplighter record opens and clicks, so the Chabad house can see who read them. Every such email includes an unsubscribe link.

5. Cookies

The app uses only the cookies needed to keep users signed in. We do not use advertising or third-party analytics cookies.

6. Where data is stored, and service providers

Supabase: database and sign-in, hosted in Seoul, South Korea.
Vercel: runs the website and app, in Seoul, South Korea.
Resend and Google (Gmail): sending emails.
Stripe, Kesher and Flowiz: payment and registration providers that a Chabad house chooses to connect. They send donation and registration details to Lamplighter.
Google, Apple and Mozilla push services: deliver encrypted notifications to a user's device.

7. Security

Each organization's data is kept separate at the database level. Data is encrypted in transit. Accounts are by invitation. Platform administrators can view an organization's data for support; every such access is logged.

8. Retention and deletion

Data is kept while the Chabad house is a customer. After cancellation it can be exported for 30 days, then it is deleted.
The raw content of requests from payment and registration providers is deleted after 90 days, and after 365 days for requests that failed.
Google data: see section 3. The stored token is removed when the user disconnects, and all stored Google data is deleted when the organization is deleted.

9. Your rights

You may ask to see, correct or delete your personal data. Users of Lamplighter can write to support@lamplightercrm.com. If a Chabad house stores your details, please contact that Chabad house; we will help it handle the request.

10. Changes

We will update the date at the top of this page when this policy changes, and tell our customers by email about any significant change.