Privacy Statement (US)

This privacy statement was last changed on August 24, 2023, last checked on August 24, 2023, and applies to citizens and legal permanent residents of the United States.

In this privacy statement, we explain what we do with the data we obtain about you via https://cancerpathways.org. We recommend you carefully read this statement. In our processing we comply with the requirements of privacy legislation. That means, among other things, that:

  • we clearly state the purposes for which we process personal data. We do this by means of this privacy statement;
  • we aim to limit our collection of personal data to only the personal data required for legitimate purposes;
  • we first request your explicit consent to process your personal data in cases requiring your consent;
  • we take appropriate security measures to protect your personal data and also require this from parties that process personal data on our behalf;
  • we respect your right to access your personal data or have it corrected or deleted, at your request.

If you have any questions, or want to know exactly what data we keep of you, please contact us.

1. Purpose and categories of data

We may collect or receive personal information for a number of purposes connected with our business operations which may include the following: (click to expand)

2. Disclosure practices

We disclose personal information if we are required by law or by a court order, in response to a law enforcement agency, to the extent permitted under other provisions of law, to provide information, or for an investigation on a matter related to public safety.

If our website or organisation is taken over, sold, or involved in a merger or acquisition, your details may be disclosed to our advisers and any prospective purchasers and will be passed on to the new owners.

3. How we respond to Do Not Track signals & Global Privacy Control

Our website does not respond to and does not support the Do Not Track (DNT) header request field.

4. Cookies

Our website uses cookies. For more information about cookies, please refer to our Cookie Policy on our Opt-out preferences webpage. 

We have concluded a data processing agreement with Google.

Google may not use the data for any other Google services.

5. Security

We are committed to the security of personal data. We take appropriate security measures to limit abuse of and unauthorized access to personal data. This ensures that only the necessary persons have access to your data, that access to the data is protected, and that our security measures are regularly reviewed.

6. Third-party websites

This privacy statement does not apply to third-party websites connected by links on our website. We cannot guarantee that these third parties handle your personal data in a reliable or secure manner. We recommend you read the privacy statements of these websites prior to making use of these websites.

7. Amendments to this privacy statement

We reserve the right to make amendments to this privacy statement. It is recommended that you consult this privacy statement regularly in order to be aware of any changes. In addition, we will actively inform you wherever possible.

8. Accessing and modifying your data

If you have any questions or want to know which personal data we have about you, please contact us. Please make sure to always clearly state who you are, so that we can be certain that we do not modify or delete any data of the wrong person. We shall provide the requested information only upon receipt of a verifiable consumer request. You can contact us by using the information below. You have the following rights:

8.1 You have the following rights with respect to your personal data

  1. You may submit a request for access to the data we process about you.
  2. You may object to the processing.
  3. You may request an overview, in a commonly used format, of the data we process about you.
  4. You may request correction or deletion of the data if it is incorrect or not or no longer relevant, or to ask to restrict the processing of the data.

8.2 Supplements

This section, which supplements the rest of this Privacy Statement, applies to citizens and legal permanent residents of California (CPRA), Colorado (CPA), Connecticut (CTDPA), Nevada (NRS 603A), Utah (UCPA) and Virginia (CDPA)

9. Children

Our website is not designed to attract children and it is not our intent to collect personal data from children under the age of consent in their country of residence. We therefore request that children under the age of consent do not submit any personal data to us.

10. Contact details

Cancer Pathways
1400 Broadway
Seattle, WA 98122
206-709-1400
United States
Website: https://cancerpathways.org
Email: info@cancerpathways.org

Annex

Complianz | The Privacy Suite for WordPress

This website uses the Privacy Suite for WordPress by Complianz to collect and record Browser and Device-based Consent. For this functionality, your IP address is anonymized and stored in our database. This service does not process any personally identifiable information and does not share any data with the service provider. For more information, see the Complianz Privacy Statement.

Hustle

Which modules collect personal data?

If you use Hustle to create and embed any Pop-up, Embed, Slide-in, or Social share module, you may need to mention it here to properly distinguish it from other plugins.

What personal data do we collect and why?

