PulseADR

Privacy policy

DRAFT, attorney review required

  1. What we collect. From the request form: hotel name, room count, city, the rate shopper you use (if you tell us), your name, role, email and phone (if given), and your two contact choices (email, and calls if you ticked that box). We also record when you sent the form, the version of the consent text you agreed to, and the page you sent it from. If we store requests in a database (not yet; see Subprocessors), we also keep a one-way hash of your IP address for abuse prevention and your browser's user-agent string. From the service: the rate-shop reports you upload, any booking data you choose to add, the email address you use to sign in, and, if you answer them, your answers to our end-of-trial questions. Reports reach us either by upload in the app or by email forwarding to a mailbox we operate on Gmail. We keep the file as you sent it, together with the data we read from it.
  2. How we use it. To reply to you, prepare your first report, set up and run a free start if you ask for one, run the service for your property only, send you messages about your account and billing, keep the service secure and block spam, and meet legal obligations.
  3. What we never do. We do not sell or rent your data. We do not tell anyone which hotels use PulseADR. We do not use your data to train models for other customers. (code verified 2026-10-24: the service calls no third-party AI; [VERIFY] no manual use of such tools on customer files)
  4. Who processes it for us (subprocessors). Cloudflare (website hosting, form handling, and sign-in protection with Access for the app), Render (application hosting and the disk that holds uploaded reports and the files built from them; region [FILL-IN]), Resend (sends our emails to you and delivers your request details to us), Google (Gmail: the mailbox that receives your forwarded reports and our request notifications), and Stripe (payments, only if you subscribe). If we turn on Cloudflare Turnstile bot protection or begin storing requests in Cloudflare's D1 database, we will update this list first.
  5. Retention. Request-form details: kept up to [24] months after our last contact, then deleted. If you do not subscribe: after your free start (or after your first report, if you never start one) your uploaded reports and the reports built from them are kept read-only until you ask us to delete them, or for [deletion period] days, then deleted. If you subscribe: kept while you subscribe and deleted within [90] days after you cancel. You can ask for earlier deletion at any time. Copies in provider backups are overwritten within [backup period] days. (to be verified: a deletion job exists before the day counts are published)
  6. Security. Data is encrypted in transit. Your board is behind a named-email sign-in (Cloudflare Access); the data store is reachable only with a secret held by William Horschak, who operates the service.
  7. Your choices. Email [email protected] to see, correct or delete your data, or to withdraw either contact choice. Deletion covers your request-form details, your uploaded reports and the reports built from them. We reply within 30 days.
  8. Cookies and analytics. The marketing site (www.pulseadr.com) sets no cookies of its own and runs no analytics. (to be verified in the Cloudflare dashboard: Web Analytics is off) If we enable Cloudflare Turnstile on the form, Turnstile will receive your IP address and browser and device signals to decide whether you are a person, under Cloudflare's privacy policy (https://www.cloudflare.com/privacypolicy/). Fonts are served from our own site. The app at app.pulseadr.com uses a Cloudflare Access sign-in cookie.
  9. Contact. [email protected] · Responsible party: AstraCivic [legal entity type and state], [postal address]
  10. Changes and effective date. Effective [effective date]. We will update this page and, for material changes, email subscribers 30 days ahead.

Your uploaded rate reports

We keep them for the period under Retention and delete them earlier if you ask.