Some website features may not work properly and it will probably run very slowly. For a better experience (and better security!) keep your browser up to date. Check here for latest versions.
Warning! Use fictitious data only; any personal data entered will become publicly available. Get free 'admin' access.
|
by at .
|
What personal data we collect and why we collect it
If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.
Submitted information is used for us to respond to your inquiry.
If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.
When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.
If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.
No one outside our organisation.
If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognise and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.
If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Visitor comments may be checked through an automated spam detection service.
If you have any questions regarding your privacy-specific concerns. Please get in touch via post:
294 Madeira Drive Arches (under Dukes Mound)
Brighton
East Sussex
BN2 1EN
All emails sent by the system contain a tracking pixel. This is used to track whether each email has been opened by the recipient, and when. This information can be viewed by those users of the system with permission to view email delivery reports. We do not display any information regarding the location of the recipient. Note that the tracking pixel is only activated if the recipient chooses to download images into their email client.
We, Martlet Kayak Club, make use of the myClubhouse software supplied by Simmetrics Ltd to process personal data we include on our myClubhouse website in accordance with our privacy policy set out above. Simmetrics Ltd processes your personal data on our behalf and they can only do so in accordance with our written instructions. You can find the details of our data processor’s privacy policy here: http://www.myclubhouse.co.uk/Home/PrivacyPolicy.
Use this form to send an email to another member. You may only send to one member at a time. Your registered email address will be passed on to this member but you may also include alternative contact details.
Note: Emails sent via the website are not entirely private. A copy of every email is held on the database and this can be accessed by certain club administrators using the Sent Emails page.
If set, then this will be the default view for those people with whom it is shared, unless they have set their own personal default.
Registration successfully completed for .
scheduled to be collected automatically by GoCardless. There is no need to record manually unless the GoCardless notification has been missed.
If you do record it: entering the GoCardless payment reference (e.g. PM...) will allow the duplicate notification to be safely ignored.
If you use an unknown or incorrect reference, myClubhouse may incorrectly mark the as paid when it processes the collection.
scheduled to be collected automatically by Stripe. There is no need to record manually unless the Stripe notification has been missed.
If you do record it: entering the Stripe charge reference (e.g. ch_...) will allow the duplicate notification to be safely ignored.
If you use an unknown or incorrect reference, myClubhouse may incorrectly mark the as paid when it processes the collection.
scheduled to be collected automatically by . There is no need to record manually unless the provider's notification has been missed. If you mark it as paid and the automatic collection also succeeds, the payment may be recorded twice.
Select the due payments that are covered by this received payment.
| ID | Purchaser | Purchase | Amount | Due Date | Allocated Amount | |
|---|---|---|---|---|---|---|
| — scheduled for automatic collection | ||||||
|
|
£
|
|||||
Loading preview …
Subscription is .
| Confirmed payments | |
| Already recorded | |
| To be recorded |
Payment subscription(s):
Payment on is for .
This amount doesn't match the sum of the payment subscriptions. Please enter how the amount should be distributed:
| Payment Subscription | Suggested | Actual Amount |
|---|---|---|
| Total entered |
Enter 0 for any subscription whose payment has not been collected — it will be marked inactive.
Actions performed:
No payments required recording.