1<!DOCTYPE html> 2<html lang="en-US"> 3 <head> 4
4<script defer="defer" src="https://cdnjs.runsignup.com/ajax/libs/webfont/1.6.28/webfontloader.js" integrity="sha512-v/wOVTkoU7mXEJC3hXnw9AA6v32qzpknvuUF6J2Lbkasxaxn2nYcl+HGB7fr/kChGfCqubVr1n2sq1UFu3Gh1w==" crossorigin="anonymous"></script>
4 5 <link rel="preconnect" href="https://fonts.gstatic.com" /> 6 <link rel="preconnect" href="https://www.gstatic.com" /> 7 <link rel="preconnect" href="https://fonts.googleapis.com" /> 8 9
9<script defer="defer" type="text/javascript" src="https://d368g9lw5ileu7.cloudfront.net/js/race/templates/raceTemplate3.min.bQCnT7.js"></script>
9
9<script defer="defer" type="text/javascript" src="https://d368g9lw5ileu7.cloudfront.net/js/ui/stickyHeader.min.bQCiQ7.js"></script>
9 10
10<script defer="defer" type="text/javascript" src="https://d368g9lw5ileu7.cloudfront.net/js/components/lazyLoad.min.bLGmDc.js"></script>
10 11 <link rel="stylesheet" type="text/css" href="https://d368g9lw5ileu7.cloudfront.net/css/frameRaceTemplate3.scss.rsu.min.bQWau_.css" /> 12 13 14 15 <meta name="viewport" content="width=device-width,initial-scale=1,shrink-to-fit=no,viewport-fit=cover" /> 16 <meta http-equiv="Content-Type" content="text/html;charset=utf-8" /> 17 18 19 20 21 <meta name="verify-v1" content="pPPI9MXDo069DhV+2itqhV46AR8OWnG+NxzCulTUTns=" /> 22<meta name="google-site-verification" content="wFyq2zuG7IBY5ilQqEELBypyn04UZIYBgKPHrTMnTUg" /> 23 24 <link rel="canonical" href="https://www.biggerintexaschallenge.com/About-Us/Privacy-Policy" /> 25 26 <link rel="search" type="application/opensearchdescription+xml" title="RunSignup" href="/opensearch.xml" /> 27 28<title>Bigger in Texas Challenge Privacy Policy</title> 29 30 <meta property="og:url" content="https://www.biggerintexaschallenge.com/About-Us/Privacy-Policy" /> 31 32 33 <meta property="og:title" content="Bigger in Texas Challenge" /> 34 <meta name="twitter:title" content="Bigger in Texas Challenge" /> 35 <meta name="keywords" content="Run, Running, Sign Up, Race Register, Race Director" /> 36 <meta name="description" content="The Bigger in Texas Challenge is on Monday June 1, 2020 to Thursday December 31, 2020. It includes the following events: Capital to Dallas, Capital to Corpus Christi, Capital to El Paso, Capital to Houston, and Capital to San Antonio." /> 37 <meta property="og:description" content="The Bigger in Texas Challenge is on Monday June 1, 2020 to Thursday December 31, 2020. It includes the following events: Capital to Dallas, Capital to Corpus Christi, Capital to El Paso, Capital to Houston, and Capital to San Antonio." /> 38 <meta name="twitter:description" content="The Bigger in Texas Challenge is on Monday June 1, 2020 to Thursday December 31, 2020. It includes the following events: Capital to Dallas, Capital to Corpus Christi, Capital to El Paso, Capital to Houston, and Capital to San Antonio." /> 39 <meta property="og:type" content="website" /> 40 41 42 <meta property="og:image" content="https://d368g9lw5ileu7.cloudfront.net/races/race92201-social1200x630.bE9DYb.jpg" /> 43 44 <meta property="og:image:width" content="1200" /> 45 <meta property="og:image:height" content="630" /> 46 47 <meta name="twitter:card" content="summary_large_image" /> 48 <meta name="twitter:image" content="https://d368g9lw5ileu7.cloudfront.net/races/race92201-social1200x630.bE9DYb.jpg" /> 49 <meta property="og:site_name" content="Bigger in Texas Challenge" /> 50 51 52 53 54 55 <link rel="icon" href="https://d368g9lw5ileu7.cloudfront.net/img/nonversioned/favicon/runsignup/icon.png" type="image/png" /> <link rel="icon" href="https://d368g9lw5ileu7.cloudfront.net/img/nonversioned/favicon/runsignup/icon.svg" type="image/svg+xml" /> 56 <link rel="apple-touch-icon" href="https://d368g9lw5ileu7.cloudfront.net/img/nonversioned/favicon/runsignup/apple-touch-icon.png" /> 57 <link rel="manifest" href="https://d368g9lw5ileu7.cloudfront.net/manifest/runsignup/site.bJOg53.webmanifest" /> 58 59 60 61 62 63 64 65 <link rel="stylesheet" type="text/css" href="https://d3dq00cdhq56qd.cloudfront.net/c34139.bQWavb.bEZbtZ/race/92201/fc5c4b74a3ef68ef752603a2045e5bdb/themedRaceTemplate3-otf.scss.css" /> 66 67 <!-- DYNAMIC_CSS_PLACEHOLDER --> 68 69 70<link rel="stylesheet" type="text/css" href="https://iad-dynamic-assets.runsignup.com/us-east-1-src/prod/iconfonts/fc33fc7151664f109ef322fa866a9307/style.css" /> 71 72
72<script type="text/javascript" src="https://cdnjs.runsignup.com/ajax/libs/jquery/4.0.0/jquery.min.js" integrity="sha512-8LENNbXmzI/Gbj+OwXmqR6V4QaUAw0/porPzy1+dQoJqC0JPHedWoe0DDOTL2uHA5XXJyIsPtiMHH86pVlay6A==" crossorigin="anonymous"></script>
72 73
73<script type="text/javascript" src="https://cdnjs.runsignup.com/ajax/libs/jqueryui/1.14.2/jquery-ui.min.js" integrity="sha512-tNGSWf0jBrMhc+g3/okGfweLw7TYGTxs3GcTK5O+gLptfqNqlkgTp8c7+mpJcJxJvAl/u8FUZtUDm3JcDJmPWQ==" crossorigin="anonymous"></script>
73 74
75<script type="application/json" id="sessionJsData"> 76{ 77 "csrf": "LyzQUaDsDr6zL3Z5lYRemvaAnqOg7T7g", 78 "serverTzOffset": -14400000 79} 80</script>
80 81
82<script type="text/javascript" src="https://d368g9lw5ileu7.cloudfront.net/js/session.min.bN4VU_.js"></script>
82<script type="text/javascript" src="https://d368g9lw5ileu7.cloudfront.net/js/utils.min.bQCman.js"></script>
82<script type="text/javascript" src="https://d368g9lw5ileu7.cloudfront.net/js/windows.min.bz27OH.js"></script>
82 83 84
84<script defer="defer" type="text/javascript" src="https://d368g9lw5ileu7.cloudfront.net/js/analytics/runalytics.min.bQCiQ7.js"></script>
84
84<script type="application/json" id="runalyticsData"> 85 { 86 "raceId": 92201, 87 "timezone": "America\/Chicago", 88 "analyticsApiBaseUrl": "https:\/\/analytics.runsignup.com\/prod\/", 89 "validTrackingSources": [1,100,200,300,400,500,600], 90 "validTrackingMediums": [1,200,201,202,203,204,300,400,500,501,600] 91 } 92 </script>
vendor: 93 bytes, lines 92-98
92 93 94 95 96 97 98 <script async src="https://www.googletagmanager.com/gtag/js?id=
98G-QKEVS8BTWC
vendor: 14 bytes, lines 98-99
98"></script> 99
99<script>//<![CDATA[ 100
vendor: 136 bytes, lines 100-103
100window.dataLayer = window.dataLayer || []; 101 function gtag(){dataLayer.push(arguments);} 102 gtag('js', new Date()); 103 gtag('config', "
103G-QKEVS8BTWC
vendor: 145 bytes, lines 103-109
103", 104 { "domain": "runsignup.com", 105 "user_type": "public", 106 "business_line": "RunSignup", 107 "site_type": "Race Site" } 108 ); 109
109//]]></script>
109 110 111
111<script>//<![CDATA[ 112 (function(w, d, s, u){ 113 if (w.oaiq) return; 114 var q = function(){q.q.push(arguments);}; 115 q.q = []; 116 w.oaiq = q; 117 var js = d.createElement(s); 118 js.async = true; 119 js.src = u; 120 var f = d.getElementsByTagName(s)[0]; 121 f.parentNode.insertBefore(js, f); 122 })(window, document, "script", "https://bzrcdn.openai.com/sdk/oaiq.min.js"); 123 124 oaiq("init", { 125 "pixelId": "8Wg59xsdryRMJdUubADX33" 126 }); 127 //]]></script>
127 128 129 130
130<script defer="defer" type="text/javascript" src="https://d368g9lw5ileu7.cloudfront.net/js/typescript-compiled/urlTracking/urlTrackingCleaner.bP344r.js"></script>
130 131 132 133
133<script>//<![CDATA[ 134 !function(f,b,e,v,n,t,s){if(f.fbq)return;n=f.fbq=function(){n.callMethod? 135 n.callMethod.apply(n,arguments):n.queue.push(arguments)};if(!f._fbq)f._fbq=n; 136 n.push=n;n.loaded=!0;n.version='2.0';n.queue=[];t=b.createElement(e);t.async=!0; 137 t.src=v;s=b.getElementsByTagName(e)[0];s.parentNode.insertBefore(t,s)}(window, 138 document,'script','https://connect.facebook.net/en_US/fbevents.js'); 139 140 // intentionally before init 141 fbq('dataProcessingOptions', []); 142 143 // init pixel 144 fbq('init', 2708282689391483); 145 fbq('track', 'PageView'); 146//]]></script>
146 147 148 149 150
150<script defer="defer" type="text/javascript" src="https://d368g9lw5ileu7.cloudfront.net/js/ui/rsuMobileNav.min.bO77bH.js"></script>
150 </head> 151 <body data-popup-style="1"> 152 153 <a href="#mainContent" class="rsuBtn rsuBtn--xs rsuBtn--themed margin-0 rsuSkipNavLink">Skip to main content</a> 154 155 <div id="blackOverlay" class="overlay overlayBlack"></div> 156 157 158 159 <div id="acceptCookies" style="display: none;"> 160 <p> 161 In order to use RunSignup, your browser must accept cookies. Otherwise, you will not be able to register for races or use other functionality of the website. 162 However, your browser doesn't appear to allow cookies by default. 163 </p> 164 <p> 165 <b>Click the âAccept Cookie Policyâ button below to accept the use of cookies on your browser.</b> 166 </p> 167 <p> 168 If you still see this message after clicking the link, then your browser settings are likely set to not allow cookies. 169 Please try enabling cookies. You can find instructions at <a href="https://www.whatismybrowser.com/guides/how-to-enable-cookies/auto">https://www.whatismybrowser.com/guides/how-to-enable-cookies/auto</a>. 170 </p> 171 <hr class="hr--gray" /> 172 <div class="ta-center submitBackLinks"> 173 <form method="post" action="/WidgetAux/AcceptCookies" target="acceptCookies">
174 <button type="submit" class="rsuBtn rsuBtn--primary">Accept Cookie Policy</button> 175 </form> 176 </div> 177 <iframe name="acceptCookies" height="0" width="0" frameborder="0" scrolling="no"></iframe> 178 </div> 179
179<script type="text/javascript" src="https://d368g9lw5ileu7.cloudfront.net/js/acceptCookiesPopup.min.bEboUX.js"></script>
179 180 181 182 183 184 185 186 187 <div class="stickyHeader" data-scroll-top-down="160"> 188 <div class="stickyHeader__container container"> 189 <div class="stickyHeader__left"> 190 <button type="button" class="rsuMobileNavMenuBtn rsuMobileNavMenuBtn--sticky" aria-label="Toggle Mobile Navigation"><i class="icon icon-menu" aria-hidden="true" ></i></button> 191 <div class="stickyHeader__logo hidden-xs-down"> 192 <a href="/" > 193 <img src="https://d368g9lw5ileu7.cloudfront.net/races/race92201-logo-0.bE9DYc.png" alt="Bigger in Texas Challenge home" /> 194 </a> 195 </div> 196 <div class="stickyHeader__details"> 197 <h2 class="" > 198 <a href="/Race/TX/Stateof/BiggerinTexasChallenge">Bigger in Texas Challenge</a> 199 </h2> 200 <span class="date"> 201 Mon June 1 - Thu December 31 202 203 </span> 204 </div> 205 </div> 206 207 <div class="stickyHeader__actions stickyHeader__actions--mobile-flex"> 208 209 <a href="/Race/Donate/TX/Stateof/BiggerinTexasChallenge" class="rsuBtn rsuBtn--
209primary rsuBtn--md rsuBtn--mobile-responsive margin-tb-0"> 210 Donate 211 212 </a> 213 214 </div> 215 <div class="stickyHeader__avatar-menu hidden-xs-down margin-l-10"> 216 217<button type="button" aria-label="User Menu" class="rsuCircleImg rsuCircleImg--xs " data-rsu-menu="userRsuMenu2" style="background-image: url(https://d368g9lw5ileu7.cloudfront.net/img/user.bOhrdK.svg);"></button> 218<div class="rsuMenu padding-0" id="userRsuMenu2" hidden="hidden"> 219 <div class="rsuMenu__content overflow-auto"> 220 <div class="rsuAccountMenu"> 221 <div class="rsuAccountMenu__header"> 222 <img src="https://d368g9lw5ileu7.cloudfront.net/img/logos/logo-rsu.bIAeuH.svg" 223 alt="" 224 class="rsuAccountMenu__logo" 225 style="width: 200px;" 226 /> 227 </div> 228 <div class="rsuAccountMenu__content"> 229 <a href="/Login" class="rsuAccountMenu__link"> 230 <div class="rsuAccountMenu__link__main"> 231 <div class="rsuAccountMenu__link__img rsuAccountMenu__link__img--signIn" aria-hidden="true"></div> 232 <div class="rsuAccountMenu__link__content"> 233 <div class="rsuAccountMenu__link__content__title">Sign In</div> 234 </div> 235 </div> 236 </a> 237 238 <a href="/CreateAccount?redirect=%2FAbout-Us%2FPrivacy-Policy" class="rsuAccountMenu__link"> 239 <div class="rsuAccountMenu__link__main"> 240 <div class="rsuAccountMenu__link__img rsuAccountMenu__link__img--createAccount" aria-hidden="true"></div> 241 <div class="rsuAccountMenu__link__content"> 242 <div class="rsuAccountMenu__link__content__title">Create Account</div> 243 </div> 244 </div> 245 </a> 246 247 <a href="https://help.runsignup.com/" class="rsuAccountMenu__link" target="_blank" rel="noopener noreferrer"> 248 <div class="rsuAccountMenu__link__main"> 249 <div class="rsuAccountMenu__link__img rsuAccountMenu__link__img--help" aria-hidden="true"></div> 250 <div class="rsuAccountMenu__link__content"> 251 <div class="rsuAccountMenu__link__content__title">Help</div> 252 </div> 253 </div> 254 </a> 255 </div> 256 </div> 257 </div> 258</div> 259
260<script defer="defer" type="text/javascript" src="https://d368g9lw5ileu7.cloudfront.net/js/ui/rsuMenu.min.bQCiQ7.js"></script>
260 </div> 261 </div> 262 </div> 263 264 265<nav class="runnerUI3Nav rsuMobileNav rsuMobileNav--left" data-focus="#rsuMobileNavCloseBtn" aria-hidden="true"> 266 <button type="button" id="rsuMobileNavCloseBtn" class="rsuMobileNav__closeBtn rsuBtn rsuBtn--text--white rsuBtn--padding-xs margin-t-25 margin-l-10 margin-b-0" aria-label="Close or Skip Mobile Navigation"><i class="icon icon-cross fs-md-2 margin-0" aria-hidden="true" ></i></button> 267 <div class="rsuMobileNav__content"> 268 <ul> 269 <li class="rsuMobileNav__link"> 270 <a href="/Race/Info/TX/Stateof/BiggerinTexasChallenge" 271 >Race Info</a> 272 273 </li> 274 <li class="rsuMobileNav__link"> 275 <a href="/Race/BiggerinTexasChallenge/Page/routes" 276 >Routes</a> 277 278 </li> 279 <li class="rsuMobileNav__submenu"> 280 <button type="button" aria-label="rsuMobileNav Submenu" > 281 Donate</button> 282 283 <ul> 284 <li class="rsuMobileNav__link"> 285 <a href="/Race/Donate/TX/Stateof/BiggerinTexasChallenge" >Donate</a> 286 </li> 287 <li > 288 <a href="/Race/Donate/92201/BecomeFundraiser" >Become a Fundraiser</a> 289 </li> 290 <li > 291 <a href="/Race/Donate/92201/TopFundraisers" >Top Fundraisers</a> 292 </li> 293 </ul> 294 </li> 295 <li class="rsuMobileNav__link"> 296 <a href="/Race/BiggerinTexasChallenge/Page/referral" 297 >Referral Rewards</a> 298 299 </li> 300 <li class="rsuMobileNav__link"> 301 <a href="/Race/BiggerinTexasChallenge/Page/faq" 302 >FAQ</a> 303 304 </li> 305 <li class="rsuMobileNav__link"> 306 <a href="/Race/Results/Overview/92201" 307 >Results</a> 308 309 </li> 310 <li class="rsuMobileNav__link"> 311 <a href="/RaceGroups/92201" 312 >Group/Teams</a> 313 314 </li> 315 <li class="rsuMobileNav__link"> 316 <a href="/Race/Photos/TX/Stateof/BiggerinTexasChallenge" 317 >Photos</a> 318 319 </li> 320 </ul> 321 </div> 322</nav> 323 324 <div class="rsuMobileNavOverlay"></div> 325 326 <div class="rsu-template-wrapper rsuMobileNavPageContainer"> 327 <div id="transparencyScreen"></div> 328 329 330 331 332<div class="rsu-racesite-template2"> 333 334 335 336<div class="head"> 337 <div class="container"> 338 <div class="flex-parent flex-wrap"> 339 <button type="button" class="rsuMobileNavMenuBtn" aria-label="Toggle Mobile Navigation"><i class="icon icon-menu" aria-hidden="true" ></i></button> 340 <div class="template-race-logo"> 341 <a href="/" > 342 <img src="https://d368g9lw5ileu7.cloudfront.net/races/race92201-logo-0.bE9DYc.png" alt="Bigger in Texas Challenge home" /> 343 </a> 344 </div> 345 <div class="flex-1 flex-parent template-head-right flex-direction-column"> 346 <div class="action-buttons flex-parent align-items-center"> 347 <a href="/Race/Donate/TX/Stateof/BiggerinTexasChallenge" class="rsuBtn rsuBtn--
347primary rsuBtn--mobile-responsive rsuBtn--full-width-sm margin-0"> 348 Donate 349 350 </a> 351 352 <div class="template-avatar-menu"> 353 354<button type="button" aria-label="User Menu" class="rsuCircleImg rsuCircleImg--xs " data-rsu-menu="userRsuMenu" style="background-image: url(https://d368g9lw5ileu7.cloudfront.net/img/user.bOhrdK.svg);"></button> 355<div class="rsuMenu padding-0" id="userRsuMenu" hidden="hidden"> 356 <div class="rsuMenu__content overflow-auto"> 357 <div class="rsuAccountMenu"> 358 <div class="rsuAccountMenu__header"> 359 <img src="https://d368g9lw5ileu7.cloudfront.net/img/logos/logo-rsu.bIAeuH.svg" 360 alt="" 361 class="rsuAccountMenu__logo" 362 style="width: 200px;" 363 /> 364 </div> 365 <div class="rsuAccountMenu__content"> 366 <a href="/Login" class="rsuAccountMenu__link"> 367 <div class="rsuAccountMenu__link__main"> 368 <div class="rsuAccountMenu__link__img rsuAccountMenu__link__img--signIn" aria-hidden="true"></div> 369 <div class="rsuAccountMenu__link__content"> 370 <div class="rsuAccountMenu__link__content__title">Sign In</div> 371 </div> 372 </div> 373 </a> 374 375 <a href="/CreateAccount?redirect=%2FAbout-Us%2FPrivacy-Policy" class="rsuAccountMenu__link"> 376 <div class="rsuAccountMenu__link__main"> 377 <div class="rsuAccountMenu__link__img rsuAccountMenu__link__img--createAccount" aria-hidden="true"></div> 378 <div class="rsuAccountMenu__link__content"> 379 <div class="rsuAccountMenu__link__content__title">Create Account</div> 380 </div> 381 </div> 382 </a> 383 384 <a href="https://help.runsignup.com/" class="rsuAccountMenu__link" target="_blank" rel="noopener noreferrer"> 385 <div class="rsuAccountMenu__link__main"> 386 <div class="rsuAccountMenu__link__img rsuAccountMenu__link__img--help" aria-hidden="true"></div> 387 <div class="rsuAccountMenu__link__content"> 388 <div class="rsuAccountMenu__link__content__title">Help</div> 389 </div> 390 </div> 391 </a> 392 </div> 393 </div> 394 </div> 395</div> 396 397 </div> 398 </div> 399 <div class="race-navigation flex-1"> 400 <nav class="runnerUI3Nav"> 401 <ul class="menu primaryMenu"> 402 403 <li > 404 <a 405 href="/Race/Info/TX/Stateof/BiggerinTexasChallenge" 406 >Race Info</a> 407 408 </li> 409 410 <li > 411 <a 412 href="/Race/BiggerinTexasChallenge/Page/routes" 413 >Routes</a> 414 415 </li> 416 417 <li > 418 <a 419 href="#" 420 data-is-parent-menu="T" 421 >Donate</a> 422 423 <ul> 424 <li> 425 <a href="/Race/Donate/TX/Stateof/BiggerinTexasChallenge" >Donate</a> 426 </li> 427 <li > 428 <a href="/Race/Donate/92201/BecomeFundraiser" >Become a Fundraiser</a> 429 </li> 430 <li > 431 <a href="/Race/Donate/92201/TopFundraisers" >Top Fundraisers</a> 432 </li> 433 </ul> 434 </li> 435 436 <li > 437 <a 438 href="/Race/BiggerinTexasChallenge/Page/referral" 439 >Referral Rewards</a> 440 441 </li> 442 443 <li > 444 <a 445 href="/Race/BiggerinTexasChallenge/Page/faq" 446 >FAQ</a> 447 448 </li> 449 450 <li > 451 <a 452 href="/Race/Results/Overview/92201" 453 >Results</a> 454 455 </li> 456 457 <li > 458 <a 459 href="/RaceGroups/92201" 460 >Group/Teams</a> 461 462 </li> 463 <li><button type="button" value="menuShowMore" class="parent icon-angle-down">More</button></li> 464 </ul> 465 </nav> 466 </div> 467 </div> 468 <div class="container"> 469 <div class="menu-more" style="display:none;"> 470 <ul class="menu container"> 471 472 <li > 473 <a 474 href="/Race/Photos/TX/Stateof/BiggerinTexasChallenge" 475 >Photos</a> 476 477 </li> 478 </ul> 479 </div> 480 </div> 481 </div> 482 </div> 483</div> 484 485 486<div class="race-branding-interior "> 487 <div class="container"> 488 <div class="p-rel race-details flex-parent flex-responsive flex-space-between "> 489 <div class="flex-2"> 490 <h1 class="runnerUITitle " > 491 <a href="/Race/TX/Stateof/BiggerinTexasChallenge">Bigger in Texas Challenge</a> 492 </h1> 493 494 <div class="race-date"> 495 496 Mon June 1 - Thu December 31 497 498 </div> 499 500 <div class="race-location"> 501 State of, TX 77546 US 502 503 </div> 504 </div> 505 506 <div class="race-socialshare margin-t-15"> 507 <div class="shareLinks"> 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522<div class="rsuSocialMediaBtnGroup padding-10"> 523 <button type="button" class="rsuSocialMediaBtn rsuSocialMediaBtn--fb rsuSocialMediaBtn--small" aria-label="Share on Facebook" 524 data-share-type="facebook" 525 data-url="" 526 > 527 <i class="icon icon-facebook" aria-hidden="true" ></i> 528 </button> 529 530 <button type="button" class="rsuSocialMediaBtn rsuSocialMediaBtn--tw rsuSocialMediaBtn--small" data-share-type="twitter" data-popup-id-prefix="raceShareLink" aria-label="Share on Twitter"><i class="icon icon-twitter-x" aria-hidden="true" ></i></button> 531 532 <div id="raceShareLink-socialSharePopup-twitter" hidden="hidden" data-append-url="true"> 533 <div class="formInput margin-t-15"> 534 <label class="formInput__label margin-t-5" for="socialShareTwitterMessage">Enter your Tweet</label> 535 <textarea rows="5" cols="100" class="noTinyMce margin-t-5" id="socialShareTwitterMessage" placeholder="Your Message" required="required"> Check out this race! </textarea> 536 </div> 537 538 <div data-action="post"> 539 <div class="ta-center submitBackLinks"> 540 <a href="#" rel="me" target="_blank" class="submit rsuBtn rsuBtn--twitter margin-0"><i class="icon icon-twitter-x margin-r-10" aria-hidden="true" ></i> Tweet</a> 541 </div> 542 </div> 543 </div> 544 545 <button type="button" class="rsuSocialMediaBtn rsuSocialMediaBtn--gray rsuSocialMediaBtn--small" aria-label="Share via Email" 546 data-share-type="email" 547 data-default-recipient="" 548 data-email-subject="Check out this race!" 549 data-email-body="Check out this race!" 550 data-append-current-url="true" 551 > 552 <i class="icon icon-mail4" aria-hidden="true" ></i> 553 </button> 554 <button type="button" class="rsuSocialMediaBtn rsuSocialMediaBtn--sms rsuSocialMediaBtn--small" data-share-type="sms" data-popup-id-prefix="raceShareLink" aria-label="Share through Text"><i class="icon icon-bubbles2" aria-hidden="true" ></i></button> 555 556 <div id="raceShareLink-socialSharePopup-sms" hidden="hidden" data-append-url="true"> 557 <div class="formInput margin-t-15"> 558 <label class="formInput__label" for="socialShareSmsMessage">Enter your message</label> 559 <textarea rows="5" cols="100" class="noTinyMce margin-t-5" id="socialShareSmsMessage" placeholder="Your Message" required="required">Check out this race!</textarea> 560 </div> 561 <p class="padding-0 ta-center fs-xs-2">Please be advised that utilizing this text feature may result in additional SMS and data charges from your mobile service provider. <
561/p> 562 <div data-action="send"> 563 <div class="ta-center submitBackLinks"> 564 <a href="" class="submit rsuBtn rsuBtn--twitter margin-0"><i class="icon icon-bubble" aria-hidden="true" ></i> Send Text</a> 565 </div> 566 </div> 567 </div> 568</div> 569
570<script defer="defer" type="text/javascript" src="https://d368g9lw5ileu7.cloudfront.net/js/rsuSocialMediaButtons.min.bQWau_.js"></script>
570 </div> 571 </div> 572 </div> 573 </div> 574 575 576 <span class="hero-opacity"></span> 577</div> 578 579 580
580<script type="application/ld+json">{"@context":"http:\/\/schema.org","@type":"SportsEvent","additionalType":"Product","name":"Bigger in Texas Challenge","location":{"@type":"Place","name":"State of","address":{"@type":"PostalAddress","streetAddress":"Anywhere!","addressLocality":"State of","postalCode":"77546","addressRegion":"TX","addressCountry":"US"}},"startDate":"2020-06-01T07:00:00-05:00","endDate":"2020-12-31T23:59:59-06:00","description":"Everything is BIGGER in TEXAS and the BIGGER in TEXAS CHALLENGE VIRTUAL RACE is no different. We'll take you on a journey all over the great state of Texas starting at the State Capital in Austin. A portion of the proceeds from the event will benefit Southern Smoke Foundation. For more details about our beneficiary visit https:\/\/southernsmoke.org\/.","url":"https:\/\/runsignup.com\/About-Us\/Privacy-Policy","image":"https:\/\/d368g9lw5ileu7.cloudfront.net\/races\/races-92xxx\/92201\/raceBanner-7MmkSoqY-bE9Er2.png","organizer":{"@type":"Organization","name":"Bigger in Texas Challenge","url":"https:\/\/runsignup.com\/"}}</script>
580 581 582 583 <div class="race-content"> 584 <main id="mainContent"> 585 <div class="container"> 586 <div class="bs4-row"> 587 <div class="col-md-12"> 588 589 590 591<h2>Privacy Policy</h2> 592<span class="note">Last Updated 09/13/2026</span> 593<hr/> 594<div class="bs4-row"> 595 <div class="col-md-12"> 596 <p> 597 RunSignup, Inc., doing business as RunSignup, BikeSignup, TriSignup, SkiSignup, PaddleSignup, AdventureSignup, TicketSignup and GiveSignup (collectively, â<b>RunSignup</b>â, âusâ, âweâ, or âourâ) operates runsignup.com, bikesignup.com, trisignup.com, skisignup.com, paddlesignup.com, adventuresignup.com, ticketsignup.io and givesignup.org, or through a mobile application or other cloud-based platform which we may make available for your use (collectively, the â<b>Site</b>â). 598 This Privacy Policy informs you of our policies regarding the collection, use and disclosure of information we receive from users of the Site. Your use of the Site will constitute your acknowledgement of your consent to abide and be bound by the Privacy Policy. 599 </p> 600 <h3>Our Commitment to Privacy</h3> 601 <p> 602 Thank you for using RunSignup. 603 RunSignup is pleased to provide registration and related services for your endurance event, membership services for your organization, and/or tickets for other events on our Site (our â<b>Services</b>â provided via our Site for your â<b>Event</b>â). 604 Your privacy is important to us. 605 Because of this, we prefer to take a minimalistic approach to collecting information from you. 606 We <b>do not</b> save any credit card information on our servers, and we <b>do not</b> sell your information or share it with anyone other than: (a) the sponsoring organization (sometimes referred to as the Event Owner) and the Event Director (collectively, the â<b>Event Organization</b>â) for the Events that you register for through RunSignup, and (b) as otherwise expressly described in this Privacy Policy. 607 We also <b>do not send</b> any mass emails and we never share credit card information with the Event Organization. 608 </p> 609 <p> 610 Please note that the Event Organization administers and oversees the Race and can seek additional information and Content (defined in the âInformation We Collectâ section below) from you through the use of our Site or through a separate data collection method. 611 The Event Organization also can control who may access the information and Content collected for their Race and posted or maintained on our Site and, in this regard, may provide certain individuals and third parties (such as the timer for your Race), and the public, with access to such information and Content. 612 We do not control, and are not responsible for, the policies and practices of the Event Organization, or the conduct of other users or participants which the Event Organization gives access to our Site, with respect to their handling of your information and Content. 613 For information about the Event Organizationâs practices and policies, please contact them. 614 </p> 615 <h3>The Information We Collect</h3> 616 <p> 617 When you register for a race Event on RunSignup using any of our sites other than TicketSignup or GiveSignup you can register yourself or someone else as a user of our website, and/or signup for a race Event. 618 On those Site pages, we will collect information about you including but not limited to: <i>Name, Address, E-mail Address, Phone Number, Date of Birth (used for race categories only), and Gender (also used for race categories)</i> (Collectively â<b>Profile Information</b>â) for those people who register as a user or sign up for a race Event on our Site. 619 Your Profile Information is stored on a permanent profile on our Site that can be used by you to register for future race Events on RunSignup. 620 We store this information to be able to better interact with you when you use our site, including providing support to you and to be able to keep track of Events you have signed up for and any related results. 621 When completing your profile on RunSignup you can select a box, which will allow you to be shown as âanonymousâ in public participant and race results published by RunSignup. 622 </p> 623 <p> 624 If you buy a ticket to an Event on our Site, using TicketSignup or GiveSignup (âTicket Purchasersâ) we may collect less information from you depending upon the need of the Event Organization to properly manage the Event. 625 For instance, we may only ask for your name and email address to confirm your ticket purchase or the Event Organization may ask for additional information such as information for individual ticket holders if they need this information to properly manage the Event. 626 Information about Ticket Purchasers is not shown in publicly available listings on the Site. 627 </p> 628 <p> 629 We will also store: (a) information collected by the Event Organization, which may include some or all of your Profile Information and/or additional information which the Event Organization chooses, in their discretion, to collect; and (b) the lists and reports of participants for races, which may include (at the election of the Event Organization) some or all of the information described
629in (a) above (collectively, the â<b>Event Data</b>â). 630 In addition, we will store your ID and password (â<b>login credentials</b>â) that permits you to access your account on our Site. 631 You should not share your login credentials with third parties. 632 </p> 633 <p> 634 We will collect credit card information from you at the time of the transaction for the purpose of completing transactions to register for Events. 635 We will not store that credit card information on our servers or on the Site. 636 The credit card information is sent directly, via secure means, to a trusted third party-operated payment service to complete a registration transaction. 637 You can request to have your credit card information stored and only then do we store your credit card information with a trusted third party-operated online credit card vault storage company and not on our servers or on the Site. 638 We confirm that these third parties have been certified as meeting high-level security standards as published by the Payment Card Industry Security Standards Council. 639 </p> 640 <p> 641 The Event that you participate in may collect and store on our Site your name, voice and images of you (also sometimes referred to as your likeness) in photographs, motion pictures, results, publications or any other print, videographic or electronic recording of the Event (collectively, âContentâ). 642 You agree and consent that: (x) we may store, use and display the Content on our Site in connection with the provision of our Services in support, and the accompanying promotion, of your Event; and (y) the Content may be used by the Event Organization for the sale of those images to participants in their Events and for the marketing and promotion of such Events which they may sponsor. 643 </p> 644 <div class="margin-l-25"> 645 <h4>Information We Automatically Collect</h4> 646 <p> 647 Like many site operators, we collect information that your browser sends whenever you visit our Site (âLog Dataâ). 648 This Log Data may include information such as your deviceâs Internet (âIPâ) address, browser type, browser version, the pages of our Site that you visit, the time and date of your visit, the time spent on those pages and other statistics. 649 Your devices may also transmit information about the type of device, information regarding your location and operating system, and identifiers associated with the device, and we collect this information. 650 We will use Log Data and the above-described device-generated information to manage, operate and improve the Site and will not share or distribute such information to any third party other than the Event Organization, except as otherwise expressly described in this Privacy Policy. 651 </p> 652 <p> 653 In addition, we may use third party services such as Google Analytics or develop our own tools that collect, monitor and analyze the collected information. 654 For example, Google Analytics may be used to measure traffic or track visitor activity on the Site. 655 We use this information to analyze and improve the usage of our Services and the type of information displayed to Site users so that we can better serve those interested in our Services. 656 Google Analytics and other third party analytics services do not reveal to us your name or other personally identifying information. 657 </p> 658 <p> 659 If you enable a âdo not trackâ signal or similar mechanism relating to the tracking of browsing activities, we do not have practices or protocols to honor or respond to such requests. 660 However, we only collect the types of information otherwise described in this Privacy Policy. 661 </p> 662 <h4>Cookies</h4> 663 <p> 664 Cookies are files with small amounts of data, which may include an anonymous unique identifier. 665 Cookies are sent to your browser from a web site and stored on your computerâs hard drive. 666 </p> 667 <p> 668 Like many sites, we use cookies to collect information to enable us to more efficiently interact with you, and to operate and improve the Site and our Services. 669 For example, cookies help us with things like remembering your user name for your next visit, understanding how you are using our Services, and improving our Site and Services based on that information (essential purposes).
670 We also use cookies for non-essential purposes like analytics and marketing that some of our Events may use to contact you about Events that they may offer. 671 You can instruct your browser to refuse all cookies or to indicate when a cookie is being sent. 672 However, if you do not accept cookies, you may not be able to use some portions of our Site. 673 You can turn off non-essential cookies by using the opt-out button provided beneath the privacy policy on this page. 674 </p> 675 <h4>AI Services</h4> 676 <p> 677 Our Site may offer AI-powered services in the following contexts: 678 </p> 679 <p> 680 (a) for general customer support about RunSignup and our Services, such as through our Help Center (a âSupport Chatâ)<br/> 681 (b) on an Event page, to help answer questions about that specific Event (an âEvent Chatâ)<br/> 682 (c) to generate text, provide data analysis, or take a configuration action regarding an Event based on a userâs natural language request (an âEvent Assistantâ) 683 </p> 684 <p> 685 Your conversations with our AI-powered services include your requests and the resulting responses. 686 We also collect, record, and store the messages you send and receive, along with related information such as the date and time of your conversation, identifying information such as your RunSignup username or originating IP address if known and the page of the Site you were using (collectively, âAI Communicationsâ). 687 </p> 688 <p> 689 In the context of a Support Chat, your AI Communications are transmitted to and processed by Poll the People, Inc (DBA CustomGPT), a third-party artificial intelligence service provider that assists us in operating the Support Chat service only. 690 That provider processes your Chat Communications on our behalf and is contractually required to protect your information consistent with this Privacy Policy and to use it only to provide the Chatbot service to us. 691 The Support Chat service communicates with OpenAI Inc, the provider of the LLM that generates responses. 692 Your AI Communications are not used by the LLM provider to train their models. 693 </p> 694 <p> 695 In the context of the Event Chat and Event Assistants, your AI Communications are transmitted to and processed by Amazon Web Services. 696 In order to analyze data and provide responses, Amazon Web Services licenses LLMs from top tier providers and operates them inside the Amazon Web Services infrastructure. 697 Our contractual agreements with Amazon Web Services provide that your AI Communications are never shared with the end LLM vendors or used to train AI models. 698 </p> 699 <p> 700 Please do not share credit card numbers, passwords, or other sensitive account information within any AI Communications. 701 Our services are not designed to request this type of information, and we are not responsible for information you voluntarily disclose in an AI Communication beyond what we ask for. 702 </p> 703 <p> 704 We review AI Communications for customer support, troubleshooting, quality assurance, and to improve the accuracy and performance of our Services. 705 </p> 706 <p> 707 If your AI Communications are part of an Event Chat, we also share them with the Event Organization for that Event. 708 The Event Organization uses Event AI Communications to help train the Event Chatbot and improve its answers to common questions asked about their Event. 709 We do not share an Event Organizationâs Event AI Communications with any other Event Organization. 710 </p> 711 <p> 712 If your AI Communications are part of a Support Chat â meaning you contacted the Chatbot for general RunSignup customer support rather than through a specific Event page â they are not shared with any Event Organization and are used only by RunSignup as described in this section. 713 </p> 714 <p> 715 We retain AI Communications indefinitely. 716 </p> 717 <p> 718 By starting a conversation with any of our AI Services, you acknowledge and consent to the collection, recording, storage, and processing of your AI Communications as described in this section â including, for an Event Chat, sharing with the Event Organization for that Event, and, in all cases, transmission to our third-party AI service provider(s). 719 If you do not wish to consent, please do not use the service; you may instead contact us at
719<script type="text/javascript">document.write(String.fromCharCode(60,97,32,104,114,101,102,61,34,109,97,105,108,116,111,58,105,110,102,111,64,114,117,110,115,105,103,110,117,112,46,99,111,109,34,32,62,105,110,102,111,64,114,117,110,115,105,103,110,117,112,46,99,111,109,60,47,97,62))</script>
719 for assistance. 720 Where applicable law requires all parties to a communication to consent before it is recorded, your affirmative acknowledgment before beginning a Chatbot conversation, as prompted on our Site, serves as that consent. 721 </p> 722 </div> 723 724 <h3>The Way We Use Information</h3> 725 <p> 726 We use the information you provide about yourself and others when registering for an Event <b>only</b>Â to complete the registration for that Event. 727 We do not share this information with outside parties except for the Event Organization for your Event. 728 </p> 729 <p> 730 We use return email addresses to answer the emails we receive. 731 Such addresses are not used for any other purpose, and are not shared with outside parties. 732 We will not use your email address to market Events or other services directly to you and we will not distribute your personally identifiable information to anyone other than to the Event Organization for the Event that you register for on our Site and as otherwise described in this Privacy Policy. 733 </p> 734 <p> 735 In addition to the other uses described herein, we may use the information we collect from you in the following ways: 736 </p> 737 <ul class="fs-md-1"> 738 <li>To respond to your questions and requests;</li> 739 <li>To allow us to provide customer support in connection with our Services;</li> 740 <li>To process your transactions;</li> 741 <li>To operate our Site and provide our Services in order to administer and facilitate your Race (for example, to facilitate your registration and event services, post results and provide Race information to you)</li> 742 <li>Comply with laws, regulations, legal processes and law enforcement requirements;</li> 743 <li>To optimize or improve our Services;</li> 744 <li>To send out service announcements, such as if there are technical issues impacting the Service.</li> 745 <li>To communicate with you about your account or transactions with us and send you information about the operation of our Site or changes to our policies; and</li> 746 <li>To detect, investigate and prevent activities that may violate our policies or be illegal.</li> 747 </ul> 748 <p> 749 We will never use or share the personally identifiable information provided to us online in ways unrelated to the ones described in this Privacy Policy without also providing you an opportunity to opt-out or otherwise prohibit such unrelated uses. 750 </p> 751 <p> 752 It is important to note that the Event that you register for may use your personally identifiable information to contact you for the purpose of completing your registration, managing and operating the Event, marketing to you for other Events that they manage and for other purposes consistent with their policies and practices. 753 Any marketing emails on behalf of an Event or directly from the Event Organization should provide you with an option for you to opt out of receiving future marketing emails from that event. 754 If you would like to be removed from ALL RunSignup email marketing communications regardless of event you can globally unsubscribe at <a href="/GlobalUnsubscribe">https://runsignup.com/GlobalUnsubscribe</a>. 755 If you would like to opt out from the use of your information directly by the Event Organization or would like other information about how the Event Organization uses your data outside of RunSignup, please contact your Event Organization. 756 </p> 757 758 <h3>Sharing Your Information With Third Parties</h3> 759 <p> 760 We do not sell, trade, or otherwise transfer to outside parties your personal information, except to your Event Organization (as noted above, your Event Organization may elect to share such information with timers and others) and as otherwise described in this Privacy Policy. 761 See the âAI Servicesâ section above for a description of how your AI Communications are shared with our AI service provider(s). 762 Without providing notice to you, we may disclose your personal information to website hosting partners, affiliates, service providers, contractors and other parties who assist or support us in: (i) operating our Site and providing our Services (including where we âoutsourceâ the hosting of the Site to a trusted third party contractor); and (ii) conducting our business in connection with the provision of Services to you (such as payment processing and data storage), or in otherwise servicing you. 763 Also, without providing notice to you, we may contract with trusted third parties to provide complementary products or services which are integrated or interfaced with our Site (for example, we may share your IP address with your Event Organizer which may, in turn, utilize a third party application to post information regarding a future Event on your browser via your IP address) and such third parties may require access to your personal information in order to effectively provide the complementary products or services to you. 764 In all cases, the parties described above will be required to agree to only use your personal information for purposes of performing the tasks described above and to keep your personal information confidential under obligations similar to those in this Privacy Policy. 765 </p> 766 <p> 767 In addition to the above and without providing notice to you, in the event of a sale or other change of control of our company, the terms, rights and practices described
767in this Privacy Policy would be transferred to the new owner. 768 We may provide your personal information to the purchaser so that you may continue the relationship or business with our products and us. 769 </p> 770 <p> 771 We may also release your personal information (without notice to you) when we believe release is appropriate to comply with the law, enforce our Site policies, or protect ours or othersâ rights, property, or safety, including in the event that we utilize a trusted third party to assist our investigation into the fraudulent or other improper use of our Site. 772 </p> 773 <h3>Data Security</h3> 774 <p> 775 Our goal is to protect the personally identifiable information that you provide to us in the course of your use of our Services. 776 We have put in place appropriate physical, administrative and technical procedures that are reasonably designed to safeguard and secure the information we collect online. 777 Security safeguards utilized at applicable stages during the collection, transmission and storage of personally identifiable information include data encryption, firewalls, data use and access limitations and physical access controls. 778 However, despite our diligent efforts, no commercial method of information transfer over the Internet or electronic data storage is 100% secure and we cannot guarantee such absolute security. 779 </p> 780 781 <h3>De-personalized Data</h3> 782 <p> 783 We may aggregate certain information we maintain with information about other individuals in a manner that does not disclose personal information specific to an individual and/or we may remove characteristics that would otherwise be personally identifying. 784 In either case, we are de-personalizing the information. 785 We shall be free to utilize all de-personalized information in any way (including providing such information to other parties for marketing, advertising or other uses) and, unless otherwise required by law, de-personalized information shall not be bound by the terms of this Privacy Policy. 786 As always, RunSignup will comply with all applicable laws and governing regulations in the collection, use and disclosure of personally identifiable information. 787 </p> 788 789 <h3>Links to Third Party Sites</h3> 790 <p> 791 In an attempt to provide you with increased value, we may include third party links on our Site. 792 These linked sites have separate and independent privacy policies. 793 We do not control and, therefore, have no responsibility or liability for the content and practices of these linked sites. 794 Nonetheless, we welcome any feedback about these linked sites (including if a specific link does not work). 795 </p> 796 797 <h3>Our Commitment to Childrenâs Privacy</h3> 798 <p> 799 Our Site and Services are a general audience website and are not specifically directed for use by children under the age of 13. 800 However, we recognize that children may be eligible to participate in Events listed on our site and protecting the privacy of the very young is important. 801 For that reason, we do not knowingly allow anyone under the age of 18 to register for an Event or create a Profile on our Site. 802 Only parents or guardians may register for an Event or create a Profile for children under the age of 18. 803 As part of the registration process we ask the individual registering a participant for an Event to confirm they are the parent or guardian of any registrants under the age of 18 and that they have consented to the collection of information for registrants under the age of 13. 804 </p> 805 <p> 806 Please see the paragraphs titled â<b>The Information We Collect</b>â and â<b>The Way We Use Information</b>â to understand what information we collect and how it is used. 807 </p> 808 <p> 809 We will not intentionally communicate directly with children under the age of 13. 810 When there is a need to communicate with children under the age of 13 for the acceptable purposes under this policy (for instance to confirm a race registration) we will use the email address of the parent, guardian or adult who has created the Profile or registered the child for a race. 811 Additionally whenever a childâs name appears in a public place on our site (for instance with their race results) the name will be truncated to first initial and last name and will not be shown with other identifying information like the
811ir street address. 812 </p> 813 <p> 814 Additionally, the Event Organization may elect to take photos or videos of participants in their Events that may include children under the age of 13 who are participating in the Event. 815 If so, we will inform the Event Organization that only parents, guardians or adults (and not any child under the age of 13) are authorized to upload such photos to our Site. 816 Please check with your Event Organization if you have any questions regarding their policies or practices regarding this topic. 817 </p> 818 819 <h3>How You Can Access or Correct Your Information</h3> 820 <p> 821 If you have signed up for an event that required the creation of a profile, you can access all your Personal Information that we collect online and maintain it, update it or correct it by Editing Your Profile after signing in. 822 We use this procedure to better safeguard your information. 823 If you have any questions regarding your attempts to correct or update your information, please contact us at
823<script type="text/javascript">document.write(String.fromCharCode(60,97,32,104,114,101,102,61,34,109,97,105,108,116,111,58,105,110,102,111,64,114,117,110,115,105,103,110,117,112,46,99,111,109,34,32,62,105,110,102,111,64,114,117,110,115,105,103,110,117,112,46,99,111,109,60,47,97,62))</script>
823. 824 You may not update your Profile with the Personal Information of another person to âtransferâ your Profile or a registration to a Race. 825 </p> 826 827 <h3>Event Directors</h3> 828 <p> 829 Event owners who use our Services enter into an agreement with us under which they agree that they will not resell or use your personal information for any purposes other than those described in this Privacy Policy, which includes the facilitation and administration of your Event. 830 By way of example, the Event owner may use your name in connection with the administration and support of the Event and to market and promote the Event as well as future events sponsored by such owner. 831 </p> 832 833 <h3>Use By Non-US Residents</h3> 834 <p> 835 The Site is operated in the United States under United States law. 836 We do not intentionally offer goods and services to individuals outside of the United States. 837 If you reside in another country, please be aware that any information you provide to us will be collected and stored in the United States or other countries that may have data privacy laws that are less protective than the laws where you reside. 838 </p> 839 840 <h3>Facebook Fundraisers Privacy Policy</h3> 841 <p> 842 The RunSignup Facebook Fundraisers integration allows fundraisers to sync their RunSignup fundraisers with Facebook Fundraisers. 843 Once users have posted their RunSignup fundraisers to Facebook, they may accept donations to their fundraiser both on RunSignup and on Facebook, as well as share their fundraisers with their Facebook network. 844 </p> 845 <div class="margin-l-25"> 846 <h5>Organizations</h5> 847 <p> 848 Nonprofit organizations which have enabled Facebook payments within Facebook may provide their Facebook page ID to RunSignup to enable the Facebook Fundraisers integration. 849 Once enabled, Facebook users may sync their RunSignup fundraisers with Facebook Fundraisers, allowing users to raise funds on both RunSignup and Facebook with a single fundraiser event that remains in sync between both platforms. 850 Nonprofit organizations can disable this integration by removing their Facebook page ID from their RunSignup dashboard. 851 </p> 852 <h5>Individuals</h5> 853 <p> 854 Individuals who are raising funds in a RunSignup fundraising event which has enabled the Facebook Fundraisers integration, will be allowed to post their RunSignup fundraisers to Facebook. 855 This will create a Facebook Fundraiser using the information provided in the usersâ RunSignup fundraiser, and will post the fundraiser to usersâ Facebook feeds. 856 Individuals who wish to disable this integration may delete their RunSignup fundraiser through the âFundraisingâ tab in their RunSignup profiles, or by deleting their Facebook Fundraiser on Facebook. 857 Deleting the usersâ RunSignup fundraiser will also remove all of a usersâ Facebook information from within the RunSignup site. 858 </p> 859 <p> 860 RunSignupâs Facebook Fundraisers integration on our site does not collect or use any personal information beyond supporting the integration with Facebook Fundraisers. 861 If you have additional questions about requesting deletion of your Facebook Fundraisers information, please contact
861<script type="text/javascript">document.write(String.fromCharCode(60,97,32,104,114,101,102,61,34,109,97,105,108,116,111,58,105,110,102,111,64,114,117,110,115,105,103,110,117,112,46,99,111,109,34,32,62,105,110,102,111,64,114,117,110,115,105,103,110,117,112,46,99,111,109,60,47,97,62))</script>
861. 862 </p> 863 </div> 864 865 <h3>Change to the Privacy Policy</h3> 866 <p> 867 This privacy policy is effective as of 04/01/2025. 868 We reserve the right to update or change our policy at any time and you should check this Privacy Policy periodically for any change. 869 Your continued use of the Site or the Service after we post any modifications to the Privacy Policy on this page will constitute your acknowledgement of the modifications and your consent to abide and be bound by the modified Privacy Policy. 870 </p> 871 872 <h3>How to Contact Us</h3> 873 <p> 874 Should you have other questions or concerns about these privacy policies or would like to submit a request for information pursuant to the California Consumer Privacy Act of 2018 or any other federal or stateâs consumer privacy laws, you should first view your profile on RunSignup, which is where we store all the data we have collected about you. 875 If you still have a question, you can email us at
875<script type="text/javascript">document.write(String.fromCharCode(60,97,32,104,114,101,102,61,34,109,97,105,108,116,111,58,105,110,102,111,64,114,117,110,115,105,103,110,117,112,46,99,111,109,34,32,62,105,110,102,111,64,114,117,110,115,105,103,110,117,112,46,99,111,109,60,47,97,62))</script>
875. 876 Include your name, address and phone number and make sure that you email us from the same email address that you have previously used with RunSignup. 877 Also include the specific nature of your request for information. 878 </p> 879 880 <h3>How to Opt-Out of Non-Essential Cookies</h3> 881 <div class="margin-b-25"> <form method="post"> 882 <p>You can opt-out of using cookies for non-essential purposes by clicking the button below, then choosing âI Declineâ in the pop-up banner.</p> 883 <button type="submit" class="rsuBtn rsuBtn--gray rsuBtn--sm margin-0" name="opt_out_nonessential_cookies">Opt-Out of Non-Essential Cookies</button> 884 <input type="hidden" name="formAction" value="opt_out_nonessential_cookies" /> 885 886 <input type="hidden" name="csrf" value="LyzQUaDsDr6zL3Z5lYRemvaAnqOg7T7g" /> 887 </form> 888 </div> 889 </div> 890</div> 891 </div> 892 </div> 893 </div> 894 </main> 895 </div> 896 897 898<div class="race-footer noPrint"> 899 900 901 902 <div class="bs4-row no-gutters race-footer-navigation"> 903 <div class="col-md-12"> 904 <div class="container"> 905 <div class="bs4-row foot-nav-column "> 906 <div class="col-md-3 col-sm-3 race-footer-logo"> 907 <div class="race-logo-footer"> 908 <span class="footer-scale"> 909 910 <img src="https://d368g9lw5ileu7.cloudfront.net/races/race92201-logo-0.bE9DYc.png" alt="Bigger in Texas Challenge" /> 911 </span> 912 </div> 913 </div> 914 915 <div class="col-md-3 col-sm-3 foot-nav-items"> 916 <ul> 917 <li> 918 <a href="/Race/Info/TX/Stateof/BiggerinTexasChallenge" class="foot-nav-item">Race Info</a> 919 </li> 920 <li> 921 <a href="/Race/BiggerinTexasChallenge/Page/referral" class="foot-nav-item">Referral Rewards</a> 922 </li> 923 <li> 924 <a href="/RaceGroups/92201" class="foot-nav-item">Group/Teams</a> 925 </li> 926 </ul> 927 </div> 928 <div class="col-md-3 col-sm-3 foot-nav-items"> 929 <ul> 930 <li> 931 <a href="/Race/BiggerinTexasChallenge/Page/routes" class="foot-nav-item">Routes</a> 932 </li> 933 <li> 934 <a href="/Race/BiggerinTexasChallenge/Page/faq" class="foot-nav-item">FAQ</a> 935 </li> 936 <li> 937 <a href="/Race/Photos/TX/Stateof/BiggerinTexasChallenge" class="foot-nav-item">Photos</a> 938 </li> 939 </ul> 940 </div> 941 <div class="col-md-3 col-sm-3 foot-nav-items"> 942 <ul> 943 944 <li> 945 <span class="foot-nav-item">Donate</span> 946 <ul> 947 <li> 948 <a href="/Race/Donate/92201/BecomeFundraiser" class="foot-nav-item">Become a Fundraiser</a> 949 </li> 950 <li> 951 <a href="/Race/Donate/92201/TopFundraisers" class="foot-nav-item">Top Fundraisers</a> 952 </li> 953 </ul> 954 </li> 955 <li> 956 <a href="/Race/Results/Overview/92201" class="foot-nav-item">Results</a> 957 </li> 958 </ul> 959 </div> 960 </div> 961 </div> 962 </div> 963 </div> 964 965 <div class="bs4-row no-gutters race-copyright"> 966 <div class="col-md-12"> 967 <div class="container"> <footer> 968 <span class="copyrightText">Powered by RunSignup, © 2026</span> 969 970 <span class="alignRight margin-r-15"> 971 <a href="/Race/92201/PrivacyPolicy">Privacy Policy</a> | 972 <a id="footerContactLink" href="/Race/Info/TX/Stateof/BiggerinTexasChallenge#contactFormSection" target="_blank" rel="noopener noreferrer">Contact This Race</a> 973 </span> 974 </footer> 975 </div> </div> 976 </div> 977</div> 978 979
979<script defer="defer" src="https://cdnjs.runsignup.com/ajax/libs/popper.js/2.11.8/umd/popper.min.js" integrity="sha512-TPh2Oxlg1zp+kz3nFA0C5vVC6leG/6mm1z9+mA81MI5eaUVqasPLO8Cuk4gMF4gUfP5etR73rgU/8PNMsSesoQ==" crossorigin="anonymous"></script>
979 980
980<script defer="defer" src="https://cdnjs.runsignup.com/ajax/libs/tippy.js/6.3.7/tippy.umd.min.js" integrity="sha512-2TtfktSlvvPzopzBA49C+MX6sdc7ykHGbBQUTH8Vk78YpkXVD5r6vrNU+nOmhhl1MyTWdVfxXdZfyFsvBvOllw==" crossorigin="anonymous"></script>
980 981 982 </div> 983 984 985 986 </div> 987 988 989 990 991 992 993 994 995 996 997<div id="cookiePolicyPopup" class="drawer drawer--bottom"> 998 <div class="drawer__content flex-parent flex-responsive align-items-center"> 999 <img src="https://d368g9lw5ileu7.cloudfront.net/img/frontend2018/cookie-img.bFehfM.png" width="40" height="40" alt="" class="margin-r-15 margin-r-0-medium-down hidden-phone" /> 1000 <div class="flex-2 margin-r-15 hidden-md-down"> 1001 <p class="fs-xs-2 margin-0 padding-tb-5 lh-initial"> 1002 If you continue to use this site, you consent to use all cookies. We use cookies to offer you a better browsing experience. Read how we use cookies and how you can control them by visiting our <a href="/About-Us/Privacy-Policy" target="_blank">Privacy Policy</a>. 1003 </p> 1004 </div> 1005 <div class="flex-2 hidden-md-up"> 1006 <p class="fs-sm-1 margin-0 padding-tb-5 lh-initial"> 1007 If you continue to use this site, you consent to use all cookies. <button type="button" class="rsuExpando bkg-none border-0 color-inherit fs-sm-1" data-content-id="cookieMsg" aria-controls="cookieMsg">Learn More</button> 1008 </p> 1009 <div class="rsuExpando__content" id="cookieMsg" aria-expanded="false" hidden="hidden"> 1010 <p class="fs-xs-2 margin-0">We use cookies to offer you a better browsing experience. Read how we use cookies and how you can control them by visiting our <a href="/About-Us/Privacy-Policy" target="_blank">Privacy Policy</a>.</p> 1011 </div> 1012 </div> 1013 <button type="button" class="rsuBtn rsuBtn--secondary rsuBtn--sm">I Accept</button> 1014 </div> 1015</div> 1016
1017<script defer="defer" type="text/javascript" src="https://d368g9lw5ileu7.cloudfront.net/js/ui/expando.min.bQCiQ7.js"></script>
1017<script defer="defer" type="text/javascript" src="https://d368g9lw5ileu7.cloudfront.net/js/frontend.min.bQCiQ7.js"></script>
1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 </body> 1052</html> 1053<!-- Response time: 0.037808 --><!-- DB: N -->
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.