Privacy Policy

Mazel is a matchmaking CRM platform built for Jewish shadchanim, shadchan organizations, and singles seeking matches. We provide software that helps organizations manage singles profiles, suggest and track matches, facilitate communication between parties, and manage team workflows.

Mazel is a professional matchmaking platform. Mazel is operated by Mazel CRM (the "Company"). For privacy inquiries, contact privacy@mazelcrm.com.

For purposes of this Privacy Policy, "Mazel," "we," "us," or "our" refers to the operator of this platform. Our primary contact for privacy matters is privacy@mazelcrm.com.

There are several categories of people who interact with Mazel, each with different relationships to data:

• Shadchanim (matchmakers): professionals who use the platform to manage their singles and matches
• Organization admins: administrators who manage a shadchan team and their settings
• Singles: individuals whose profiles are created and managed on the platform, who may also have their own accounts
• Super admins: Mazel operators who manage the platform overall

2.1 Account data

When you create an account, we collect:

• First and last name
• Email address
• Password (stored as a one-way hash: we never see or store your actual password)
• Your role on the platform (shadchan, org admin, single, etc.)
• Account creation date and last login date

2.2 Organization data

For shadchan organizations, we collect:

• Organization name
• Organization logo (if uploaded)
• Seat count and subscription tier
• Team member list and their roles

2.3 Singles profile data

This is the most sensitive category of data on our platform. Singles profiles may contain:

• First and last name (and Hebrew first and last name, where provided), date of birth, age, gender
• Location (city, state, country)
• Contact information (phone number, email address)
• Parent or family contact details (name, phone number, email address), where a shadchan records them
• Photos (profile photos and additional gallery photos)
• Resume / shidduch resume document
• Height
• Religious background and observance level
• Working/learning status and related preferences
• Shlichus interest
• Education history (schools attended, degrees)
• Work history (employers, positions)
• Personal references (names, phone numbers, relationship)
• Matchmaker notes and follow-up records
• Match suggestions, responses, and pipeline status
• Dating history and date tracking entries
• Tags and categories assigned by shadchanim
• A record of whether AI processing was consented to for this profile, and when

Singles profiles are created and managed primarily by shadchanim. If you are a single whose profile exists on the platform, you have rights to access, correct, and request deletion of your data. See Section 11.

2.4 Communication data

• Messages sent between users within the platform (text, photos, voice notes)
• Text transcriptions of voice notes (see Section 6)
• Match idea suggestions and responses
• Profile shares and share recipient logs
• In-app notifications and read status

2.5 Booking and scheduling data

• Consultation appointment details
• Service type and notes
• Booking status and history

2.6 Automatically collected data

• IP address and approximate geographic location
• Browser type, operating system, and device type
• Pages visited and features used, with timestamps
• Referring URL (how you arrived at Mazel)
• Error logs and crash reports
• API usage statistics: which feature ran, for which account and organization, and what it cost us (see Section 6.1)

2.7 Push notification subscription data

If you enable browser push notifications, we store:

• Your push subscription endpoint URL (provided by your browser)
• Encryption keys for the push subscription (p256dh and auth keys)
• Your browser/device user agent string

If you enable notifications in the Mazel iOS app, we store the device token issued to the app by Apple Push Notification service, together with the platform (iOS) and the time it was last refreshed, so we can deliver notifications to that device. If you enable notifications in the Mazel Android app, we store the equivalent device token issued by Google's Firebase Cloud Messaging service, together with the platform (Android) and the time it was last refreshed.

2.8 Share-link viewer data

A shadchan can send a single's profile to someone who does not have a Mazel account, using a share link (see Section 7). Before the profile is displayed, the person opening the link must enter their first name, last name, and email address. We record those details, the profile and share they relate to, and the time of the view. They are shown to the shadchan who sent the link and to Mazel operators as a lead, and the shadchan is notified the first time the link is opened.

We use your data for the following purposes:

• Platform functionality: to create and manage your account, display your profile, process match suggestions, facilitate messaging, and provide all core platform features
• Authentication and security: to verify your identity when you sign in and protect your account from unauthorized access
• Notifications: to notify you of match ideas, responses, messages, bookings, and other relevant activity, via in-app notifications, email, and browser push (with your permission)
• AI-powered features: to power resume and document scanning, photo headshot detection, voice-note transcription, profile summaries, content screening, and the help assistants. Section 6 lists every AI feature and what each one sends
• Billing and payments: to process subscription payments and manage your plan. Subscriptions purchased in the iOS app are processed by Apple; subscriptions purchased on our website are processed by Stripe. See Section 6.4.
• Referral tracking: to apply referral credits when users join via a referral link
• Platform improvement: to understand how the platform is used, diagnose errors, and improve the product (using aggregated, anonymized data only)
• Legal compliance: to comply with applicable laws, respond to lawful requests, and protect our legal rights

