Privacy Policy

עברית · Terms

About this policy

Effective date: October 21, 2026. This policy covers joinbji.com and the current BJI pilot waitlist. BJI’s founder manages the list and decides why and how its personal information is used, acting as the data controller. Contact support@joinbji.com for privacy questions or requests.

Data you provide

We collect your email address, chosen language, practitioner or reviewer interest, signup source, registration time, and contact preferences. Current forms ask you to choose practitioner, reviewer, or both, and provide email and email-update consent, not identity documents, belt certificates, or an entrance test. Optional self-reported belt, completed training years, name, and phone details submitted through earlier forms can remain in existing records. We record the time email ownership is confirmed; this does not verify identity or BJJ qualifications. Consent records include times and the consent-text version. We also hold unsubscribe identifiers and opt-out or delivery-suppression status. Support messages contain the address, message, and any attachments you choose to send. Do not send identity documents or unnecessary sensitive information.

Your choice to provide data

Registration is voluntary; you are not legally required to join or provide these details. A role choice, an email address, and permission for registration and launch emails are needed for this notification list. New welcome emails include a seven-day link for confirming inbox ownership by opening the valid link, without a second button press. Existing signups are not automatically confirmed or sent another welcome email. Contact support if you need a fresh confirmation link. Confirmation does not reverse an opt-out or authorize new purposes. Belt, training years, name, and phone are not conditions of joining. A phone number alone never gives permission for SMS. No SMS provider is connected and no SMS messages are currently sent.

Request, security, and delivery data

When you visit, the hosting infrastructure processes connection and request information such as your IP address, requested page, request time, and browser or device information supplied by your browser. Signup protection uses a changing, secret-derived hash of the IP address to count attempts; the signup database does not save the raw IP address in the registration record. This security identifier is not a customer profile. We store queued email content, recipients, provider message identifiers, attempt and status information, and delivery, bounce, or complaint events to operate and troubleshoot messages. Cloudflare also uses your connection IP address in short-window counters to limit repeated analytics requests and protect service capacity. These counters are separate from registration and analytics records; we do not send their IP keys to PostHog. Excess analytics events may be discarded without blocking page access or signup. Delivery diagnostics also include a limited provider error or bounce explanation and SMTP diagnostic codes when supplied. These may include an email address or mail-server information and are visible only in restricted administration; full provider response bodies are not stored as diagnostics or copied into application logs. Operational logs in Cloudflare record internal registration and email-job identifiers, request or scheduled-run identifiers, action names, status codes, timing, and restricted code locations for troubleshooting. These identifiers can be linked to registration records by authorized administrators. We do not intentionally include contact details, message bodies, confirmation or unsubscribe tokens, full URLs, or raw exception messages in these application logs. Logs have separate provider retention (currently three days on Workers Free or seven days on Workers Paid); deleting a registration does not immediately erase previously written operational logs. We also collect limited browser error reports for troubleshooting: a page category, an approved script filename and code location, and an error category. Reports exclude error messages, full URLs, stack contents, form data and persistent browser identifiers; browser privacy opt-outs are honored. Cloudflare processes the connection IP for rate limiting; our incident records do not store it. Browser reports are untrusted and capped separately from server incidents. Bounded incident counts and up to ten examples per category per UTC day are kept in D1 for up to eight days with daily cleanup. At most two alert-email submission attempts per UTC day send summaries and internal diagnostic identifiers to the operator through Resend. These summaries can remain in the operator mailbox until removed; deleting a registration does not automatically remove these separate incident summaries or emails.

Cookies and analytics

BJI uses anonymous visit and signup reporting to understand traffic sources and successful registrations. A random identifier is kept in this tab’s session storage under bji-visit and renewed after 30 minutes without activity, or after 24 hours. Closing the tab normally clears it. It does not identify you across later visits or devices. Tagged sources take precedence over referring-domain classification; missing sources remain direct/unknown. We honor Global Privacy Control and Do Not Track and exclude development previews and administrator pages. Blocking JavaScript or storage can reduce coverage or cause visits to be counted again. Signup still works without analytics.

When PostHog is enabled, our Cloudflare Worker sends PostHog anonymous pageview and server-confirmed new-registration events. They contain random browser/session/event identifiers, event time, language, a normalized public-page category, traffic source, and validated medium, campaign, and post labels from tagged links. New-registration events also include the selected role: practitioner, reviewer, or both. Campaign labels allow only letters, digits, underscores, and hyphens, up to 64 characters; marketing links must not contain personal information in these labels. The first attribution is retained within the current visit. We use these events to measure page-to-registration conversion by role and campaign, without identifying return visitors across sessions or devices. We do not forward contact details, other form contents, full query strings, raw referral URLs, browser IP addresses or user-agent headers. PostHog person profiles, session replay, automatic click/form capture, heatmaps and advertising connections are disabled. Our PostHog project uses EU hosting and IP anonymization; provider operational and support processing may still involve international transfers. Free-plan events and metadata have a one-year guaranteed retention period; older data may be deleted or moved to cold storage. Anonymous identifiers are pseudonymous data, not a promise that all data is inherently non-personal.

