Plymouth Rocket, Inc.

Privacy Policy - November 2, 2020

Overview

With technology changes, software enhancements, and new laws, as well as increased law enforcement surveillance, web service providers must ensure that confidential information in all formats is protected from abuse.

Plymouth Rocket, for both legal and ethical reasons, has developed the following privacy guidelines to protect the personally identifiable information ("PII") of our clients and their users.

The general goals of this policy are to insure that we:

Limit the degree to which PII is collected and disclosed
Avoid creating unnecessary records.
Avoid retaining records that are not needed
Avoid placing PII on public view without the consent of the user.

Data Categories

There are three categories of data involved in the services offered by Plymouth Rocket.

First, there is the organizational data which is collected from our clients and is required in order to offer and sell a particular service. This includes client data, such as a point of contact, billing address, etc. In addition, in order for a client to use the services, certain additional data about system administrators and editors is collected.
The second category is that of content data which is either entered by the client (e.g. information about a particular event shown on an EventKeeper calendar) or data that is requested of a user by the client (e.g. a name and email address required to register for a particular event).
The third category is that of authentication data which is obtained by Plymouth Rocket from either the client or, with the client's permission, from another party. An example of this type of data is the borrowing status of a library patron, obtained from a circulation system database, in order to authenticate and grant permission for the patron to borrow a Museum Pass.

Confidentiality

General

Plymouth Rocket will not share data in any of the 3 categories above with third parties unless required by law.

Plymouth Rocket may occasionally hire or use other parties to provide limited services on our behalf, e.g. answering client questions about services and sending postal mail. We only provide those parties the information they need to deliver the service, and they are prohibited from using that information for any other purpose.

Content Data

Plymouth Rocket does not monitor or control the content which is made available to the public via its dynamic data content services. Accordingly, PII may be published by a client, using a Plymouth Rocket service but without the knowledge of Plymouth Rocket and Plymouth Rocket may not be held responsible.

Authentication Data

Data which is obtained by Plymouth Rocket as part of a user authentication process is used only to validate the attributes of system users as part of the authentication process and is not made available to the public.

Data Retention

Organizational Data

In the ordinary course of business, Plymouth Rocket is required to retain some client information.

Content Data

The retention of content data is controlled primarily by the client. Clients are provided with the means to delete all dynamic content data but are not required by the system to do so.

Due to the system backup procedures, once content data has been deleted by a client, it will take approximately 2 weeks for the deleted data to be purged from the records of Plymouth Rocket.

In the case of Plymouth Rocket's dynamic forms service, EKRegistration (Basic and Advanced), clients are given the choice of whether to save user data at all or only to generate email messages that contain the form data.

Authentication Data

Plymouth Rocket does not save any data which is obtained solely as part of a user authentication process. However, data obtained as part of authentication may be used to populate fields in a web-based form. If this is done, users will be provided with the opportunity to change the data before the form is submitted. The requiring of such data on the form is the responsibility of the client, not Plymouth Rocket. If the data in such a form is saved, it becomes Content Data and the previous section applies.

Our Server Host Policy

https://www.databank.com/privacy/

Privacy Policy Updates

This policy may be amended as needed. The current version is available at:

http://www.eventkeeper.com/privacy_policy.doc