We do not:

• Sell personal information for monetary consideration or disclose it to third parties for their independent commercial use
• Use personal information to serve targeted or behavioral advertising to you or others
• Make a single's profile visible to another organization automatically, in bulk, or as part of any shared or cross-organization directory
• Use your personal information to train machine learning or AI models for our own or any third party's benefit

Profile sharing is different, and it is deliberate: a shadchan can choose to send one specific profile to one specific person, including a matchmaker in another organization or someone with no Mazel account at all. Section 7 describes exactly what that sends and what it withholds.

If you are located in the European Economic Area (EEA) or the United Kingdom, we process your personal data under the following legal bases:

• Contract performance: processing necessary to provide the service you signed up for (account management, core platform features)
• Legitimate interests: fraud prevention, platform security, product improvement, and sending transactional notifications related to your use of the platform
• Consent: for push notifications and any optional marketing communications (you can withdraw consent at any time)
• Legal obligation: when we are required by law to process or retain data

For sensitive personal data (religious affiliation, etc.), we rely on your explicit consent, which you provide by using the platform and submitting a profile. Where a profile was created by a shadchan rather than by the individual it describes, the organization that entered the data is responsible for obtaining that consent before entering it, as our Terms of Service require.

Mazel necessarily handles categories of personal data that are considered sensitive under privacy laws, including:

• Religious beliefs and practice level
• Ethnic and cultural background (where relevant to matchmaking)
• Relationship status and history

We apply the following additional protections to sensitive data:

• By default, sensitive profile fields are accessible only to members of the organization that holds the profile. The one exception is a share a shadchan deliberately sends (Section 7), which releases a fixed list of resume fields to the specific person it was sent to.
• Sensitive data is not used for any purpose outside of facilitating matchmaking
• We do not aggregate or analyze sensitive data across organizations or profiles for any purpose other than direct service delivery
• Row-level security policies in our database scope ordinary queries to your own organization. A shared profile is not released by relaxing those policies: it is served by a server-side route that first verifies a specific share recorded for a specific recipient, and then returns only the allowed fields.

6.1 Where AI is used, and what each feature sends

Our AI provider is OpenAI. Every AI feature in Mazel sends data to OpenAI's API, and this is the complete list of them. Nothing else on the platform sends your data to an AI provider.

• Resume and document scanning (GPT-4o-mini): when a shadchan (or a single uploading their own resume) scans a resume or profile document, the pages of that document are uploaded to OpenAI and read to extract profile fields (name, contact details, education, work history, references, religious background, and so on). This is a manual action, and it requires AI-processing consent. The uploaded copy is deleted from OpenAI's file storage once the scan finishes.
• Bulk resume import (GPT-4o): when a matchmaker imports a batch of files at once, each file is sent to OpenAI to identify what it is (a resume, a photo, something unusable) and to extract the fields it can read, so the files can be grouped into people. This also requires AI-processing consent.
• Headshot detection in photos and resumes (GPT-4o, vision): a photograph you upload (or an image our server extracts from an uploaded resume PDF) is sent to OpenAI to locate the face in it, so the picture can be cropped to a headshot.
• Voice-note transcription (Whisper): audio you record as a voice note in messaging is sent to OpenAI and returned as text.
• Content screening (OpenAI moderation): free text that people write is sent to OpenAI's moderation endpoint to check it for abusive or objectionable content before it is delivered or saved. This applies to message bodies (direct messages and group chats, including poll questions and answer options), free-text profile fields when a profile is created or edited, intake-form and kiosk sign-up submissions, profiles created by a parent or family member, and follow-up message templates. We do this to keep the platform safe and to meet app store requirements for user-generated content. Content that is not screened automatically can still be reported in the app, and reports are reviewed.
• Profile summaries (GPT-4o-mini): when a shadchan asks for a summary of a profile, the free-text description of the person and of who they are looking for is sent to OpenAI to be condensed into a couple of sentences, which is then stored on the profile. The person's name is not included in that request.
• In-app help assistant (GPT-4o-mini): the messages you type to the assistant and your role on the platform are sent to OpenAI.
• Assistant on our public website (GPT-4o-mini): messages typed into the assistant on our marketing site are sent to OpenAI. No account is needed to use it, and we do not attach it to an account.

