MyShul Privacy Policy

Effective Date: October 26, 2026

1. About This Policy

This Privacy Policy explains how MYSHUL LLC (“MyShul,” “we,” “us,” or “our”) collects, uses, shares, and retains personal information. It applies to:

myshul.com, the MyShul platform, including the MyShul iOS and Android applications
myshul.com/software (also reached through start.myshul.com), our marketing website
MyShul kiosks and related hardware
Communications we send in connection with the above

This Policy covers everyone whose personal information we hold. That includes people who use the platform, members and donors whose records a Shul enters into it, visitors to our marketing website, and staff at synagogues and other organizations we contact about MyShul, whether or not those organizations ever become customers. This Policy uses several terms defined in the MyShul Administrator Terms of Service and the MyShul End User Terms of Service. “Customer” or “Shul” means a synagogue or organization that subscribes to the Services. “User” means any natural person who uses the Services, including Shul administrators, members, and donors. “Claimed Account” means a MyShul account a person has created and verified for themselves; it exists at the platform level and is not owned by any Shul. “Shul Data” means data submitted to or generated within a Shul’s workspace. By using the Services, you agree to this Policy.

2. Who We Are

Legal name: MYSHUL LLC Trade name: MyShul Entity: A Florida limited liability company Address: 2843 Pembroke Rd, Suite 3 Hollywood, FL 33020 United States Privacy contact: info@myshul.com MyShul is based in the United States, and the synagogues and organizations that subscribe to the Services are located in the United States. Individual members, donors, and other Users may be located anywhere. Wherever you are located, your information is collected, processed, and stored in the United States and is subject to United States law. By using the Services, you understand that your information will be handled in the United States.

3. How MyShul Works, and Who Controls What

MyShul is a multi-tenant platform, and it matters which category you fall into. This section is about the two categories of User: Shuls, and the members and donors whose records they hold. Not everyone this Policy covers is a User of the Services. If we hold your contact information because we approached your organization about MyShul, Section 4.10 describes that information and this section does not apply to you. Shuls decide what happens to member data. A Shul chooses what information to collect about its members and donors, what fields to create, who on its staff can see what, and how long to keep it. For that information, MyShul acts on the Shul’s instructions. If you are a member or donor and you want your information changed or removed from a Shul’s records, the Shul controls that decision, not MyShul. MyShul controls its own account and platform data. This includes your Claimed Account, your sign-in credentials, information you give us directly, and information about how you use the Services. A Claimed Account is yours, not a Shul’s. It can be associated with more than one Shul. A Shul cannot delete it, disable it, or change its credentials. Not everyone in the Services has one. A Shul can hold a record about you that you never created and cannot sign in to; Section 4.3 explains how those arise and how they differ. A Shul’s workspace is the Shul’s, not any individual’s. The workspace and the records in it belong to the organization. Whoever holds the super admin role administers the workspace on the Shul’s behalf; the role is a designation held for the Shul, not a personal possession, and it gives that individual no ownership of the workspace or the records in it. The role can pass from one person to another — when a term of office ends, when a staff member leaves — and the workspace, its records, and the Shul’s subscription are unaffected. Handing off the role does not touch anyone’s Claimed Account either, including the outgoing administrator’s, which remains their own. A person holding the super admin role can close their own Claimed Account at any time, on the same terms as anyone else.

4. Information We Collect

4.1 Information you provide

Name
Email address
Phone number
Mailing address
Account credentials (passwords are stored as salted hashes, never in readable form)
Messages you send us, including support requests and contact form submissions

4.2 Information a Shul provides about you

A Shul may enter information about you into the Services whether or not you have a MyShul account and whether or not you provided that information to MyShul yourself. This includes your name, contact details, mailing address, membership and household records, and any other information the Shul chooses to record. This also happens during onboarding. When a Shul moves to MyShul from another system, we import its existing records and may email its members an invitation to sign up. The Shul is responsible for having the right to give us those contacts.

4.3 Records that exist without an account