PostHog replaces the custom analytics collector when enabled. While disabled, first-party reporting records visit time, normalized channel, campaign labels, signup attempts, validation failures and saved registrations in Cloudflare D1. Those analytics tables do not store contact details, raw referral URLs or IP addresses. Legacy visit details are removed after 90 days without activity; nonidentifying time/channel aggregates remain. Existing historical records are not automatically imported into PostHog. Analytics delivery is best effort; D1 registrations remain authoritative. PostHog is enabled for production traffic; development previews remain excluded.

The public waitlist has no customer login or advertising cookie. The private administrator area uses authentication cookies, and security infrastructure may process necessary browser signals. Any future expansion requiring consent will be explained and enabled only with the required consent.

Optional accessibility display settings are stored only in this browser using local storage under bji-accessibility. BJI does not receive these choices or use them for analytics or advertising. Reset removes them. If storage is blocked, settings work only for the current page.

Why we use information

We use the information to maintain the waitlist, record your choices, send a welcome and a requested launch update in your language, inform the founder of registrations, consider reviewer interest, answer support requests, and prevent abuse. Delivery records help us retry failed messages and honor bounces, complaints, and opt-outs. We use operational errors and support feedback to improve reliability. This does not authorize unrelated marketing, sale of your information, or new tracking.

We use first-party visit reporting to identify signup problems and measure traffic and signup conversion by page, selected role, marketing channel, campaign, and post. We may send up to three email-confirmation reminders, starting after six days and spaced at least six days apart. Reminders stop after confirmation, unsubscribe, or email suppression.

Legal grounds

Where the GDPR or a similar law applies, consent is the basis for the requested email updates and any separately agreed future SMS. You can withdraw consent without affecting processing that was lawful beforehand. Our legitimate interests in running a reliable, secure waitlist support necessary administration, abuse prevention, support, delivery troubleshooting, and keeping evidence of communication preferences, subject to your rights and interests. We may retain or disclose information where a specific legal obligation requires it. Acceptance of the Terms of Service is not consent to optional data uses.

Service providers

Hosting, database, and security providers process website requests and store registration details, consent records, queued email content, and delivery records to operate and protect the website. The founder accesses these records through restricted administration.

Email delivery providers process recipient addresses, message content, and delivery identifiers to send welcome and launch emails and report delivery, bounce, or complaint events. They also send a separate registration notification to the founder’s mailbox. That notification contains the submitted contact details, language, interest, reviewer details when supplied, signup time, and SMS preference. The founder’s mailbox provider processes that notification, and your own email provider processes messages delivered to you.

Support email providers process your sender address, messages, attachments, and correspondence metadata when you contact support@joinbji.com or reply to a BJI email. The founder uses that mailbox to handle your request. Support conversations are held in the mailbox and are not automatically copied into the registration database.

When enabled, PostHog processes the limited analytics events described above. No registration contact details are sent to PostHog. See https://posthog.com/privacy and https://posthog.com/terms for the provider’s terms.

Sharing links

The public email and WhatsApp sharing links contain a suggested message and public landing-page URL, without your signup details or private unsubscribe link. If you choose to share, the messaging service or your email app and provider process that action under their own privacy terms.

Development previews

If you use a development preview instead of joinbji.com, a tunnel provider relays the request to a developer’s local application and separate local database. When preview email sending is enabled, an email delivery provider routes test messages to the developer’s configured recipient. They are not delivered as production signup messages. Use test details for previews.

AI and future services

The current service has no external AI model or AI API integration. It does not accept AI prompts or footage for automated analysis, and it does not send registration data, support messages, or user content to an AI model for inference or training. There is therefore no external AI inference retention period or model-training use in the current application flow. This statement concerns BJI’s data flows; it is not a blanket claim about every infrastructure provider’s separate products.

The intended review service uses human reviewers. Video uploads, payments, SMS delivery are not active. First-party visit reporting is described above. Before introducing AI or other new data flows, we will explain who processes the information, what is sent, the purpose, retention, training use where relevant, and your choices, and obtain consent where required.

Other disclosures and international processing

We do not sell personal information or share it for cross-context behavioral advertising. We may disclose information when legally required or necessary to protect rights and investigate abuse, limited to the relevant purpose. The infrastructure and email providers described above may process information outside your country. The configured outbound email region is Ireland and the database has been recorded in Western Europe; these settings do not establish exclusive European processing or residency for every provider, mailbox, support operation, or backup. Contact support for information about the recipients, locations, and transfer protections applicable to your information. Any transfer subject to GDPR or other restrictions requires an applicable legal transfer mechanism; this notice does not assert that unverified contractual safeguards are already in place.

Retention

