Privacy
What we keep, and what we do not.
This is a plain description of the starter site. If a host or a vendor changes, this page should change with it.
Who
CardioPay is operated independently. Questions and deletion requests go through the contact form.
What the forms collect
- Newsletter: email address, and a role if you add one.
- Job submission: your name, email, organization, and the job details you type.
- Contact: name, email, organization, topic, and message.
- Pay note: modality, state, staff or travel, a range, and optional credential or years. Do not put your name in that form. Notes are not published as individual reports.
Where it goes
Newsletter signups are stored with Resend so the weekly note can be sent. CardioPay keeps the address, adds it to the newsletter list, and records an opt-in for that note. A short confirmation may be sent from hello@getcardiopay.com. The API key stays on the server.
Other submissions are appended to data/submissions/*.jsonl when the disk is writable. That folder is not part of the public site. On a host with a read-only filesystem, the same record is held in process memory and disappears when the process restarts. If mail delivery is configured, a copy of those other forms is also emailed.
Sample jobs and wage tables
Seeded jobs are fictional demo posts. Wage tables are public statistics and labeled examples. They are not information you submitted.
Payments
Sponsor buttons open a Stripe Payment Link. Stripe collects the card. CardioPay does not store the card number. The advertise-page checkout is still a stub and does not charge a card. Returning to the thank-you page does not publish a listing. We confirm the payment, then email you.
Cookies and logs
This starter does not add analytics cookies or advertising pixels. If the site is deployed on Vercel, the host may keep standard request logs. We do not sell email addresses or pay notes.
Deletion
Email the contact form from the address you want removed and write “unsubscribe” or “delete my submission.” If mail delivery is not configured yet, the request is stored with the other contact messages and has to be handled from that file.