A record can come to exist for you without your doing anything. A Shul may enter you into the Services manually. A Shul may import you along with its other records when it moves from a prior system. A record may be created when you pay at a MyShul kiosk or check out as a guest without signing in. A record created this way is unclaimed. It is not a Claimed Account. It exists only within that one Shul’s records, is visible only to that Shul, and is not shared across the platform. It becomes a Claimed Account only if you make it one. That happens when you create sign-in credentials and verify them yourself. Until you do, no one can sign in as you. An unclaimed record is Shul Data. The Shul controls it. If you want it changed or deleted, ask that Shul — not MyShul. See Section 14.2. If you later create a Claimed Account using the same phone number the Shul has on file, the matching described in Section 9 applies.

4.4 Information generated in the Services

Depending on how a Shul uses the platform, records associated with you may include:

Membership status and household or family relationships
Dates, including dates of birth, anniversaries, and yahrzeits
Seat assignments
Aliyah honors and other synagogue honors
Hebrew names
Donation, pledge, dues, tuition, and event payment history
Invoices, receipts, and payment records
Event registrations and attendance
Notes written by Shul administrators

4.5 Custom fields

Shuls can create their own custom fields and record anything they choose in them. MyShul does not control and does not review what a Shul puts in a custom field or a notes field. If you want to know what a particular Shul records about you, ask that Shul.

4.6 Information collected automatically

When you use the Services, we may collect your IP address, device and browser type, operating system, usage and interaction data, and diagnostic and performance data.

4.7 Payment information

See Section 8, which describes payment information in full.

4.8 Records of agreement to our terms

When an individual accepts the MyShul Administrator Terms of Service on behalf of a Shul, we record who accepted them, the date and time, the IP address the acceptance came from, and the version of the terms that was accepted. We keep these records so that both sides have evidence of what was agreed and when.

4.9 Administrator activity and audit logs

We keep logs of what administrators do in a Shul’s workspace, including sign-ins and actions taken on records. These logs are used for security, troubleshooting, and audit.

4.10 Prospective customers and business contacts

We collect and hold contact information for staff at synagogues and other organizations that are not customers, obtained through our sales and outreach activities. This includes:

Name
Role or title
Organization
Email address
Phone number
Records of our outreach and of demo and sales conversations

This information is used to run our business, not to build a profile of anyone as an individual. We do not sell it. See Section 13.

5. Information That May Be Sensitive

Some information in the Services can reveal sensitive personal characteristics, and we want to be direct about that rather than leave it unsaid. Religious affiliation. MyShul is synagogue management software. A record showing that you belong to, attend, donate to, or hold honors at a synagogue can reveal religious or ethnic affiliation, whether or not you consider yourself religious. Records such as aliyah honors, Hebrew names, and yahrzeits are more specific still. Family and life-event information. Yahrzeit records identify the death of a relative. Household records identify family relationships. Custom fields. Because Shuls can create their own fields, we cannot predict or limit what categories of information a particular Shul may record. We do not ask for, and the Services are not designed to hold, Social Security numbers, government identification numbers, driver’s license numbers, health or medical records, or biometric information. There is one place where a government identification number may be collected, and it is collected by Stripe rather than by us. Each Shul accepts payments through a Stripe connected account, and that account identifies a representative. Stripe collects identity and verification information from the representative directly, which may include a Social Security number or other government identification number. MyShul does not receive that information. Stripe’s handling of it is governed by Stripe’s own terms and privacy policy.

6. How We Use Information

We use personal information to:

Create, verify, and authenticate accounts
Operate, maintain, and secure the Services
Process payments and generate invoices, receipts, and statements
Send transactional messages, including verification codes, billing notices, and account notices
Provide customer support
Operate features that use artificial intelligence, as described in Section 7
Monitor performance, diagnose problems, and improve the Services
Detect and prevent fraud, abuse, and security incidents
Keep records evidencing who agreed to our terms of service, and when
Maintain security and audit logs of administrator activity
Contact prospective customers about MyShul, and manage our sales process and customer accounts
Comply with legal obligations and enforce our terms of service

