Privacy Policy

Plain-language summary: Kahal stores your name, email, phone, the classes you book, and the payments you make — only so the platform works. We set no analytics cookies and store nothing on your device for analytics, which is why you see no cookie banner, and we do not record your screen. We do not sell your data. You can ask us what we hold and tell us to delete it. Questions: support@mykahal.com.

1. Who we are

Kahal is a software-as-a-service platform for community centers, operated by AmihaiTech ("we", "us", "Kahal"), a sole proprietorship based in Israel. We are the controller of personal data processed about visitors to our marketing site (mykahal.com) and account holders. For data processed about end-members of a community center using Kahal, the community center is the controller and Kahal is the processor.

The purchase terms of an organization in Israel name the organization as the controller of its buyers' data, and link back to this policy.

Contact: support@mykahal.com

2. What data we collect

2.1 Account & profile data

Name, email address, phone number (optional)
Authentication identifiers (Google OAuth ID where used; encrypted 2FA secrets and backup codes for admins)
Organization role (admin, instructor, member) and the organization(s) you belong to

2.2 Activity data

Bookings, class attendance, check-in records
Purchased passes / session packs and remaining credits
Health declaration responses and digital signatures (where the community center uses this feature)

2.3 Payment data

We do not store full card numbers. Each organization chooses one third-party payment provider, which processes member payments, returns a transaction reference and status, and issues tax invoices or receipts on the organization's behalf. Organizations in Israel choose Sumit or HYP (היפ); organizations outside Israel connect their own Stripe account, and their members' payments are processed by Stripe under that organization's own agreement with it.
When you buy a pass from an organization whose purchase terms are in force in Kahal, the checkout asks for your first and last name and your phone number, and shows the email address your receipt will go to. These details go to the organization, and to its payment provider to process the payment and issue the receipt. We also record that you accepted the organization's purchase terms: which version, and when.
For Solo and Pro subscriptions, how Kahal bills your plan depends on where your organization is based. Israeli organizations are billed through Kahal's own Sumit account: when you start a paid trial we save a payment token (a Sumit “CustomerID”) with Sumit and store only that token reference on our servers — never your full card number — so we can charge your subscription when the trial ends and at each renewal. Organizations outside Israel are billed through Paddle, which acts as merchant of record: your card details are given to Paddle and never reach our servers, and we store only Paddle's customer and subscription identifiers.
We retain transaction metadata (amount, date, gateway reference, payer identity) for accounting and legal retention requirements.

2.4 Technical data

IP address, browser type, device type, pages visited, and timestamps — for security (rate limiting, abuse prevention) and for diagnosing errors.
Site analytics — no cookies, and nothing stored on your device. Page views and interactions are captured by PostHog (EU), our product-analytics provider, in its cookieless mode: no cookie, no local storage, no device identifier of any kind. Visits are counted using a value PostHog calculates on its own servers from your IP address and browser type together with a salt it changes daily, so the count resets roughly every 24 hours and cannot follow you between visits. Client IP addresses are discarded by PostHog and not stored with events. This is why Kahal shows you no cookie banner. We use no advertising and no cross-site tracking.
Signed-in account events: when you are signed in, we also record product events (sign-ins, bookings created or cancelled, purchases initiated, onboarding steps) tied to your account. These are sent from our servers, not from your browser, and store nothing on your device. Legal bases: legitimate interest (Art. 6(1)(f) GDPR) and performance of contract (Art. 6(1)(b)); under the Israeli PPL, the notice and consent given when your account was created. You may request access to or deletion of this data — see Section 7.
Session recordings: we do not record your screen. Session replay is switched off. We previously recorded on-screen interactions for product improvement; we no longer do, and any recordings captured before this change are deleted on request — see Section 7.
The only cookies we set are the ones the site needs to work, plus a few that remember a choice you made. No analytics cookies at all. See Section 10.

2.5 Marketing-site leads

