Cookies

The membership finder stores nothing on a visitor's device. No cookies, no local storage, no session storage, no fingerprinting. The reference that keeps one visitor's answers together lives in the page's memory for the length of the visit and is gone when the tab closes.

Because nothing is stored on or read from the device, regulation 6 of the Privacy and Electronic Communications Regulations is not engaged and no consent banner is needed for the finder.

That cookie is strictly necessary for a service you asked for — signing in — so it does not need consent either. We run no analytics, advertising or tracking cookies on memberly.co.uk.

Both the admin app and, when a club picks a Google font for its widget, the finder load that font from Google Fonts. Google receives the visitor's IP address in order to serve the file. Nothing is stored on the device. A club that would rather avoid this can choose one of the system fonts in Branding.

If you enter a Google Analytics measurement ID or a Meta pixel ID in Settings, two things happen. On your own website the finder passes events to tags that are already there — those tags are yours and belong in your own cookie banner. On the standalone campaign page we host for you at /m/your-key, we load Google Analytics and the Meta pixel for you, and both set cookies.

Those are not strictly necessary, so they need consent. Until the campaign page asks for it, leave the two ID fields empty unless your own consent tooling covers that page.