Server access policy
If we need to fix a bug that we can't reproduce, provide our installation service, or if we are asked to provide professional services that involves code modification, we may ask permission to access your server. We cannot do this without the relevant passwords, as we don't place any 'back-doors' in the software itself.
If you don't want us to go near your server, that's fine and we quite understand – but sometimes if something is wanted from us, such access is required. We only offer in situations where for us to provide a service, or fix a problem, we need direct access in order to 'get the job done' in a reasonable time.
It is possible we could forget to remove this, so if you see we have accidentally left an IP address in here, please remove it.
If you don't want us to go near your server, that's fine and we quite understand – but sometimes if something is wanted from us, such access is required. We only offer in situations where for us to provide a service, or fix a problem, we need direct access in order to 'get the job done' in a reasonable time.
Requirements
If you do decide to give us access to your server we require certain provisions:- that you have a full backup of your site, including both files and database, and that you know how to restore it
- that the FTP (or hosting control panel, or SSH) details we are given are temporarily and will be deleted when we have finished
- that any administration user account given is temporary and is removed or de-authorised as soon as we are finished
- that you do not post login details on a public forum (supply details by privately contacting us)
- that you accept that when we are done, it is your responsibility to secure your site and that you cannot claim we are continuing to log-in without permission, or causing damage, or have placed any kind of permanent back-door (it is your responsibility to make sure we haven't – although of course, we wouldn't ever intentionally do so, we have to protect ourselves against being made a false suspect)
Temporary restricted back-door
When we are granted access, the typical process involves us adding a temporary back-door to the _config.php file, to an office IP address. This is a clean way for us to be automatically logged in as an Composr administrator without having to know any temporary passwords, have a separate account, or reset any password.It is possible we could forget to remove this, so if you see we have accidentally left an IP address in here, please remove it.