The Fruitland Peninsula Historical Society (FPHS) collects certain information from members and occasionally non-members. We do not sell or share any personal information with third parties.
Memberships
FPHS collects information on its membership forms, including name, address, email address, phone number(s), and spouse (for family memberships). This information is stored in the membership portion of FPHS’s website. It is accessible to FPHS board members, but not to other members, and not to third parties, with one exception. FPHS uses MailChimp for some mailings. Members’ names, email addresses, and membership status are included in the MailChimp account. The webmaster and two others have access to that account.
Membership payments are tracked on FPHS’s MemberPress site, but not payment information. All online payments are processed through PayPal. FPHS neither receives nor retains any member’s credit card, bank account, or other financial information.
Newsletters and Announcements
FPHS sends members announcements of upcoming events, new services, or news that affects the Society. You can unsubscribe at any time.
Web forms or email
Personally identifying information that you provide by e-mail or web forms will be used only for those purposes that are described at the point of collection, such as to send information to you or to respond to your questions or comments.
Surveys
FPHS may occasionally survey its members. Any information requested, such as age, address, etc., will be used only for its intended purpose.
Server log data
Our WordPress website collects server log data, which may include an IP address, the type of browser and operating system used, the time of day visited, the pages viewed and search requests. This aggregated data is used for statistical purposes.
Cookies, Pixel Tags, Tracking Code
The FPHS website uses technologies such as “cookies”, “pixel tags”, and other tracking code to improve the functioning of the website and the user experience. Cookies are small data files that are automatically sent to your browser from a Web server and stored on your computer’s hard drive. Cookies enable us to personalize your experience. “Pixel tags” are tiny graphical images embedded in emails or webpages. Pixel tags are used to determine what parts of a website a visitor has viewed, or whether an email was successfully opened. These technologies do not contain any personal information about you; they are used to gather information to analyze traffic to the websites, to improve content and navigation.
You may choose to set your browser so that it does not accept cookies, but some areas of FPHS websites will not function properly without cookies.
Links to Other Sites
The FPHS website has links to other websites. When you go to another site, you are subject to the privacy and security policies of that site. FPHS cannot attest to the accuracy of information provided there.
Children and Privacy
FPHS does not currently request information from people who are under 18, and does not track ages of its users or members.
Changes to the Privacy Policy
FPHS reserves the right to change the policy on use of information collected. Any changes in policy will be noted in a revised privacy policy statement and will be posted at least 30 days prior to implementation. You may direct any privacy policy questions to webmaster@fphistory.com.
Through MemberPress:
What personal data we collect and why we collect it
We collect information about you during the signup process as well as some basic activities such as the dates you make purchases, login to the site, or cancel/pause/resume your subscriptions with us.
What we collect and store
When you subscribe with us, we’ll ask you to provide an email address. We’ll use this information for purposes, such as, to:
- — Send you information about your account and subscriptions. This may include payment receipts, password reset emails, and payment reminders.
- — Create your membership account
How long we retain your data
We store information about you for as long as your account exists.
Who on our team has access
Members of our team have access to the information you provide us. For example, site Owner/Administrators can access:
- — Order information such as your membership subscriptions, payment dates and amounts, and username / email address.
Any additional information added in your Member Profile can also be visible to the Administrator(s).
What we share with others
We share information with third parties who help us provide additional contact services to you; for example – MailChimp, which we use for email, and PayPal for payment processing.
Payments
We accept payments through PayPal. When processing payments, some of your data will be passed to PayPal, including information required to process or support the payment, such as the purchase total and billing information.
Please see the PayPal Privacy Policy for more details.
Through our Events Plugin:
Event, Venue, and Organizer Information
If you create, submit, import, save, or publish Event, Venue, or Organizer information, such information is retained in the local database:
- Venue information: name, address, city, country, state, postal code, phone, website, geographical coordinates (latitude and longitude)
- Organizer information: name, phone, website, email
- Event information: website, cost, description, date, time, image
Importing Events, Venues, and Organizers:
- All data present within a CSV or ICS file and external URLs (for events, venues, organizers, and tickets)
- Import origin data (URL from where events are being imported—such as Eventbrite, MeetUp, other compatible URL sources, and more, which can include similar or same data as listed above)
- Eventbrite Ticket information: name, description, cost, type, quantity
Please note that to create new events through the Community Events submission form, a user must hold a website account on this domain. This information is retained in the local database. It is also possible to create events anonymously, if the site owner has this option enabled.
When purchasing Eventbrite Tickets, attendee, purchaser, and order information are stored and managed by Eventbrite.
API Keys
We make use of certain APIs, in order to provide specific features.
These APIs may include the following third party services: Google Maps (API key), PayPal (email, Client ID, Client Secret), Eventbrite (API key, auth URL, Client Secret), and Zoom (email, Client ID, Client Secret).
We use the WP Statistics plugin to analyze traffic on our website.
WP Statistics stores its data on our own server and does not transmit it to any third parties. Below, we describe what information we collect through WP Statistics, why we collect it, and how it is handled. If you have questions or concerns about our analytics practices, please contact us or review the WP Statistics Data Privacy guide.
We track certain details about logged-in visitors on our site. Specifically:
- User ID & Page Views: If you are logged in, we associate your account (username/ID) with your page visits.
- Purpose: This helps us understand how registered members use our site and improve their experience.
- Local & Secure Storage: These logs are kept securely on our server and are not shared externally.
- Your Choices: You can choose to browse without logging in if you prefer not to link your visits with your user account. You may also contact us to request removal of any collected data where legally applicable.