If you submit the interest form on mykahal.com, we store your name, email, and message to reply to you. If you also tick the box agreeing to it, we send you a short series of emails about Kahal. Every one of them has an unsubscribe link, and unsubscribing stops the series.

3. Why we process this data (legal bases under GDPR)

Performance of a contract — to deliver the booking, payment, and account features you (or your community center) signed up for.
Legitimate interests — security, fraud prevention, service improvement, and responding to support requests.
Legal obligation — tax and accounting record retention; responding to lawful requests from authorities.
Consent — for optional features such as health declarations or marketing emails. You can withdraw consent at any time.

Under the Israeli Privacy Protection Law, 5741–1981, our processing relies on the consent (express or implied through use of the service) you provide when creating an account or being added by a community center, together with the purposes registered for the relevant database.

We share personal data only with the following categories of recipients, and only to the extent necessary:

Hosting & infrastructure: Hetzner (servers in the EU), Cloudflare (edge / DNS / TLS).
Payment processing & invoicing (member payments): Sumit or HYP (היפ) for organizations in Israel, Stripe for organizations outside it — each organization uses one of these, which processes its members' payments and issues tax invoices or receipts on its behalf. Each is subject to its own privacy policy.
Subscription billing (your Kahal plan): Sumit for organizations in Israel; Paddle, as merchant of record, for organizations outside it. Each is subject to its own privacy policy.
Email delivery: Resend — for transactional emails such as magic links, invitations, and notifications, and for the short series of emails about Kahal sent to people who asked for it on the interest form.
Product analytics: PostHog Cloud (EU region, eu.i.posthog.com) — processes analytics events on our behalf under a Data Processing Agreement. Session replay is switched off. See PostHog's privacy policy.
Authentication: Google (where you choose to sign in with Google OAuth).
Authorities: when required by Israeli law, a court order, or a binding regulatory request.

We do not sell personal data and we do not share it for advertising.

5. International transfers

Our primary infrastructure is in the EU. Some sub-processors (e.g. Cloudflare, Google) may process data outside Israel and the EEA. For transfers from the EEA, we rely on adequacy decisions or Standard Contractual Clauses; transfers from Israel rely on the conditions set out in the Privacy Protection Regulations (Transfer of Data Abroad), 5761–2001.

6. How long we keep data

Account data: for as long as your account is active, plus up to 90 days after deletion request to handle disputes and backups.
Booking and attendance records: for as long as the community center retains them, subject to its own retention policy.
Payment and tax records: at least 7 years, as required by Israeli tax law.
Marketing leads: until you ask us to delete them, or 24 months of inactivity.
Analytics events: retained by PostHog for 1 year (the retention applied by our current PostHog plan tier). Session recordings are no longer captured; those taken before replay was switched off age out on the same 1-year window.
Server logs: typically 30 days.

7. Your rights

Subject to applicable law, you have the right to:

Access the personal data we hold about you
Correct inaccurate or incomplete data
Delete your data ("right to be forgotten" under GDPR; right of inspection and correction under Israeli PPL)
Restrict or object to certain processing
Data portability — receive your data in a machine-readable format
Withdraw consent at any time, without affecting prior lawful processing
Lodge a complaint with the Israeli Privacy Protection Authority or, if you are in the EEA, your local data protection authority

To exercise any of these rights, email support@mykahal.com. We will respond within 30 days.

If you are a member of a community center using Kahal and want to delete or correct data the center holds about you, please contact the community center directly — they are the controller of that data and we act on their instructions.

8. Security

We use industry-standard practices: TLS for all traffic, encryption at rest for sensitive fields (authentication secrets, 2FA keys, backup codes), per-user session timeouts, magic-link tokens with 15-minute expiry, rate limiting on sign-in and invite endpoints, and least-privilege access for our own staff. No system is perfectly secure — if you suspect unauthorized access to your account, contact us immediately.

8.1 Support access to your account

To diagnose a problem you report, Kahal staff can temporarily view the platform as your account sees it — the same pages, bookings, passes and payment history you see. We use this only to investigate a support request or a technical fault, never to browse accounts casually.

