Copyright

 

© Organic Fruit Growers Association (hereinafter: OFGA), 2019-2020. 

 

Unauthorized use and/or duplication of any material on the OFGA website without express and written permission from the authors and/or owners is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to OFGA with appropriate and specific direction to the original content.

 

Privacy policy

 

We recognize that privacy of your personal information is important. Below you will find information on what types of personal information we receive and collect when you use our website, and how we (Google and us) safeguard your information. We never sell your personal information to third parties.

 

Log Files

As with most other websites, we collect and use the data contained in log files. The information in the log files include your IP (internet protocol) address, your ISP (internet service provider, such as AOL or Shaw Cable), the browser you used to visit our site (such as Internet Explorer or Firefox), the time you visited our site and which pages you visited throughout our site.

 

Cookies and Web Beacons

We do use cookies to store information, such as your personal preferences when you visit our site. This could include only showing you a popup once in your visit, or the ability to login to some of our features, such as forums.

 

Third-Party Advertisements

We do not use third-party advertisements on the OFGA website. Some of our pages (e.g. “Resources” or “Events”) contain links to websites of our partners. OFGA has no control over the privacy policies and measures of these websites.

 

You can choose to disable or selectively turn off our cookies or third-party cookies in your browser settings, or by managing preferences in programs such as Norton Internet Security. However, this can affect how you are able to interact with our site as well as other websites. This could include the inability to login to services or programs, such as logging into forums or accounts.

 

Deleting cookies does not mean you are permanently opted out of any advertising program. Unless you have settings that disallow cookies, the next time you visit a site running the advertisements, a new cookie will be added.

 

 

Web Store

 

We use Stripe for online payment processing. Below is the information about security at Stripe, as shown on their website (https://stripe.com/docs/security/stripe, downloaded on 12/3/2019).

 

Stripe has been audited by a PCI-certified auditor and is certified to PCI Service Provider Level 1. 

This is the most stringent level of certification available in the payments industry. To accomplish this, we make use of best-in-class security tools and practices to maintain a high level of security at Stripe.

 

HTTPS and HSTS for secure connections

 

Stripe forces HTTPS for all services using TLS (SSL), including our public website and the Dashboard.

• Stripe.js is served only over TLS

• Stripe’s official libraries connect to Stripe’s servers over TLS and verify TLS certificates on each connection

 

We regularly audit the details of our implementation: the certificates we serve, the certificate authorities we use, and the ciphers we support. We use HSTS to ensure browsers interact with Stripe only over HTTPS. Stripe is also on the HSTS preloaded lists for both Google Chrome and Mozilla Firefox.

 

Encryption of sensitive data and communication

 

All card numbers are encrypted at rest with AES-256. Decryption keys are stored on separate machines. None of Stripe’s internal servers and daemons are able to obtain plaintext card numbers; instead, they can just request that cards be sent to a service provider on a static whitelist. Stripe’s infrastructure for storing, decrypting, and transmitting card numbers runs in separate hosting infrastructure, and doesn’t share any credentials with Stripe’s primary services (API, website, etc.).