Skip to content

Who owns what, and what happens if we stop

Last updated: Written by Blake Cowan, NCSO

A safety program you cannot leave is a risk to your certificate. Here is exactly what you own, and what happens on the day you stop paying us.

The short answer

You own the program documents, the data and the accounts the system runs on. The software is open source, so you own your copy of that too. We are a member you invite in, and if you stop working with us, we hand over what we hold and the system keeps running.

Who owns the code

Cor Pathway 360 is free software under the AGPL licence. You can run it, change it and keep it, with no licence fee at any crew size. The program documents we write for you are yours as well. They are not part of the open source repository.

Who owns the database and your files

Your records and uploaded files live in a Supabase project, which is a hosted Postgres database. Where practical, the project is in your name and on your bill. Where we open it for you, the bill passes through at cost and the account transfers to you if you leave.

Where the data lives

The region a database runs in is chosen when the project is created. If your client or your insurer requires your data to stay in Canada, say so before setup and we will create the project in a Canadian region.

Backups and restoration

On managed hosting, backups are part of what we run and check, and restoring from one is our job. If you run the system yourself, the backup schedule is yours to set on your own Supabase plan.

Roles and access

Every company starts with four permission profiles, and you decide who gets which. We sit in the member list like anyone else, with the access you give us, and you can remove us.

Updates and maintenance

On managed hosting, we apply upgrades and check them. If you run it yourself, you decide when to upgrade, and nothing updates without you.

Support

Support is Blake, by phone or email, both at the foot of this page. There is no ticket queue and no offshore help desk. If something breaks on a system we run, you call. We find it, fix it, and tell you in plain words what happened.

If you stop working with us

You keep the application, the data, the documents and the accounts. We hand over any credentials we hold. There is no export fee and no wind down charge, and because the data is in a standard database, leaving is a handover rather than a rescue.

Where the product is today

Cor Pathway 360 is new, and it is built and maintained by Blake. Features are added as clients need them. If something you need is not there yet, you will hear that plainly on the call, along with whether it is planned.

Questions people actually ask

Whose name are the accounts in?
In your name wherever that is practical. Where it is cheaper or simpler for us to open an account, we open it, pass the bill through to you at cost, and the account transfers to you if you ever leave. Either way there is no account we would keep that your system depends on.
What happens if I cancel?
You keep the application, the data, the documents and the accounts, because they were always yours. We hand over any credentials we hold, and you carry on self hosted or with anyone else you hire. There is no export fee and no wind down charge.
Can I move off it later?
Yes. The data is in a standard Postgres database you control, so an export is a normal database export rather than a support ticket. A compliance system you cannot leave is a business risk, and this one is built so you can leave.
Can you remove our access to the system?
No. We are a member you invite in. You can remove us, and we cannot remove you. There is no licence server and no switch we can flip.

Ask the awkward questions on the call

If your insurer, your client or your own IT person has a list of questions about data and access, bring it. You get straight answers, including the ones where the answer is not yet.