Why PaddleSafe exists

A short talk for committees, coaches, and partners. How each role uses the app is a separate walkthrough: How PaddleSafe works (by role).

PaddleSafe records. People decide.
Two books, one session.
The club is the data controller.

Origin

It started with a workable first problem: the Paddle Safety & Rescue (PSRC) course, and session booking so a club night had a roster instead of a paper list.

That was the seed, not the destination. The product was always meant to be:

a personal log — your journey and skills, without other people’s names
club session booking — join link / QR, spaces, family enrol, duty booking a verified leader
personal and organisational responsibility — the app records and warns; people and clubs still own the decision

Safety & Rescues is still a family in the skills catalogue. The book is for every session, not only a rescue course.

flowchart LR
    A[PSRC and booking] --> B[Every club session]
    B --> C[Personal log]
    B --> D[Club archive]

National award courses still book through your home-nation Delivery Centre. CPD points still live on JustGo. That split is a choice, not an unfinished feature.

Four jobs

Job	What happens
Book	Create the session, share join / QR, keep spaces honest. Duty can book a verified leader. Each club chooses who may see dates (members, public, partners, or join-link only) — that is not a booking import.
Log	After Complete, a personal Log / Profile snapshot. Training and club programmes stamp the same Profile.
Return	Each person Mark as safe. Nothing counts as safe until someone acts.
Oversee	Shore duty: live map, traffic lights, overdue alerts. The club keeps its own procedures.

PaddleSafe does not replace JustGo, issue a Paddle Award, or grant a leadership remit.

Two books

One session writes two stores on purpose.

	Past sessions	Log / Profile
Whose record?	The organisation’s operational archive	Your journey and can-do log
Names and ICE?	Yes, where role allows	No — pseudonyms only
After GDPR purge	Named session can be deleted	Personal entry is kept (detached)
Menu	Past sessions	Paddler → Profile and You → Log

Need who was on the water? → Past sessions. Need your lasting CPD / skills book? → Log.

Detail: Log book and Past sessions · Skills and learning outcomes.

Privacy

The organisation remains the data controller. PaddleSafe records a versioned privacy notice, a tick on join, role-based rosters, redaction, a 24-month archive purge, and a JSON copy of your information.

In the app	Still the club / association
Where to tick, download, hide a name, redact	Who answers the request; lawful basis; insurance retention
Two books so CPD can survive a GDPR purge	Whether you keep named medical sign-ins after the trip

Paddlers: Privacy and your data. Committee: Handling a data request (slides). Notice: Privacy.

One session loop

Booking is how a session gets a roster and a log line.

flowchart LR
    A[1 Plan] --> B[2 Join]
    B --> C[3 On the water]
    C --> D[4 Safe return]
    D --> E[5 Close and archive]

Step	What happens
1. Plan	Leader (or duty booking a leader) creates the session and shares join / QR
2. Join	Paddlers sign in; each person gets a safe-return link
3. On the water	Leader Starts; duty can watch the live map
4. Safe return	Each person marks themselves safe
5. Close	Wrap-up → Complete → Past sessions and personal Log / Profile

How each role does that loop: How PaddleSafe works (by role).

People decide

PaddleSafe records. It does not take the decisions people still own.

Does not call 999, text emergency services, or trigger rescue. People call; then share the roster and ICE.
Awards, first aid, and safeguarding dates are self-declared. Blank or expired dates do not stop a session launching.
The remit map warns; it does not hard-block. Wind, tide, river level, and the group still decide.
Pinning launch (A) and take-out (B) records a planned route for shore duty. It is not a sea passage plan (charts, tides, forecast). Sea kayak leaders: Planning a sea kayak trip (A to B).
The Code of Conduct line on print packs is a reminder. The official tick stays on JustGo.
Profile is a can-do log, not a Paddle Award and not a remit.

If something goes wrong: Emergency response.

What the club still owns

The organisation remains the data controller. This app does not replace club procedures.

Still the club’s	What PaddleSafe does
Risk assessment, ratios, on-the-day judgement	Planning aid and remit overlay (warn, not block)
Sea passage plan (charts, tides, forecast, landings)	A-to-B pins and a dashed route for shore duty — not a go decision. Planning a sea kayak trip (A to B)
Safeguarding consent for under-18s	Blocks solo under-18 self-registration
Membership and who may lead	Pending members; duty books a verified leader
Operating areas and shore coverage	Polygons duty draws; live map uses the session envelope; away trips warn, not block
Paper / JustGo as source of truth	Self-declared FA/SG glance; CPD and Coach packs as evidence
Committee hats (chair, welfare, safety officer)	Labels — grant Org admin or Org duty separately
Lawful basis, retention policy, answering data requests	Tools: notice tick, JSON copy, redact, purge — not a DPO
Importing medical data from another form	Does not import; people re-enter and tick privacy here

Detail: Account roles · Leadership remits · Handling a data request.

If you are…	Open
Using the app today	How PaddleSafe works (by role) (slides)
Planning a coastal A-to-B	Planning a sea kayak trip (A to B)
Checking Log vs Past sessions	Log book and Past sessions
Logging skills	Skills and learning outcomes
On shore duty	Organisation duty and live map
Writing procedures	Emergency response · Handling a data request · Club tools and member data · Privacy
Checking your own data	Privacy and your data

Use ← → keys, or swipe on touch screens. Esc returns to Help.