We also record which AI feature ran, which account and organization ran it, and what it cost, so we can monitor spend. Those records contain no message, document, or profile content.

6.2 How OpenAI handles what we send

OpenAI's API terms state that data submitted through the API is not used to train OpenAI's models, and is retained only for a limited period for abuse monitoring. See openai.com/enterprise-privacy. We do not use your data to train any model of our own.

6.3 Categories of third-party service providers

We use the following categories of third-party service providers. These providers access personal data only as necessary to perform services on our behalf and are contractually prohibited from using it for other purposes. Our current service providers include:

• Cloud infrastructure and database hosting (Supabase), to store and process application data
• Authentication providers (Supabase), to manage account credentials and sign-in
• Application hosting (Vercel), which serves the website and the app's API and keeps short-lived request logs
• AI processing providers (OpenAI), for the features listed in Section 6.1
• Payment and subscription providers (Apple, Stripe, RevenueCat): see Section 6.4
• Transactional email providers (Resend), for account notifications and communications
• Communications infrastructure (Daily.co), for voice calling features (where available)
• Push notification delivery (Apple Push Notification service for the iOS app; Google Firebase Cloud Messaging for the Android app), to deliver notifications to your device
• Rate limiting (Upstash), which briefly stores counters keyed to an account or IP address to block abuse
• Error monitoring providers (Sentry), to diagnose crashes and improve reliability

A current list of our service providers is available upon request at privacy@mazelcrm.com. We will update this section when we add or change material service providers.

6.4 Payments and subscriptions

Mazel is sold through two separate billing paths, and which one applies depends on where the subscription was purchased:

• In the Mazel iOS app: the purchase is an Apple In-App Purchase. Apple processes the payment and holds the billing relationship; we never see or receive your payment card details. We use RevenueCat as our subscription-management provider: it receives your Mazel account identifier and the subscription events Apple reports (purchase, renewal, cancellation, billing problem, expiry) and passes them to us so we know what your account is entitled to. We store the resulting subscription status, the Apple transaction identifier for your subscription, and the date the current period ends.
• On our website: the payment is processed by Stripe. Stripe receives your name, email address, and payment details directly and holds your card data; we store the Stripe customer and subscription identifiers and your subscription status, not your card number.

Apple, Stripe, and RevenueCat each handle your data under their own privacy policies as well as ours.

We do not sell, rent, or trade your personal information. We share data only in the following limited circumstances:

• With your organization: Singles profile data is visible to the shadchanim and admins of the organization that holds the profile. No other organization can browse, search, or list it.
• With service providers: The third-party infrastructure providers listed in Section 6 receive data only as necessary to provide their services. They are bound by data processing agreements.
• With people a shadchan deliberately shares a profile with: sharing a profile is a core feature of Mazel, and it can reach outside your organization. See Section 7.1.
• For legal reasons: We may disclose data if required by law, court order, or to protect the rights, property, or safety of Mazel, our users, or the public.
• In a business transfer: If Mazel is acquired or merges with another company, your data may be transferred as part of that transaction. We will notify you before your data is subject to a different privacy policy.

7.1 Profile sharing, in detail

Sending a profile to another matchmaker is how shidduchim actually get made, so Mazel supports it directly. It is always a deliberate act by a shadchan in the organization that holds the profile, always one named profile at a time, and always to recipients that shadchan chooses. There is no automatic, bulk, or background sharing, and no shared pool of profiles that other organizations can browse.

A shadchan can send a profile to:

• Another Mazel matchmaker, including one in a different organization. The shadchan searches for that person by name or email address and picks them. The recipient gets a direct message and a read-only copy of the profile in their "Shared with me" area. Nothing else about your organization becomes visible to them, and they do not gain access to any other profile.
• Someone with no Mazel account, using a share link. Before the profile is shown, that person must enter their first name, last name, and email address, which is recorded as described in Section 2.8. Anyone who receives the link and completes that step can see the profile.
• A single's own account, or an approved parent or family member of the single whose profile is being shared.

A matchmaker who was sent a profile can forward it onward to another matchmaker. Forwarding is capped in length and a forwarded copy can never outlive the share it came from.