By default, Hustle captures the IP Address for each conversion and for each view only if the “tracking” functionality is enabled. Other personal data such as your name and email address may also be captured, depending on the form fields.

Note: In this section you should include any personal data you collected and which form captures personal data to give users more relevant information. You should also include an explanation of why this data is needed. The explanation must note either the legal basis for your data collection and retention of the active consent the user has given.

Suggested text: When visitors or users submit a form or view a module, we capture the IP Address for analyisis purposes. We also capture the email address and might capture other personal data included in the form fields.

How long we retain your data

By default Hustle retains all form submissions and tracking data forever. You can delete the stored data in Hustle » Settings » Privacy Settings, and under each module’s settings.

Suggested text: When visitors or users submit a form or view a module we retain the data for 30 days.

Where we send your data

Suggested text: All collected data might be shown publicly and we send it to our workers or contractors to perform necessary actions based on the form submission.

Third Parties

If your forms use either built-in or external third-party services, in this section you should mention any third parties and its privacy policy.

By default Hustle Pro optionally use these third-party integrations:

  • ActiveCampaign. Enabled when you activate and setup ActiveCampaign on Email Collection settings.
  • Aweber. Enabled when you activate and setup Aweber on Email Collection settings.
  • Campaign Monitor. Enabled when you activate and setup Campaign Monitor on Email Collection settings.
  • Constant Contact. Enabled when you activate and setup Constant Contact on Email Collection settings.
  • ConvertKit. Enabled when you activate and setup ConvertKit on Email Collection settings.
  • e-Newsletter. Enabled when you activate and setup e-Newsletter on Email Collection settings.
  • GetResponse. Enabled when you activate and setup GetResponse on Email Collection settings.
  • HubSpot. Enabled when you activate and setup HubSpot on Email Collection settings.
  • iContact. Enabled when you activate and setup iContact on Email Collection settings.
  • Keap. Enabled when you activate and setup Keap on Email Collection settings.
  • Mad Mimi. Enabled when you activate and setup Mad Mimi on Email Collection settings.
  • Mailchimp. Enabled when you activate and setup Mailchimp on Email Collection settings.
  • MailerLite. Enabled when you activate and setup MailerLite on Email Collection settings.
  • Mautic. Enabled when you activate and setup Mautic on Email Collection settings.
  • reCAPTCHA. Enabled when you activate and setup reCAPTCHA on non-Social sharing modules.
  • Pinterest. Enabled when you activate and setup Pinterest in Social Share Module.
  • SendGrid. Enabled when you activated and setup SendGrid on Email Collection settings.
  • SendinBlue. Enabled when you activated and setup SendinBlue on Email Collection settings.
  • Sendy. Enabled when you activated and setup Sendy on Email Collection settings.
  • Zapier. Enabled when you activated and setup Zapier on Email Collection settings.
Suggested text: We use ActiveCampaign to manage our subscriber lists. Their privacy policy can be found here : https://www.activecampaign.com/privacy-policy/. We use Aweber to manage our subscriber. Their privacy policy can be found here : https://www.aweber.com/privacy.htm. We use Campaign Monitor to manage our subscriber. Their privacy policy can be found here : https://www.campaignmonitor.com/policies/#privacy-policy. We use Constant Contact to manage our subscriber. Their privacy policy can be found here : https://www.endurance.com/privacy. We use ConvertKit to manage our subscriber. Their privacy policy can be found here : https://convertkit.com/privacy/. We use e-Newsletter to manage our subscriber. You can learn more about it here https://wpmudev.com/project/e-newsletter/. We use GetResponse to manage our subscriber lists. Their privacy policy can be found here : https://www.getresponse.com/legal/privacy.html?lang=en. We use HubSpot to manage our subscriber. Their privacy policy can be found here : https://legal.hubspot.com/legal-stuff. We use iContact to manage our subscriber. Their privacy policy can be found here : https://www.icontact.com/legal/privacy. We use Keap to manage our subscriber. Their privacy policy can be found here : https://keap.com/legal/privacy-policy. We use Mad Mimi to manage our subscriber. Their privacy policy can be found here : https://madmimi.com/legal/terms. We use Mailchimp to manage our subscriber list. Their privacy policy can be found here : https://mailchimp.com/legal/privacy/. We use MailerLite to manage our subscriber. Their privacy policy can be found here : https://www.mailerlite.com/privacy-policy. We use Mautic to manage our subscriber. Their privacy policy can be found here : https://www.mautic.org/privacy-policy/. We use Pinterest to share media. Their privacy policy can be found here : https://policy.pinterest.com/privacy-policy/. We use reCAPTCHA to protect your website from fraud and abuse. Their privacy policy can be found here : https://policies.google.com/privacy. We use SendGrid to manage our subscriber. Their privacy policy can be found here : https://sendgrid.com/policies/privacy/. We use SendinBlue to manage our subscriber. Their privacy policy can be found here : https://www.sendinblue.com/legal/privacypolicy/. We use Sendy to manage our subscriber. Their privacy policy can be found here : https://sendy.co/privacy-policy. We use Zapier to manage our integration data. Their privacy policy can be found here : https://zapier.com/privacy/.