We retain registration and contact-preference records while operating the pilot list and until deletion is requested under the current process. There is no automatic expiry date for the waitlist records. Unsubscribing keeps the registration and opt-out status so we do not contact you again; it is not deletion. Queued email bodies and delivery history remain linked to the registration until removed. Delivery event records have a separate 30-day cleanup cycle; temporary signup-protection records expire and are removed by scheduled cleanup.

The documented database plan provides a recovery window of up to seven days; this is a database recovery window, not a seven-day lifetime for registrations. The documented outbound email delivery plan has 30-day provider data retention. Provider plans and legally required records can differ. No fixed deletion schedule is documented for support mail, founder notification mail, or separately retained exports. A deletion request must therefore cover those copies as well as the database. We do not promise immediate erasure from every provider or backup. Where lawful retention is necessary for a specific obligation or dispute, we limit it to that purpose and explain the applicable exception.

Anonymous visit details are removed after 90 days without activity. Aggregate analytics counts by time window and channel are retained without visit identifiers or contact details.

PostHog analytics event retention follows the one-year free-plan guarantee described above. Deletion requests should include any relevant analytics identifiers if available; we do not link them to email addresses in PostHog. Provider backups and lawful retention exceptions may apply. The latest stored provider explanation remains with the email job until that job or its registration is deleted, even after the separate delivery-event cleanup.

Access, correction, deletion, and opt-out

Email support@joinbji.com from the address you registered, describe your request, and identify any relevant support conversation. You can request a copy of your information, correction, or deletion of all personal data we control, including registration, related email jobs, and relevant mailbox or export copies, subject to lawful exceptions. We may ask for proportionate verification to prevent disclosure or deletion of someone else’s information. There is no customer account screen for these requests; repeating a signup does not correct an existing record.

The administrator can delete the registration, its stored email jobs, and linked delivery-event records from the active database. That action alone does not remove messages already submitted to the email delivery provider, notifications in the founder’s inbox, support mailbox conversations, unlinked delivery-event metadata, or backups. We will assess the other copies and relevant provider deletion processes as part of your request, explain any retained data and reason, and avoid restoring deleted information to ordinary use. We cannot recall a message already delivered to your own mailbox. To stop updates, open the unsubscribe link in a BJI email and confirm; this also removes SMS eligibility and cancels pending customer messages, although a message already being sent may still arrive.

Rights under local law

Your rights depend on the law that applies. Where GDPR or UK GDPR applies, you may also request restriction or portability where its conditions are met, object to processing based on legitimate interests, and object to direct marketing. We will respond within the applicable deadline, normally one month for GDPR requests; any lawful extension will be explained. You may complain to your local data protection authority and, where relevant, the UK Information Commissioner. You do not have to contact us first.

Where California’s CCPA/CPRA applies to BJI and your information, you may request access or knowledge of categories and specific information, correction, deletion, and information about disclosures; you may use an authorized agent subject to verification and may exercise rights without unlawful discrimination. Sale and advertising-sharing opt-out rights, including qualifying browser signals, apply where relevant; BJI currently conducts neither activity. We do not use sensitive information for purposes that would require offering a limit-use option under that law. California requests are generally answered within 45 days, with notice of a permitted extension. Where Israeli law applies, statutory rights to inspect personal information and request correction or deletion of incorrect, incomplete, unclear, or outdated information remain available, as do applicable rights concerning direct mail and complaints to the Privacy Protection Authority.

Security

The documented production design uses HTTPS, a private administrator area protected by email sign-in, server-side validation of administrator access, checks against forged state-changing requests, signup rate limits, a bot-trap field, and verified email-delivery callbacks. Runtime secrets are kept outside public files. These safeguards reduce risk but cannot guarantee complete security. A hashed security identifier is not a guarantee that information is anonymous. We do not claim a security certification or a verified backup-restoration process.

Children and future footage

The initial pilot is intended for adults aged 18 or over, and no children’s enrollment or parental-consent workflow is available. If you believe a child has registered, contact support so we can review and remove the information as appropriate. We do not currently collect video uploads. Before uploads open, we will explain participant permissions, eligible-reviewer previews before a claim, administrator access, storage, retention for each footage state, deletion, and any separate permission for public use. Development examples are not established production retention promises.

The planned review app will collect client answers about whether feedback addressed the request, was clear, and provided a useful next step, plus optional comments. Answers will be required before another review request, while delivered feedback and support remain accessible. Completed reviews and positive client feedback will inform BJI progression. The technical team will inspect reviews and investigate reports; support may restrict access for confirmed abuse and review disputed decisions. These workflows and levels are not active in the current waitlist. We will explain their access, retention, and decision rules before collecting this data.

Policy updates

We will show a new effective date when this policy changes and give notice of material changes where required. A new purpose or consent-dependent feature will not be treated as authorized merely because this page changed. Contact support@joinbji.com for questions or to exercise your rights.

support@joinbji.com

Back to BJI