Privacy Policy, Terms and Conditions

Effective Date
August 9, 2017

Use of Your Information

By accessing freedomfy, you agree to the following terms and conditions (“Terms and Conditions” or “Agreement”).  You are bound by this Agreement, which is between you and freedomfy and its affiliates and defines your rights and responsibilities.  Use of freedomfy as a registered user results in your information being stored, processed and used by freedomfy in the United States, and you specifically agree and consent to freedomfy’s storage, processing and use of any personal data that you may submit. freedomfy reserves all rights in and to personal data or content that users may submit, including the right to use or transfer. freedomfy is intended to be used by adults.  By using freedomfy, you acknowledge and agree that all terms, conditions and policies stated herein shall constitute the entire agreement between you and freedomfy and its affiliates.

For all campaigns and organizational users, by submitting content to freedomfy you represent and agree that you have the right to do so and you have obtained all consents by the candidate, campaign, group or organization.  You agree that you will be held liable to us and indemnify us for any loss or damage we suffer as a result of your breach of these warranties.

Use of Your E-mail Address

Your e-mail address is required so we can e-mail you a donation receipt. You may receive occasional e-mail updates as freedomfy is developed. You can unsubscribe any time by e-mailing, but please allow approximately one week for processing.

Information freedomfy Collects

When you contribute to candidates, causes and committees through freedomfy, we may be required to collect your name, postal address, phone number, email address, occupation, employer, and employer’s address, and send this information along with your donation to the candidate committee or organization. Each candidate, committee, or organization receiving your donations may include this information in their regulatory reports.

As required by state law, freedomfy may also record this information together with your contribution amounts and recipients in the campaign finance reports we may file with the respective state agency on a rolling basis if required. These reports are generally publicly available through the designated state agency that oversees campaigns and elections.

Use of Your Credit Card Information

All credit card information is transmitted securely to Stripe. freedomfy will not handle or store your credit information. freedomfy uses Stripe as the payment processor for every donation, as well as providing a unique “Stripe Customer ID” to charge your card. Again, credit card information is never stored on freedomfy servers. Neither freedomfy nor Stripe will share your payment information with anyone.

When you register for freedomfy, Stripe alone will store a copy of your credit card number. Stripe then provides a code called a Customer ID to our system. This ID allows freedomfy to make charges against your credit card in the future without you having to re-enter your card information.

Important Information Regarding Stripe

Stripe is a global payment gateway and is a PCI Level 1 payment processor, providing industry-standard security for all user information. Click here: for more information on Stripe’s security details.


Some parts of our site use cookies. A “cookie” is a small text file that is stored on your computer by websites that you visit. Cookies on the freedomfy website enables you to return to password-protected areas, without re-entry of your password. Cookies can be disabled by modifying your browser preferences.

IP Addresses

freedomfy logs IP addresses, which are identifying numbers that correspond with the location of computers or networks on the Internet, and analyze them for systems administration and troubleshooting purposes. To improve the quality of our site and to track the popularity of certain webpages, we will also collect the number of page hits. No personal identifying information is collected in our log files.

Effective date

August 9, 2017