Privacy

• If you only read, we hold nothing about you beyond what the server that delivers the page records in its ordinary logs.
• If you sign up for the newsletter, we hold your email address, your first name if you gave one, and a note of which page you signed up on. Your mailing list also records which groups you were placed in, such as the audience you picked or a quiz result.
• If you take a quiz, your answers stay in your browser and in the address of your result page. We do not store them.
• If you use the contact form or the certification application, we hold what you typed into it, and it arrives in an inbox.
• Nothing on this site takes payment yet.
• If you sign in, we hold your email address, your first and last name if you add them, when you signed in, and a record of any course you’ve bought or been given. A cookie keeps you signed in; it does nothing else.
• There is no analytics on this site, no advertising, no tracking pixels, and — for anyone who never signs in — no cookies that we set. We do not sell anything about you, and we do not pass it to anyone beyond the services named below, which exist to deliver the thing you asked for.

The signup forms ask for an email address and, optionally, a first name. Some also let you say who you are: dating, young married, a parent of teenagers, in a high-conflict marriage, or someone who works with couples and families. The site adds a few things you did not type: a label for where the signup happened, such as the newsletter page, and a short list of tags. A tag is either an audience you picked, or one the page adds on its own, such as the result of a quiz or the name of a program you asked to hear about.

Once Weinberg Compass has a mailing list account, MailerLite runs the list and sends the letters. Three things go to it: your email address, your first name if you gave one, and a place in a MailerLite group for each tag that has a group set up. The groups are named for the tags. They cover the five audiences, the four quiz patterns (pursuer, withdrawer, controller and defender), and the interest lists for the membership, the masterclass, certification info sessions, finding a coach, events and each program. MailerLite holds all of that from then on, under its own privacy policy.

The source label, and the small internal label some pages attach, stay with us in a server log and are not sent to MailerLite. A tag that has no group yet is logged the same way and not sent.

The groups are how writing gets matched to the person who asked for it. They also mean that MailerLite holds a record linking your address to something like “high-conflict marriage” or a quiz pattern. Nobody else can see that on this site. It lives in the mailing list account.

Signup is double opt-in. The site adds you to MailerLite as unconfirmed, MailerLite sends one email asking you to confirm, and nothing follows until you answer it. Every letter carries an unsubscribe link, and unsubscribing is handled by MailerLite without going through us.

Until a MailerLite account is connected, no mailing list exists. The address, first name, source label and tags you submit are written to our own server log and go nowhere else, and no confirmation email is sent, because there is nothing yet to send it.

There are two quizzes: one on the pattern you reach for when love feels threatened, and one for people thinking about the certification. Neither needs an account.

Your answers are held in the page, in your browser’s memory, while you answer. Nothing is sent to us question by question. When you finish, the site takes you to a result page whose address ends in a short string of letters, one for each question. That string is your answers in code, and the result is worked out from it. No database sits behind it, and nothing about your answers is stored on our side.

Two things follow from that. The address is the result, so anyone you send it to sees what you saw, and it stays in your browser history and wherever you paste it. And when your browser asks for that address, the server that delivers the page sees it, as it sees any other address, in the ordinary request logs described under “Hosting” below. We have added no logging of it.

If you then sign up from the result page, your email address and your first name, if you give one, go with the result of the quiz and a label saying the signup came from it. Your twelve answers and the counts behind them do not go with it. For the pattern quiz, the result is one of four patterns, and it reaches MailerLite only as membership of the group for that pattern. The same form asks which situation you are in: dating, young marrieds, parents of teens, high-conflict marriage, or working with people professionally. If you pick one, it goes the same way, as membership of that group, and it decides which version of the longer result you see. The certification quiz works the same way: its one signup, on one of its endings, carries a label saying it came from that quiz and that the timing was not right this time.

The pattern result also offers a link to send to someone else. That link carries the name of your pattern and nothing else: not your answers, not your email, not your name.

Neither quiz sets a cookie or stores anything in your browser.

The contact form at /contact asks for a name, an email address and a message. The certification application at /apply asks for a name, an email address or WhatsApp number, and one line about the work you do. What reaches us is what you put in those boxes; nothing is gathered around the edges of them.

A submission is turned into an email and delivered to two Weinberg Compass inboxes. As this is written, that is done by Formspree, which receives what you typed, the name of the form and a subject line, and forwards them by email. Formspree therefore handles the message in passing, and may keep a copy in its own account, under its own privacy policy. The site can also be set up to send through Resend instead, in which case Resend handles it. If neither were configured, the submission would be written to our server log and not delivered anywhere.

