Terms of use
The rules that come with an account
[ ]
still need filling in.
Who may use it
The TXC Toolkit is a closed internal tool provided by [organisation]. Access is by invitation or by an approved sign-up, and is granted for work on South Yorkshire's bus service data. It isn't a public service.
Your account is yours
- Don't share your password, and don't let someone else work under your account. Records here are stamped with who made them, which only means anything if that's true.
- Use a password you don't use anywhere else.
- Tell [contact] straight away if you think someone else has got into your account. Changing your password immediately signs out every session, including theirs.
- Say when you no longer need access — for example when you change role or leave — so the account can be closed.
Using it properly
- Only work on data you're responsible for. Being able to open a record isn't authorisation to change it.
- Check what you're publishing. Publishing a stop and exporting a registration both produce data that other organisations rely on and that is hard to withdraw once sent.
- Don't upload files containing personal data that has nothing to do with a bus registration.
- Don't try to get at parts of the system you haven't been given access to, and don't automate against it in a way that would affect other users.
- Exports carry the authority's name and area. Send them on deliberately, not by habit.
Accuracy and responsibility
The tool helps you produce data; it doesn't verify that the data is right. Timetables, stop details and registrations exported from here are the responsibility of the person who produced them and of the authority, not of the software. Where a file is checked against a published schema, that check is a check of the file's shape and never of whether the timetable is correct.
Availability
This is an internal tool under active development. It may be unavailable without notice for deployment or maintenance, and features may change. Keep your own copy of anything you can't afford to lose, particularly work in progress that hasn't been exported.
Monitoring
Changes made in the tool are recorded in an audit log, and the server keeps ordinary access logs. These are used to support the service and to investigate problems — see the privacy policy for what's held and for how long.
Suspension
Access can be suspended if these terms are broken, if an account looks compromised, or if it's no longer needed. Where it's practical, you'll be told why.
Questions
Ask at [contact], or see Support for reporting a problem with the tool itself.