The Daniell Bap­tist Asso­ci­a­tion (dbachurches.com or the DBA) takes online pri­va­cy seri­ous­ly, and we active­ly pro­tect the pri­va­cy of the users of our web­sites and those who sub­scribe to our ser­vices.

RSS Sub­scrip­tions: We record infor­ma­tion about how peo­ple access our RSS feeds, but we do not col­lect any per­son­al­ly iden­ti­fy­ing infor­ma­tion from or about our RSS sub­scribers.

E‑mail Sub­scrip­tions: We col­lect the e‑mail address­es of indi­vid­u­als that sub­scribe to our RSS feed via e‑mail. This infor­ma­tion is held in strict con­fi­dence; we do not (and will not) release or dis­close any spe­cif­ic sub­scriber infor­ma­tion under any cir­cum­stances, unless required by law. Gen­er­al aggre­gate infor­ma­tion (e.g., total num­ber of sub­scribers, etc.) may be dis­closed.

Web Serv­er Traf­fic: We record infor­ma­tion about how peo­ple access the web site in our serv­er logs. This includes things such as your IP address (or DNS), your brows­er, and your oper­at­ing sys­tem.

Com­menter E‑mail: E‑mail sent to the site is con­sid­ered prop­er­ty of this site, and ques­tions or tips might be pub­lished. In such cas­es, we will not dis­close any per­son­al­ly iden­ti­fy­ing infor­ma­tion.

Com­ments: Com­ments left on the site are the respon­si­bil­i­ty of the com­menter. We reserve the right to remove com­ments or edit them. Site URLs (if pro­vid­ed) may or may not be pub­lished, at the dis­cre­tion of

Exter­nal Links: The web site con­tains numer­ous links to oth­er sites. Due to the con­stant­ly chang­ing nature of the Inter­net, we can­not vouch for the reli­a­bil­i­ty of those sites or their pri­va­cy poli­cies.

Cook­ies and web bea­cons: Third par­ties (includ­ing adver­tis­ing ser­vices) may be plac­ing and read­ing cook­ies on your brows­er in the nor­mal course of pro­vid­ing ser­vices to this web­site. Some ser­vices on this site also may use web bea­cons (tiny small trans­par­ent images) to col­lect infor­ma­tion in the course of pro­vid­ing ser­vices to this web­site. Your web broswer should have options to man­age cook­ies should this be desir­able. Con­sult your browser’s help sec­tion for infor­ma­tion on view­ing, set­ting, and chang­ing these options.

Col­lec­tion of non-per­son­al­ly-iden­ti­fi­able infor­ma­tion by third par­ties: Third par­ties (includ­ing adver­tis­ing ser­vices) may be plac­ing and read­ing cook­ies on your brows­er in the nor­mal course of pro­vid­ing ser­vices to this web­site. Some ser­vices on this site also may use web bea­cons (tiny small trans­par­ent images) to col­lect infor­ma­tion in the course of pro­vid­ing ser­vices to this web­site. Your web broswer should have options to man­age cook­ies should this be desir­able. Con­sult your browser’s help sec­tion for infor­ma­tion on view­ing, set­ting, and chang­ing these options. We use third-par­ty adver­tis­ing com­pa­nies to serve ads when you vis­it our web­site. These com­pa­nies may use infor­ma­tion (not includ­ing your name, address, email address, or tele­phone num­ber) about your vis­its to this and oth­er web­sites in order to pro­vide adver­tise­ments about goods and ser­vices of inter­est to you.

Per­son­al infor­ma­tion that can iden­ti­fy a vis­i­tor, such as name, address or con­tact infor­ma­tion, is col­lect­ed only when vol­un­tar­i­ly offered and sole­ly for pur­pos­es that are clear­ly iden­ti­fied on our sites. Access to pages with con­tent spe­cif­ic to a min­istry area and/or its con­stituents is pass­word-pro­tect­ed and requires pre-reg­is­tra­tion. Per­son­al infor­ma­tion acquired through reg­is­tra­tion is kept con­fi­den­tial and will not be dis­closed to third par­ties except as may be required by law. DBA does not seek per­son­al infor­ma­tion from chil­dren online.

Cook­ies

The DBA may place an elec­tron­ic “cook­ie” in the brows­er files of a guest’s com­put­er. Cook­ies are pieces of infor­ma­tion that a web site trans­fers to an indi­vid­u­als com­put­er hard dri­ve for record-keep­ing pur­pos­es. Cook­ies them­selves do not enable us to access any per­son­al infor­ma­tion about our vis­i­tors; how­ev­er, they do allow DBA to ana­lyze guests’ use of our sites and to improve the user expe­ri­ence. This analy­sis helps us bet­ter under­stand which areas of our sites are most use­ful and pop­u­lar so we can plan improve­ments and updates accord­ing­ly. DBA does not use cook­ies to retrieve infor­ma­tion from a vis­i­tor’s com­put­er that was not orig­i­nal­ly sent in a cook­ie.

Ana­lyt­ics

DBA may use Google Ana­lyt­ics to help us gath­er details about usage of our web­sites. Google Ana­lyt­ics is a web ana­lyt­ics tool that helps web­site own­ers under­stand how vis­i­tors engage with their web­site. Google Ana­lyt­ics col­lects infor­ma­tion anony­mous­ly. It reports web­site trends with­out iden­ti­fy­ing indi­vid­ual vis­i­tors. For more infor­ma­tion please vis­it http://www.google.com/policies/privacy/.

Inter­net Com­mu­ni­ca­tion

The pri­va­cy of com­mu­ni­ca­tion over the Inter­net can­not be guar­an­teed, because the Inter­net is not a secure medi­um. The DBA does not assume any respon­si­bil­i­ty for any harm, loss, or dam­age you may expe­ri­ence or incur by the send­ing of per­son­al or con­fi­den­tial infor­ma­tion over the Inter­net by or to the DBA.

Con­sent

By using this site, you sig­ni­fy your con­sent to the DBA’s on-line pri­va­cy pol­i­cy. If you do not agree to this pol­i­cy, please do not use this site. We reserve the right, at our dis­cre­tion, to update, change, mod­i­fy, add, or remove por­tions of this pol­i­cy from time to time.

Cred­it Card / Pay­ment Infor­ma­tion Pol­i­cy — How We Pro­tect Cred­it Card Num­bers

Pub­lished August, 2013

DBA may col­lect cred­it card infor­ma­tion in the course of busi­ness on our sites. We strive to pro­tect the con­fi­den­tial­i­ty and secu­ri­ty of this infor­ma­tion in our pos­ses­sion, cus­tody or con­trol by (i) lim­it­ing access to card num­bers, and (ii) main­tain­ing rea­son­able safe­guards to pro­tect against the loss, mis­use or unlaw­ful dis­clo­sure of card num­bers. No cred­it card infor­ma­tion is stored or logged on any sys­tem housed at the DBA — this infor­ma­tion is passed straight to our pay­ment proces­sor and always com­mu­ni­cat­ed over encrypt­ed com­mu­ni­ca­tion chan­nels.