The speaking inquiry form at /speaking asks for a name, an organisation, an email address, and, if you choose, a phone number, the kind of event, the audience size, preferred dates and a message. It is delivered the same way as the contact form, unless a separate form service has been set up for speaking inquiries, in which case what you typed is sent to that service and handled under its privacy policy.

All three forms carry a hidden field that a person never sees. A submission that fills it in is treated as automated and dropped rather than sent on.

Signing in creates an account. There is no separate signup step: you enter your email, we send you a link, and clicking it both confirms the address is yours and opens the account. From then on we hold the email address you signed in with, your first and last name if you choose to add them on your profile, when the account was created, and when you last signed in.

Staying signed in works through a cookie set once you click the link in the sign-in email. It holds a random session id and nothing else — no name, no email, nothing readable on its own — and its only job is letting the site recognise you on the next request instead of asking you to sign in on every page. We don’t keep a copy of the cookie itself on our side either: what we store is a one-way hash of it, the same idea as a password never being stored in the clear. It is not used to track you around this site or anywhere else, and nothing reads it for advertising or analytics.

If a course is bought or given to you, we also keep a record of that: which course, what was paid for it (or that it was given rather than paid for), and when. The terms say what owning a course actually commits us to.

Changing the email on an account, or closing one, isn’t self-service yet. [email protected] or the contact form and we’ll take care of it by hand.

Nothing on this site takes payment yet. Until a payment processor is chosen and its links are added, no payment can be made here, and no card details are asked for.

When there is one, it will be named here, along with what it receives and keeps. Our intention is that card details are entered on the processor’s own page and never pass through this site, and that what we keep is a record of what was bought, as described under “If you sign in” above.

The site is served by Cloudflare Pages. Delivering a page means the server sees the ordinary things a web request carries: your IP address, the address you asked for, the time, and what your browser says about itself. Cloudflare keeps its own request logs as part of running the network, on its own terms.

We have added no logging on top of that, and we run nothing that builds a record of what an individual reader looked at. The application writes lines to the server log when a form is submitted, as described above, and those lines contain what was submitted.

Every page on this site loads its typefaces from Google Fonts. That is a request from your browser directly to Google, which means Google sees your IP address and the fact that a page on this site was opened, whether or not you do anything else here. Google describes what it does with those requests in its Google Fonts privacy note.

Article illustrations, when there are any, are served from Sanity’s image CDN, so your browser fetches those from Sanity too. There are no video players anywhere on the site at the moment. If one is switched on later, the video host will see the same kind of request, and this section has to say so.

For anyone who never signs in, this site sets no cookies of its own. It stores nothing in your browser, runs no analytics, has no tag manager, and carries no advertising or tracking pixels. There is nothing here to consent to, which is why nothing on the page asks you to.

The one exception is the sign-in cookie described in “If you sign in” above, set only for someone who signs in and there only to keep them signed in.

Cloudflare may set cookies of its own as part of serving and protecting the site. We have configured none, and the account’s settings need reading once it exists — see the note above.

If analytics is ever added here, this section stops being true, and rewriting it is part of adding it.

The articles live in Sanity, the content system Weinberg Compass writes into. It holds the articles and, when the coach directory opens, the coaches’ own profiles. It holds nothing about the people who read the site.

A newsletter address stays on the list until you unsubscribe or ask us to remove it. A form submission stays in an inbox the way an email does.

An account, and any purchase record on it, is kept for as long as the account exists. That is what “yours to keep” and “access forever” on the course pages actually rest on — there is no timer anywhere that clears a purchase out from under someone who owns it. A sign-in session is kept only for as long as it takes to recognise you on your next visit, and is replaced automatically as you use the site.

In the meantime, the practical position: ask us through the contact form to see what we hold about you, to correct it, or to delete it, and we will. Unsubscribing from the newsletter is a link at the foot of every letter and does not need to go through us at all.

Weinberg Compass is run from Israel. The services named on this page are run from elsewhere, mostly the United States, and their networks reach further than that. So information you send here does cross borders, as a matter of how any of this works.

This site is written for adults. Nothing here is aimed at children, and we do not knowingly collect anything about them.

Questions about this notice, and requests about your own information, go through the contact form, or directly to [email protected]. Either way a person reads it.

It will change, because the site is not finished. The date near the top moves whenever it does.