Every such session is recorded: which staff member started it, whose account was accessed, which organization, the time it began and ended, and the originating IP address. While it is active, a banner is shown on the page indicating that the account is being viewed by support. Staff cannot read your password (we don't store one — sign-in is by magic link or Google) and cannot see your full card number, which is held by our payment providers and never reaches Kahal's servers — only the card brand and last four digits, as shown on your own payment settings page.

You may ask us whether your account has been accessed this way, and we will tell you. Email support@mykahal.com.

9. Children

A child can appear in an organization's records in two ways. In both, a parent or legal guardian is the person who supplies the information and gives the consent — never the child.

A child added by their guardian. A guardian, or an organization admin acting at the family's request, can add a child to the organization. For that account we store the child's name and date of birth, and nothing else — no email address, no phone number. Such an account is managed: it has no sign-in of its own and never receives email from us. Bookings, attendance, passes and payments for the child are made by the guardian, and anything we would send the child is sent to the guardian instead. The child's membership in that organization records which adult is responsible for them.

Why we hold a date of birth. It tells the organization whether the person is a minor, which is what makes a guardian's consent required rather than optional. We do not use it for marketing or profiling.

Consent. Where an organization requires a health declaration or similar form, the guardian signs it for the child, and the record stores which adult signed. It is therefore always clear on the record that an adult gave the consent.

A child who is later given their own login. A guardian can give their child an email address of their own. The child confirms it from that inbox, and from that point the account is an ordinary account and the rest of this policy applies to it in full.

Erasing a child's record. A guardian can export or delete their child's data themselves, from the family page in their account. Deletion is never one click: we email the guardian a confirmation link. You can also write to support@mykahal.com. If a managed child's account is left belonging to no organization at all, we delete it automatically after 30 days.

10. Cookies

We set no analytics cookies, which is why you see no cookie banner. Our analytics provider runs in a cookieless mode and stores nothing on your device — see Section 2.4.

Everything we set in your browser, or store for it, falls into three categories:

Strictly necessary — always set. Session cookies for authentication and session continuity, and CSRF tokens for security.
Preferences — set by your own actions. On a phone, after each of your first two bookings, we may offer to add your organisation's page to your home screen. If you close that offer or install the app, kahal_pwa_dismissed records it so we do not ask again; on iPhone and iPad, where the browser cannot tell us whether you installed it, kahal_pwa_ios_seen counts how many times the offer has been shown so it stops after the second. If you close the separate offer to turn on notifications, kahal_push_dismissed records that too, so we do not ask again for 30 days. All three are scoped to a single organisation's address, hold no personal data, and are not used for analytics or tracking.
Notifications — only if you ask for them. If you turn on notifications, your browser gives us an address to deliver them to, plus two keys that let only your device decrypt them. We store those together with your browser's name, so you can see which devices are connected. We use them for one thing: reminding you about a booking an hour and a half before it starts. Turning notifications off or signing out removes that device's record right away. Revoking permission in your device settings doesn't tell us anything happened — we only find out, and remove the record, the next time we try to send you a reminder and it bounces. If you want it gone immediately, turn notifications off here instead of at the OS level. Each organisation's address is separate, so turning them on in one does not turn them on in another.

We do not use cookies for advertising, profiling, or cross-site tracking. There is no analytics consent to revoke, because no analytics cookie is ever set; if you previously answered our old cookie banner, that cookie is deleted automatically on your next visit. To object to the account-tied product events described in Section 2.4, or to ask for them to be deleted, contact us — see Section 7. Clearing all cookies signs you out.

11. Changes to this policy

We may update this policy from time to time. Material changes will be announced by email or by a notice on the platform at least 14 days before they take effect. The "Last updated" date at the top reflects the most recent revision.

This policy is published in English and in Hebrew. The Hebrew and English versions say the same thing. If they ever differ, the English version governs.

12. Contact

For privacy questions, data requests, or complaints:
AmihaiTech — Israel
Email: support@mykahal.com