Cookies

By default Hustle uses cookies to count how many times each module is visualized. Cookies might be used to handle other features such as display settings, used when a module should not be displayed for a certain time, whether the user commented before, whether the user has subscribed, among others, if their related settings are enabled.

WP Smush

Plugin: Smush

Note: Smush does not interact with end users on your website. The only input option Smush has is to a newsletter subscription for site admins only. If you would like to notify your users of this in your privacy policy, you can use the information below. Smush sends images to the WPMU DEV servers to optimize them for web use. This includes the transfer of EXIF data. The EXIF data will either be stripped or returned as it is. It is not stored on the WPMU DEV servers. Smush uses the Stackpath Content Delivery Network (CDN). Stackpath may store web log information of site visitors, including IPs, UA, referrer, Location and ISP info of site visitors for 7 days. Files and images served by the CDN may be stored and served from countries other than your own. Stackpath’s privacy policy can be found here.

The Events Calendar

Hello,

This information serves as a guide on what sections need to be modified due to usage of The Events Calendar and its Add-ons.

You should include the information below in the correct sections of you privacy policy.

Disclaimer: This information is only for guidance and not to be considered as legal advice.

What personal data we collect and why we collect it

Event, Venue, and Organizer Information

Through the usage of The Events Calendar, Events Calendar PRO, The Events Calendar Filter Bar, Eventbrite Tickets, and Community Events plugins, as well as our Event Aggregator Import service (contained within The Events Calendar plugin), information may be collected and stored within your website’s database.

Suggested text:

If you create, submit, import, save, or publish Event, Venue, or Organizer information, such information is retained in the local database:
  1. Venue information: name, address, city, country, state, postal code, phone, website, geographical coordinates (latitude and longitude)
  2. Organizer information: name, phone, website, email
  3. Event information: website, cost, description, date, time, image

Importing Events, Venues, and Organizers:

  1. All data present within a CSV or ICS file and external URLs (for events, venues, organizers, and tickets)
  2. 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)
  3. 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

The Events Calendar suite offers the use of third-party API keys. The primary functions are to enhance the features we’ve built in, some of which use Google Maps, PayPal, Eventbrite, and Meetup. These API keys are not supplied by The Events Calendar.

Suggested text:

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), Meetup (OAuth token), PayPal (email, Client ID, Client Secret), Eventbrite (API key, auth URL, Client Secret), and Zoom (email, Client ID, Client Secret).

How Long You Retain this Data

All information (data) is retained in the local database indefinitely, unless otherwise deleted.

Certain data may be exported or removed upon users’ requests via the existing Exporter or Eraser. Please note, however, that several “edge cases” exist in which we are unable to perfect the gathering and export of all data for your end users. We suggest running a search in your local database, as well as within the WordPress Dashboard, in order to identify all data collected and stored for your specific user requests.

Where We Send Your Data

The Events Calendar does not send any user data outside of your website by default.

If you have extended our plugin(s) to send data to a third-party service such as Eventbrite, Google Maps, or PayPal, user information may be passed to these external services. These services may be located abroad.