Oshawa Aquatic Club anniversary logoOSHAC AnalyticsSWIM CLUB PERFORMANCE
A PRIVATE PERFORMANCE PLATFORM
PRIVACY, SECURITY & TRANSPARENCY

Your swimmer’s data deserves thoughtful protection.

OSHAC Analytics is built to make swimming progress easier to understand while treating swimmer records with care. Here is what the website does, who it is intended for, and which safeguards matter most.

Account sign-inFamily / coach accessDatabase permissionsResponsible data handling
01 / YOUR INFORMATION

What information is kept—and why?

The dashboard uses swimmers’ names and training groups, meet information, and recorded race results to show times, personal bests and progress. It does not need families to post results publicly to make those charts useful.

Records are organized by internal IDs so that a performance is connected to the right swimmer and meet. Data is prepared with R scripts, reviewed during import, and stored in a structured Supabase database.

Having data in one database does not mean everyone with a login should be able to view all of it. Access needs to be checked for each account.

02 / WHO CAN SEE WHAT

A family account is not a coach account.

FAMILY ACCESS

Designed around your family.

The Family Portal is intended to display only swimmers linked to the signed-in family and their results. It is a viewing experience, not a tool for changing club-wide records.

That separation must be enforced by database-level access rules, not just a menu or a filter.

COACH / ADMIN ACCESS

Designed for authorized staff.

Club staff who have been approved for coaching access can browse the wider swimmer and meet dashboard, including AG1, AG2, AG3, Senior and Varsity. Viewing the dashboard does not automatically confer database editing rights.

Data imports and maintenance are separate authorized operations.

03 / HOW ACCESS WORKS

Multiple checkpoints, not just a password.

01

Sign in

Supabase Authentication identifies the account. A password is not displayed to coaches or other families through the dashboard.

02

Check the role

The coaching pages check whether the signed-in account has the required club membership before loading their data.

03

Enforce permissions

Supabase Row Level Security (RLS) can limit which records each account may request. Family-to-swimmer boundaries need to be configured and tested there.

04

Show the allowed records

Only the records permitted by the database should reach the browser. Group labels and on-screen filters organize the view; they are not security protection.

04 / PROTECTION

What the website does to reduce exposure.

Sign-in and access checks: The site integrates Supabase Authentication. Coach pages require approved club access before attempting to load the dashboard. Family accounts use a separate, scoped experience.

No administrator secret in browser code: The frontend uses a publishable Supabase key. A publishable key is not a master password; it depends on correctly configured database policies to protect records.

Minimal offline storage: The current service worker is set up for network-only requests rather than saving swimmers’ personal data as an offline PWA cache. As with other websites, a browser or device may still retain temporary information.

Responsible data changes: Imported meet and swimmer records are prepared using a separate R workflow. The viewing screens do not provide unrestricted editing of underlying records.

A clear commitment to accuracy

The source code shows these intended safeguards, but the live Supabase RLS policies, hosting configuration, backups and retention practices have not been independently audited here. Those settings must be verified before anyone promises that a family can never access another family’s data.

05 / QUESTIONS

How to stay safe as a family.

Use your own account, keep sign-in details private and sign out on a shared device. If an athlete is missing or a result seems wrong, contact the club administrator rather than sharing account credentials with someone else.

If you ever see another swimmer’s information that does not seem appropriate for your account, stop browsing and report it to the club administrator. Access restrictions should be tested and any unexpected exposure investigated promptly.

Privacy also means keeping information relevant, correcting mistakes and reviewing who still needs access when roles change.

06 / PLAIN ENGLISH

What Ryley can tell families.

“This is a swimming-results dashboard with separate areas for families and coaches. Families are meant to see swimmers linked to their own account; approved coaches can work with the club’s results. The data is kept in Supabase, and database permissions are meant to enforce who can see what. We take that seriously and check those rules before broader use.”

The goal is straightforward: useful progress information, careful access boundaries and honest explanations of how the system works.

BUILT TO MAKE EVERY SWIM COUNT

Every swim. Every milestone.

Thoughtful tools for a club's swimmers, families and coaches.

Back to the dashboard