7. Artificial Intelligence

The Services include features that use artificial intelligence, provided through a third-party AI provider. This section describes what those features do today and what they are being built to do. Today. Our AI features operate on structural information about a Shul’s workspace, such as table schemas, custom field names, and the options configured within those fields. They are used, for example, to help an administrator filter or search member lists. As these features expand. We are developing AI features that will operate on member records themselves. These features will be able to read and modify records within a Shul’s workspace, including member details, custom field values, notes, and invoices. Where such a feature runs, the relevant records may be transmitted to our AI provider in order to process the request. AI features act on a Shul’s instruction. An AI feature operating in a Shul’s workspace is directed by that Shul’s administrators and is subject to the same access controls as those administrators. It does not give one Shul access to another Shul’s data. Development and improvement. We may use Shul Data to provide, maintain, secure, support, and improve the Services, where that is necessary or useful for those purposes. This includes developing, training, and improving the machine learning and artificial intelligence features of the Services. Each Shul grants us this permission in its agreement with us, and it lasts for as long as we hold the relevant Shul Data. Aggregated and de-identified data. We also create aggregated and de-identified data from Shul Data and from use of the Services — counts, trends, benchmarks, and similar statistics. Aggregated data does not identify any Shul, any User, or any individual person. We own it, we may use and publish it for any lawful purpose including analytics, benchmarking, research, marketing, and product development, and we may continue to do so after a Shul’s subscription ends. Because aggregated data does not identify anyone, it is not personal information, and Section 13 is unaffected. Our AI provider. We currently use Anthropic. Anthropic’s commercial terms provide that inputs and outputs from its commercial products are not used to train Anthropic’s models by default. This is a statement about Anthropic, not about us. It does not limit our own use of Shul Data to develop and improve MyShul’s features, described above.

8. Payment Information

8.1 What we store, and what Stripe stores

Payment processing is provided by Stripe. Each Shul operates through its own Stripe connected account and is the merchant of record for its own transactions. Card details are entered through Stripe-hosted input fields. MyShul does not receive or store full card numbers, CVC or CVV codes, PINs, or magnetic stripe data. Those are held by Stripe, which is a PCI-DSS compliant processor. What MyShul stores is limited payment method information:

Card brand
Last four digits
Expiration month and year

8.2 Payment methods you save yourself

You may save a payment method to your own MyShul account. Administrators at a Shul you are affiliated with can see the limited details listed in Section 8.1, subject to the permissions the Shul grants them. Not every administrator has access to everything; a Shul assigns roles and permissions to the people on its staff. No administrator can charge a payment method you saved without your approval. To charge it, the Shul must send a payment request. A one-time verification code is sent to your email address, and the payment proceeds only if you approve it. The request identifies the Shul, the amount, the invoice it relates to, and the schedule if it relates to a recurring rule. You may decline any request without penalty. A payment method you authorize for a specific recurring obligation may be used only for that obligation, not for one-time charges or other invoices.

8.3 Payment methods entered by a Shul administrator

This section describes a different situation, and the rules are different. Please read it. If you give your card details to a Shul administrator so they can charge you, the administrator enters those details into the Services on your behalf. A payment method entered this way may be stored by that Shul and charged again by that Shul, for one-time or recurring charges, without a further verification code. What this means in practice:

Scope. The stored payment method is available only to the Shul whose administrator entered it. It is not shared with any other Shul and is not added to your saved payment methods for use elsewhere on the platform.
Authorization. Before storing a payment method this way, the administrator must confirm that you have given the Shul permission to store it and to charge it for future payments. That confirmation is recorded. It is a representation by the Shul, not verification by MyShul, and MyShul does not independently confirm your authorization. The Shul is responsible for obtaining and documenting it.
Notice. We may notify you when a payment method is stored this way and when it is charged.
Removing it. If you want a payment method removed that a Shul stored on your behalf, contact that Shul. Under the Shul’s agreement with MyShul, the Shul is obligated to remove a stored payment method promptly on the cardholder’s request. If the Shul does not do so, you may contact us at info@myshul.com, and we may remove or disable it.