What a share sends

A single, fixed list of resume information (the same list for every share, in the app and over a link): name and Hebrew name, age and date of birth, gender, height, location, profession, the profile photo and the additional photos, the religious profile (observance, background, yeshiva or seminary, dress and head covering, and similar fields), working or learning status, languages, education and work history, references (including a reference's phone number and email address, so the recipient can call them), the free-text description of the person and of who they are looking for, and, if one is attached, the resume document itself.

What a share withholds

The single's own phone number and email address, and the parents' contact details, are not included: contact stays with the shadchan. Neither is anything from the matchmaker's internal workspace: private notes, AI summaries, tags, the activity and follow-up history, who the profile is assigned to or who brought them in, or the pipeline status.

One honest caveat: the resume document is written by the single or their family, not by us, and a shidduch resume very often prints contact numbers on it. A recipient who opens the attached document may therefore see contact details that the profile fields themselves withhold. If that matters to you, ask the shadchan not to attach the document.

A share stays open until someone closes it: the shadchan who sent it can revoke it at any time, and the single can switch their own share links off from their profile at any time. Revoking also revokes anything that was forwarded from it. Shares no longer expire on a timer: a link that was sent months ago still works unless it has been revoked or switched off. The shadchan is notified the first time a share link is opened.

We retain your data for as long as your account or your organization's account is active, or as needed to provide services. Specifically:

• Active accounts: Data is retained indefinitely while the account is active
• Canceled or terminated accounts: Upon written request to privacy@mazelcrm.com, we will initiate deletion of your personal data and complete deletion within 30 days of receiving the verified request, subject to the exceptions noted below. Account data may be retained for up to 90 days following cancellation to allow for account recovery.
• Singles profiles: When a single's profile is deleted, the profile record and everything attached to it in our database (notes, references, match history, shares and the view records of those shares) is deleted with it. The photo and resume files themselves are removed from storage when the account they belong to is deleted, or on request to privacy@mazelcrm.com.
• Share links and share leads: A share link stays open until it is closed. It does not expire on a timer. The shadchan who sent it can revoke it at any time, the single can switch their own share links off, and revoking a share also revokes anything that was forwarded from it. The record of the share, including the name and email of anyone who opened a share link (Section 2.8), is retained with the profile it relates to and is deleted when that profile is deleted.
• Messages: Conversation messages are retained while the associated accounts are active. You may request deletion of specific messages.
• Payment records: Billing records may be retained for up to 7 years as required by tax and accounting laws
• Push subscriptions: Automatically removed when a subscription expires or is revoked by your browser; you can also manually remove them from your browser settings

Exceptions: We may retain data longer when required by applicable law, necessary for pending legal proceedings or disputes, required for billing dispute resolution, or during standard backup retention cycles.

You may request a full export of your data before deletion. To do so, contact privacy@mazelcrm.com.

Cookies

We use cookies for the following purposes:

• Authentication session cookie: set by Supabase Auth to keep you logged in. This is a strictly necessary cookie required to use the platform.
• Organization preference cookie: remembers which organization you were viewing if you have access to multiple organizations. This is a functional cookie.
• App-detection cookies: set when the site is opened inside the Mazel iOS app, so the app can be shown the right version of certain screens. They contain no personal data. Functional cookies.
• Share-link cookie: when someone opens a profile share link and enters their details (Section 2.8), we set a signed cookie recording that this browser completed that step, so the profile, its photos, and the resume stay viewable without asking again. The cookie holds no readable personal data and cannot be read by the page. Strictly necessary for that feature.
• Referral cookie: if you reach our website through another user's referral link, we remember that referral code for 30 days so the referral can be credited if you sign up. Website only.

We do not use advertising cookies or third-party tracking cookies.

Local storage

We use your browser's local storage (not cookies) to remember small preferences, such as whether you have dismissed certain in-app prompts (e.g., push notification permission request). This data never leaves your device.

We take security seriously and implement the following protections:

• All data is encrypted in transit via HTTPS/TLS
• All data is encrypted at rest in Supabase's infrastructure
• Passwords are hashed using industry-standard algorithms (bcrypt via Supabase Auth). We never store or see plain-text passwords
• Row-level security (RLS) policies in PostgreSQL ensure each user can only query data they are authorized to access. Where a feature has to cross that boundary, such as serving a profile to the person it was deliberately shared with, the request is handled by a server-side route that verifies the specific share first and returns only the fields listed in Section 7.1.
• Authentication uses industry-standard JWT tokens with short expiry windows and automatic refresh
• Service-level API keys are stored only in server-side environment variables and never exposed to the browser
• File uploads (photos, resumes, voice notes) are stored in cloud storage. Files you upload now go to private storage and are served through routes that authorize the viewer before issuing a short-lived link: the members of the organization that holds the profile, the person a profile was deliberately shared with, and, for a share link, only someone who has completed the step described in Section 2.8 in that same browser. A limited number of files uploaded before we moved to private storage still sit in an older storage area that a signed-in Mazel account could reach directly; we are moving them, and you can ask us to delete any of your files at any time (Section 11).

No digital system is 100% secure. If we become aware of a security breach that affects your personal data, we will notify affected individuals in accordance with applicable law. We will make commercially reasonable efforts to provide notification without unreasonable delay, and take all necessary steps to contain and remediate it.

If you discover a security vulnerability, please report it to privacy@mazelcrm.com before making it public.

Depending on your location, you may have the following rights regarding your personal data:

• Right to access: You can request a complete copy of all personal data we hold about you.
• Right to correction: You can request correction of inaccurate or incomplete personal data.
• Right to deletion: You can request that we delete your personal data. We will do so within 30 days, except where we are required by law to retain it.
• Right to restriction: You can request that we restrict how we process your data while a dispute is being resolved.
• Right to portability: You can request your personal data in a structured, machine-readable format, upon written request to privacy@mazelcrm.com. We will fulfill verified portability requests within 30 days.
• Right to object: You can object to processing based on legitimate interests. We will stop unless we have compelling grounds.
• Right to withdraw consent: Where processing is based on consent (e.g., push notifications), you can withdraw consent at any time without affecting the lawfulness of prior processing.

To exercise any of these rights, email privacy@mazelcrm.com with your request. We will respond within 30 days. We may need to verify your identity before fulfilling the request.

If you are in the EEA and believe we are not handling your data correctly, you have the right to lodge a complaint with your local supervisory authority (your country's data protection regulator).

If you are a California resident, you have additional rights under the California Consumer Privacy Act (CCPA):

• Right to know: You can request disclosure of the categories and specific pieces of personal information we have collected about you, the sources from which it was collected, the business purposes for which it was used, and the categories of third parties with whom it was shared.
• Right to delete: You can request deletion of your personal information, subject to certain exceptions.
• Right to opt out of sale: We do not sell personal information. You therefore do not need to opt out of any sale.
• Right to non-discrimination: We will not discriminate against you for exercising your CCPA rights.

To submit a CCPA request, email privacy@mazelcrm.com. We will respond within 45 days.

California Privacy Rights Act (CPRA): We limit our use of sensitive personal information (including religious beliefs, racial or ethnic origin, and relationship history) to purposes necessary to provide the matchmaking services you have requested. We do not use sensitive personal information for any secondary commercial purpose.

Residents of Virginia, Colorado, Connecticut, Texas, and other states with applicable privacy laws have rights similar to those described above, including rights to access, correct, delete, and obtain a copy of personal information. To exercise these rights, contact privacy@mazelcrm.com. We will respond within the timeframe required by applicable law.

Mazel is a professional matchmaking platform intended for adults. We do not knowingly collect personal information from anyone under the age of 18. Users are required to confirm they are 18 or older at the time of account creation. If we learn that a user is under 18, we will terminate the account and delete associated data promptly upon notification. Matchmaking services facilitated through the platform are intended only for adults of marriageable age.

If you believe a minor has submitted data through our platform, please contact us at privacy@mazelcrm.com and we will promptly delete it.

Mazel is operated from the United States. If you are located outside the United States, your data will be transferred to and processed in the United States, where data protection laws may differ from those in your country.

We maintain data processing agreements with our infrastructure providers as required by applicable law. For transfers of personal data from the European Economic Area, we rely on appropriate transfer mechanisms including Standard Contractual Clauses where applicable.

We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or for other reasons. When we make material changes, we will:

• Update the "Last updated" date at the top of this page
• Notify you via in-app notice at least 7 days before material changes take effect, and will also attempt email notification where feasible

Continued use of the platform after the effective date constitutes acceptance of the updated policy. If you disagree with the changes, please stop using the platform and contact us to request data deletion.

For any privacy-related questions, requests, or concerns, please contact us: