Panhandle CPR Privacy Policy

Contact and privacy requests

For privacy questions or to request access to, correction of, or deletion of information, email info@panhandlecpr.com or call (850) 381-4288. Our business address is 97 W Oak Ave, Suite 10, Panama City, FL 32401.

Identify the relevant account, class, transaction, or request and describe what you would like us to review. Do not send passwords, full payment-card details, or identity documents in ordinary email or a website inquiry. A request to close an account is different from a request to remove its associated records.

Information provided through our services

• Website inquiries: contact details and your message. Group-training requests include your organization, training needs, student count, and location. Instructor inquiries include contact details, state, instructor status, location answers, and your reason for joining or transferring. Virtual-training inquiries can include a mailing address.
• Training and registration: student contact details, registrations, optional shipping details, course and instructor information, attendance, completion, scores, remediation, and certification or eCard references.
• Instructor and portal activity: account information, onboarding and alignment records, compliance and class documents, teaching activity, messages, support tickets, attachments, and training or simulator history.
• Rentals and purchases: order details, amounts, payment status, transaction references, and invoice links. Rental records can also include an address, agreement and signature details, consent records, and the IP address and browser information associated with signing.
• AED services: client and site contacts, addresses, device information, inspections, support incidents, and notification records. AED-use reports can include reporter contact details, incident answers, and free-text notes. Include only information needed for the report.

We use these records to respond to inquiries, arrange and administer services, support instructors, document training and certification, manage purchases and rentals, maintain AED programs, communicate about services, and resolve support or operational issues.

Documents and automated analysis

The portal accepts document uploads and can import supported attachments from our Titan email mailbox over an encrypted connection. Email attachment intake and automatic document scanning are enabled. Intake records can include the original file and filename, uploader or source, timestamps, review status, analysis results, and processing errors. Email-based intake can also include sender, subject, date, message identifiers, mailbox information, and attachment details.

When the portal’s AI document-analysis feature is used, PDF or image content is sent to OpenAI’s Responses API for analysis. PDF requests can include the filename. The portal retains analysis results for review. OpenAI’s handling of API content is governed by the applicable service agreement and API data controls; API content can be retained according to those terms and account controls. Rejecting a detected section does not by itself delete the original uploaded file. This document-analysis feature is separate from the Google Calendar connection described below.

Website chat and virtual sessions

CORA, the website chat assistant, uses rules in your browser and a knowledge feed from this website. Its inquiry and lead-collection steps submit information through our website forms. Those submissions are stored with other form records. Clearing the chat display does not delete a submitted inquiry.

The portal includes a Daily integration for virtual sessions. When a session uses Daily, it processes the connection information and live audio or video needed for participants to communicate. If recording is offered for a session, we will provide a separate notice explaining what is recorded, its purpose, access, and retention, and obtain any required consent before recording. A live audio or video connection is distinct from a saved recording.

Service providers and other recipients

Information is handled by the services used to deliver the feature you choose:

• Registration: our public class links lead to Enrollware. Review the information and privacy terms shown there when registering.
• Portal payments: supported purchase flows use Stripe Checkout. Checkout can receive your email address, purchase details, amounts, and record references and can request a billing address. Rental checkout can request a payment method for later charges under the agreement presented to you. The portal stores payment references and status. When a registration uses hosted Stripe Checkout, payment-card entry takes place on Stripe’s checkout page.
• Document analysis: OpenAI receives the document content described above when that feature is used.
• Training and certification: portal features support instructor and administrator review, roster exports, and service emails. The employer portal can display student eCards assigned to that client. AHA eCard lookup sends the card code to the American Heart Association’s eCard service.
• Website operation and communication: hosting and email services process information needed to store records, run the website, and deliver messages. Titan supplies the mailbox used for document intake. Website form submissions can be emailed to Panhandle CPR addresses as well as stored in the website database. People with administrative access to the application, database, or hosting systems can have access to stored information.

The website loads Google Fonts and Google Maps and displays reviews through Trustindex. These services receive browser connection information when their content loads. Signed-in WordPress administration can also load Gravatar profile images. Our links to other services, including the American Heart Association and Code Blue Training, lead to services with their own privacy information. External providers’ handling and retention of information are subject to their applicable policies and agreements.

Technical information and browser storage

Website forms and portal functions can record submission times, the page or referrer, IP address, browser information, logged-in user identifiers, and processing results. Portal audit records can include who performed an action, the affected record, the action and related details, and its time. Email delivery records can include recipient, subject, message type, status, and time.

WordPress uses login, test, and preference cookies. The portal also uses a client-session cookie with a 12-hour lifetime, local storage, and session storage for session and web-app functions. Cookie expiry is not deletion of records stored on our servers. Embedded third-party content can receive browser connection information when it loads. You can manage cookies and stored site data in your browser; blocking or removing them can affect sign-in and other functions.

Retention and account closure

Records support training and certification history, instructor administration, transactions, rentals, AED programs, and support. Information can remain after an inquiry, class, or other service has ended. Retention varies by record type and system; there is no single automatic deletion period or account control that removes every associated record.

The portal’s recoverable account-deletion function archives or disables access and revokes sessions while preserving linked classes, student records, cards, files, and audit or compliance history. Ordinary portal messages are configured for cleanup after 30 days, with a daily cleanup schedule. This is separate from support-ticket retention: a conversation copied into a support ticket can remain after the ordinary message is removed. The 30-day message setting does not apply to class, certification, payment, rental, document, audit, or backup records.

Removing information from active records does not necessarily remove copies already held in backups, logs, exports, or separately retained documents. The timing for removal of those separate copies is not the same as the ordinary-message schedule. Contact us about the particular records you want reviewed rather than relying on account closure or removal of a single item to erase all copies. The Google Calendar section below explains its separate retention and disconnect behavior.

Optional Google Calendar connection

Feature status: The Google Calendar connection is being prepared and is not currently active. This section describes the prepared feature. Publishing this policy does not connect your Google account.

Your choice and access

When available, the optional connection will require your Google authorization. It is designed to synchronize future assigned classes and accepted dispatch assignments to a separate Panhandle CPR Classes calendar.

The requested permission is https://www.googleapis.com/auth/calendar.app.created. It allows the app to create secondary calendars and view, create, change, and delete events on those calendars. The connection does not request Gmail or Google Drive access, fetch your Google profile or email address, or list events from your unrelated personal calendars.

Information exchanged and stored

The connection sends Google the course label, start and end times, time zone, training location or address, a portal link, and identifiers used to match events and the calendar to portal records. It does not supply attendees or request event-update invitations. Dedicated student, contact, payment, and meeting-credential fields are excluded. Location fields are free text, so do not put unrelated private information in them.

Google returns authorization tokens and calendar or event information. The connection processes responses to verify and synchronize events. It stores tokens, portal and source identifiers, calendar and event identifiers, preferences, matching records, synchronization status, timestamps, and error codes, rather than complete copies of those responses. Temporary authorization records support connection setup.

Use, sharing, and protection

Google receives the information needed for synchronization. Events are marked private, but visibility also depends on your Google Calendar sharing settings, which the connection does not inspect or manage. Connection records are stored with the portal and can be accessible to people with privileged application, database, or hosting access.

Our use and transfer of information received from Google APIs will follow the Google API Services User Data Policy, including its Limited Use requirements. Google user data will be used for this calendar feature, not sold or used for advertising, credit decisions, lending, or training generalized artificial intelligence or machine-learning models. Transfers and human access will be limited to purposes Google permits. Support access to specific Google data requires your affirmative permission unless access is necessary for security or to comply with law. Providers handling this information on our behalf must follow these restrictions.

The prepared Calendar implementation encrypts access tokens, refresh tokens, and temporary connection verifiers. It does not apply that encryption to every item of synchronization metadata.

Disconnecting and deleting information

You can remove Google access in your Google Account linked-app settings. Removing access does not itself delete events or information already stored by Panhandle CPR.

The prepared portal offers two disconnect choices:

• Keep events and disconnect: stop synchronization, clear active token fields and temporary authorization records, and attempt Google revocation. Existing events and the calendar remain.
• Remove events before disconnecting: queue removal of verified managed events and retain credentials while cleanup is pending. After cleanup, attempt revocation and clear token fields. Lost access, changed ownership information, or manually added attendees can prevent cleanup.

Neither choice deletes the Google calendar itself. If revocation cannot be confirmed, remove access through Google. Naturally elapsed events remain as history unless removed during managed-event cleanup. Routine synchronization can remove managed future events when an assignment stops being eligible or moves into the past.

Connection metadata, event matching records, and class/dispatch linking decisions have no automatic deletion schedule in the prepared implementation. Disconnecting does not erase them. Temporary authorization records become unusable after ten minutes, but unused expired records can remain until a later connection, settings, or disconnect action removes them.

An authorization failure pauses synchronization and clears the access token but can leave the encrypted refresh token stored. Disabling the feature or archiving an account does not automatically revoke access or erase calendar records. Contact us about local data removal or unresolved event cleanup. Deleting active database values does not establish deletion from backups or database history.

Changes to this policy

Updated wording will appear on this page with a revised date. Before accessing a new type of Google user data or using it for a new purpose, we will explain the change and obtain the required consent.