If you would rather not have a card stored this way, save the payment method to your own account instead, where the verification code requirement in Section 8.2 applies.

8.4 Recurring payments you set up yourself

You may set up recurring payments from your own account, and view, update, change the payment method for, or cancel them at any time. Changes take effect according to the billing cycle in place when you make them.

8.5 Kiosks

MyShul kiosks process cards in person through a Stripe Terminal reader. Kiosks do not save payment methods. Card data is handled by the reader and by Stripe.

9. Claimed Accounts and Multiple Shuls

Phone numbers are used as unique identifiers across the MyShul platform. This has a consequence you should understand. When a Shul adds a member by entering a phone number, and that number matches an existing Claimed Account, the Shul is shown the name on that account so it can confirm it has the right person. If confirmed, your Claimed Account is associated with that Shul. Once associated, that Shul can see your name, email address, phone number, mailing address, and the limited payment method details described in Section 8.1 for any payment methods you have saved. Which individual administrators at that Shul can see them depends on the permissions the Shul grants each of them. Seeing those details does not allow the Shul to charge you; the verification code requirement in Section 8.2 still applies. We send you an automatic email when a new Shul is associated with your Claimed Account. The same association can occur when a Shul imports records from a prior system. This means a Shul may gain access to your contact information even if you did not give that information to that particular Shul. If you do not want to be associated with a Shul, contact that Shul or write to us at info@myshul.com. If your phone number changes. Because your phone number identifies your account and is used for verification, tell us promptly if it changes or is no longer yours. Until you do, someone who later acquires that number may be able to access your account and receive verification codes sent to it. We have no way to know a number has been reassigned unless you tell us. To change the number on your account, write to info@myshul.com.

10. Cookies, Analytics, and Session Recording

The MyShul platform at myshul.com and the MyShul mobile apps do not use advertising or analytics cookies. They use only the technical storage necessary to keep you signed in and to operate the Services. Our marketing website at myshul.com/software does use cookies and similar technologies, through the following third-party services:

Service	Purpose
Google Analytics	Website usage measurement
Google Ads	Advertising measurement and conversion tracking
MouseFlow	Session recording and analytics

MouseFlow records how visitors interact with our marketing website, including mouse movement, scrolling, clicks, and pages viewed, and captures information submitted through our contact form. Input fields are configured to be masked. MouseFlow is not used on the MyShul platform or in the mobile apps. You can control cookies through your browser settings. Blocking them may affect how our marketing website functions.

11. Communications

Messages from MyShul. We send transactional messages required to operate the Services, including verification codes, payment requests, invoices, receipts, billing notices, account notices, and notices about Shul associations. These are part of the Services and are not marketing. If you are a member or donor, we do not market to you. The messages you receive through the platform are either the transactional messages described above or messages sent by your Shul. We do not use member and donor contact information to promote MyShul. We do send business outreach. We contact staff at synagogues and other organizations to tell them about MyShul, by email and by phone, whether or not their organization is a customer. Those messages are marketing. Every marketing email includes a way to unsubscribe, and we honor it. Unsubscribing from marketing does not stop the transactional messages described above, which are necessary to operate an account and process payments. Messages from Shuls. Shuls can send messages to their members through the Services. In those messages the Shul is the sender, and MyShul acts as a conduit. Questions about a message you received from a Shul should go to that Shul. Unsubscribing. Our emails include an unsubscribe mechanism. Transactional messages necessary to your account and payments may continue. Text messages. Where SMS is offered through the Services, no one receives SMS without affirmatively confirming consent first, and replies of STOP are honored automatically and immediately.

12. Service Providers

We share information with third parties that help us operate the Services:

Provider	Role
Stripe	Payment processing and storage of card credentials
SendGrid	Email delivery
Twilio	Text message delivery
Vultr	Cloud hosting infrastructure
Anthropic	Artificial intelligence features
QuickBooks	Accounting (aggregate financial totals only; not individual member records)
Salesmate	Customer relationship management and sales pipeline
Google Analytics, Google Ads	Marketing website analytics and advertising measurement
MouseFlow	Marketing website session recording

These providers may access personal information only as needed to perform their services for us. Our current subprocessor list is maintained at myshul.com/software/subprocessors/.

13. We Do Not Sell Personal Information

MyShul does not sell personal information, and does not share it for cross-context behavioral advertising. This applies to everyone covered by this Policy. It includes the contact information we hold for prospective customers and business contacts described in Section 4.10: we use it for our own outreach, and we do not sell it, rent it, or trade it. We disclose information only:

To the service providers listed in Section 12
Between Shuls and Users within the platform, as described in Sections 8 and 9
When required by law, subpoena, or legal process
To protect the rights, safety, or property of MyShul, our Shuls, or the public
In connection with a merger, acquisition, financing, or sale of assets

Payment method information is never sold or disclosed outside the platform except to Stripe.

14. Retention and Deletion

We keep information for as long as we need it to provide the Services and to meet our legal and accounting obligations. There are three situations in which a Shul’s data may be deleted, and they come from the agreement between MyShul and each Shul.

14.1 When a Shul’s data may be deleted

If a Shul stops paying. If a Shul misses a payment and does not resolve it, we may delete its Shul Data once 180 days have passed since the first missed payment. The Shul receives written notice before that happens, on the schedule set out in its agreement with us. If a Shul cancels, or its subscription is terminated. We keep the Shul’s Shul Data for 90 days after its access to the Services ends. We send written notice at least 14 days before deleting it. After the 90 days have run and that notice has gone out, we may delete the data. Where both situations apply, for example where an account is unpaid at the time of cancellation, we do not delete before the later of the two dates. A free copy is always available first. Throughout every period described above, and up until deletion actually happens, a Shul can ask us in writing for a copy of its Shul Data and we provide it free of charge. An unpaid balance does not affect this; we do not withhold a Shul’s data on account of amounts it owes us. If a Shul asks us to delete sooner. A Shul may ask us in writing to delete its Shul Data before either period above has run, and we will act on that request. We may first verify that the person asking is authorized to ask on the Shul’s behalf, and we may decline or hold a request where we are aware of a dispute inside the Shul about who is entitled to act for it, or where we reasonably believe the request is not authorized. Timing is at our discretion. Deletion requested this way cannot be undone, and it ends the free copy described above — a Shul should obtain its copy before asking.

14.2 If you are a member or donor

Shul Data belongs to the Shul. A Shul’s records about you are owned and controlled by that Shul. MyShul does not delete them at a member’s request. Direct those requests to the Shul. Ask your Shul. If you want a Shul’s records about you deleted, ask that Shul. A Shul can request deletion of its Shul Data from us, as described in Section 14.1. Your Claimed Account is separate and is not affected. Your Claimed Account exists at the platform level and belongs to you. It is not deleted, disabled, or altered by the deletion of a Shul’s Shul Data, by a change in who holds the super admin role, by a change to anyone’s permissions, or by the suspension or termination of a Shul’s subscription. A Claimed Account is deleted only at the request of the person it belongs to. To request deletion of yours, write to info@myshul.com. What can be removed is subject to the limits in Section 14.3.

14.3 What is kept regardless

Transaction records are retained. We retain records of funds processed through the Services, including transaction history, regardless of any other deletion, for accounting, audit, tax, fraud prevention, dispute resolution, and legal compliance. This applies to every deletion path described above. Records held by Stripe are governed by Stripe’s own terms and are outside our control. Backups and logs. Information may persist in backups, archives, and system logs after deletion, in accordance with our ordinary retention cycles.

14.4 Everything else we hold

