Skip to content
MasonBase

Terms of service

Effective from · Version 1

1. Who these terms are between

These terms are between Julien Tidmarsh, trading as MasonBase ("MasonBase", "we"), and the lodge, chapter, council or other Masonic unit that signs up ("the unit"). The person who accepts them confirms that they are authorised to do so on the unit's behalf, for example as Secretary or Worshipful Master.

2. The service

MasonBase provides a website, members' area, diary, booking and payment system and related tools for the unit. We aim for the service to be available at all times, but we can't promise that it will never be interrupted. We will give notice of planned maintenance where we can.

3. The unit's responsibilities

The unit must:

  • keep its sign-in details safe and give access only to people who need it;
  • make sure the information it adds is accurate and that it is allowed to hold it;
  • use the service lawfully and in line with its own constitution and the rules of its Grand body;
  • keep its own Data Protection page accurate (MasonBase provides a template).

4. Payments through Stripe

Card payments for bookings and dues are processed by Stripe. Each unit connects its own Stripe account through Stripe Connect, and money from bookings goes to that account, not to MasonBase. By connecting, the unit also agrees to the Stripe Connected Account Agreement. The unit is the seller in every booking and is responsible for its own refunds, disputes and accounts. MasonBase charges a platform fee of 0.5% of each card booking. Stripe deducts it automatically before paying the rest to the unit, and it is shown in the unit's accounts.

5. Fees

The subscription is charged a year in advance.

PlanFirst yearEach year after
Website hosted by MasonBase£199£139 (includes hosting)
Unit keeps its own website£149£99

If a unit doesn't pay within 30 days of the invoice, we may suspend access until it does. We will give 30 days' notice of any price change.

6. Data protection

The unit is the controller of its members' and visitors' personal data; MasonBase is its processor. The data processing terms below form part of these terms.

7. Ending the service

The unit can stop using MasonBase at any time. We can end the service with 30 days' notice, or straight away if the unit seriously breaks these terms. When the service ends, the unit can download its data for 30 days, after which we delete it, except for anything we must keep by law.

8. Liability

We are not liable for indirect losses, or for losses caused by Stripe, the unit's own mistakes, or events outside our control. Our total liability in any year is limited to the fees the unit paid us in that year. Nothing in these terms limits liability that cannot be limited by law.

9. Changes and law

We will tell units about material changes to these terms at least 30 days in advance. These terms are governed by the law of England and Wales.

Data processing terms (part of these terms)

  1. Instructions. MasonBase processes the unit's personal data only to provide the service and on the unit's documented instructions.
  2. Confidentiality. Anyone at MasonBase who can access the data is bound by confidentiality.
  3. Security. We use encryption in transit and at rest, role-based access, row-level database security, and regular backups.
  4. Sub-processors. The unit authorises Supabase, Lovable, Resend, Stripe and Cloudflare. We will give 30 days' notice before adding a new one, and the unit may object.
  5. Assistance. We help the unit respond to requests from data subjects and to the ICO.
  6. Breaches. We tell the unit without undue delay, and within 48 hours, after we become aware of a personal data breach affecting its data.
  7. Deletion. At the end of the service we delete or return the data, as described in section 7.
  8. Audit. We provide the information the unit reasonably needs to show compliance.