Sections 14.1 through 14.3 are about Shul Data. This is how long we keep the other categories described in this Policy. We do not commit to fixed retention periods for these, and we may keep information longer where we need it for security, dispute resolution, or legal reasons. Your Claimed Account and platform data. We keep your account, your credentials, and the information you have given us directly for as long as your account exists. It is deleted at your request, as described in Section 14.2. Usage, diagnostic, and performance data collected under Section 4.6 is kept for as long as it is useful for operating and securing the Services. Records of agreement to our terms. The acceptance records described in Section 4.8 are the evidence of a contract. We keep them for as long as the agreement is in effect and afterward for as long as it could matter — a dispute, an audit, a question about what was agreed and when. These are not deleted when a Shul’s Shul Data is deleted. Administrator activity and audit logs. The logs described in Section 4.9 are kept according to our ordinary log retention cycles, which are shorter than the periods above. We may keep a particular log longer where it is relevant to a security incident or an investigation. Prospective customers and business contacts. We keep the contact information described in Section 4.10 for as long as we have a business reason to, and we remove it sooner on request. See Section 16. The backups and logs point in Section 14.3 applies to these categories as it does to Shul Data.

15. Security

We maintain administrative and technical measures designed to protect the Services, including:

Passwords stored as salted hashes, never in readable form
Encryption of data in transit
Phone-based verification during account creation
Two-factor verification mechanisms
Verification codes for charges to user-saved payment methods
Role-based restriction of access to production systems
Full card numbers handled by Stripe and never received or stored by MyShul

No system is completely secure, and we cannot guarantee that the Services will be free from vulnerability, intrusion, or compromise. If a security incident occurs, we will notify affected Shuls without undue delay and provide the information reasonably available to us, and we will provide any notice required of us by applicable law.

16. Your Choices

Some of these require a MyShul account and some do not. You may:

Access and update the information in your Claimed Account by signing in
Tell us if your phone number changes, so that your account stays secure
View, change, or cancel recurring payments you have set up
Remove payment methods you have saved to your own account
Decline any payment request sent to you for approval
Unsubscribe from non-transactional emails
Tell us to stop contacting you about MyShul. If you have received business outreach from us, you can opt out by using the unsubscribe link in the message or by writing to info@myshul.com. You do not need an account to do this
Ask us to remove your contact details if we hold them as a prospective customer or business contact under Section 4.10. Write to info@myshul.com. This applies only to contact information MyShul collected itself through sales outreach. It does not reach information a Shul holds about you, which is Shul Data controlled by that Shul — including where a Shul created an account for you, imported you from a prior system, or a record was created when you paid at a kiosk or as a guest. For those records, ask the Shul. See Sections 4.3 and 14.2
Contact a Shul about the records it holds about you, since those records are controlled by the Shul
Request a copy of information we hold about you by writing to info@myshul.com. Please describe specifically what you are looking for. We do not offer a self-service export for individual Users, and we will make reasonable efforts to respond to reasonable and lawful requests
Contact us at info@myshul.com with any privacy question or request

We do not charge for these requests and we will not deny you service for making one.

17. Children

The Services are intended for adults. A person must be at least 13 years old to register a MyShul account, and we do not knowingly permit registration by anyone under 13. Two roles carry a higher minimum. The individual who holds the super admin role for a Shul, and any individual who accepts the Administrator Terms of Service on a Shul’s behalf, must be at least 18 years old. The 13-year minimum governs registration of an account generally and does not apply to those roles. Records about children under 13 may be entered into the Services by a Shul administrator or another authorized adult, for example on a family membership record or a Hebrew school roster. The Shul is responsible for having the right and, where required, the parental or guardian consent necessary to submit those records. If you believe a child under 13 has registered an account, contact us at info@myshul.com.

18. Changes to This Policy

We may update this Policy. We will post the updated version with a new effective date and, for material changes, provide notice by email to the address on your account or by prominent notice within the Services. Continued use of the Services after the effective date constitutes acceptance. We maintain an archive of prior versions and will provide a copy on request.

19. Contact Us

MYSHUL LLC | 2843 Pembroke Rd, Suite 3, Hollywood, FL 33020 | info@myshul.com